PtrackParticle tracking server

2Ptrack – 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)

3Ptrack – 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

4Ptrack – Client

• http://ambwd02.stccmop.org/datamart/forecasts/ptrack

• Other clients possible – just need to follow server API.

5Ptrack – 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

6Ptrack – Results

• From this:– http://rdfs.stccmop.org/ptrack/server/run

ptrack.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/ne

wtest/particle.pth– http://rdfs.stccmop.org/ptrack/server/pjt

est/particle.kml

7Ptrack – TODO

• Schema changes in particle track tables

• Drifter run through• Test, test• Mapserver – cruise mapper