At 08:39 11/09/2007, Gabriel Roldán wrote:
seems to be simply that the schema referenced by the gml file is not accessible.
That's what we thought/assumed, and that's why Yann wrote this: On Monday 10 September 2007 19:48:55 Yann Semet wrote:
> We did check that the urls for the .xsd files are indeed correct. We also > tried to modify these urls to point directly on the hard drive, in the .gml > file containing folder where copies of all the necessary .xsd files were > present as well. Nothing we tried proved successful yet and we found no way > yet to get our hands on the actual features. There seems to be a problem in > the hierarchical resolution of xsd file names to their actual physical > locations.
But none of that worked. So, what we're really asking is this:
> Being newcomers, we're a little confused as to what the step we missed > actually is. Are we facing a simple path problem (just letting the parser > know where to look for .xsd files) or do we need to write a bunch of code > to allow the parser to correctly work with our data? In particular, do we > simply need to override stuff as suggested in > http://docs.codehaus.org/display/GEOTDOC/2+SchemaLocationResolver+and+Schem >a Locator ?
Note: we can easily supply all these schemas and the sample GML file to anyone who thinks they know how this should work.
cheers, Vince. _______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
