aximgeo / arcgis-level-fixer Goto Github PK

after a conversation i had with @jonahadkins at FedGIS, i thought i'd provide an extremely belated followup regarding the behavior of ArcGIS Server 'out of the box'.

based on my understanding of what Jonah was asking, it looks like ArcGIS Server 10.3 behaves as it should (ie: when a Google/Bing tiling scheme is selected, but only a subset of tile levels are cooked, ensure that the indicies of the individual layers present correspond with well known tile level numbers, don't just start counting at zero).

you can see an example here

for the JSAPI, its worth a reminder that since LODs are now referenced in the layer metadata which may not be present, this makes it necessary to restrict with a subset manually if you'd like to disable zoom beyond the levels present in your own service.

let me know if you guys have any other questions. i'm happy to chat about it more.

Cross posting this with the Esri Leaflet issue.

Over the weekend I got a support request from the City of Philadelphia who has the following tile service http://tiles.arcgis.com/tiles/fLeGjb7u4uXqeF9q/arcgis/rest/services/CityBasemap_2015/MapServer with non standard zoom levels AND a non-standard origin [-20037700, 30241100] vs [-20037508.342787, 20037508.342787]. The zoom level correction code is working great but all the tile values are offset because of the custom origin.

@jonahadkins @cbupp @jgravois what do you think about trying to make Esri Leaflet/Arcgis Level Fixer also handle custom origins? How difficult would that be?

Esri/esri-leaflet#567

@JCSanford asked: Yes, that looks promising! Does that expect a tile cache to exist for that service or can it be uncached?

https://twitter.com/JCSanford/status/524205272257269760