Canadian Council on Geomatics Reading List

ccog-readinglist.md

• The presentation in PDF format.
• Publishing Landsat on AWS, the use of cloud infrastructure for public data distribution and processing.
• On the size of Google Maps, now larger than most national mapping agencies.
• OpenTripPlanner and OpenStreetMap, how open data and open source leverage each other and are in turn re-consumed by governmnet and civil society.
• Michael H Goldhaber on the attention economy, a prescient take on content and the internet from 1997.
• Google aquires Skybox Imaging.
• Bibiana McHugh on Portland Trimet's triple open strategy: open data, open standards, open source.
• Paul Ramsey on why SDIs fail.
• The General Transit Feed Specification.
• The places developers get data now, instead of governments:
  • http://openstreetmap.org
  • http://openaddresses.io
  • https://openaerialmap.org
  • https://github.com/openimagerynetwork/oin-register
  • http://geonames.org
  • http://www.naturalearthdata.com
• Three start-ups prominent in the new take on geomatics:
  • MapBox
    • How MapBox is using automated trajectory matching, another fully automated process of data cleansing.
    • User guided feature extraction, with enhancement to the the Id OSM editor.
  • CartoDB
    • Visualizing Change with CartoDB
    • Web Mapping at Scale
  • Planet Labs
    • Planet Labs already has more satellites than most governmments and are launching dozens more every year
    • How Planetlabs is rectifying the planet, with automated ground rectification of very poorly registered images at a rate of 1M images per day.

Great list... seems the emerging OIN is aligned with frictionless raw data sharing - I would give you a PR if it wasn't a GIST [email protected]:e69d0f377f4f81c2054b.git

Thanks. OIN seems a little moribund and skeletal, though I like the approach.

Great presentation and list of resources. You're observations on industry trends are very astute and I hope it is seen by a wide audience.

@RobertLRead had similar ideas here https://medium.com/@RobertLeeRead/the-minimum-government-responsibility-api-first-24cf67b9ec73#.yufzf7su9. That is to get the raw data out there first, API first, GUI second. Maybe the raw data can be shared best through http://data.gov. What do you think?

Thanks for your direct approach Paul. I think developers need not be the gatekeepers of the spatial flame, however. That approach failed for SDI. What mobile needs is consumer-level standards for geo: HTML needs to support maps and the spatial "Web". Come and join us over at the Maps for HTML Community Group. We are small, but growing https://github.com/Maps4HTML

@pramsey, hello. maybe you have done some more research on data harvesting, do you have an idea about creating datapipes and streaming my own data to my own tilers and serving them customly same way mapbox does from places like OSM. i don't mind the technicality and all softwares involved, maybe i can be a little startup in africa.