Weekly OSM Summary #2

11/14/2010 – 11/21/2010

Every week a lot of things are happening in the OpenStreetMap world. New map renderings are created, new services are released and the map gets better and better every day. It can be hard to keep track of all the different communication channels and don’t miss any important news. Since we read most of those channels anyway, we decided to collect all the things we find newsworthy enough to list them at the end of the week here. To every news we’ve attached a short description and you can always find more information on the linked websites. Enjoy!

• The License-Working-Group of the the OpenStreetMap-Foundation has published a new draft of the Contributor Terms, now version 1.2.
• Jochen Topf has done some improvements on OSM Taginfo – here is his email to OSM-Talk explaining the changes.
• Iván Sánchez Ortega wrote about his work in Mosambik for the Humanitarien OSM Team in this blog post.
• Kate Chapman wrote about “OpenStreetMap and Crisis Response Why it is Often About the License” here.
• A “actually working” scalebar is back on the openstreetmap.org front page (thanks to Openlayers 2.10 and Andy Allan)
• New stats of the OSM Inspector routing-views are published in Pascal’s blog.
• A new “about page” explains the colors of the ODbL-Map and shows some more statistics for certain keys like highways.
• “How did you contribute to OpenStreetMap?” has been improved with some small add-ons. You can now get the information, if the OSM contributor has agreed to the new ODbL/CTs. Read more in Pascal’s blog.
• A weekly, curated digest from OpenStreetMap community in the Netherlands is now also available here.
• The free-map.org.uk, a topographic OSM map, gets a new server: blog post.
• A scientific corner of OSM is available in the Wiki.

For more news, especially regarding new tags and wiki pages, you can check-out the community-updates over here.

Authors: Pascal, Jonas, Matthias & Brice.
We missed something? You want to help us collecting the news for next week’s issue? 
You can contact us via mail or Twitter.