The nice programmers at Google have done some clever things with dynamic HTML and big fast servers with mountains o' maps and aerial imagery. Recently Google unveiled an interface to let other people create and display zoomable scrollable maps. My initial crude efforts along these lines are visible at — the locations of mileposts 0 through 13 along Rock Creek Trail near where I live. (Click on a point to see its identity; drag the map around or click the up/down/left/right arrows in the upper left corner to pan the view; click or drag the vertical +/- slider to expand or contract the scale; click the Map/Satellite/Hybrid buttons to see alternative images and overlays.)

Much remains to be done, but it's starting to get slightly cute now, at least to the proud eyes of the programmer who gave birth to it. Really, all I did was adapt the sample scripts that Google provided, and then pour in latitudes and longitudes from one of my old coordinate collections. But I had to (re)learn some Javascript and XML to get it working, and that was fun.

What's next? On the data side I see that some of my GPS coordinates are off by tens of meters and need to be corrected. Maybe some day I'll put in better captions and plot other points along Paint Branch Trail, Northwest Branch, Northeast Branch, and my other favorite jogging paths. It might also be cute to draw lines along the trail routes, add sidebars with links to supplemental information, and so forth. I have an album of photos of the mileposts along the trails, and perhaps it would be neat to make those pop up too.

A higher-level question, however, remains: can (or should) this sort of thing be Wiki-fied? Perhaps people could add new points and commentary to the waypoints.xml data file, for instance, and edit existing markers. The "Katrina Information Map" site does this in a spiffy fashion.

How might that be implemented most easily here? What sorts of data would people want to share? Is the programming worth the trouble? I dunno ...

(for the Google Maps API see; cf. CoordinateCollection (19 May 2002), RockCreekTrail (31 May 2002), MarathonCoordinates (3 Oct 2002), MarineCorpsOrdnance (1 Nov 2002), AnacostiaTributaries (28 Jan 2003), EdwardsFolly (13 Apr 2003), RileysRumble (27 Jul 2003), ...)

TopicProgramming - TopicRunning - TopicPersonalHistory - 2005-09-11

Comment 25 Sep 2005^ at 15:55 UTC

Yesterday morning I carried an antique GPS receiver and took waypoints
every 1-2 minutes (100-300m, roughly) on the double-back double-loop
course of the Lake Needwood 10k cross-country MCRRC race ... see for
the ugly connect-the-dots result. My low sampling rate combined with
other GPS errors makes for an impressionistic scribble that a
two-year-old might be proud of! But at least now I've figured out how
to draw lines on a Google map, so if anybody has some good waypoints
feel free to send them to me and I'll try to help you plot them ...

And BTW, here's an image of 42:21:00 N 71:04:41 W = my GPS measurement
on 20 June 2002 of the endpoint of the Boston Marathon, as painted on
the street just north of the Boston Public Library:'00%22+N+71%C2%B004'41%22+W&spn=0.003947,0.005942&t=h&hl=en

^z — !!!!Comment 1 Oct 2005^ at 02:17 UTC Points for W&OD (Washington and Old Dominion) Trail have now been added ... mileposts 0-25, with half-mile-markers 18.5-24.5 also included ... ^z
— !!!!Comment 3 Oct 2005^ at 23:59 UTC See for GPS coordinates collected by ^z = MarkZimmermann in Rock Creek Park during a jog on 2 October 2005 with Ken Swab ...
— !!!!Comment 4 Oct 2005^ at 00:01 UTC The page has been superseded now by a much more comprehensive coordinate collection at ...
— !!!!Comment 12 Nov 2005^ at 14:01 UTC For a good time see — a Google Map page showing locations of 10 of the DC Boundary Stones which I visited yesterday. I also took photos of them which I'll be happy to send to anybody with who is foolish enough to feign interest ... for decimalized latitude & longitude see (the XML which generates the aforementioned Google Map) ... To read about DC Boundary Stones see and ... and if you want to undertake a science project — computing the errors in the stone locations (including both my GPS errors and the errors made in the original placement) please let me know ... tnx! ^z
— !!!!Comment 27 Nov 2005^ at 16:50 UTC Mike Pegg of "Google Maps Mania" posted some kind remarks on his blog about my DcBoundaryStones project — see "Sunday Google Maps Assortment" ...
— !!!!Comment 28 Nov 2005^ at 03:18 UTC Four more stones located today — SW9, WEST, NW1, and NW2 — see as updated for their locations, and for images ... ^z — !!Comment 23 Dec 2005 See for index to my Google Map experiments ... ^z
— !!!!Comment 11 Apr 2006^ at 01:55 UTC For excellent information on the stones see Mark Kennedy's site .
(correlates: AddictiveTrope, DcBoundaryStones, September2005JogLog, ...)