ODbL License: How to Use OpenStreetMap Data Legally
OpenStreetMap is the world's largest open mapping project. The data is free, but not "unlicensed." It's distributed under the Open Database License (ODbL). Violating the license terms can lead to legal consequences. Let's break down what you can and can't do, and how to properly use OSM data.
What Is ODbL
Open Database License (ODbL) v1.0 is a license for databases, developed by Open Data Commons. It has applied to OpenStreetMap data since September 12, 2012 (previously CC-BY-SA was used).
Key principles of ODbL:
- You are free to share, create derivative works, and use the database
- As long as you provide attribution, share-alike for derivative databases, and keep things open
Three ODbL Obligations
1. Attribution
You must credit the data source in any use. Standard wording:
(c) OpenStreetMap contributors
Or with a link:
Data (c) <a href="https://www.openstreetmap.org/copyright">OpenStreetMap</a> contributors
Where to place it: - On a map: in a corner or caption - In an application: in "About" or "Credits" section - In print: on the copyright page - In an API/service: in the documentation
Minimum requirements: attribution must be reasonably visible. Small print in a 300-page document is acceptable. Complete absence is not.
2. Share-Alike
If you create a Derivative Database based on OSM, it must also be published under ODbL or a compatible license.
What counts as a Derivative Database: - Correcting errors in OSM data and publishing the corrected version - Merging OSM with another database into a single dataset - Adding new attributes to OSM objects
What does NOT count as a Derivative Database: - Creating a map (visualization) based on OSM data - Extracting a subset of data for specific use - Geocoding (determining an address from coordinates)
3. Keep Open
You cannot apply technical protection measures (DRM) that restrict access to the data. If you distribute a derivative database, it must be accessible without technical restrictions.
Commercial Use
Can you make money from OSM data? Yes, without restrictions.
Examples of legal commercial use:
- Selling printed maps (with attribution)
- Paid mobile apps with OSM maps
- Commercial SaaS service based on OSM data
- Selling analytical reports based on OSM
- Paid navigation devices with OSM maps
ODbL does not restrict commercial use. The only obligations are attribution and share-alike for derivative databases.
Produced Works vs Derivative Databases
This is the key distinction in ODbL that often causes confusion.
Produced Work
A map, visualization, image, PDF, SVG — this is a Produced Work. Share-alike does not apply to it. You can:
- Sell the map under any license
- Keep rendering styles proprietary
- Use proprietary fonts and symbols
- Add your own design elements
Obligation: attribution only.
Derivative Database
A modified or extended version of the OSM database. Share-alike applies:
- Must be published under ODbL
- Must be available for download
Practical Scenarios
Scenario 1: Printing a Map for Sale
You export a map of Moscow to PDF via osm2cdr, print a poster, and sell it.
This is legal. The map is a Produced Work. Obligation: include "(c) OpenStreetMap contributors" on the poster.
Scenario 2: Mobile App with Map
You create a delivery app with an OSM map.
This is legal. The map in the app is a Produced Work. Obligation: include attribution in the "About" or "Licenses" section.
Scenario 3: Enriching OSM Data
You download buildings from OSM, add energy efficiency data, and publish the result.
This is a Derivative Database. Obligation: publish under ODbL and provide data access.
Scenario 4: Geo-Analytics
You use OSM data to calculate Walk Score or infrastructure density.
The result is a Produced Work (a numeric score, a report). Share-alike doesn't apply. Obligation: attribution.
Scenario 5: Your Own Tile Server
You deploy a tile server with OSM data for corporate use.
Tiles are Produced Works. If you haven't modified the OSM database, share-alike doesn't apply. Obligation: attribution on the map.
OpenStreetMap Tiles
People often confuse OSM data with tiles from tile.openstreetmap.org. OSM tiles have additional restrictions:
- The Tile Usage Policy prohibits bulk downloading
- Limit: 250 requests per second (not formalized, but recommended)
- For commercial use, your own tile server is recommended
osm2cdr.ru uses its own PostGIS server and doesn't depend on OSM Foundation tile servers.
OSM Attribution in Different Contexts
Web Maps
<div class="map-attribution">
(c) <a href="https://www.openstreetmap.org/copyright">OpenStreetMap</a> contributors
</div>
Printed Maps
In the bottom corner or on the reverse:
Map data (c) OpenStreetMap contributors, openstreetmap.org/copyright
Mobile Applications
In "About" / "Licenses":
Map data: (c) OpenStreetMap contributors
License: Open Database License (ODbL)
Scientific Publications
In "Data Sources":
Spatial data obtained from OpenStreetMap (openstreetmap.org)
under the Open Database License (ODbL) v1.0.
Extraction date: 2026-04-01.
APIs and Services
In API documentation:
This service uses OpenStreetMap data, (c) OpenStreetMap contributors, ODbL.
Frequently Asked Questions
Can I use OSM without attribution? No. Attribution is mandatory in all cases.
Can I use OSM in a closed project? Yes, if it's a Produced Work (map, visualization). No, if it's a Derivative Database.
Do I need to pay for using OSM data? No. The data is free. But infrastructure (servers, rendering) costs money.
Can I patent an algorithm that works with OSM? Yes. ODbL doesn't restrict algorithm patents. The restriction is only on data.
Can I mix OSM with proprietary data? Yes, if the result is a Produced Work. If the result is a database and the data is "inextricably mixed," the entire database falls under ODbL.
Does ODbL apply to my own data? No. ODbL applies only to OSM data and its derivatives. Your own data remains under your license.
Conclusion
ODbL is a liberal license that allows virtually any use of OpenStreetMap data, including commercial. The key is remembering attribution and understanding the difference between Produced Work and Derivative Database. If you're creating maps, apps, or analytics — it's almost always a Produced Work, and the only obligation is crediting the data source.