Notes from Where Camp Boston 2011

I had a great time at this little event and it was good prep for the Maine GIS User group’s Ignite meeting tonight. Hopefully I’ll be able to attend more stuff like this in the future. But, before then, I’d better get some materials together about Spatialite in return for the kind gentleman giving the spatial sql talk at my request (from the session board).

So what follows are my notes from Where Camp Boston 2011, and in generally chronological order.

The session board at Where camp Boston 2011

Geocouch – finally heard someone using this spatially-enabled, NoSQL data storage technology. It does seem that many NoSQL solutions have at least X,Y spatial capabilities and data types. I’m kinda torn between Cassandra and MongoDB. Although, there are SOoo many commercial/cloud offerings out there if you just want to store points. See below
— CouchDB – http://couchdb.apache.org/
Open Geo Portal. could be interesting. http://opengeoportal.org/
Fascinating use of VGI/Crowd sourcing to collect hi-res data. Now if they can just harness all that information and use it effectively. Hopefully the Where Camp Boston folks can post some slides from the keynotes. I missed a lot of detail from this one. http://publiclaboratory.org/home
— Tools – Had some great tools for rapid georeferencing and other processing of Kite-collected images, etc. http://publiclaboratory.org/tools
— Your [nearest] Superfund – http://macwright.org/superfund/
— Firebird commander for RC remote sensing with a $300 HD video camera – http://www.amazon.com/Firebird-Commander-2-RTF-Electric/dp/B000AUO7B8
Google Refine for cleansing dirty data. I’m totally going to use this – http://code.google.com/p/google-refine/
Open street map geocoder – http://wiki.openstreetmap.org/wiki/Nominatim
Cartodb, yet another point-in-cloud service – http://cartodb.com/
Request Tracker, flexible OSS for (not just software) issue tracking. We are quite happy hacking on Mantis, but I met a Best Practical engineer at this conf. and spoke with a few attendees who use rt. Turns out people still develop successful commercial products in Perl (but not your grandma’s perl CGIs) http://bestpractical.com/rt/
Tilemill and carto for styling – very cool and hip as presented by Tom MacWright (http://www.wherecampboston.com/keynote-speakers/) – http://mapbox.com/
AppInventor – Rapid Android app development for non-developers – Presentation by Daniel Sheehan, MIT GIS Lab about rapidly building Android apps. I saw this years ago but needed a little push like this presentation to take it for a spin. I hope MIT is able to keep it going after Google sends it back home. – Appinventorbeta.Com
— scratch – basic programming
— starlogo TNG (java)
— appspot.com -to store data – but now fusion tables
— Fusion tables – will limit to several hundred megs of geodata
— Change setting/app on phone to allow unknown sources and development
— Kinda useful – http://gmaps-samples.googlecode.com/svn/trunk/fusiontables/fusiontableslayer_builder.html
jQuery Geo. Yep, might turn into our JS mapping toolkit of choice. Very nice, and very jQuery compliant. Definitely takes the “less is more approach” It can use Esri tiles and internal builds have mobile app builder with geo ready templates. These might get released – http://jquerygeo.com/
— See also:
— http://modestmaps.com/
— http://polymaps.org/
— http://mbostock.github.com/d3/
— http://leaflet.cloudmade.com/

sailing, snow, halloween, boston, crazy, awesome!

Crazy folks out sailing. When I left at 6pm-ish it was raining hard with snow mixed in and nearly dark out – they were still sailing. I take my hand off to them.

Tom McWright keynote speaker: technology, spatial curmudgeon

— Tilemill– http://mapbox.com/tilemill/docs/manual/
— Vizzuality interesting- http://vizzuality.com
— Carto – is styling language for mapnik and tilemill (incestual rship here). But jQuery Geo is going to use SVG CSS style sheets – http://developmentseed.org/blog/2011/feb/09/introducing-carto-css-map-styling-language/
- Metro Area OSM Extracts. I need to contact him to add Portland, MAINE to the list – http://metro.teczno.com/
- The OSM data – http://planet.osm.org
- Vector in the browser is limited to Google maps WebGL. Nothing else out there yet.
- Cartodb IS postgis
- Spatialite license is terrible… hmm
- No more projections in data, just in presentation
- Node.js – all the cool kids do it, and github
- Check out wax on github
- Bones – ruby on rails with JavaScript. runs on browser and server – https://github.com/developmentseed/bones#readme

<Soapbox>: Data without metadata are useless crap

There was some talk about various projects using (1) publicly available historical data, or (2) data from a range of public, crowd-sourced, etc sources. There were also related discussions about collecting data for broad public use (use case 2). But all the discussions left out an important topic — which is a common malady in many discussions in the open, free, non-government (not necessarily related, but often coincident concepts) circles: documentation/metadata. I love open data. But when I use it, I need to have convenient, parse-able, understandable, hopefully standards-based information about this stuff I am about to use. It doesn’t have to be elaborate, but it needs to be present.

I wish the spatial community would agree on some simple, general, common approach to embed metadata right into the data so that the two could never be separated. When you create/maintain/manage/supply data, you’d better assume responsibility for the metadata and the data, as they should be two sides of the same coin. So, in your spatial DBs, maybe always include a table called.. DOCUMENTATION, link to the information_schema and create records contains Dublin Core RDF, or SOMETHING. Now I just need to follow my own advice…

</Soapbox>

See:

Scratch pad