Hi, In the case of a waypoint, adding a new attribute is fine, but a track may have separate timestamp for each node, so an attribute should hold a list of timestamps. (Which might be a good idea, or might be not...)
As the gpx file itself stores the tracks as series of waypoints, not only a timestamp could be added to a node of a track, but many other information. But imho the timestamp is the most useful of all of them. (maybe after elevation, but storing elevation is not a question) Best, Peter Chris Holmes wrote: > Hmmm... I'd be more inclined to just make the time a new attribute. You > can hardcode the attribute name, like we do in shapefiles with > 'the_geom', call it 'timestamp' or something. If time is just an > attribute then we can use it straight away with GeoServer's KML Time > support - we have a template thing that lets you just enter the name of > the attribute to use. Raster data often does the time thing with 4 > dimensions, but I feel like if you're working with vector data, as GPX > is, then you should just throw an extra attribute on. Elevation should > likely be handled the same way, perhaps in addition to doing it as a > third coordinate. But an attribute can make it clear that it's in fact > elevation, and not another type of 3d thing, like distance above the > ground or something. > > best regards, > > Chris > > Bolla Péter wrote: >> Hi, >> >> I've comitted a new version of the gpx data store, that now uses >> Justin's xml parser (so xstream and xpp dependency dropped). It's >> still r/o, but write support is the next step. >> >> I tried to add it to uDig, but failed to do so, so tested only with a >> simple test case (loading a file, and printing the loaded feature). >> >> If you feel like testing, give it a try! >> >> I also had a discussion with Jody on how to implement the temporal >> data (in the gpx file every point of a track, so the nodes of a line >> segment, has lon, lat, elevation and time data). This could be used >> when visualizing the features. The easiest way might be to extend the >> JTS Coordinate class, to support a 4. dimension, which can be the >> Date, and create the geometries using these extended coordinates. >> >> Has any of you worked with temporal data like this, or with any 4D >> data? Or just any idea on how this could be best implemented? >> >> Best, >> Peter >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Geotools-devel mailing list >> Geotools-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geotools-devel >> >> !DSPAM:4005,46d78f8168541849620573! >> ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
