Revise geomarkers

[mizmay]

Replaces the original geomarkers.json, which looked to be a large collection of intersections in Seattle, named and labeled as such, with points near 5 local Seattle landmarks. Other changes:

• label is set to Tour Stop 1 to Tour Stop 5
• name is a descriptor such as "In front of Seattle Art Museum"

I used these conventions because:

1. For demo purposes, it makes sense to set the name and label differently
2. To distinguish the geo $type from derived a derived lat lon you might get by geocoding an address or looking up a fsq foursquare ID (or aggregating to an hthree hexbin)
3. Rounded coordinates to 5 decimal places (here's why)

Next steps:

• Simpler base map without animation or extruded buildings / forced isometric perspective
• Change marker type from circle to extruded point

Future horizons (possible if desired):

• Simple sandbox / implementation of hosted custom tiles containing foursquare data, address points, hexbins that would eliminate the need for external back-end services to define how "locations" in the lexicon can correspond to mapped locations (this would go the rest of the way toward resolving Create new geodata #21 and enabling the core functionality I believe this app is meant to represent)