New answers tagged

1

Hmm. Yes, most tile provider use 3857 but, 4326 is also native supported by leaflet. Before you asked question did you try retrieved data from mongo to use with leaflet? As far as I know it's shouldn't be a problem. When you add geojson with points in 4326 leaflet will internally reproject them to 3857.


0

The best thing is to keep things simple. Most of all tile provider use 3857 and the simple way is to publish wms also in 3857. For wms server like geoserver is not big deal, he will give you wms in every projection you want.


0

I solved by using conversion functions from proj4js.js


1

For proj.4 those two mean exactly the same and conversion from one system to another changes only the EPSG code. If you work with geodetic problems which require accurate ellipsoid model you will need some other tools. # ETRS89 <4258> +proj=longlat +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +no_defs <> # WGS 84 <4326> +proj=longlat +datum=WGS84 ...


1

Do read the Leaflet tutorial on using WMS - it specifically addresses how to use WMS services in other projections. Also note that you can not have raster layers in different CRSs in Leaflet. It's simply not supported due to the complexity of on-the-fly raster reprojection.


4

There is nothing wrong with your data. It is just the fact that OS still issues coordinates in OSGB36, while Google uses WGS84: So you have to assign EPSG:4277 to your degree coordinates, or EPSG:27700 for raster data in projected coordinates. Make sure that both projections have a `+towgs84' datum shift.


0

I have partly found answer in this link How to get raster corner coordinates using Python GDAL bindings? I find corners distance between corners and divide it by size in pixels. It is work. P.S. In some projection I have a strange result. See Wrong corners distance by geopy's Vincenty Distance formula



Top 50 recent answers are included