Most features (like most geometries) are "simple" and do not support lists of associated information. GeoTools feature model will let you work with lists (you can access content via xpath expressions) but the facility is not commonly used - indeed has only really been exercised by the application schema module.
Jody Garnett On Mon, Oct 27, 2014 at 6:22 AM, Anthony F <afc...@gmail.com> wrote: > I noticed that capability within JTS. I have been thinking about parallel > arrays keeping the information. For each coordinate within the linestring, > there's an associated time at which the entity was at that coordinate. I > can store all the times in an attribute in a SimpleFeature of type > List<Date>. This is inline with how KML deals with tracks in the extension > namespace. However, I don't think geotools serializes a SimpleFeature to > KML in a way that uses the extension namespace. Is there a way to plug in > to the serialization mechanism that can generate KML Tracks or MultiTracks? > > On Fri, Oct 24, 2014 at 9:41 PM, Jody Garnett <jody.garn...@gmail.com> > wrote: > >> You can create custom Coordinate implementations, and coordinate sequence >> implementations that allow the use of metadata for each location in your >> track. >> >> Out of the box JTS Coordiante does x,y,z - you can see we have a few >> implementations that focus on representing only xy as a coordinate sequence >> backed by an array. You can actually go the other direction and create a >> Coordinate that maintains additional "measures" (although this is not very >> common). JTS will politely leave that information alone, but can cary it >> around it the data structure for you. >> >> You can see a few functions for linear referencing, you would want to >> create a similar approach for accessing your metadata. >> >> Perhaps try asking on the JTS list for additional tips and tricks? >> -- >> Jody Garnett >> >> On October 17, 2014 at 6:01:37 AM, Anthony F (afc...@gmail.com) wrote: >> >> Hi all, >> >> I have been digging around in geotools looking to see if it supports >> tracks and have so far come up empty handed. I'm looking for advice and >> best practices on how to work with tracks. Basically, I want to store a >> LineString so that I can do proper geospatial queries on the geometry. >> Each point in the LineString has meta-data associated with it. I've >> thought about storing parallel arrays of the attributes associated with >> each way point. I have found the kml extension namespace which supports >> Tracks and MultiTracks but I don't know how to work with it within >> geotools. I have also found dynamicFeatures within the GML namespace but >> I'm not sure how that gets parsed by geotools. If anyone has any code >> samples they can point me to, I'd appreciate it. >> >> Thanks, >> Anthony >> ------------------------------------------------------------------------------ >> >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> http://p.sf.net/sfu/Zoho_______________________________________________ >> GeoTools-GT2-Users mailing list >> GeoTools-GT2-Users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users >> >> >
------------------------------------------------------------------------------
_______________________________________________ GeoTools-GT2-Users mailing list GeoTools-GT2-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
