New answers tagged proj4
Please note that Proj.4 and proj4js are not identical. If you download the latest version of proj4js, you find the defined projections in the lib/projections folder. Regarding EPSG codes, proj4js only has a few definitions, look into lib/global.js or see http://proj4js.org/ But it is possible to build all other definitions yourself if you take the proj4 ...
You can use the transform set up in proj4leaflet. I expect that you have already crated a CRS in your map.options. var my_crs = map.options.crs; // get the CRS var my_proj = my_crs.projection; // get the projection // transform the lat lon Point to a utm point var my_utm_point = my_proj.project(point_in_latlng); If you want to set the internal coordinate ...
"Add feature" came back! A green X on endpoint of a line on a different layer than I wanted to use and that was left over from a previous session (and that I could not turn off, even after restarts and reboots) became a start point once things suddenly began to work. Still a mystery.
QGIS offers these proj strings for NAD83 Louisiana South (ftUS): EPSG:3452 EPSG:3457 EPSG:3553 +proj=lcc +lat_1=30.7 +lat_2=29.3 +lat_0=28.5 +lon_0=-91.33333333333333 +x_0=999999.9999898402 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=us-ft +no_defs EPSG:102282 (from ESRI) +proj=lcc +lat_1=29.3 +lat_2=30.7 +lat_0=28.5 +lon_0=-91.33333333333333 ...
As as there is no support EPSG:6479 (NAD83(2011) / Louisiana South (ftUS)) in PROJ4 (look at the comment of mkennedy) I will illustrate the problem with EPSG:3452, NAD83 / Louisiana South (ftUS) because the problem is the same, the units of the projection. Solution with Pyproj import pyproj southla = pyproj.Proj('+proj=lcc +lat_1=30.7 +lat_2=29.3 ...
PROJ.4 strings always want the false easting (x_0) and false northing (y_0) in meters, no matter what the coordinate reference system units are. Change +x_0 to 1000000.0 and you should get the results you want.
This looks ok. If you run into reprojecting problems, try the spherical version, as I explained here: Manipulating Azimuthal Equidistant Projections in QGIS
You have missed out two parts from your code. To add the GeoJSON layer, you have to call the addTo() method within the L.geoJson object. var geojsonLayer = new L.geoJson().addTo(map); The second part is the most vital. Even though you have defined a custom projection with L.Proj.CRS, your map will be in the Leaflet-native WGS 84 projection (EPSG:4326). ...
Google Mercator is now EPSG:3857, while 900913 has been dropped from the list of EPSG codes. Furthermore, there is some kind of hack inside the projection definition, because Google mercator is calculated on a sphere (a=b), but the lat/lon coordinates are that of the WGS84 ellisoid. This is only implemented correctly for EPSG:3857.
+vunits=m is for vertical datums. Since QGIS is still two-dimensional, it has no impact on the projection. For more details, see http://trac.osgeo.org/proj/wiki/VerticalDatums and http://osgeo-org.1560.x6.nabble.com/Vertical-and-geocentric-coordinate-support-in-OGR-PROJ4-td3841151.html
I was actually trying to do the same thing except with the OH south state plane grid and I came across your question. I was getting wrong results with 3735, now I get correct results with 3729. I expect if you change from 3734 to 3728, you will get the correct results. EPSG:3728: NAD83(NSRS2007) / Ohio North (ftUS) EPSG:3729: NAD83(NSRS2007) / Ohio South ...
Top 50 recent answers are included