Ocean Basemap Full Extent problem

[IanWatkins]

Really love this new basemap but there does seem to be a problem with the extents given by the MapServer service.

If we look at at World Topo basemap (http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_Map/MapServer) you will see that the Full Extent is given as:

Full Extent:
XMin: -20037507.0671618
YMin: -19971868.8804086
XMax: 20037507.0671618
YMax: 19971868.8804086
Spatial Reference: 102100 (3857)

You'll see you get the same for World Street, World Terrain etc.

However, for Ocean Basemap (http://server.arcgisonline.com/ArcGIS/rest/services/Ocean_Basemap/MapServer) you get the following:

Full Extent:
XMin: -22041259.1770665
YMin: -33265069.1542242
XMax: 22041259.1770665
YMax: 33265069.1542243
Spatial Reference: 102100 (3857)

So if you load Ocean Basemap into a new Flex application (etc.) the JSON reports this Full Extent and when the user pans "off the edge of the world", you get lots of failed tile requests, because they don't exist but the map viewer clears a large enough area for the new tiles which makes it look clunky.

Only way around it at the moment is to define your primary basemap as one of the ones that does work then overlay the Ocean Basemap over the top. Not ideal as doubles tile requests/bandwidth

Any chance this can be fixed?

Cheers

Ian

(ian.watkins@metoffice.gov.uk)

[MikeWilburn]

Hi Ian,

Glad to hear you like the basemap!

The extent problem you indicated has since been fixed and will roll out in an update during the next couple of weeks. Thank you for your feedback.