0

I try to insert a WMS but Google Earth says WMS capability failed. This is the WMS: https://ccff02.minfin.fgov.be/geoservices/arcgis/services/WMS/Cadastral_Layers/MapServer/WMSServer

I know it is a 1.3.0 WMS server, could that be the issue?

1

This may be more of an extended comment than answer but, Google Earth is correct in identifying that the WMS 1.3.0 service is giving an invalid response.

For example, the name of the service cannot be <Name>CadastralLayers</Name> for a WMS 1.3.0 response it must be <Name>WMS</Name>

Also the MinScaleDenominator and MaxScaleDenominator in all the layers are in the wrong order, that is the service has:

<MaxScaleDenominator>9449.404762</MaxScaleDenominator>
<MinScaleDenominator>0.944940</MinScaleDenominator>

but it needs to be:

<MinScaleDenominator>0.944940</MinScaleDenominator>
<MaxScaleDenominator>9449.404762</MaxScaleDenominator>
  • Thanks for the pointers, so the name must be literaly "WMS"? – Raymarcher Mar 21 at 8:57
  • @Raymarcher yes, see the schema schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd ~ <element name="Name"><simpleType><restriction base="string"><enumeration value="WMS"/>... – nmtoken Mar 21 at 9:48
  • Both issues are resolved but still Google Earth cannot load the layers :-/, I suspect there are still orher issues. – Raymarcher Mar 21 at 15:04
  • Is GE still saying that capability failed? – nmtoken Mar 21 at 15:11
  • Yes, it still says "WMS Capability fetch failed". – Raymarcher Mar 21 at 15:23
1

Trying again following previous advice given in answer Linking Geoserver WMS layer to Google Earth?

With Google Earth Pro (using desktop version as I don't have/want Chrome) I too get the WMS Capability fetch failed message when trying to load your service, and it is indeed due to version, Google Earth sends a WMS version 1.1.1 GetCapabilities request and your service doesn't support it.

The reason as much as anything is that GE wants to use 2D WGS84 in long/lat order (which is what a WMS 1.1.1 GetMap request will give you if you request SRS=EPSG:4326&), however EPSG:4326 is actually a 2D WGS84 in lat/long order, the issue of using the correct axes order for coordinate reference systems was corrected with WMS version 1.3.0, but not so helpful for using GE.

To the rescue CRS:84, that is a WMS version 1.3.0 request that uses CRS=CRS:84& is equivalent to a WMS version 1.1.1 request that uses SRS=EPSG:4326&.

Luckily, as GE retains as a connection string for a layer a list of parameters except the bounding box like below:

http://maps.dgs.udel.edu/geoserver/DGS_Surficial_and_Contact_Geology/wms?service=WMS&TRANSPARENT=TRUE&version=1.1.1&request=GetMap&EXCEPTIONS=INIMAGE&FORMAT=image/png&SRS=EPSG:4326&STYLES=&LAYERS=US-DE_DGS_100k_Surficial_Geology

all you need to do is get GE to accept a layer connection string like

http://ccff02.minfin.fgov.be/geoservices/arcgis/services/WMS/Cadastral_Layers/MapServer/WmsServer?VERSION=1.3.0&REQUEST=GetMap&SERVICE=WMS&FORMAT=image/png&width=1024&height=1024&STYLES=&TRANSPARENT=TRUE&CRS=CRS:84&LAYERS=Regional building

One way of doing this is to use KML like:

    <GroundOverlay>
        <name>Province</name>
        <Snippet/>
        <visibility>0</visibility>
        <open>0</open>
        <Icon>
            <href>
                http://ccff02.minfin.fgov.be/geoservices/arcgis/services/WMS/Cadastral_Layers/MapServer/WmsServer?VERSION=1.3.0&amp;REQUEST=GetMap&amp;SERVICE=WMS&amp;FORMAT=image/png&amp;width=1024&amp;height=1024&amp;STYLES=&amp;TRANSPARENT=TRUE&amp;CRS=CRS:84&amp;LAYERS=Province </href>
            <viewRefreshMode>onStop</viewRefreshMode>
            <viewRefreshTime>5</viewRefreshTime>
        </Icon>
        <LatLonBox>
            <north>48.41564493451794</north>
            <south>45.57192031406902</south>
            <east>5.287537680116226</east>
            <west>0.703481821844738</west>
        </LatLonBox>
    </GroundOverlay>

To give:

Google Earth Pro with KML from WMS 1.3.0 only service

  • You are the hero of the day, worthy of your reputation. I already tried to reverse engineer the link layer connection but with limited knowledge no succes. So the root of the problem is that there is no 1.1.1 version of the WMS? If that gets added then it is probably good to go. Thanks a lot. – Raymarcher Mar 22 at 16:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.