Opened 17 years ago
Closed 6 years ago
#1869 closed defect (fixed)
Improve XSD lookup based schemaLocation
Reported by: | Mateusz Łoskot | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | OGR_SF | Version: | unspecified |
Severity: | normal | Keywords: | gml |
Cc: |
Description
Currently, the GML driver searches for XSD file using name of GML file with .xsd extention. We really ought to look for it based on the rules schemaLocation in the GML feature collection but for now we just hopes it is in the same director with the same name.
Change History (3)
comment:1 by , 9 years ago
comment:2 by , 6 years ago
Now we have a shiny GMLAS driver, I suppose that it has solved this issue.
comment:3 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The GML driver has received lots of improvements since the creation of this ticket. This one is addressing partly this issue:
"Starting with OGR 1.10, it is possible to specify an explicit filename for the XSD schema to use, by using "a_filename.gml,xsd=another_filename.xsd" as a connection string."
Direct reading of schema from schemaLocation is not implemented. A general solution would not be trivial, see mailing list thread http://osgeo-org.1560.x6.nabble.com/gdal-dev-Reading-gml-with-schema-td5056381.html
I can't judge if the work done with the GML driver is enough for closing this ticket.