130 likes | 380 Views
Google/Where 2.0 report June 23, 2005 B. McLeod, GeoConnections. Google Developer Day – June 12, Googleplex, Mountain View, CA. “Life inside the Googleplex” www.time.com. New at Google….
E N D
Google/Where 2.0 reportJune 23, 2005B. McLeod, GeoConnections
Google Developer Day – June 12, Googleplex, Mountain View, CA
New at Google… • Positioning of Google Earth (new release) as “the geobrowser” for the Web with KML as the “markup” language • Street level geocoding addition to Google Maps API (limit 50,000 address/day) includes Canada, US, France, Italy, Germany, Spain and Japan) • New satellite data • - four times more land mass covered in hi-res • New focus on building the 3D world building models (Sketchup) and local content
Google statistics • 100,000,000 downloads of Google Earth • 1/3 of world’s population can now “see their neighbourhood” • 12 new employees/day • 1400 job openings
Where 2.0™ : O’Reilly, June 13-14, San Jose, CA • HIGHLIGHTS… • Key geo-portal providers • - Google (Maps/Earth), Microsoft (Virtual Earth/windows live local), Yahoo (Yahoo local), Mapquest • “Mash-ups” combine data with Map content • - estimate of 10,000 Google Map mash-up applications • - e.g. http://www.beerhunter.ca/OttawaArea
Where 2.0 highlights… • “Web 2.0” is the “read-write” Web Local focus – major new content focus simple geotagging (address, postal/zip code, etc.) allows anyone to publish geodata - weather, business, social networking information, 3D building models from many sources - high-res satellite (Google - new imagery, Microsoft – bird’s eye) - syndication feeds, general public - minimal metadata - issues: authoritativeness, privacy, licensing/IP rights - Wikipedia model for Geodata (e.g. Open street map)
Where 2.0 Highlights – Open Source GEO - Open Source GIS will continue to expand feature offerings and continues to mature - OSGeo foundation solidifies Geo-based Open Source
Where 2.0 highlight - STANDARDS • - KML and GeoRSS frequently mentioned in presentations - GeoRSS can allow for syndication feeds for Geo content - Suggested gap for tile-based Web mapping service • Simple = uptake (10,000 Mash-ups) • Raise the bar - Typical OGC standard “learning curve” is two-three months (e.g. WFS/GML) - Typical Google API “learning curve” is two-three days Process - defacto standard (e.g. KML) - “open” standards development (e.g. GeoRSS)
SO WHAT??? - How does the emergence of consumer-oriented Geo impact the CGDI? - Recommendations for GeoConnections?