New answers tagged wgs84
I don't know the software you use, but I could get the data into QGIS: The corner points and the one from the second screenshot seem to be correct in North Kansas, and correspond to real estate borders in Google satellite imagery. Two sides are made up of streets that are in OSM maps as well. As you found out, the base point WGS84 coordinates are wrong ...
Based on the steps you tried so far I think you have only created an on-the-fly version of what you want. Mosaic datasets do not change or create any new rasters, they just process them on the fly for fast visualization. If you export the resulting mosaic dataset as a new raster you should get the result you want.
If you are particularly interested in using meters as the unit for the search, you can use geography data types instead of geometry types. All geography based calculations return values in meters. Also, ST_DWITHIN is designed for this type of queries: select * from zones z where ST_DWITHIN(Geography(ST_Transform(z.geom,4326)), ...
You can use Mapshaper for this, and then dissolve from the command line: mapshaper --dissolve -i your_data.geojson
It's easy to do with QGis. Open QGis Drag&Drop the geojson file to qgis use the "dissolve" tool in the vector menu (it's inside a submenu). use the "dissolve all" option from the dropdown this will create a shapefile (check the box to output to the map) which you can then again save as a geojson file by right-clicking it in the layer pane and choosing ...
Just mousing over a location shows the elevation at the bottom of the screen, along with lat/lon. There's also the Elevation Profile feature: https://support.google.com/earth/answer/181393?hl=en
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.
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 ...
Late to the party, but with a hopefully useful contribution. Building on scw's answer using geopy, I wrote a small function that does the calculation for a shapely LineString object with arbitrarily many coordinates. It uses a pairs iterator from Stackoverflow. Main feature: the docstrings are much longer than the snippets. def line_length(line): ...
Top 50 recent answers are included