Tag Archives: OpenStreetMap

OpenStreetMap on ArcGIS.com

I’m confident that my recent post asking that ESRI add some support for OpenStreetMap had nothing to do with it, but I’m still happy to report that ESRI rolled out its new ArcGIS.com web site and one of the new basemaps is OSM.  Pretty cool.

OSM in ArcGIS.com

I could quibble. For example, there are no tiles for the highest zoom levels, and that just seems like a sad omission. Nonetheless, there’s global coverage and it’s a major vote of support for OSM.  BTW, I also think the design of the new ArcGIS.com web site represents a vast improvement overt the ArcGIS Online system.  It’s got a straightforward user interface and muted style that’s easy on the eye.
OSM BaseMap Limits

When will ESRI Support OpenStreetMap?

OpenStreetMap: the free wiki world map

ESRI has a perception problem. It is similar to the one that Microsoft and other commercial software firms have developed vis-a-vis open source software projects. ESRI is perceived by many in the open source world as being opposed to open source software. While I think ESRI has fed this perception to some extent, the open source community has also cultivated a “David vs. Goliath” approach that encourages an adversarial relationship with the larger software companies that I don’t think it terribly helpful either.

But as Paul Ramsey recently pointed out in his address at the FOSS4G 2009 conference in Sydney, most of the mainstream commercial software firms now support open source software platforms, melding commercial and open source business models. Commercial software firms contribute to open source projects for a myriad of reasons including:

  • As a critical component of their platform
  • Low cost R&D
  • Build a broad constituency for a standard
  • Increase the number of developers focused on a particular platform
  • Retire a platform while still enabling customers to receive support

ESRI has pursued at least three of these approaches in its work with open source projects, and while projecting a competitive attitude about some open source projects (and justifiably so), they also deserve some credit for supporting open source projects in a variety of areas including:

ESRI also gave us an open specification on the now venerable shapefile and looks set to do the same (after some years of delay) for the File Geodatabase. And ESRI has contributed resources to development as well as platform support for many of the OGC standards. I would also argue that many of the most successful open source projects could not exist without substantial support from commercial software companies.  PostGIS would not have got off the ground without early and ongoing support from Refractions. Apache and many Java projects gained from substantial investments by IBM.  In other words, I don’t think we gain by having open source software seen as being in opposition to commercial software.  It’s simply part of a complex software development ecosystem.

But I opened by saying that ESRI has a perception problem. In addition to continuing to support select open source projects when it makes strategic sense, I’d like to make a pitch for ESRI supporting the OpenStreetMap project. OpenStreetMap is really multiple projects. It does include open source (GPL) software that would probably be of limited interest to ESRI, but it’s primary output is an open map of the planet. Just as ESRI has helped to encourage the broad use of free government data sets like the Census TIGER and USGS data sets, it should help promote the OpenStreetMap effort.

Why support it?

  • More data means more use of GIS: In the same way that free distribution of TIGER, USGS, Dept of Defense and other data sets catalyzed GIS development in the 1980′s and 1990′s, more data in more parts of the world will encourage more sophisticated uses of GIS, where ESRI really shines.
  • PR value: Support for the OpenStreetMap project will give ESRI some of the street cred that companies like AutoDesk have gained by contributing software projects to the open source community.
  • Free data for ArcGIS Online: The OpenStreetMap data set offers a free, global data set with distinctive cartography that covers some parts of the world even better than the commercial providers. Providing an OSM map service to ArcGIS Online will only make it more attractive for ESRI’s customers.

How should it be supported?

  • ArcGIS Desktop: Enable ArcMap to both display data from OSM and be an editor. The ESRI desktop GIS community are some of the most skilled and knowledgeable people engaged with map production. By enabling them to use the software tools with which they are already familiar (rather than the capable, but clunkier tools like Mercartor and JOSM), they will be able to make valuable contributions to OSM that will make the map better in every part of the world.
  • Toolboxes: Create tools that convert OSM data formats to feature classes.
  • ArcGIS Online: Provide an OSM-based map tile set.

The OSM project is not public domain, so there are important license considerations, but even with the currently proposed revisions, it’s a pretty open license with only attribution and share-alike provisions limiting its use.  But as the Haiti earthquake response demonstrated, OSM is an important and evolving piece of infrastructure that will only be better with ESRI’s support.

——–

UPDATE: 3/22/2010

I should have also cited a recent ESRI blog on some techniques for incorporating OpenStreetMap into ArcGIS Server that are possible now.  These include:

  • Use the WMS extension
  • Use the Data Interoperability Extension (a nice package from Safe Software that is an extension for both the ArcGIS desktop and ArcGIS Server) which now support the OSM XML file directly.  Export the data from OSM to shapefiles or a geodatabase and serve it up.
  • You can also use an extension Azavea (that’s us) created for the ArcGIS Flex API that supports direct integration of the OSM tile structure for Flex apps.

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.