For the past week, I've been up to my eyeballs in the ISO19123 schema.
I've been writing a little document relevant to the coverage effort.  It's
28 pages long now and I'm not quite done.  (It seems that every time I go
back over something I've already covered, I figure out how I missed
something which makes me wrong.)  Also, there's one section that needs
finishing and another which needs to be written.  This is on top of the
endless nitpicking and revisions I seem to do.

Comments and criticisms are welcomed.

Some topics:
* difference between OGC Features and ISO/TC211 Features (NOTE: OGC is
going to have to address this sometime soon, like before adopting 19123.)
* difference between OGC Features and coverages
* instance relationship of ISO/TC211 features and coverages
* definition of common Quadrilateral Grid terms, as per the usage in the
standard
* detailed examination of Discrete Grid Point Coverage and friends.
* detailed examination of Discrete Point Coverage and friends (includes a
proposed fix for illegal UML)
* detailed examination of CV_Grid and children (access to grid data w/o CRS
info; includes proposed fix to realize a separation of access by index and
access by location)
* detailed examination of how to evaluate spatiotemporal coverages
* many UML diagrams to illustrate relationships of note.

http://docs.codehaus.org/display/GEOTOOLS/ISO+19123+progress+and+future+plan

It's in the hotbox on the above page.  I provided OpenOffice and PDF
versions this time.  I will be updating this as time goes on.

Bryce



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to