Is this the thing where you have extra "measures" stored against each
coordinate.
We have talked about this before - with the idea of some functions which could
process (say a line string with measures) into a multi line string of all the
sections that match the requested threads hold ( in your example time ranges).
There was some work on this in the Oracle SDO code base (based around
coordinate sequences) but it looks like we only have the interface left - with
out the default implementation.
I think this would be fine to implement on trunk .. I have some ideas beyond
your slice interval query hint if needed.
--
Jody Garnett
On Wednesday, 28 March 2012 at 3:39 AM, Andrea Aime wrote:
> Hi,
> I'm looking into a funding opportunity that might bring some measured
> geometries support in Geotools.
>
> The requirement I have is to be able to handle measured linestring,
> stored in postgis, the measure in question is a time,
> feature also has, as explicit attributes, the absolute times of start and end,
> while the measure is teh relative time in seconds since the start point.
> Those need to play in a GeoSever WMS + time support so that when
> a time interval is chosen, the features intersecting it are selected
> (this we already have) but also that they are sliced so that only the
> points within the linestring that are between the chosen stand and end
> time show up (time based geometry slicing)...
> and oh, possibly using a native postgis function to do the slicing, too :-)
>
> Laundry list:
> - be able to advertise that a geometry is measured and eventually
> load the measure, at least in postgis, but with a mechanism that
> is not postgis specific. For this one I was thinking to mimim the
> "partial 3d support"
> http://docs.codehaus.org/display/GEOTOOLS/Partial+3D+data+support,
> adding a new metadata entry in the geometry descriptor, "MEASURED",
> marking that the geometry is measured
> - slice natively, but also recognize native slicing is not there, and
> be able to do it in memory instead. For this I was thinking about
> a query hint, that can be either supported by the store, or not.
> SLICE_INTERVAL would be the name and the value is a bean
> with (startMeasure,endMeasure,attributeWithStartValue)
>
> Do you believe something like the above would be ok to implement
> on trunk?
>
> Cheers
> Andrea
>
>
> --
> -------------------------------------------------------
> Ing. Andrea Aime
> GeoSolutions S.A.S.
> Tech lead
>
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax: +39 0584 962313
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.youtube.com/user/GeoSolutionsIT
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
> -------------------------------------------------------
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
>
> _______________________________________________
> GeoTools-Devel mailing list
> [email protected]
> (mailto:[email protected])
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
>
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
