New answers tagged

1

No. Leaflet does not implement fancy reprojection. You will have better luck if you manually reproject your data from EPSG:4326 into EPSG:3857, and then use the EPSG:3857 coordinates into a Leaflet map with CRS.Simple. My tool of choice for reprojections is ogr2ogr, although you can do it in javascript only by using proj4js.


-2

After weeks of trying to solve this same problem, this amazing set of code samples absolutely saved me: http://wiki.openstreetmap.org/wiki/Mercator#Spherical_Mercator


4

I'd recommend using something like the proj4 library, which has wrappers in several languages, including JavaScript - Proj4JS. For C#, there's proj4net It has the advantage you can translate between all sorts of projections, not just OSGB. I'm not a great JS developer, but something like this should do the trick to convert OSGB back to WGS84 EDIT oops.. ...


6

There is a JavaScript from Convert between Latitude/Longitude & OS National Grid References which converts between easting/northings to lon/lat, which could be helpful. It is also available in GitHub


5

Solved: My map's data frame is in NAD_1927_StatePlane_New_Mexico_East_FIPS_3001. When I added the NAD83 UTM data I had assumed it was spatially accurate "on the fly" not knowing that, as @Vince, pointed out, when using "on the fly" projection for NADCON the transformation must be specified manually. After re-adding the NAD83 UTM data and manually ...


1

Do they both have a defined coordinate system? I think this occurs because although Arc can project data on the fly, this does not apply when the data is in two different coordinate systems or datums, such as NAD 1927 vs NAD 1983. You need to apply a transformation. See related. I would recommend choosing a coordinate system and projection, and re-project ...


2

The usual way to reproject a layer is: for vector layers: Save As ... for raster layers: Raster -> Projections -> Warp Both need a different filename and the CRS you want to reproject to. You can not reproject to the same file. If you want that, copy the source data to another folder, and replace the data within the project with the copy.


0

Thank you for the input. I've solved my issue. Long story short, I was importing the wrong elevation model file. See, the elevation data with which I'm working is an Arc grid, so several files work together to provide a meaningful elevation model in QGIS. (Forgive the triviality here, but this is new to me. In my case, I was importing dem_10.ovr, which ...


0

Thanks all for your responses, they are the clues for me to realize what was happening. First think to notice is that when I drag and drop the raster into the dataframe in Arcmap, it pops up an alert saying “Unknown spatial Reference”, that means this raster map was not referenced and hasn’t a defined a projection. Assigning a projection to the dataset is ...


0

Unfortunately, your test example is not online anymore, so I took a gobal Land-Sea-Temperature sample from ftp://landsaf.ipma.pt/pub/Example_of_Product/ As mentioned in my answer to Transforming geostationary satellite image to lon/lat, the size of global geos reprojected files is 3712x3712 pixels (3-km-resolution), but the actual data array is smaller. ...


0

If you've access to ArcGIS, open a new map, add a 'basemap' from the server, with a known coordinate system, and then add your two data files. One or both of them will come in without a defined coordinate system. Then change the coordinate system on the MXD until they all line up properly. The one that works will be the coordinate system to assign to your ...


4

This is the Lo system used in southern Africa. You mentioned that it's Lo 19/WGS 84. I suspect it's really Hartebeesthoek94 / Lo19. Hartebeesthoek94 should be almost equivalent to WGS 84. The EPSG code, or well-known ID (WKID), is 2048 but Esri software doesn't support that WKID because the axes order and directions are positive west, positive south and ...


3

If you reproject a raster to a different projection, the cell sizes do not match to the original. For this reason, the new cell value will be calculated with respect to neighbouring cells as a weighted mean value. In your original files, both cell sizes matched exactly (0.000833333 degrees), and the cell values were identical. But after reprojection, cell ...


1

Try loading proj4 before OL3. I had issues until I was told to load them in that order.


1

I would just read directly from the source HDFs with raster, you'll need to make sure you have the right HDF libraries installed when GDAL is installed / built. What Linux are you on? On Ubuntu with apt-get I use (something like) this install script: https://github.com/mdsumner/nectar/blob/master/r-spatial.sh That has fuller notes about RStudio and other ...


1

latest versions of ol3 support client reprojection for both raster and vector data. even for tile layers. example here and here I think your fault is that you use the projection config on map and not on view. The rest of our code seems to be correct. Try this var view = new ol.View({ center: birmingham, projection:projection, zoom: 6 ...


2

You don't need to reproject a WMS layer, OpenLayers should make the request in the map projection for you automatically. The only time there might be an issue is if the WMS Server doesn't support the projection of your map, but checking the capabilities of your server shows that the layers are available in 3 CRS: <CRS>EPSG:25830</CRS> ...



Top 50 recent answers are included