Martin Davis wrote:
One approach might be to emit a more standard GML file, along with a
schema, but add some attributes to the first record in the file which
JUMP would understand. This would allow providing simple typing
information, and could also indicate that the first record was simply
a dummy record, if the file was actually empty. Other tools wouldn't
understand this, but they could at least read the file. JUMP could
read and write these file quite happily.
By the way, there's good precedent for doing something like this. At
GeoWeb ESRI gave a talk on their version of GML, which involved adding
lots of extra information to basic GML to accomodate their richer data
model. Obviously other tools are very unlikely to be able to write this
format, but they should be able to at least read it.
I guess this would be the same situation (readable but not writable by
other tools) for my proposed "JML2". So maybe that only meets half of
the need. Sigh... It seems to me to be *very* difficult to develop an
full-blown GML reader for JUMP that can handle arbitrary GML. (GeoTools
apparently has one, though... deegree too maybe?)
--
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
(250) 383-3022
_______________________________________________
jump-users mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jump-users
