Closed arctelix closed 8 years ago
The issue was due to incorrect proj4js data from epsg.io. I used the data from spatialreference.org and it worked perfectly. Is there perhapse another setting for units. It appears the difference was with units=us-ft
vs datum=NAD83 +to_meter=0.3048006096012192
epsg.io provided this (incorrect):
"+proj=lcc +lat_1=41.03333333333333 +lat_2=40.66666666666666 +lat_0=40.16666666666666 +lon_0=-74 +x_0=300000.0000000001 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=us-ft +no_defs"
spatialreference.org provided this (correct):
"+proj=lcc +lat_1=41.03333333333333 +lat_2=40.66666666666666 +lat_0=40.16666666666666 +lon_0=-74 +x_0=300000.0000000001 +y_0=0 +ellps=GRS80 +datum=NAD83 +to_meter=0.3048006096012192 +no_defs"
Thanks for reporting, and thanks for also providing a fix.
I'm not sure, but it sounds possible this would be an issue in proj4js, interpreting the +units
parameter the wrong way.
Do you know which proj4js version your using? If not latest, I would try that. The both proj4 strings look like they should be equivalent.
For some reason EPSG:2263 projections seem to be incorrect. The tile server works properly at all zoom levels as configured. However, the tiles are rendering at the incorrect latLng.
I feel like i have tried everything possible here, any ideas appreciated.
Current Proj4Leaflet config: