Currently there’s a video shot by Ikiya, but I believe there should’ve have been a video with better sound quality recorded by the venue people (not released yet, but maybe one day)

I think one of the best ways for companies to “pay for getting (attribute) coverage”, is for companies to sponsor good visualisations of those attributes and the development of easy to use editor support for them. One nice example for this is the josm turn-restriction editor originally sponsored by skobbler, or their OSM bugs page focused on routing attributes. Or indeed also the great visualisation work sponsored by ITO, which helps to motivate the community to go out and collect these features.

- i think OSM needs a kick arse web interface to show case the power of the OSM data, the kind to compete with the Google Maps to allow folk to search the rich local information OSM has captured.
- someone else mentioned this above, usability of the editors also needs attention
- usability of the data via an api needs attention. cloudmade’s api is a good example but they are commercial organisation and i think OSM needs an api of its own to provide that usability layer

I think usability in these aspects is key to growing OSM beyond the geo geeks to being an option on the table whenever people sit down to discuss their mapping needs in organisations around the world.

Good luck Chris, hope the discussion is fruitful.

Is OSM Finished?
Is OSM Just About The Map?
To Fork Or Not To Fork?
The Unfortunate License Question?

Too much to cover in a comment so these points are fleshed out in a post over on my blog – http://vtny.org/9C

Shame I won’t be at Girona this year … this will be a humdinger of a panel to participate in and to watch.

I can see that this panel discussion could end up being very philosophical: The evils of “top-down control” versus the difficulties of “blind faith in the wiki anarchism”. All quite interesting. I imagine Chris may have to work to keep the discussion anchored to real problems users have.

Harry is right about outreach but wrong about making them come to us.

To add to others usability points, the many tools to check data for common faults, differences with public data, missing data, etc. vary in quality and are spread all over the place.

And yes, after five years I miss blank spaces!

How can I “pay” or “incentivise” completion/coverage in areas I am interested in?
How can I facilitate/initiate capture of attributes I need?
How can i get clarity on the license and what I can do with the data?
etc etc