New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation for tiledmapLayer is not strictly accurate. Can use alternatives to epsg:3857 #1357
Comments
yup. there's an example here: https://developers.arcgis.com/esri-leaflet/samples/non-mercator-projection/ my impression is not that what you're saying isn't possible, just that they don't take responsibility for it working correctly. |
As stated, you would read that statement and give up immediately. A link to the sample would make it clear that it is actually possible. |
@scaddenp thank you for the report. In your original post you said, "The docs state". What is the URL to the page from where you got that wording? |
On the docs for tiled map layer. https://developers.arcgis.com/esri-leaflet/api-reference/layers/tiled-map-layer/ |
@scaddenp I propose we update to this:
Can you write up a sample showing the use of a non-mercator tileset that we can add to the samples? Currently we only show feature layers and dynamic map layers. |
Should be able to but not immediately. Last weeks of FY has huge pressure on... |
I have a CodePen sample that uses Proj4Leaflet and a tiled map service using state plane projection. |
Description
The docs state: "Your map service must be published using the Web Mercator Auxiliary Sphere tiling scheme (WKID 102100/3857) and the default scale options used by Google Maps, Bing Maps and ArcGIS Online. Esri Leaflet will not support any other spatial reference for tile layers."
This is not strictly true. Other epsg can be used but you have to also use the proj4leaflet plugin. Many tiled layers are published in NZ with EPSG:2193 (a national grid) and I consume these with leaflet without issue provided they use the same tilesize. (and working on a fix for that too).
Link to page
No response
The text was updated successfully, but these errors were encountered: