120 likes | 220 Views
GML discussion (Emmen, 26 January 2006). The srs syntax is not standardized enough (there is variety in the practice GMLs) What would be the solution for this?. One feature, one geometry attribute Easier for several software packages. It should not be needed to write GML files
E N D
GML discussion (Emmen, 26 January 2006)
The srs syntax is not standardized enough (there is variety in the practice GMLs)What would be the solution for this?
One feature, one geometry attribute Easier for several software packages.
It should not be needed to write GML files according to the top10nl schema The purpose of GML is to be model-driven and good software should be flexible enough to read this.
TOP10NL should not use deprecated GML2 e.g. instead of using <gml:Polygon><gml:exterior> <gml:LinearRing> it would be better to use <gml:Surface><gml:patches> <gml:PolygonPatch><gml:exterior> <gml:LinearRing>
Multi-schema class inheritance is good • + it is a reflection of the information model. • don’t make the GML schemas too complicated.
1+ user-defined namespace is a problem NEN3610, TOP10NL and the inheritance…
Without Safe Software this event would not have been possible
A WFS simple feature profile is needed For the TOP10NL (two versions?)
What is a valid polygon? It seems different systems have different orientation for outer and inner boundaries (the (counter) clockwise issue).