I've updated the site to use the Google Maps V3 APIs.

For what it's worth [not much -ed], I've updated the mapping code (seen on itinerary pages and selected essays) to use the Google Maps V3 APIs. I won't miss managing different API keys for each URI path.

If you see any weirdness, let me know.

[Update: 15 Dec] Using the “bounds_changed” callback to manage adding photos to the map was exhibiting a nasty performance issue. The callback occurs dozens of times in a fraction of a second as the map is moving; calling the AJAX function to retreive image data that frequently was just silly. I've now added a timer and avoid doing the AJAX call until there's been ¼s of stability in the map.

I like that better, but again, if you see any weirdness…

There are no comments on this essay.
Add a comment or subscribe to (existing and future) comments on this essay.
Name:
Email*:
 *Please provide your real email address; it will not be displayed as part of the comment.
Homepage:
Comment**:
 **The following markup may be used in the body of the comment: a, abbr, b, br, code, em, i, p, pre, strong, and var. You can also use character entities. Any other markup will be discarded, including all attributes (except href on a). Your tag soup will be sanitized...