New answers tagged wgs84
I thought at first the arcpy.Polyline.getLength() method would work, as you can specify a measurement type and units but it did not because it is GCS. As you can see here, we are still in Decimal Degrees: >>> with arcpy.da.SearchCursor("line_wgs", 'SHAPE@') as rows: ... for row in rows: ... print row.getLength('PLANAR', 'METERS') ... ...
A KML file stores coordinates as latitude, logitude (WGS84). Steps to do in QGIS: load your dxf set (double check) the projection setting of your dxf layer right click on the layer name in the layer list and select save as set the output format to KML and the projection to WGS84 (epsg:4326) simply open your kml file in google earth I hope it helps you
I'm not sure what NOAA thinks are the right coordinates, but I have no problem loading the file into QGIS, or reprojecting it to WGS84 with gdalwarp: QGIS uses this custom projection string: +proj=lcc +lat_1=25 +lat_2=25 +lat_0=25 +lon_0=265 +x_0=0 +y_0=0 +a=6371229 +b=6371229 +units=m +no_defs You can use the same string with pyproj.Proj(). where you ...
The WGS84 geoid is not a sphere with a constant radius, but rather an ellipsoid. According to https://en.wikipedia.org/wiki/World_Geodetic_System, the ellipsoid has a = 6378137 m and b = 6356752 m. It seems that without OTFR the distance is calculated using the sphere, and with OTFR using the ellipsoid.
I agree with Micky T, it looks like you are using the wrong proj4 string. First, you will need to ensure which projection your numbers are in. WGS84 is the datum, not the projection. One possible projection is UTM, which defines your starting point for your easting and northing in meters. The x and y values that you give sure look like they are a ...
Top 50 recent answers are included