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 On Mon, 2006-09-25 at 12:35 -0400, Justin Deoliveira wrote: > Hi all, > > Currently, TemporalAttributeType just tries the default java date format > when trying to parse a date value from a string. I would like to > slightly modify this to include a set of "common" date formats to try > (including the default). > > Any objections? > > -Justin > ------------------------------------------------------------------------- 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
