Tag Archives: OpenStreetMap

OSM Maps Port au Prince in Haiti Response

The OpenStreetMap community has really stepped up to the plate and delivered some amazing vector data using a mix of Yahoo! imagery, old CIA maps and new GeoEye imagery.  Some people were digitizing, while others were making sure updated shapefiles were generated every 5 minutes.  Hundreds of sessions were generated in a few days.  The images below, swiped from the Mikel’s post at the OpenGeoData blog, demonstrate the dramatic progress:

OSM at the time of the quake

OSM at the time of the quake

OSM after a couple of days

OSM after a couple of days

OSM, after quake, zoomed in

OSM, after quake, zoomed in

Sean Wohltman made some interesting observations, however, that Google’s similar MapMaker effort was working at cross-purposes to the OSM efforts, leaving users of the maps needing to make a decision about which version they should use.  A common effort would benefit more people, but the legal terms and conditions prevent a straightforward resolution.  Geospatial data developers and users have made great contributions to the Haiti relief efforts, but while the geo-geeks are playing a leadership role in one respect, they are also exposing some tough contradictions in our legal infrastructure.

Update 1/18/2010:

Some additional OSM Resources related to the Haiti quake:

OSM Haiti with Mapnik rendering and earthquake related locations

OSM Haiti with Mapnik rendering and earthquake related locations

OpenStreetMap License is Changing

OpenStreetMap: the free wiki world map

Whether for commercial software or open source projects, the crafting of a license is one of the most important decisions a company or team can make.  The license determines who can use the software, how it can be used as well as how it can be shared.  Open data projects, while different from open source software, face the same types of questions.

OpenStreetMap is probably the single largest and most significant open data project in the geospatial realm.  The project was started because “most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive, or unexpected ways.” Up until now, OSM has been using a license called Creative Commons Attribution Share Alike (CC-BY-SA).  However, OpenStreetMap is more like a database than it is like a text document or photograph and database projects have run into some specific problems with the CC family of licenses.  The OpenStreetMap project is proposing a move to the Open Database License (ODbL).  Like many collaborative projects, the move is being made by submitting the change and the justification for it to the community for review, comment and vote.

Why make this move?  What’s wrong with the CCBYSA license? A lot of people use the CC licenses to publish their articles, photos, paintings and other creative work.  But the various forms of the Creative Commons licenses are designed to work within the legal infrastructure the surrounds the concept of copyright.  Structured databases are collections of facts.  When factual data (like streets drawn on a map) are arranged the way you’d expect it to be, it’s not necessarily protected by copyright law, particularly under U.S. copyright law, which only protects works that arise from creativity.  If copyright doesn’t apply to factual data and the CC licenses are based on copyright law, we have a problem.  The is the core of the issue.  Even the Creative Commons folks have said that the CCBYSA license should not be applied to databases.

The new proposal, ODbL, resolves the issues by applying copyright where it applies and applying contract law where it does not.  It attempts to take the best of both worlds and create a happy medium that applies to database projects like OSM. As perhaps the largest open database in the world, OSM was one of the touchstone cases that the Open Data Commons and Open Knowledge Foundation used to build the license.

But it’s also interesting to note what it won’t cover.  The ODbL will only apply to distribution of the OSM database.  Contributions to OSM (like GPX tracks and other database edits) are covered by a Contributor Agreement which will refer to the ODbL as the means of distributing their contributions.  It won’t cover image tiles generated based on the OSM database.  It won’t cover the OSM wiki, which, since it is text and therefore considered a creative work, will remain covered by CCBYSA.  And it won’t cover the software source code used to run the entire OSM system – that will be usually, but not always, be covered by the GPL.

There remains some controversy within the OSM community. Many members, including one of the founders advocating for the change, feel that a completely free, Public Domain license (no limits on usage) would be preferable.  The ODbL will retain the “share-alike” concept of the current CCBYSA license (requiring both attribution and that changes be submitted back to the community and distribution carry the same terms). They feel that the spirit of reciprocity codified in this approach is stronger. The new OSM license will include both the concept of attribution and share-alike because many members of the community feel that this limitation benefits the project.  Nonetheless, others feel strongly that a truly public domain situation would be better in the long run, encouraging broad usage without consideration for consequences.  In the best democratic tradition, however, both sides express their positions in Vote Yes and Vote No pages.  Check them out.  And if you are an active member of the OSM Foundation, make sure you cast your vote.

You may be tempted to file this under “boring”, but the nuances of licenses are an important part of the creative economy in which we operate.  They set the terms under which we interact with each others work.

Safe Software Adding OpenStreetMap Data Support to FME

Safe Software announced that it is adding support for OpenStreetMap format data to their FME product line.  Safe Software makes the leading spatial ETL (extract, transform and load) software on the market.  It’s also the toolkit upon which the ESRI Data Interoperability extensions are based.  It’s exciting to see that Safe will support reading OSM-formatted data.  This will make it a lot easier to use the planet file to generate new data sets.  We recently had a need for a higher resolution country boundary layer than we could get from many of the default sources.  The OSM country boundaries would be ideal, but it’s not necessarily straightforward to extract just that bit and convert it to a shapefile.  Something like FME would make that a lot easier.

Along those same lines, I’d love to see more support for the OpenStreetMap API in other commercial software as well.  While JOSM, Merkaartor and Potlatch are all adequate ways to edit the OSM database, they don’t have many of the editing features of ArcMap.  I’d do more OSM editing if ArcMap supported it as a data source.

It would also be cool to be able to use the OSM basemap as an ArcGIS Online cached map set.  The OSM servers themselves aren’t stable enough (in my experience) to support production applications, but with ESRI adding several new base map source including third party data from Microsoft Virtual Earth and Delorme, I think this would be a good data set that wouldn’t cost much to add and would give a nice basemap that, in many parts of the world, is superior to what TeleAtlas and Navteq can offer.

OpenStreetMap for U-Penn Campus

OpenStreetMap for U-Penn Campus

Microsoft Patent Suit against TomTom

In the closing days of February, Microsoft announced that it had filed suit against navigation device maker, TomTom, for violation of certain patents (I’m a bit late – I just found out last week).  There has been much speculation since about why they are taking this action at this particular point in time.  DirectionsMag did a podcast on the subject last week.  Joe and Adena suggested that motivations might include:  a) a bid to make a low-cost takeover of TomTom, which is heavily burdened with debt from its acquisition of TeleAtlas; b) an initial shot at leveraging its huge patent portfolio.  The open source world has been particularly fixated on the latter possibility, with Slashdotters quickly suggesting that this was an opening salvo directed at Linux by the newly elevated corporate vice president, Horacio Gutierrez.  While Linux is not named in the Microsoft filing, some of the patents in question involve file access protocols in TomTom devices that use the Linux kernel.  Microsoft denies that any open source software is the target, but I can see why the move would make the OS community nervous.

However, in a conversation with Russ Nelson at yesterday’s Philly OpenStreetMap meetup, I made the following suggestion that I’ll summarize here.  Last September, Google announced that it has moved to exclusively using TeleAtlas street data for all of its online map products.  This had already been the case in the GoogleMaps API, but autumn saw the Navteq data was dropped from the browser tools and mobile products as well (probably due to the acquisition of Navteq by Nokia).  I’m wondering if the target of Microsoft’s patent move is not TomTom itself but rather the TeleAtlas unit, which would give it a global street database as well as leverage over Google and many other enterprises.  If this turns out to be the case, I would speculate that we will likely see greatly increased attention to OpenStreetMap from many directions and perhaps a major investment in the project by Google and others.

Or, perhaps a cigar is just a cigar, and MS is simply going after TomTom because it’s a large commercial firm infringing on its file system and navigation patents.  Given the customary speed of patent suits, it may be a while before we know.