[Geomoose-users] TMS layers in GeoMOOSE 3.x

[Jim Klassen]

On #2, Brent basically covered it.  If the tile webserver is different from the GeoMoose webserver then the webserver serving the tiles needs to set a header to allow CORS requests otherwise the browser will block the request.

And you probably also need the:

     <param name="cross-origin" value="anonymous"/>

parameter in the <map-source> so that OpenLayers will actually make the CORS request.

Basically GeoMoose is just setting this in OpenLayers behind the scenes.

https://gis.stackexchange.com/questions/71715/enabling-cors-in-openlayers
http://dev.openlayers.org/apidocs/files/OpenLayers/Tile/Image-js.html#OpenLayers.Tile.Image.crossOriginKeyword



On 12/20/21 12:08 PM, Brent Fraser wrote:
> Hi Mark,
>
>   Regarding Issue #1 (the tile id problem), try using
>
> <url>https://geomoose.lyonco.org/lyonmapcache/tms/1.0.0/LyonPictoPhotos2020@GoogleBingArcGISCompatible/{z}/{x}/{-y}.jpg</url>
>
> Note the {x}/{-y} order and the minus sign.
>
> As for Issue #2 (the cross-origin problem), Jim would be the expert.  If you are in control of the tile server (and it is running Apache as the web server) you could try adding
> Header set Access-Control-Allow-Origin "*"
> to the configuration (as an example see https://github.com/geomoose/gm3-demo-data/blob/c29e41a341a300532984a4daeb26fa14bddc156a/docker/etc/000-default.conf#L14 <https://github.com/geomoose/gm3-demo-data/blob/c29e41a341a300532984a4daeb26fa14bddc156a/docker/etc/000-default.conf#L14> )
>
> Other possible solutions are:
> -  serve the GeoMoose page from the same origin as the tiles, or
> - put a proxy on the GeoMoose page server to get the tiles when requested and pass them to the Geomoose page.
>
> Best Regards,
> Brent Fraser
>
>
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> *From*: "Mark Volz" <MarkVolz at co.lyon.mn.us>
> *Sent*: 12/20/21 8:43 AM
> *To*: "geomoose-users at lists.osgeo.org" <geomoose-users at lists.osgeo.org>
> *Subject*: Re: [Geomoose-users] TMS layers in GeoMOOSE 3.x
>
> Brent and Jim,
>
> Thank you for your replies.
> I am using MapCache to serve out imagery in Web Mercator (GoogleBingArcGISCompatible). The Web Mercator tiles are working correctly in ArcGIS as well as QGIS when using WMTS. Unfortunately, I am still having a couple issues:
>
> Issue 1:
> *GeoMOOSE is requesting a tile that it out of range. I am not sure what is causing this issue:
> GeoMOOSE is working with other XYZ tile servers such as OpenLayers.
> MapCache is working with ArcGIS and QGIS clients.
> The tiles requested and served are 256*256.
> I think the tiles should be working however I am still getting an error that my tiles are out of range even after I checked to make sure that I did not swap the X and Y. One error is that MapCache is reporting tile y=189759 is not within 334028 to 334954.
>
> Issue 2:
> *Firefox is reporting that a cross-origin request is blocked.
>
> Please let me know if you might know how I can fix these problems. For reference I the public server and configuration information is below.
>
> Thank You!
>
>
> The public server is:
> https://geomoose.lyonco.org/lyonmapcache/tms/1.0.0/LyonPictoPhotos2020@GoogleBingArcGISCompatible <https://geomoose.lyonco.org/lyonmapcache/tms/1.0.0/LyonPictoPhotos2020@GoogleBingArcGISCompatible>/
>
> GeoMOOSE Configuration:
> <map-source name="Picto2020BackgroundTMS" type="xyz" transitionEffect="resize">
> <layer name="LyonPictoPhotos2020"/>
> <url>https://geomoose.lyonco.org/lyonmapcache/tms/1.0.0/LyonPictoPhotos2020@GoogleBingArcGISCompatible/{z}/{y}/{x}.jpg</url>
> <type>"jpeg"</type>
> </map-source>
>
> MapCache Configuration:
> <grid name="GoogleBingArcGISCompatible">
> <metadata>
> <title>GoogleBingArcGISCompatible</title>
> <WellKnownScaleSet>urn:ogc:def:wkss:OGC:1.0:GoogleMapsCompatible</WellKnownScaleSet>
> </metadata>
> <extent>-20037508.3427892480 -20037508.3427892480 20037508.3427892480 20037508.3427892480</extent>
> <srs>EPSG:3857</srs>
> <srsalias>EPSG:900913</srsalias>
> <units>m</units>
> <size>256 256</size>
> <resolutions>156543.0339280410 78271.51696402048 39135.75848201023 19567.87924100512 9783.939620502561 4891.969810251280 2445.984905125640 1222.992452562820 611.4962262814100 305.7481131407048 152.8740565703525 76.43702828517624 38.21851414258813 19.10925707129406 9.554628535647032 4.777314267823516 2.388657133911758 1.194328566955879 0.5971642834779395 0.29858214173896975 0.149291070869484875</resolutions>
> </grid>
>
>
>
>
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geomoose-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20211220/ba875176/attachment.html>