CARTOGRAPHIONS L’AVENIR EN LIGNE MAPPING THE FUTURE TOGETHER ONLINE Mass-market Geo: Emerging trends and standards Sept. 12, 2006 B.McLeod, CCRS/GeoConnections
Jan 19, 2016
CARTOGRAPHIONS L’AVENIR EN LIGNE
MAPPING THE FUTURE TOGETHER ONLINE
Mass-market Geo: Emergingtrends and standards
Sept. 12, 2006B.McLeod, CCRS/GeoConnections
Google Developer Day – June 12, Googleplex, Mountain View, CA
“Life inside the Googleplex” www.time.com
Systems Engineering – Google road map
“100 foot” rule
Opening session: Sergey Brin, Larry Page, Eric Schmidt
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 (Sketchup modeling tool) and local content
KML for Google maps
Enterprise version licensing model
Google statistics
100,000,000 downloads of Google Earth
30,000 users of API
1/3 of world’s population can now “see their neighbourhood”
12 new employees/day
1400 job openings
Google data infrastructure (“close” to your network)
Google-container
10m box
5000 Opteron processors
3.5 petabytes disk
Transportable by tractor-trailer
This shipping container is a prototype data center. Google can “park” containers close to major Internet peering points/hubs
Google server farms
2003: 1
2005: 64 (est)
2007: 300 (est)
Where 2.0™ Conference: June 13-14, San Jose, CAO’Reilly conference
Primary Tracks:
- Geoportals/mashups
- Gaming
- Location-based services
- Open source geo/open data
Where 2.0™ : O’Reilly, June 13-14, San Jose, CA
Key geo-portal providers
- Google (Maps/Earth), Microsoft (Virtual Earth/windows live local), Yahoo (Yahoo local), Mapquest
- Portal providers also provide APIs for application developers
“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 (participatory Web)
Local content – new focus for Geoportal providers
simple geotagging (address, postal/zip code, etc.) allows anyone to publish geodata
- weather, business, social networking information, 3D building models,…
Where 2.0 highlights…
“Web 2.0” is the “read-write” Web (participatory Web)
Local content – new focus for Geoportal providers
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 maturity
- Geospatial IT “evolution of mainstream IT” thru standards (GML, Simple features, SQL/MM, OGC W*S services)
- Core geospatial standards available thru Open Source (Mapserver, Geoserver, PostGIS,…)
- Mapserver now is the number 2 “Web mapping” platform – estimated 50,000 sites
Where 2.0 Highlights – Open Source GEO
Open Source Geo Foundation – OSGEO.org
- Founded Feb, 2006
- Mission: “to support and promote the collaborative development of open geospatial technologies and data”
- Home for all leading Open Source mapping/geo initatives
- Contribution of MapGuide s/w from Autodesk, and initial funding for establishment of foundation
- Key components/projects: Mapserver, GeoTools, GDAL, Grass, MapGuide, MapBender, MapBuilder, OSSIM
Additional info: Free and Open source software for Geomatics conference (this week in Lausanne)
Where 2.0 highlights - STANDARDS- KML and GeoRSS frequently mentioned in presentations
- GeoRSS can allow for syndication feeds for Geo content
- Abstract encoding for point, line, polygon and box
- Two XML encodings: “simple” and GML (subset of GML simple feature profile)
Where 2.0 highlights – STANDARDS- KML and GeoRSS frequently mentioned in presentations
- GeoRSS can allow for syndication feeds for Geo content (use with RSS, Atom)
- Abstract encoding for point, line, polygon and box
- Two XML encodings: “simple” and GML (subset of GML simple feature profile)
Point (GML)
<georss:where>
<gml:Point>
<gml:pos>45.256 -71.92</gml:pos>
</gml:Point>
</georss:where>
STANDARDS: GeoRSS examples<georss:where>
<gml:Polygon>
<gml:exterior>
<gml:LinearRing>
<gml:posList>
45.256 -110.45 46.46 -109.48 43.84 -109.86 45.256 -110.45
</gml:posList>
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
</georss:where>
STANDARDS: GeoRSS example – real-time traffic feed
http://api.local.yahoo.com/MapsService/rss/trafficData.xml?appid=YahooDemo&zip=90210
STANDARDS: GeoRSS Implementation
Implementation of GeoRSS
- Microsoft Virtual Maps
- Yahoo Maps API
- ESRI ArcWeb Services API
- Cadcorp SIS
- other, interest from Google, but no formal support
STANDARDS: GeoRSS Additional info
Addition info:
- www.georss.org
- OGC white paper: http://www.opengeospatial.org/pt/06-050r3
- Allan Doyle (key contributor to the specification)
Summary Simple standards = significant uptake (10,000 Mash-ups 1
year after Google API released)
Lower the bar for Geo-Application developer
- Typical OGC standard “learning curve” is two-three months (e.g. WFS/GML)
- Typical Google API “learning curve” is two-three days
- Microsoft, Yahoo APIs are more rich increased learning curve
Standards Process
- significant emerging defacto standard (e.g. KML)
J. Dangemond stated that ESRI will publish content in formats “to be mashed-up”
- “open” standards development process (e.g. GeoRSS) being executed outside OGC/ISO; market-driven
Response?
-Consumer-geo does raise the bar for geo-applications in terms of:- Accessiblity (non-expert); usability
(performance and ease-of-use); content integration, content depth/breadth; new “open data” content suppliers; large scale replicated data warehouse; uptake
-Increasing maturity level of Open Source Geo market and alignment with mainstream IT-Impact on Architecture for SDIs and GEOSS?