-
Notifications
You must be signed in to change notification settings - Fork 173
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
L.Proj.GeoJSON #32
L.Proj.GeoJSON #32
Conversation
Thanks, this looks like a really nice addition. I have some questions:
|
|
I did not know about the work being done on modernizing Proj4js, so thanks for the heads up. It's definitely a project that needs some refactoring. The core functionality is very nice, but API and structure... not so much. |
Ok, I added a complete example to the directory and further clarified the usage caveats. In order for the example to work, I needed to update Leaflet to 0.6 which adds the |
I also added a reference to geojson/draft-geojson#6 for completeness. |
Adds L.Proj.GeoJSON for projected GeoJSON support.
Thanks again. Sorry about the delay, I've been away for a couple of weeks. |
Hi, this pull request adds
L.Proj.GeoJSON
(andL.Proj.geoJson
). Note that unlike the other Proj-aware layers, the CRS code is read from the JSON object directly, rather than being an argument to the constructor. This means it is not possible to set the Proj4js definition via the CRS constructor, so it must be done manually beforehand (see example).One nice thing about this approach is that it makes it possible to display GeoJSON stored in a different projection than the map.