> Adrian Custer wrote:
> > Hey,
> >
> > TemporalAttributeType seems like a total hack. It should look a whole
> > lot like GeometryAttributeType. That is, it should provide access to a
> > TemporalReferencingSystem and should allow lots of different forms: an
> > instant (point), an interval (line), a collection (collection: series
> > (multipoint), multiinterval (multiline), arbitrary collection), as well
> > as an undefined state representing the way things are now where we
> > assume all elements exist conjointly and overlap totally.
> >
> > So I can't suggest any reasonable answer to your question apart from
'do
> > whatever you like'; we presumably will have to address the temporality
> > of elements at some point in the future. ;-)
> >
> > --adrian

...if you need it...
Alex partially implemented ISO 19108 as both GeoAPI interfaces and code (I
don't think he did the "topology" part.)  Eventually we're going to give it
to geotools.  I'm sure he'd enjoy having someone debug it for him. (oops
did I say that out loud?)


Bryce


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to