New 'Share a link to a map at its current extent' feature not working as intended

[EmilyGoldsmith]

Hello,

In the June Update, the following feature was added:

• "While creating or editing a map that you own, you can now share a link to a map at its current extent that will open in Map Viewer."

However, when I try to share a URL of a webmap at a new mapview, it only applies the centrepoint of that new mapview and not the zoom level.

Instead, in the URL, the zoom level parameter seems to always be -1, regardless of how zoomed in/out the map is. So, only an incomplete version of the new mapview is returned.

Hope this can be sorted as it would be a useful feature to have.

Thank you.

[CodyPatterson]

Hey @EmilyGoldsmith 

Could you show your process of copying the link? I attempted this on my own machine and had no issue getting it to go to current extent and location, my level parameter is changing as well. What I did notice was that when the map came from the Living Atlas, or is shared publicly, it doesn't seem to share the level, instead going to -1, only organizationally shared and personally shared items keep the extent. Is this the same in your case? If so, a bug report may be needed!

Cody

[EmilyGoldsmith]

Hi @CodyPatterson 

I followed the method described on the 'Share Maps (Map Viewer) page under  'Share a link to a map': The page 

So this was: 

1) Open a saved webmap in Web Viewer

2) Move the map to a new mapview

3) In the contents toolbar on the left, go to 'Share Map > Copy link to map' to get the URL.

I did a bit more testing and interestingly got the opposite to what you mentioned.

But then I tested to see if the basemap had any impact and I think this was the cause of the issue. By default, our webmaps use a custom basemap projected to British National Grid (BNG.) Switching to any of the WGS84 basemaps (World Imagery, Topographic, etc) fixed the issue and returned a fully functional link regardless of how the item was shared. 

So a bug report might be necessary, or at least some documentation on how to fix this if our custom basemap needs to be re-configured.

Hope this helps.

[CodyPatterson · Accepted solution]

Hey @EmilyGoldsmith 

Thank you for doing the additional search, it definitely seems like a potential basemap issue as I observed the same results after creating a map with that projection, I didn't notice it at the time but the public layer I used was actually using that projection just by coincidence which is really interesting!

I would open a bug ticket with ESRI and see if they've noticed similar, good luck!

Cody

[KathrynWalker]

Hi @EmilyGoldsmith, 

I tested with OS Open Raster Tile Layer - Overview which is in British National Grid (BNG) projection as well and wasn't able to reproduce. Is your map shared publicly, or at least the basemap layer which you are working with?

Thank you,
Katie

[EmilyGoldsmith]

Hi @KathrynWalker ,

We use a basemap via the Ordnance Survey (OS) Maps API (WMTS). The following endpoint is used to bring it into map viewer: https://api.os.uk/maps/raster/v1/wmts

See here for API documentation: www.data.gov.uk/dataset/b6d2c93a-a57c-422e-931a-349f6ceab3e7/os-maps-api-wmts

This isn't the specific webmap I was working with, but you should be able to reproduce the issue here, given it uses the same endpoint: https://www.arcgis.com/apps/mapviewer/index.html?webmap=600172679cdf411589046e930780db84

Can confirm that the zoom/scale issue occurred my basemap regardless of how it was shared.

Hope this helps.

[bbollin]

Thanks for bringing this up @EmilyGoldsmith, the team is looking into this. This appears to be a known limitation with WMTS basemaps for the moment