You are not logged in.


*** NOTICE: is being retired. Please request a category for your community in the new ones as soon as possible using this process, which will allow you to propose your community moderators.
Please create new topics on the new site at We expect the migration of data will take a few weeks, you can follow its progress here.***

#1 2021-12-08 19:39:29

Registered: 2021-12-08
Posts: 5

Legally and responsibly using a tile source in a commercial app

I developed a hiking app about a year ago. In my haste I went with Google Maps Api. For a commercial product, the legal terms were easier to understand. It's been out on the Google Play Store for almost a year and has a tiny user base. I think in part due to Google's lack of details in parks and trails. Most parks are just a green squares. Which doesn't help my user orientate themselves. OSM on the other hand, has plenty of park details.
I initially wanted to build my app using OSM, but like mentioned above. Google Maps API had a very straightforward tile provider. Not to mention the API Console has all sorts of analytics. Google Maps API also has a $200 threshold. Basically if your bill is under $200, they don't charge you. Which my app never exceeds.

I want to make the jump to OSM. But I'm finding it hard to understand what is need to legally distribute my app. Do I need a paid tile provider? Can I use for my app with a tiny userbase? If so, what's the cutoff limit? How do I find the analytics for that?
Aside for what other tile providers should devs with a tiny user base consider?


#2 2021-12-08 20:37:27

Registered: 2009-01-26
Posts: 2,856

Re: Legally and responsibly using a tile source in a commercial app

It all depends on what your app is doing. Do you show a live map or do you do bulk downloads for offline use? If you have only a small user base, online use should be fine with most tile providers, while bulk downloads are prohibited and blocked by most as they bascially are a DOS attack on the live rendering.

You need to check every map you want to include separately, for a compatible license and for the usage limits.

Some maps have a "commercial use" license so you can always include them. Some have a "non-commercial" license, so you not use them under that general license.

The limits differ widely depending on how the respective maps are funded. The maps on the OSM main page are OSMF-funded and the OSM usage policies apply only to these maps. The OpenTopoMap is University hosted, the download for live maps is only limited to two parallel threads at a time. Some maps are privately funded and must be much more careful about their resources. You should always get in touch with the map provider before using a map in an app - it's simply polite.

Last edited by Nop (2021-12-08 20:39:26)

Nothing is too difficult for the man who does not have to do it himself...
Projekte: Reit- und Wanderkarte mit Navigation - Kartengenerator Map Composer - GPS Track Editor Track Guru


#3 2021-12-09 03:13:51

Viajero Perdido
Registered: 2016-10-13
Posts: 194

Re: Legally and responsibly using a tile source in a commercial app

Thunderforest and MapBox are two commercial providers of OSM tiles that I'm aware of.  I'm more familiar with the former, and have included a link to their pricing page which I had handy.  You'll see there's a free tier for getting started, and payable tiers above that.  MapBox would be similiar, I imagine.

Tiles directly from OpenStreetMap websites are discouraged, but tolerated in very small quantities.  You run the risk of being cut off without warning.  But between the two companies (plus any others I don't know of), there are lots of styles to choose from.

You're familiar with Leaflet?  It's a JavaScript library for managing tiles.  I gather Google's code can be used to display non-Google tiles too.  That might make the conversion go more smoothly.  Good luck.  smile

PS, I don't think Google will ever catch up to OSM for trail details, so...  good choice!

Last edited by Viajero Perdido (2021-12-09 03:22:49)


Board footer

Powered by FluxBB