I have an existing application that uses geoserver to deal with 4D data
(lat,lon,altitude,time).  However, I'm now considering a new data type that
actually moves.  That is, it has a geometry, a speed, and a heading.  So
depending on the time I use in my filter, it may be in different locations.  

While I'm totally open to other suggestions, I wonder if this is what was
intended for the OGC Moving Features spec (as well as the new Moving Feature
Access spec).

Here's more detail if needed:
http://www.opengeospatial.org/standards/movingfeatures

Does geoserver deal with this standard?  

Is there some alternative way to handle this in geoserver?

I can imagine solutions that involved writing a plugin or hacking in the
logic elsewhere in my application, but was curious if geoserver is perhaps a
step ahead of me (as usual). 

Thanks!



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to