Attribution

Mapricot's results and map tiles come from open data, and some of the data's licenses require a credit when people see it. This page covers the minimum those licenses require.

The short version:

• On a map from Mapricot's tiles, keep the OpenStreetMap credit in the map's corner. The styles already show it, so leave it in place.
• Anywhere else, such as a list of search results, an address on an order page, or a route drawn on a map, an attribution page linked from your site's footer or your app's about screen is enough.
• If nobody outside your organization sees the data, you don't need to credit it.

What each source requires

Map tiles and routing use only OpenStreetMap. Geocoding and places use OpenStreetMap, OpenAddresses, Who's On First, GeoNames, and Overture. IP geolocation uses DB-IP. The open-source software behind them, such as Valhalla, Pelias, and Protomaps' tile builds, needs no credit.

Each geocoding, places, and routing response also lists the sources of its results in attribution, with the text and link for each. You don't need it if your attribution page lists every source, but it tells you which sources you use.

On a map

OpenStreetMap's attribution guidelines require the credit on a map built from its data, usually in a corner. It can shrink to an ⓘ button, on a small screen or once someone uses the map, as long as tapping it shows the credit again. Mapricot's styles show "Mapricot © OpenStreetMap" this way.

You don't need to add anything for the results you draw on the map. The attribution page covers them.

MapLibre GL JS

MapLibre shows the style's credit in the corner by default. Don't turn off its attribution control with attributionControl: false.

Leaflet

Leaflet draws Mapricot's tiles through the MapLibre GL Leaflet plugin, which puts the style's credit in Leaflet's attribution control. Keep that control on the map. Geocoding and routing with Leaflet builds a complete map.

iOS and Android

MapLibre Native, on iOS and Android, shows an ⓘ button in the map's corner that lists the style's credit, and so does MapLibre React Native. Leave the button visible.

Outside a map

OpenStreetMap's geocoding guideline requires apps that use a geocoder or a router built on its data to credit it, and CC BY requires a credit wherever the data is shared with people. Neither requires the credit next to the results, and CC BY says a link to a page that holds the attribution can meet it.

So when you show results anywhere but in a Mapricot map's own tiles, such as in search suggestions, a saved delivery address, "20 minutes away", or markers and routes drawn on a map, an attribution page covers them:

• List the attribution in the table above for the sources you use. Mapricot's own is an example.
• Link to it from your site's footer, or your app's about or settings screen. DB-IP asks for its link on the pages that show or use its data, which a footer link covers, including when you use an IP location without showing it, such as to fill in a country.

If you share a file or a dataset that includes results, put the attribution and licenses in its readme or metadata instead.

When you don't need to credit

• Nobody outside your organization sees the data. Internal dashboards, analytics, data cleaning, and testing need no credit. ODbL and CC BY require credit only when the data, or something made from it, is shared publicly.
• A thumbnail too small to matter. OpenStreetMap's guidelines exempt small static images, such as icons, and maps of fewer than 100 features covering less than 10,000 m².

Storing results

You can keep results for as long as you like and show them later, as the terms say. Your attribution page covers them whenever you show them.

ODbL has one more condition for results from OpenStreetMap. Storing the addresses your customers enter with their coordinates is fine. But if you collect results into a database that holds a large part of OpenStreetMap, such as by geocoding every business in a city to build your own places database, and then share it or use it publicly, ODbL requires you to offer that database under ODbL too. The geocoding guideline explains where the line is.

This page explains the licenses in plain words. It isn't legal advice, and the licenses themselves are what count. If your use doesn't fit any of these cases, ask us.