|
Posted by Ronald Müller on June 20, 2005, 10:27 am
Please log in for more thread options Paul Cooper wrote:
> On Fri, 17 Jun 2005 12:26:23 +0200, Ronald Müller
>
> [...]
>
>
> GML is a transfer mechanism, so validation of geometry isn't its job -
> it is the job of the software that creates it and receives it. The
> latest version (3.1.?) of GML does include mechanisms for expressing
> topology that might help, but basically validation at that level is
> not possible wiithin the XML validations that can be applied. We can
> only check that the XML is valid and conforms to the schema that
> defines XML. As the coordinate information may well be held (for
> example) as strings of coordinates, then it is below the level of
> granularity of that XML "sees" and can validate.
>
> And I wouldn't be so sure that a self-intersection is automatically an
> error. Yes, it is in most instances, but (for example) it used to be
> perfectly possible to create a polygon in a shapefile that
> self-intersected. And, of course, a polygon that is the two
> dimensional projection of a figure in 3 dimensions could very well
> self-intersect! GML is intended for all manner of spatial information,
> not just geographic information, and in an engineering context it
> could be perfectly correct.
>
> Paul
Hallo Paul,
thanks for your comprehensive answer. Let me do some additional notes to
this topic.
I found out that GML 2 (and 3 too) are definitly based on the Simple
Feature Specification from OGC, for that reason selfintersecting
polygons are NOT valid at all.
Ronald
|