Bike maps: Difference between revisions
From Wildsong
Jump to navigationJump to search
Brian Wilson (talk | contribs) m Created page with "Oregon Bike Map Proposed Tunison bike path" |
Brian Wilson (talk | contribs) |
||
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
[[Oregon Bike Map]] | [[Oregon Bike Map]] | ||
Proposed Tunison bike path | == Proposed Tunison bike path == | ||
=== Google Maps === | |||
The finished page is here: http://alseageo.com/Maps/tunison.html | |||
=== Google Earth === | |||
The unfinished page is here: http://alseageo.com/Maps/t_tunison.html | |||
=== Method === | |||
* Digitized routes in ArcMap | |||
* Saved as shapefiles in Benton county projection | |||
* Reprojected to Web Mercator and convert to KML with ogr2ogr | |||
* Edited KML files in emacs to make them look good in Google Earth | |||
* Created web page on hostmonster.com hosted site | |||
Note the backwards source and destination | |||
for shp in *.shp | |||
do | |||
b=`basename $shp .shp` | |||
ogr2ogr -f "KML" -t_srs EPSG:900913 $b.kml $shp | |||
done | |||
This creates KML files that can be loaded into a Google map (Google Earth or Google Maps). | |||
After all the bother of creating and editing KML files, | |||
I ended up taking the linestrings and points out of the KML file and making a Google javascript program instead. | |||
The KML looked good (after extensive edits) in Google Earth but the symbology did not come through in the Google Maps API. |
Latest revision as of 23:44, 13 March 2012
Proposed Tunison bike path
Google Maps
The finished page is here: http://alseageo.com/Maps/tunison.html
Google Earth
The unfinished page is here: http://alseageo.com/Maps/t_tunison.html
Method
- Digitized routes in ArcMap
- Saved as shapefiles in Benton county projection
- Reprojected to Web Mercator and convert to KML with ogr2ogr
- Edited KML files in emacs to make them look good in Google Earth
- Created web page on hostmonster.com hosted site
Note the backwards source and destination
for shp in *.shp do b=`basename $shp .shp` ogr2ogr -f "KML" -t_srs EPSG:900913 $b.kml $shp done
This creates KML files that can be loaded into a Google map (Google Earth or Google Maps).
After all the bother of creating and editing KML files, I ended up taking the linestrings and points out of the KML file and making a Google javascript program instead.
The KML looked good (after extensive edits) in Google Earth but the symbology did not come through in the Google Maps API.