70 likes | 207 Vues
The Ptrack project focuses on developing a robust particle tracking server and client interface to generate forecasts and visualize particle movements. The server provides an API to output data in formats such as Postgres, KML, NetCDF, and CSV. Clients can access the server via a web application or command line tools like Wget. The system allows tracking single particles using unique IDs and has provisions for conversion between vector formats. Despite its capabilities, performance optimization is needed for faster processing. Notifications via email enhance user experience.
E N D
Ptrack – Project Overview • Project • Server (Paul) • Provide API • Outputs to Postgres and other formats • kml, netcdf, csv, .pth • Client (Nate and Paul) • Web app • Command line • Wget • Product generation (Nate)
Ptrack – Server • Server • Track a single particle • Track ID • Run directory created using the ID • Output to .pth, .kml, and database • Ogr2ogr does conversions of vector formats • Allows for other particle tracking codes • Problem, ptrack is slow – need to review Aaron R’s modifications
Ptrack – Client http://ambwd02.stccmop.org/datamart/forecasts/ptrack Other clients possible – just need to follow server API.
Ptrack – Server API • API • ID – character, used to create a directory, not unique • Lat, lon or X, Y – 3601 assumed • Email - for notifications • Depth – fixed (drifter) or variable (tracer) • Forecast id • Run day or start time – e.g 2009-211
Ptrack – Results • From this: • http://rdfs.stccmop.org/ptrack/server/runptrack.php?id=newtest&x=316458.73&y=292331.92&fcast=fca200nb&depth=1.0&runday=2009-212 • To this: • http://rdfs.stccmop.org/ptrack/server/newtest/particle.pth • http://rdfs.stccmop.org/ptrack/server/pjtest/particle.kml
Ptrack – TODO Schema changes in particle track tables Drifter run through Test, test Mapserver – cruise mapper