[mapserver-dev] Simple features profile
Rahkonen Jukka (Tike)
jukka.rahkonen at mmmtike.fi
Mon Aug 25 08:32:53 PDT 2014
I apologize, I did not notice the difference between using surfaceMembers vs. a list of "surfaceMember" s. I was too much remembering the time when deegree was the only brand which was using surfaces and curves and therefore deegree services could not be cascaded with other brands even is the curves and surfaces were all straight lines and polygons.
I should have checked what my own Mapserver is doing
Sorry for the noise. I am very keen on improving interoperability.
Even Rouault wrote:
> Selon "Rahkonen Jukka (Tike)" <jukka.rahkonen at mmmtike.fi>:
> > Hi,
> > After reading the discussion from the github issue (which is
> > discussion forum that I do not like a lot as a pure Mapserver user) I
> > would say that principally you seem to be right with it. However, when
> > it comes to interoperability I consider it would be better to discuss
> > first with Geoserver, TinyOWS and deegree and ArcGIS developersAll
> > these WFS brands seem to send multiCurves and multiSurfaces. I base
> > this from the deegree side on the 5 year old OpenLayers ticket and
> > from Geoserver, TinyOWS and ArcGIS side on these
> Jukka, I'm a bit confused by what you tried to demonstrate with the above
> examples and am not sure if you've understood the suggested change.
> The above examples show that at least GeoServer and ArcGIS (and likely
> TinyOWS, but couldn't open it through the proxy I'm behind) use
> <surfaceMember> and not <surfaceMembers> (like MapServer and Deegree do).
> Currently, MapServer emits :
> With the proposed change, it would become :
> Spatialys - Geospatial professional services http://www.spatialys.com
More information about the mapserver-dev