A Cycling & bikes forum. CycleBanter.com

Go Back   Home » CycleBanter.com forum » rec.bicycles » Rides
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Bicycle Rides on Google Earth.



 
 
Thread Tools Display Modes
  #1  
Old May 20th 06, 07:07 AM posted to rec.bicycles.rides
external usenet poster
 
Posts: n/a
Default Bicycle Rides on Google Earth.

Has anyone used Google Earth to describe and share bicycle routes?
Linked it back to web pages?

Apparently you need to subscribe to the $US20pa version to draw routes.

I would like to find out what was possible and the limitations before
committing hours of work to something.

Sadly, FOSS doesn't seem to have delivered a workable solution to roll
your own.
Ads
  #2  
Old May 20th 06, 02:31 PM posted to rec.bicycles.rides
external usenet poster
 
Posts: n/a
Default Bicycle Rides on Google Earth.

"Terry Collins" wrote in message
...
Has anyone used Google Earth to describe and share bicycle routes?
Linked it back to web pages?

Apparently you need to subscribe to the $US20pa version to draw routes.



Why not use Gmaps Pedometer? http://www.gmap-pedometer.com/ I use it all the
time to show people routes locally, or calculate mileage of a possible
route.

--
Warm Regards,

Claire Petersky
http://www.bicyclemeditations.org/
See the books I've set free at: http://bookcrossing.com/referral/Cpetersky


  #3  
Old May 21st 06, 12:52 AM posted to rec.bicycles.rides
external usenet poster
 
Posts: n/a
Default Bicycle Rides on Google Earth.

Claire Petersky wrote:
"Terry Collins" wrote in message
...

Has anyone used Google Earth to describe and share bicycle routes?
Linked it back to web pages?

Apparently you need to subscribe to the $US20pa version to draw routes.




Why not use Gmaps Pedometer? http://www.gmap-pedometer.com/ I use it all the
time to show people routes locally, or calculate mileage of a possible
route.


1) Basically, the interface is crap and it is slow.
2) I want to do multi-day rides with stages
3) I'd like to link to web pages with a description.

  #4  
Old May 21st 06, 03:18 AM posted to rec.bicycles.rides
external usenet poster
 
Posts: n/a
Default Bicycle Rides on Google Earth.

In article

,

Terry Collins wrote:

Claire Petersky wrote:
"Terry Collins" wrote in message

s.com.au ...

Has anyone used Google Earth to describe and share bicycle routes?
Linked it back to web pages?

Apparently you need to subscribe to the $US20pa version to draw
routes.


Why not use Gmaps Pedometer? http://www.gmap-pedometer.com/ I use
it all the time to show people routes locally, or calculate mileage
of a possible route.


1) Basically, the interface is crap and it is slow.


Depends, of course, on what you're looking for. Never having seen it
before, I was able to map out today's 54 mile club ride in about 15
minutes, print it up, and take it with me to give to the other riders.
Seemed pretty quick and simple to me.

2) I want to do multi-day rides with stages


Ummm. Yeah? So?

3) I'd like to link to web pages with a description.


Doesn't seem like that ought to be a problem.
  #5  
Old May 21st 06, 06:23 PM posted to rec.bicycles.rides
external usenet poster
 
Posts: n/a
Default Bicycle Rides on Google Earth.



Terry Collins wrote:
Has anyone used Google Earth to describe and share bicycle routes?
Linked it back to web pages?

Apparently you need to subscribe to the $US20pa version to draw routes.

I would like to find out what was possible and the limitations before
committing hours of work to something.

Sadly, FOSS doesn't seem to have delivered a workable solution to roll
your own.


My brief experience with Google Earth shows that it is not currently an
easy task. Basically you create a Google Earth file, which is importing
a bunch of coordinates. You can then create a fly by view. Best
examples I have seen are the Marin Cyclists and the routes for their
centuries or the Grizzly Peak Cyclists and their file of the route for
their recent century. It would appear that coordinates where imported
from a GPS device or possibly the pedometer file referenced earlier.
Either way, you have to learn how write the file. I don't think it is
necessarily hard, just clumsy at the moment. It does look time
consuming. You could also check out the files from the Tour of
California as reference.

I am not sure if you need the $20 version but it can't hurt since you
can import GPS data.

  #6  
Old May 22nd 06, 07:35 PM posted to rec.bicycles.rides
external usenet poster
 
Posts: n/a
Default Bicycle Rides on Google Earth.

www.MotionBased.com can export routes to Google Earth. You have to
load them into MotionBased from a GPS though. MotionBased is free
except if you want to link to a route externally (i.e., give someone
else a URL to view the route). But you could send people the Google
Earth file to run on their own.

  #7  
Old May 22nd 06, 08:33 PM posted to rec.bicycles.rides
external usenet poster
 
Posts: n/a
Default Bicycle Rides on Google Earth.

Hi terry.

I used google earth to map out my first century route.

The ride was in buffalo.

It started at the university at buffalo in amherst, all the way to
lockport, to somerset, and then we took the lake road (famous for its
long stretch along the lake ontario and the orchard plantations beside
the road), and we went all around north western buffalo (into wilson,
porter, wheatfield, niagara and to the falls) The ride ended up back at
UB.

I used the measure tool in google earth which was very handy and
accurate enough because when we did the actual ride, the mileage was
102.3miles whereas google earth gave us 100 miles.

I would love to use the fly feature etc in the advanced versions of
google earth. Mapping routes could be easier in the pro version. At
times I was tempted to steal it off the internet , but I realised how
much Google emphasizes on the security of its product. Basically, if
you're willing to spend some time with the basic version, you can map
your route using that and any image editor like photoshop if you wish.


What I love using google earth more for is as a supplement to the bike
route maps I have. I love to see a satellite images of what I will be
riding. It helps me greatly in getting a mental imagery, understanding
and appreciation of routes. At times, it has helped me even from losing
my way.

A disadvantage of google basic is that if you're looking to ride a bike
in some other specific country, say somewhere in the middle-east like
the United Arab Emirates or Qatar, known for high temperatures,
quality, winding roads and a favorite training spot for famous
triathletes, Google earth might not be able to show you anything at
all, leave alone roads. All I see is a mess of pixels. I don't quite
know if others experience the same thing. Try checking, please. These
countries are very developed as far as transportation infrastructure is
concerned.

Thats about what I can tell you about Google Earth. Its a promising
product for now.

Thanks

Ron

  #8  
Old May 23rd 06, 12:02 AM posted to rec.bicycles.rides
external usenet poster
 
Posts: n/a
Default Bicycle Rides on Google Earth.

this the the Montauk metric century from Sunday off of gmap-pedometer:
(caution - 24 KB of text)

save it off as a .gpx file and open it in google earth.


?xml version="1.0"?
gpx version="1.1"
creator="GMapToGPX 4.9 - http://www.elsewhere.org/GMapToGPX/"
xmlns="http://www.topografix.com/GPX/1/1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.topografix.com/GPX/1/1
http://www.topografix.com/GPX/1/1/gpx.xsd"
rte
nameGmaps Pedometer Route/name
cmtPermalink: ![CDATA[
Permalink temporarily unavailable.
]]
/cmt
rtept lat="40.79833" lon="-72.86433"
nameStart/name
/rtept
rtept lat="40.80104" lon="-72.84049"
nameTurn 1/name
/rtept
rtept lat="40.80339" lon="-72.84051"
nameTurn 2/name
/rtept
rtept lat="40.8052" lon="-72.83881"
nameTurn 3/name
/rtept
rtept lat="40.80617" lon="-72.8374"
nameTurn 4/name
/rtept
rtept lat="40.80607" lon="-72.83568"
nameTurn 5/name
/rtept
rtept lat="40.80625" lon="-72.83336"
nameTurn 6/name
/rtept
rtept lat="40.8078" lon="-72.82839"
nameTurn 7/name
/rtept
rtept lat="40.80791" lon="-72.82497"
nameTurn 8/name
/rtept
rtept lat="40.80698" lon="-72.82034"
nameTurn 9/name
/rtept
rtept lat="40.80437" lon="-72.81435"
nameTurn 10/name
/rtept
rtept lat="40.80432" lon="-72.80277"
nameTurn 11/name
/rtept
rtept lat="40.8065" lon="-72.78835"
nameTurn 12/name
/rtept
rtept lat="40.8089" lon="-72.77717"
nameTurn 13/name
/rtept
rtept lat="40.81143" lon="-72.76785"
nameTurn 14/name
/rtept
rtept lat="40.81387" lon="-72.757"
nameTurn 15/name
/rtept
rtept lat="40.81518" lon="-72.75629"
nameTurn 16/name
/rtept
rtept lat="40.81983" lon="-72.75152"
nameTurn 17/name
/rtept
rtept lat="40.82496" lon="-72.74522"
nameTurn 18/name
/rtept
rtept lat="40.82619" lon="-72.74275"
nameTurn 19/name
/rtept
rtept lat="40.82673" lon="-72.74056"
nameTurn 20/name
/rtept
rtept lat="40.82684" lon="-72.73848"
nameTurn 21/name
/rtept
rtept lat="40.82548" lon="-72.72908"
nameTurn 22/name
/rtept
rtept lat="40.82545" lon="-72.72485"
nameTurn 23/name
/rtept
rtept lat="40.82451" lon="-72.71728"
nameTurn 24/name
/rtept
rtept lat="40.82233" lon="-72.71554"
nameTurn 25/name
/rtept
rtept lat="40.82014" lon="-72.71303"
nameTurn 26/name
/rtept
rtept lat="40.81811" lon="-72.712"
nameTurn 27/name
/rtept
rtept lat="40.81541" lon="-72.71163"
nameTurn 28/name
/rtept
rtept lat="40.81395" lon="-72.71209"
nameTurn 29/name
/rtept
rtept lat="40.81283" lon="-72.71123"
nameTurn 30/name
/rtept
rtept lat="40.80828" lon="-72.70951"
nameTurn 31/name
/rtept
rtept lat="40.80762" lon="-72.70848"
nameTurn 32/name
/rtept
rtept lat="40.80801" lon="-72.69958"
nameTurn 33/name
/rtept
rtept lat="40.80857" lon="-72.69561"
nameTurn 34/name
/rtept
rtept lat="40.80797" lon="-72.68498"
nameTurn 35/name
/rtept
rtept lat="40.80844" lon="-72.68005"
nameTurn 36/name
/rtept
rtept lat="40.80856" lon="-72.67026"
nameTurn 37/name
/rtept
rtept lat="40.81324" lon="-72.66994"
nameTurn 38/name
/rtept
rtept lat="40.81371" lon="-72.65567"
nameTurn 39/name
/rtept
rtept lat="40.81358" lon="-72.65224"
nameTurn 40/name
/rtept
rtept lat="40.81135" lon="-72.64681"
nameTurn 41/name
/rtept
rtept lat="40.80866" lon="-72.64739"
nameTurn 42/name
/rtept
rtept lat="40.80801" lon="-72.64707"
nameTurn 43/name
/rtept
rtept lat="40.80997" lon="-72.64265"
nameTurn 44/name
/rtept
rtept lat="40.81004" lon="-72.64162"
nameTurn 45/name
/rtept
rtept lat="40.80763" lon="-72.64033"
nameTurn 46/name
/rtept
rtept lat="40.80711" lon="-72.64001"
nameTurn 47/name
/rtept
rtept lat="40.80445" lon="-72.63688"
nameTurn 48/name
/rtept
rtept lat="40.80619" lon="-72.63467"
nameTurn 49/name
/rtept
rtept lat="40.80323" lon="-72.63055"
nameTurn 50/name
/rtept
rtept lat="40.79993" lon="-72.62724"
nameTurn 51/name
/rtept
rtept lat="40.80094" lon="-72.6225"
nameTurn 52/name
/rtept
rtept lat="40.80146" lon="-72.621"
nameTurn 53/name
/rtept
rtept lat="40.80196" lon="-72.61808"
nameTurn 54/name
/rtept
rtept lat="40.80367" lon="-72.61364"
nameTurn 55/name
/rtept
rtept lat="40.80531" lon="-72.60851"
nameTurn 56/name
/rtept
rtept lat="40.80786" lon="-72.59821"
nameTurn 57/name
/rtept
rtept lat="40.81033" lon="-72.59186"
nameTurn 58/name
/rtept
rtept lat="40.81325" lon="-72.58276"
nameTurn 59/name
/rtept
rtept lat="40.81536" lon="-72.57293"
nameTurn 60/name
/rtept
rtept lat="40.81702" lon="-72.5677"
nameTurn 61/name
/rtept
rtept lat="40.81897" lon="-72.56049"
nameTurn 62/name
/rtept
rtept lat="40.82173" lon="-72.55135"
nameTurn 63/name
/rtept
rtept lat="40.82352" lon="-72.54281"
nameTurn 64/name
/rtept
rtept lat="40.82501" lon="-72.54036"
nameTurn 65/name
/rtept
rtept lat="40.82624" lon="-72.53306"
nameTurn 66/name
/rtept
rtept lat="40.82793" lon="-72.52963"
nameTurn 67/name
/rtept
rtept lat="40.8292" lon="-72.52439"
nameTurn 68/name
/rtept
rtept lat="40.83196" lon="-72.51307"
nameTurn 69/name
/rtept
rtept lat="40.83511" lon="-72.5068"
nameTurn 70/name
/rtept
rtept lat="40.83777" lon="-72.49701"
nameTurn 71/name
/rtept
rtept lat="40.85072" lon="-72.50495"
nameTurn 72/name
/rtept
rtept lat="40.85141" lon="-72.5056"
nameTurn 73/name
/rtept
rtept lat="40.85459" lon="-72.50478"
nameTurn 74/name
/rtept
rtept lat="40.85647" lon="-72.505"
nameTurn 75/name
/rtept
rtept lat="40.85637" lon="-72.50349"
nameTurn 76/name
/rtept
rtept lat="40.86199" lon="-72.50105"
nameTurn 77/name
/rtept
rtept lat="40.86767" lon="-72.49629"
nameTurn 78/name
/rtept
rtept lat="40.87182" lon="-72.49551"
nameTurn 79/name
/rtept
rtept lat="40.87283" lon="-72.49598"
nameTurn 80/name
/rtept
rtept lat="40.87331" lon="-72.4971"
nameTurn 81/name
/rtept
rtept lat="40.87399" lon="-72.50204"
nameTurn 82/name
/rtept
rtept lat="40.87649" lon="-72.50199"
nameTurn 83/name
/rtept
rtept lat="40.87666" lon="-72.50131"
nameTurn 84/name
/rtept
rtept lat="40.88061" lon="-72.50362"
nameTurn 85/name
/rtept
rtept lat="40.88263" lon="-72.50375"
nameTurn 86/name
/rtept
rtept lat="40.88383" lon="-72.50444"
nameTurn 87/name
/rtept
rtept lat="40.8848" lon="-72.50178"
nameTurn 88/name
/rtept
rtept lat="40.88486" lon="-72.4989"
nameTurn 89/name
/rtept
rtept lat="40.88353" lon="-72.49495"
nameTurn 90/name
/rtept
rtept lat="40.88376" lon="-72.48457"
nameTurn 91/name
/rtept
rtept lat="40.88535" lon="-72.48272"
nameTurn 92/name
/rtept
rtept lat="40.88493" lon="-72.47496"
nameTurn 93/name
/rtept
rtept lat="40.88535" lon="-72.47298"
nameTurn 94/name
/rtept
rtept lat="40.88519" lon="-72.47024"
nameTurn 95/name
/rtept
rtept lat="40.88584" lon="-72.46775"
nameTurn 96/name
/rtept
rtept lat="40.88581" lon="-72.46564"
nameTurn 97/name
/rtept
rtept lat="40.88431" lon="-72.4632"
nameTurn 98/name
/rtept
rtept lat="40.88353" lon="-72.45908"
nameTurn 99/name
/rtept
rtept lat="40.88509" lon="-72.45114"
nameTurn 100/name
/rtept
rtept lat="40.88577" lon="-72.44616"
nameTurn 101/name
/rtept
rtept lat="40.88555" lon="-72.43389"
nameTurn 102/name
/rtept
rtept lat="40.88457" lon="-72.42522"
nameTurn 103/name
/rtept
rtept lat="40.88366" lon="-72.42191"
nameTurn 104/name
/rtept
rtept lat="40.88473" lon="-72.40891"
nameTurn 105/name
/rtept
rtept lat="40.87542" lon="-72.40887"
nameTurn 106/name
/rtept
rtept lat="40.87013" lon="-72.41063"
nameTurn 107/name
/rtept
rtept lat="40.86329" lon="-72.4114"
nameTurn 108/name
/rtept
rtept lat="40.86413" lon="-72.40835"
nameTurn 109/name
/rtept
rtept lat="40.86478" lon="-72.40702"
nameTurn 110/name
/rtept
rtept lat="40.86682" lon="-72.39981"
nameTurn 111/name
/rtept
rtept lat="40.86729" lon="-72.39895"
nameTurn 112/name
/rtept
rtept lat="40.86765" lon="-72.39779"
nameTurn 113/name
/rtept
rtept lat="40.86849" lon="-72.39775"
nameTurn 114/name
/rtept
rtept lat="40.8684" lon="-72.39485"
nameTurn 115/name
/rtept
rtept lat="40.86892" lon="-72.39348"
nameTurn 116/name
/rtept
rtept lat="40.86992" lon="-72.39082"
nameTurn 117/name
/rtept
rtept lat="40.8724" lon="-72.39043"
nameTurn 118/name
/rtept
rtept lat="40.87305" lon="-72.38898"
nameTurn 119/name
/rtept
rtept lat="40.87336" lon="-72.38749"
nameTurn 120/name
/rtept
rtept lat="40.87348" lon="-72.38443"
nameTurn 121/name
/rtept
rtept lat="40.8751" lon="-72.37921"
nameTurn 122/name
/rtept
rtept lat="40.87675" lon="-72.3722"
nameTurn 123/name
/rtept
rtept lat="40.87769" lon="-72.37117"
nameTurn 124/name
/rtept
rtept lat="40.88133" lon="-72.37522"
nameTurn 125/name
/rtept
rtept lat="40.88311" lon="-72.37825"
nameTurn 126/name
/rtept
rtept lat="40.88354" lon="-72.3784"
nameTurn 127/name
/rtept
rtept lat="40.88495" lon="-72.37585"
nameTurn 128/name
/rtept
rtept lat="40.88654" lon="-72.36825"
nameTurn 129/name
/rtept
rtept lat="40.88735" lon="-72.3623"
nameTurn 130/name
/rtept
rtept lat="40.88827" lon="-72.35932"
nameTurn 131/name
/rtept
rtept lat="40.89093" lon="-72.35981"
nameTurn 132/name
/rtept
rtept lat="40.89278" lon="-72.36003"
nameTurn 133/name
/rtept
rtept lat="40.89463" lon="-72.35962"
nameTurn 134/name
/rtept
rtept lat="40.89552" lon="-72.35893"
nameTurn 135/name
/rtept
rtept lat="40.89637" lon="-72.35775"
nameTurn 136/name
/rtept
rtept lat="40.89765" lon="-72.35464"
nameTurn 137/name
/rtept
rtept lat="40.89933" lon="-72.35456"
nameTurn 138/name
/rtept
rtept lat="40.90113" lon="-72.35492"
nameTurn 139/name
/rtept
rtept lat="40.90321" lon="-72.35599"
nameTurn 140/name
/rtept
rtept lat="40.90491" lon="-72.35752"
nameTurn 141/name
/rtept
rtept lat="40.90798" lon="-72.35612"
nameTurn 142/name
/rtept
rtept lat="40.90953" lon="-72.35481"
nameTurn 143/name
/rtept
rtept lat="40.91159" lon="-72.35065"
nameTurn 144/name
/rtept
rtept lat="40.91234" lon="-72.34934"
nameTurn 145/name
/rtept
rtept lat="40.91336" lon="-72.3484"
nameTurn 146/name
/rtept
rtept lat="40.91597" lon="-72.3466"
nameTurn 147/name
/rtept
rtept lat="40.91887" lon="-72.34359"
nameTurn 148/name
/rtept
rtept lat="40.92161" lon="-72.33911"
nameTurn 149/name
/rtept
rtept lat="40.92371" lon="-72.33638"
nameTurn 150/name
/rtept
rtept lat="40.92319" lon="-72.33304"
nameTurn 151/name
/rtept
rtept lat="40.921" lon="-72.32874"
nameTurn 152/name
/rtept
rtept lat="40.91949" lon="-72.32638"
nameTurn 153/name
/rtept
rtept lat="40.91735" lon="-72.32381"
nameTurn 154/name
/rtept
rtept lat="40.91472" lon="-72.31999"
nameTurn 155/name
/rtept
rtept lat="40.91239" lon="-72.32087"
nameTurn 156/name
/rtept
rtept lat="40.91104" lon="-72.31804"
nameTurn 157/name
/rtept
rtept lat="40.91114" lon="-72.31505"
nameTurn 158/name
/rtept
rtept lat="40.91171" lon="-72.31226"
nameTurn 159/name
/rtept
rtept lat="40.91091" lon="-72.30671"
nameTurn 160/name
/rtept
rtept lat="40.91114" lon="-72.30379"
nameTurn 161/name
/rtept
rtept lat="40.91187" lon="-72.3036"
nameTurn 162/name
/rtept
rtept lat="40.91602" lon="-72.30173"
nameTurn 163/name
/rtept
rtept lat="40.92025" lon="-72.30051"
nameTurn 164/name
/rtept
rtept lat="40.92136" lon="-72.30053"
nameTurn 165/name
/rtept
rtept lat="40.92118" lon="-72.29887"
nameTurn 166/name
/rtept
rtept lat="40.91891" lon="-72.29209"
nameTurn 167/name
/rtept
rtept lat="40.91798" lon="-72.28991"
nameTurn 168/name
/rtept
rtept lat="40.91763" lon="-72.28501"
nameTurn 169/name
/rtept
rtept lat="40.91651" lon="-72.28117"
nameTurn 170/name
/rtept
rtept lat="40.91719" lon="-72.28038"
nameTurn 171/name
/rtept
rtept lat="40.91808" lon="-72.27926"
nameTurn 172/name
/rtept
rtept lat="40.91883" lon="-72.279"
nameTurn 173/name
/rtept
rtept lat="40.91755" lon="-72.27658"
nameTurn 174/name
/rtept
rtept lat="40.91905" lon="-72.27514"
nameTurn 175/name
/rtept
rtept lat="40.92113" lon="-72.27156"
nameTurn 176/name
/rtept
rtept lat="40.92246" lon="-72.26774"
nameTurn 177/name
/rtept
rtept lat="40.92376" lon="-72.26317"
nameTurn 178/name
/rtept
rtept lat="40.925" lon="-72.25787"
nameTurn 179/name
/rtept
rtept lat="40.9256" lon="-72.25559"
nameTurn 180/name
/rtept
rtept lat="40.928" lon="-72.24965"
nameTurn 181/name
/rtept
rtept lat="40.93176" lon="-72.25296"
nameTurn 182/name
/rtept
rtept lat="40.9375" lon="-72.24169"
nameTurn 183/name
/rtept
rtept lat="40.93797" lon="-72.2422"
nameTurn 184/name
/rtept
rtept lat="40.93933" lon="-72.2421"
nameTurn 185/name
/rtept
rtept lat="40.9439" lon="-72.2413"
nameTurn 186/name
/rtept
rtept lat="40.94567" lon="-72.2403"
nameTurn 187/name
/rtept
rtept lat="40.94812" lon="-72.23976"
nameTurn 188/name
/rtept
rtept lat="40.94984" lon="-72.24038"
nameTurn 189/name
/rtept
rtept lat="40.95264" lon="-72.23296"
nameTurn 190/name
/rtept
rtept lat="40.95301" lon="-72.2313"
nameTurn 191/name
/rtept
rtept lat="40.95309" lon="-72.22972"
nameTurn 192/name
/rtept
rtept lat="40.95277" lon="-72.22772"
nameTurn 193/name
/rtept
rtept lat="40.95136" lon="-72.22268"
nameTurn 194/name
/rtept
rtept lat="40.95078" lon="-72.22045"
nameTurn 195/name
/rtept
rtept lat="40.95078" lon="-72.21843"
nameTurn 196/name
/rtept
rtept lat="40.95164" lon="-72.21528"
nameTurn 197/name
/rtept
rtept lat="40.95428" lon="-72.20862"
nameTurn 198/name
/rtept
rtept lat="40.9545" lon="-72.20659"
nameTurn 199/name
/rtept
rtept lat="40.95439" lon="-72.20281"
nameTurn 200/name
/rtept
rtept lat="40.95296" lon="-72.19414"
nameTurn 201/name
/rtept
rtept lat="40.9529" lon="-72.194"
nameTurn 202/name
/rtept
rtept lat="40.95286" lon="-72.1937"
nameTurn 203/name
/rtept
rtept lat="40.95692" lon="-72.19133"
nameTurn 204/name
/rtept
rtept lat="40.95762" lon="-72.19081"
nameTurn 205/name
/rtept
rtept lat="40.95518" lon="-72.17966"
nameTurn 206/name
/rtept
rtept lat="40.95515" lon="-72.17513"
nameTurn 207/name
/rtept
rtept lat="40.9586" lon="-72.16794"
nameTurn 208/name
/rtept
rtept lat="40.96178" lon="-72.15957"
nameTurn 209/name
/rtept
rtept lat="40.96565" lon="-72.1508"
nameTurn 210/name
/rtept
rtept lat="40.96651" lon="-72.14867"
nameTurn 211/name
/rtept
rtept lat="40.9694" lon="-72.14605"
nameTurn 212/name
/rtept
rtept lat="40.97082" lon="-72.14219"
nameTurn 213/name
/rtept
rtept lat="40.96692" lon="-72.13972"
nameTurn 214/name
/rtept
rtept lat="40.96857" lon="-72.13472"
nameTurn 215/name
/rtept
rtept lat="40.9705" lon="-72.13127"
nameTurn 216/name
/rtept
rtept lat="40.97262" lon="-72.12668"
nameTurn 217/name
/rtept
rtept lat="40.97703" lon="-72.11711"
nameTurn 218/name
/rtept
rtept lat="40.97826" lon="-72.11468"
nameTurn 219/name
/rtept
rtept lat="40.98043" lon="-72.10777"
nameTurn 220/name
/rtept
rtept lat="40.98291" lon="-72.09923"
nameTurn 221/name
/rtept
rtept lat="40.98981" lon="-72.07529"
nameTurn 222/name
/rtept
rtept lat="40.99444" lon="-72.05954"
nameTurn 223/name
/rtept
rtept lat="40.99684" lon="-72.05018"
nameTurn 224/name
/rtept
rtept lat="40.998" lon="-72.04421"
nameTurn 225/name
/rtept
rtept lat="41.00325" lon="-72.02847"
nameTurn 226/name
/rtept
rtept lat="41.00412" lon="-72.02486"
nameTurn 227/name
/rtept
rtept lat="41.00568" lon="-72.02156"
nameTurn 228/name
/rtept
rtept lat="41.00801" lon="-72.01357"
nameTurn 229/name
/rtept
rtept lat="41.01008" lon="-72.00915"
nameTurn 230/name
/rtept
rtept lat="41.01248" lon="-72.00259"
nameTurn 231/name
/rtept
rtept lat="41.01377" lon="-71.99817"
nameTurn 232/name
/rtept
rtept lat="41.01607" lon="-71.99323"
nameTurn 233/name
/rtept
rtept lat="41.01776" lon="-71.9874"
nameTurn 234/name
/rtept
rtept lat="41.02229" lon="-71.97405"
nameTurn 235/name
/rtept
rtept lat="41.02621" lon="-71.96607"
nameTurn 236/name
/rtept
rtept lat="41.02676" lon="-71.96276"
nameTurn 237/name
/rtept
rtept lat="41.03087" lon="-71.95384"
nameTurn 238/name
/rtept
rtept lat="41.0319" lon="-71.94899"
nameTurn 239/name
/rtept
rtept lat="41.03288" lon="-71.94708"
nameTurn 240/name
/rtept
rtept lat="41.035" lon="-71.94364"
nameTurn 241/name
/rtept
rtept lat="41.0353" lon="-71.94433"
nameTurn 242/name
/rtept
rtept lat="41.03963" lon="-71.9456"
nameTurn 243/name
/rtept
rtept lat="41.04293" lon="-71.94768"
nameTurn 244/name
/rtept
rtept lat="41.04433" lon="-71.95025"
nameTurn 245/name
/rtept
rtept lat="41.04531" lon="-71.95083"
nameTurn 246/name
/rtept
rtept lat="41.04542" lon="-71.95409"
nameTurn 247/name
/rtept
rtept lat="41.04298" lon="-71.95753"
nameTurn 248/name
/rtept
rtept lat="41.04063" lon="-71.96165"
nameTurn 249/name
/rtept
rtept lat="41.03985" lon="-71.95999"
nameTurn 250/name
/rtept
/rte
/gpx

  #9  
Old May 23rd 06, 11:54 AM posted to rec.bicycles.rides
external usenet poster
 
Posts: n/a
Default Bicycle Rides on Google Earth.

If you want, check out www.geobike.com. Click on "RAGBRAI", "RAGBRAI
XXXIV", and "Google Earth Maps". Google Earth is a *great* tool for
sharing route data. In this example, I not only can show route data,
mileage information and waypoints, I can also use image data to show
weather radar and other information. The other thing to consider about
GE is that a user also has access to all the other data/information from
Google: parks, hotels, attractions, etc...

I've found GE to be the easiest tool to share mapping information. I
don't have to worry about hosting a map server, the GE files can be
easily emailed or made available on a web site, and the cost is $0. The
GE maps have been real popular. The riders can learn about the route,
the terrain option allows them to explore all facets of a route. You
can actually "play" a route and let GE fly you along the route.

The key thing about GE is that it is based on Lat and Lon data. If you
have a GPS, you can easily obtain this data. If your GPS is a Garmin,
their Mapsource tool can directly generate a GE file. If you don't have
a Garmin, there are low cost tools that can generate a GE file. If you
want, you can also author a GE file in Windows Notepad. The programming
syntax is *extremely* easy. Study the above mentioned file or the file
that was posted in this thread.

Cheers!

Rich

Terry Collins wrote:
Has anyone used Google Earth to describe and share bicycle routes?
Linked it back to web pages?

Apparently you need to subscribe to the $US20pa version to draw routes.

I would like to find out what was possible and the limitations before
committing hours of work to something.

Sadly, FOSS doesn't seem to have delivered a workable solution to roll
your own.

  #10  
Old May 30th 06, 03:15 AM posted to rec.bicycles.rides
external usenet poster
 
Posts: n/a
Default Bicycle Rides on Google Earth.

wrote:
this the the Montauk metric century from Sunday off of gmap-pedometer:
(caution - 24 KB of text)

save it off as a .gpx file and open it in google earth.


Thanks, much appreciated.
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Bicycle is king of the road as gas costs rise cfsmtb Australia 14 May 9th 06 12:35 AM
COLORADO BANNING BIG GROUP RIDES FW: FROM BICYCLE COLORADO Colorado Bicycler Rides 20 December 27th 05 09:53 PM
police say it is illegal to ride bicycle on the street [email protected] General 16 April 18th 05 08:20 PM
Does public health care pay for your head injuries? John Doe UK 187 November 30th 04 02:51 PM
Billy removes support from Peewee (seeXXXVII for a Laugh) Di Social Issues 3 October 29th 04 05:31 AM


All times are GMT +1. The time now is 08:59 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 CycleBanter.com.
The comments are property of their posters.