The document discusses open source, open data, and collaborative geospatial tools and projects. It highlights platforms like QGIS, GRASS, OpenStreetMap, Ushahidi, and others that enable open mapping and crowdsourced data collection. It addresses criticisms around accuracy and reliability but argues these projects are "good enough" and evolve based on user needs. The document emphasizes that open data and tools allow anyone to engage in mapping and analysis.
5. Free and Open Source
use for any purpose;
study and adopt to your own
needs;
redistribute and;
improve and share to the public.
http://www.gnu.org/gnu/manifesto.html
6. For whatever OS
QGIS on Ubuntu Linux; MS Windows; Mac OSX and; Android Tablet.
http://epsg4253.wordpress.com/2012/02/29/qgis-is-for-the-93/
17. Others
Python
general purpose programing
language
Github
fork, copy, share code
18. Availability of the code
is necessary for
Open Science
"scientific communication relies
on evidence that cannot be entirely
included in publications", but
"anything less than the release of
source programs is intolerable for results
that depend on computation".
Ince, D.C., et al. (2010). The case for open computer programs. Nature 482, 485–488.
http://www.nature.com/nature/journal/v482/n7386/full/nature10836.html
20. OpenStreetMap
The Wikipedia for Maps
Geospatial data for free
so that you can use it
for any creative purpose
you can think of!
http://openstreetmap.org
30. Common criticisms to open,
distributed, collaborative GEO
projects
Accuracy/Reliability?
Authoritativeness?
31. Good enough for
now
Quick-and-simple
(but extensible) designs over
elaborate systems designed by
committees.
Quickly deployed, evolve as
needed, driven by user
requirements.
Fit for purpose
suitable for the intended purpose
http://en.wikipedia.org/wiki/Principle_of_good_enough
http://en.wikipedia.org/wiki/Quality_assurance
32. Some examples
GNU/Linux
MP3 format
Gmail
SRTM 90M DEM
Project NOAH website
53. “Usable line generalization for OSM roads
and routes has been a hobby project of mine
…”
“I’ve finally put the last piece of this project
with the use of Amazon's Hadoop
distribution to parallelize the geometry
processing.”
“The entire process is exactly equivalent to
this:”
cat input | mapper | sort | reducer > output
54. “If you don’t need the results fast,
save the five bucks and let it run overnight.
If you don’t use spot pricing, this same job would
have cost $40 slow or $78 fast.”
“To try all this yourself, I’ve set up a bucket with
sample data from the OSM route relations job.”
http://mike.teczno.com/notes/elephants-osm-hadoop.html
https://github.com/migurski/Skeletron
56. "My employer, The New York
Times, generously sponsors my
open-source work. Most of my
recent projects are listed on my
GitHub profile."
- Mike Bostock
57. If everybody can do it, are we still
relevant?
As geospatial professionals, what
do we make out of this situation?
59. “Like guns and
crosses, maps can be
good or bad,
depending on who’s
holding them, who
they’re aimed at, how
they’re used, and
why.”
Mark Monmonier
How to Lie with Maps