New answers tagged


You can rotate the coordinates of an SP object using elide from maptools, but you'll lose any true geographic location reference. You also won't be able to overlay on map tiles since they are fixed at that alignment. Example using scot_BNG from readOGR: > plot(scot_BNG) > plot(elide(scot_BNG, rotate=-45)) Alternatively use an oblique mercator ...


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.. ...


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


This kind of calculation is often referred to as CoGo (for coordinate geometry). If you have several of them to do, and you don't wish to do any programming (or a lot of hand calculations) you can use Copan for Windows -- a free tool for CoGo and many other kinds of land survey calculations. You can enter known coordinates in one place and known bearings ...


Your assumption of linear conversion is wrong. In Transverse Mercator, only the central meridian is straight northward, all others are bended. So 11.5 vs 12 degrees makes a difference. Besides Gabon 2010, there is a Gabon 2011 coordinate system, with this proj.4 parameter string: +proj=tmerc +lat_0=0 +lon_0=11.5 +k=0.9996 +x_0=1500000 +y_0=5500000 ...


Try with other zone it has no problem, I guess GDAL cannot wrap it outside. gdalwarp -t_srs '+proj=utm +zone=12 +datum=WGS84 +units=m +no_defs' test.tif test_utm1.tif


To get the coordinates of the points you can use these equations: Delta Y = Distance * Cos (Azimuth) Delta X = Distance * Sin (Azimuth) New Y = Y + Delta Y New X = X + Delta X First you'll have to get the coordinates of B using these equations then go from there to C.


Looks like you're trying to add data to the insert cursor one column at a time. Cursors think about the world one row at time. I recommend the following code. A few other notes... Python code runs in order, so make sure you declare your outpath variable before you set your env.workspace to outpath. Also, this code is going to create a shapefile with the ...


Problem solved. Geoserver had problems with the projection. The tiffs were in EPSG:32633. It works after reprojecting the tiffs to EPSG:3857.


Here is the answer I got back from NOAA. It's in the form of java code, and the order of parameters has to be inferred, but in case it proves useful to someone else here it is: public static final HTDP NAD83 = new HTDP(0.9910, -1.9072, -0.5129, 0, 0, 0, 1.25033e-7, 0.46785e-7, 0.56529e-7, 0.00258e-7, -0.03599e-7, -0.00153e-7, 0, 0, 1997); public static ...


There are no default transformations in the EPSG Geodetic Parameter Registry. Sometimes you can use the remarks and or the accuracy value to determine which is the currently accepted transformation as defined by the government or the most accurate transformation. For instance, in Belgium, there are two transformations between BD72 and ETRS89: 1652 and ...

Top 50 recent answers are included