[mapguide-internals] [RFC Review] RFC095 OGC WMS 1.3.0 Support

[Arthur Liu]

Hi Jason,

Thanks for your feedback.

I have update the milestone to 2.3, so all the updates will not affect the release cycle for 2.2.

To your second question about the CS-Map, I heard that CS-Map will extend their API to determine the axis orientation for EPSG coordinate systems. I am not sure if CS-Map will support the CRS and AUTO2 namespaces this release. There's another reason for the workaround is the limitation of MapGuide. For the current implementation of MapGuide, I think MapGuide only support EPSG:4326 and Mentor CS code like LL84 (if I'm wrong please point this out). If user want to use other EPSG CRSs, he has to modify the OgcWmsServer.config file manually. Back to your question, if CS-Map supports the CRS and AUTO2 namespace and provides us relevant API, I think we can resolve this problem thoroughly.   

To the third question about reverse axis order, I know that MapServer just check the EPSG code, if the EPSG code between 4000 and 5000, it will be considered as having reversed axis order. I have discussed with some CS experts, they thought that's not a proper solution, because there are lots of EPSG CRS doesn't reverse their axis order in that range. And they recommend us to use the API GetQuadrant to determine the axis order for EPSG axis order. Besides the WMS server, all the WMS clients which follow the WMS 1.3.0 specification should also check the axis order. For example, if a client sends a request will a boundingbox in EPSG:4326, the boundingbox will like (minlat,minlon,maxlat,maxlon) instead of (minlon,minlat,maxlat,maxlon).

About the MapDefinition publishing, do you mean that MapGuide combine all the layers in a map as a single WMS layer or make the map as the parent WMS layer for all WMS layers which come from this map? 

Regards,
Arthur



-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Saturday, June 12, 2010 4:08 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] [RFC Review] RFC095 OGC WMS 1.3.0 Support

Hi Arthur,

Is 2.2 really the target for this RFC?  How will this affect our release
cycle for 2.2, which has already gone to beta?

Is the reason for the workaround because CS-Map does not currently support
these namespaces, and we don't want to wait for a CS-Map update?

Because of the nasty history around WMS 1.3 axis order, I believe that
several other WMS servers apply sanity checks against passed values
(Latitude < -90 or > 90?), and may even fall back to old behaviour.  I could
be wrong or have outdated information.  Have the clients caught up to the
point where we can safely just implement the standard as written?

This is out of scope for this RFC, but it sure would be REALLY handy if we
could publish MapDefinitions as WMS, rather than just LayerDefinitions.  And
if I'm wrong about this, please let me know :)

Jason

On 11 June 2010 23:19, Arthur Liu wrote:

> Would you please review the RFC095<
> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc95> for OGC WMS 1.3.0
> support? Your suggestion and feedback are very appreciated!
>
>
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals