[MS4W-Users] [mapserver-users] Mapcache WMTS - imagery is offset in ArcGIS when using WMTS services.

[TC Haddad]

Hi Mark, can you post the mapcache settings that you are using for the WMTS
you are setting up?

Post the <source> block, and the <tileset> blocks of your Mapcache.xml, and
if you are referencing a Mapserver map file configuration, post the LAYER
definition.



On Mon, Apr 15, 2019 at 7:59 AM Mark Volz via MS4W-Users <
ms4w-users at lists.ms4w.com> wrote:

> Steve,
>
>
>
> Thank you for your reply.  When I changed the Mapcache projection to WGS84
> the basemap did display in the correct location.  However, when using UTM
> 15 (SRS 26915), and Lyon County MN Coordinates (103749) the image is still
> offset.  What I find unusual is that when using WMS instead of WMTS the
> maps display in the correct location no matter what projection I am using.
>
>
>
> Test Results for the service called “TestLyonBasemap” on
> http://geomoose.lyonco.org/mapcache/wmts/1.0.0/WMTSCapabilities.xml
>
> WMTS:  WGS84 – pass, Lyon County Coordinates 103749 – fail, UTM 15 – fail.
>
> WMS:  WGS84 – pass, Lyon County Coordinates 103749 – pass, UTM 15 – pass
>
>
>
> I am not sure if I have something configured incorrectly, if there is a
> bug in MS4W 3.3.0, or if there is a limitation in WMTS when using UTM or
> Lyon County projections.  Please let me know if you have any thoughts.
>
>
>
> Thank You!
>
>
>
>
>
>
>
>
>
>
>
>
>
> Sincerely,
>
> *Mark Volz, GISP*
>
> *Lyon County GIS Coordinator*
>
>
>
> *From:* Lime, Steve D (MNIT) <steve.lime at state.mn.us>
> *Sent:* Friday, April 12, 2019 5:00 PM
> *To:* Mark Volz <MarkVolz at co.lyon.mn.us>; mapserver-users at lists.osgeo.org
> *Subject:* RE: [mapserver-users] Mapcache WMTS - imagery is offset in
> ArcGIS when using WMTS services.
>
>
>
> *SWHHS/LYON/LINCOLN COUNTY SECURITY NOTICE:*
>
> *This email originated from an external sender. Exercise caution before
> clicking on any links or attachments and consider whether you know the
> sender. For more information please contact IT support.*
> ------------------------------
>
> The resolution doesn’t matter. That just impacts scale computations
> internally so when layers/classes are on/off and how symbol/font scaling is
> done.
>
>
>
> I just tried our Compass MapCache/WTMS service overlaid with a shapefile
> in UTM projected appropriately and they line up perfectly in ArcGIS 10.6.
> You can try it too with your data since you’re in MN (
> http://maps1.dnr.state.mn.us/mapcache/wmts/1.0.0/WMTSCapabilities.xml).
> Does it behave any differently for you?
>
>
>
> --Steve
>
>
>
> *From:* mapserver-users [mailto:mapserver-users-bounces at lists.osgeo.org
> <mapserver-users-bounces at lists.osgeo.org>] *On Behalf Of *Mark Volz
> *Sent:* Friday, April 12, 2019 12:08 PM
> *To:* mapserver-users at lists.osgeo.org
> *Subject:* [mapserver-users] Mapcache WMTS - imagery is offset in ArcGIS
> when using WMTS services.
>
>
>
> Hello,
>
>
>
> I noticed that WMTS services are extremely fast when using Mapcache to
> serve tiles to ArcGIS clients.  However, the imagery appears to be shifted
> down significantly from the actual location.   I did notice that Mapserver
> and Mapcache use a 72 DPI while ArcGIS is using a 90.714 DPI.  In addition
> the image is the correct width and height.  In addition, when I use WMS the
> imagery appears in the correct location, however it is not as fast as WMTS.
>
>
>
> Please let me know if there is a way to get ArcGIS to place imagery in the
> correct location when using WMTS and Mapcache.
>
>
>
> Thanks
>
>
>
> Sincerely,
>
> *Mark Volz, GISP*
>
> *Lyon County GIS Coordinator*
>
>
> _______________________________________________
> MS4W-Users mailing list
> MS4W-Users at lists.ms4w.com
> https://lists.ms4w.com/mailman/listinfo/ms4w-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ms4w.com/pipermail/ms4w-users/attachments/20190415/0c669b0f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 28131 bytes
Desc: not available
URL: <https://lists.ms4w.com/pipermail/ms4w-users/attachments/20190415/0c669b0f/attachment-0001.jpg>