Be aware that this page can be edited by any registered user and does not represent the views of the OSMF. The data is licensed by the OSM Foundation as granted by the contributor terms. Refer to their legal FAQ for a more authoritative answer to legal questions:
What is the license for OpenStreetMap's geodata?
When you upload data to OSM, you remain the copyright holder of your data, but you grant certain rights to the OpenStreetMap Foundation under the Contributor Terms. Some contributors additionally release their contributions to the public domain.
Please note that although OpenStreetMap data is free to all, access to our volunteer-donated servers is not. A tile usage policy applies.
(OpenStreetMap changed license on 12 September 2012. Any data downloaded before then is licensed under CC-BY-SA 2.0: see the Legal FAQ/CC-BY-SA Archive)
What is the license for the software?
The core Rails port that powers the main osm.org site is licensed under the GPL v2. Individual projects have their own licenses. For example, JOSM is GPL v2 but Potlatch is WTFPL. If you're writing software that uses OSM data, you may choose any license you like, including proprietary (non-open).
I found a website using OSM that doesn't display the license
Our license says you have to display both the author and license (see question below). This may be worth documenting at Lacking proper attribution.
Can I trace data from Google Maps/Nokia Maps/...?
It is ok to trace from:
- Bing aerial imagery, as Microsoft has given specific permission;
- a very small amount of imagery from local government agencies, as negotiated by local OpenStreetMap communities;
Better still, survey the data yourself!
XYZ Organisation has data for free download under licence N. Can I use it in OSM?
Approach the data owners, explain OSM, and seek written permission to licence their data under our licence and contributor terms.
Unless the data is genuinely offered without any restrictions on use at all (i.e. public domain), please contact the Licensing Working Group for advice. Do not rely on your own legal interpretation of the licence. OSM is all about creating a freely and easily redistributable data set. Anything which taints the dataset or exposes OSM to possible legal action interferes with that objective.
Even if you only want to use a minor part, or compare the sources, you should still seek approval in writing. The legal principles involved are not well developed, and the OSM community wants to develop a free and untainted dataset and not test any of the legal issues involved here.
In short: be ultra-cautious.
I think someone's been entering copyrighted data - how do we deal with that?
If you find data that you suspect may have been copied from a copyrighted source or imported from a copyrighted source into OpenStreetMap without the owner's permission, please:
- Contact the user via using the 'send message' link from their user page (i.e. "www.openstreetmap.org/user/[user-name]") with the evidence. Be polite: it is important to remember that you might be wrong, they might have permission or it could be a simple misunderstanding. See Contact for more information.
- If there is no response (after 5 days) or you are deeply unconvinced by the response, email your evidence to the OSM Foundation so that the problem can be investigated.
- It may be that your report will be posted to the legal-talk mailing list (or a country specific list if this is more appropriate) for discussion - if so, you will be informed so you can join the discussion.
I would like to use OpenStreetMap maps. How should I credit you?
What credit to use
You must also make it clear that the data is available under the Open Database Licence. This can be achieved by providing a "License" or "Terms" link which links to www.openstreetmap.org/copyright or www.opendatacommons.org/licenses/odbl.
Because OpenStreetMap is its contributors, you may omit the word "contributors" if space is limited.
You may optionally qualify the credit to explain what OSM content you are using. For example, if you have rendered OSM data to your own design, you may wish to use "Map data © OpenStreetMap contributors".
(If you are using tiles from osm.org that were downloaded before 1st July 2020, you must also make it clear that the tiles are available under the Creative Commons Attribution-ShareAlike 2.0 licence. This may also be fulfilled by linking to www.openstreetmap.org/copyright.)
Where to put it
This credit needs to appear in a place reasonable to the medium you are utilising. In other words, you should expect to credit OpenStreetMap in the same way and with the same prominence as would be expected by any other map supplier. Therefore:
- For a browsable electronic map (e.g. embedded in a web page or mobile phone application), the credit should appear in the corner of the map, as commonly seen with map APIs/libraries such as Google Maps.
- For a printed map, the credit should appear beside the map if that is where other such credits appear, and/or in the "acknowledgements" section of the publication (often at the start of a book or magazine).
If you are producing library code that offers OpenStreetMap data or tiles, you should make sure library users are aware of these terms. We strongly recommend that you display this credit by default when your library is used.
If I have data derived from OSM data, do I have to distribute it?
The license does not force you to distribute or make any data available.
But if you do distribute or publicly use anything derived from it - a Derivative Database - then the derivative database must be available under the same licence as the OSM data (the Open Database License). You must make the derivative database available on request to anyone who received your data, viewed the work made from it, or used your service. You could do this by putting it on a site for free download, or offering your users the option of emailing you for a copy.
Any of these are acceptable ways of making the derived data available:
- The full database, as a dump or in a commonly understood format (e.g. OSM XML or shapefiles);
- The 'diff' between the original OSM data, and your derived database (i.e. a machine-readable list of changes);
- Instructions on how to make the changes, such as an algorithm, some software, or something as simple as an Osmosis command line.
If you're thinking of building something using OSM, there is a Use Cases page which goes into detail about the license implications in various different scenarios.
If I make something with OSM data, do I now have to apply your license to my whole work?
No. For example, if you have written a game or published an artistic map which includes OSM data, only the data is covered by the license. This is called a Produced Work.
However, if you make a database which includes OSM data and any additional information (including using information to decide on OSM features NOT to include in your database), then this would be classed as a "derivative database" and should be made available under the Open Database License as in 3b above.
If I use your data together with someone else's data, do I have to apply your license to their data too?
If the two datasets are independent, no, you don't; this is a Collective Database.
If you adapt them to work together (for example, by taking footpaths from the OSM data, roads from the third-party data, and connecting them for routing), this is a Derivative Database and so you must (as per 3b). However, if the two datasets are matched "trivially" by, for example, automated matching using a simple criterion such as name/locality, this is not "substantial" and remains a Collective Database. There is a Community Guideline on what constitutes a trivial transformation.
Can I charge for distributing OSM data or data derived from OSM data?
Yes. You can charge any amount of money you want for any service or data you provide. However, since the data that is derived from OSM data must be licensed as above, other people may then redistribute this without payment.
Can I get permission to distribute OSM data under an alternative licence?
Probably not. The copyright to OSM data is vested in the individual contributors. However, if you happen to use data provided solely by one or a few OSM contributors, you can ask them if they are willing to provide their data to you under a different license.
Yes, provided that you are only comparing and do not copy any OpenStreetMap data. If you make any changes to your data after making the comparison, you should be able to reasonably demonstrate that any such change was made either from your own physical observation or comes from a non-OpenStreetMap source accessed directly by you. I.e you can compare but not take!
- Example 1: You notice that a street is called one name on your map and another in OpenStreetMap . You should visit the street and check the name, then you are free to put that name in your data as it is your own observation.
- Example 2: You notice that a boundary is different in your data and OpenStreetMap. You should check back to original authoritative sources and make any correction required.
You have infringed my copyright
- If you are the copyright owner or represent the copyright owner, refer to our take-down procedure here. We can assist you directly by e-mail at firstname.lastname@example.org with an informal request. Please cite the exact content in question. Correspondence is answered by a small team of volunteers.
- This address is not for requesting permission to copy content from OpenStreetMap.
- If you prefer to use or make a formal OCILLA request, you can send it to our designated agent. Digital Millennium Copyright Act Notice
Finding out more
I have questions. Can you answer them?
OpenStreetMap cannot provide legal advice. However, our volunteers and community members may be able to provide non-binding interpretations on an informal basis, subject to time constraints.
- OpenStreetMap Foundation, Licensing Working Group: email@example.com
- Community-powered help centre: help.openstreetmap.org
- Other Contact channels (Levels of response may vary, for example please do not expect discussion pages on this wiki to be actively monitored)