Please contact us if you'd like to present at the March or April meetup.
Listen to Part 1 of this event[audio:BarKode-Episode2-WebMappingPartTwo.mp3]
Listen to Part 2 of this event[audio:BarKode-Episode3-WebMappingPartTwo.mp3]
Subscribe to the podcast of the event
Web Mapping Part Two: Google Maps and Beyond
We'll discuss best practices, our favorite mashups, and what makes the good ones so good. We'd also like to see if anyone in the group has any experience with the Mapstraction library.
Google Maps Wrap-up
Last month we talked a little bit about web mapping in general and ran through a Google Maps tutorial. All of the materials from last month's meetup are available on our website, including a podcast of the presentation.
- Web Mapping Part 1
- theMechanism neogeography demos + tutorials
- schiller labs GIS Day 2006 materials
- Donna Lichaw's post "Web 2.0, Maps, and You! LOL"
Any questions about developing Google Maps? Any observations?
Other Mapping APIs
I remember that Marco was very concerned about the fact that Google is a corporation last month, but OpenLayers is an open source solution.
I briefly worked with MapQuest in 2006, prior to driving directions in Google Maps, but I found it kind of a pain and would stick with Google—their API is faster, cuter, and easier
When initially working with the the MapQuest OpenAPI, I had a lot of difficulty getting the map to render correctly. The culprit turned out to be the DOCTYPE directive! Remove it if you want your map to display at all in Firefox and correctly in IE. Not sure if this is still true.
What are the best practices when doing a mashup? Is it using abstraction layers? What makes a good UI? What are people's favorite mashups and why? What makes a good one so good?
Google has a New Year's Resolution to help produce more usable maps.
Vincent Lim sent this one: http://www.onnyturf.com/subway/. Custom tiles. Stemless markers.
They also released an open source interaction library called Modest Maps for displaying tile-based maps like Google's in Flash.
Mapstraction—Client-side abstraction layer
Published by: jeffreybarke in The Programming Mechanism