[geodesk]

OpenStreetMap is an excellent alternative. At this point, OSM data (which is freely available under the Open Database License) is equal (and often superior) to commercial offerings throughout much of the world. There's a great amount of detail, especially for tourism-related features (points of interest, difficulty level of hiking trails, opening hours of museums, etc.).

Google tends to have a greater number of commercial POIs (since it caters to potential advertisers), but OSM is catching up in this area as well.

Full disclosure: GeoDesk develops a spatial database engine for OpenStreetMap data, so obviously biased on this issue.

[throwaway120222]

I find it a bit difficult to navigate the open source alternatives. Some needs a lot of work for downloading / transforming the data, and others are split into multiple software components.

Are there any plug-and-play options where I can just download a docker image and get a simple backend that can be used for frontend maps and an address auto-complete? Alternatively a separate docker image for the tile server (if that is the right terminology). Preferably with an option to only include data for certain geographical areas to save space.

[NanoWar]

I think maptiler might be what you are looking for: https://www.maptiler.com/server/

[Ovid7]

Interesting. We thought about it, but we found that for many venues it seemed to lack basic details.

Theoretically, we'd like to merge OSM data with some licensed databases. And then perhaps it could "compete" with Google's offering.

However, we're not sure which are good sources for the licensed DBs and how much do these licenses cost ? Is it something feasible?

[geodesk]

What specific data were you looking for? When did you last check out OSM? (There's been a huge push on data completeness in recent years that is now bearing fruit)

Combining datasets: You'll have to check the terms of the license agreements. In general, for ODbL-licensed data (like OSM), if you generate a "derivative database" (e.g. by merging multiple datasets), you will have to release this derivative database under ODbL terms as well. This would essentially rule out commercial data.

One way companies avoid this is by segregating the datasets, e.g. use a commercial dataset for hotel data, and use OSM data for streets and non-hotel POIs, without ever combining them into a single database. (But you'll have to check with an IP lawyer to be certain about the correct way to implement this).

[Ovid7]

One example, but probably pretty representing : I saw a high-rated restaurant on a food ordering app in a big city, just this week. Opened Google - saw immediately the details for that place. Then opened OSM - the place wasn't even there.

This sort of thing is problematic for travel startups that help plan or share venues/places for example. We already heard some potential users of our product saying "we only use and trust google for maps/places", and realized the bar is quite high in terms of what we have to offer in that respect.

Regarding the ODbL licensed OSM data, good thing you mentioned that! Do you know by any chance what would be the magnitude of costs for licensed databases that would cover the majority of businesses/venues/places in the world (excluding non-touristic countries/cities, e.g N. Korea, Afghanistan, etc.)?

I'm trying to understand if that's really an option, or one must have Google's resources to be able to set up this sort of thing. (We do have the tech and engineering talent on our team, we're just somewhat scarce on our financial resources)

Thank you!

[toast0]

> Do you know by any chance what would be the magnitude of costs for licensed databases that would cover the majority of businesses/venues/places in the world (excluding non-touristic countries/cities, e.g N. Korea, Afghanistan, etc.)?

Licensed databases are going to be 'call for price', but you might see if you can get free/low cost feeds from companies that want to sell something: food ordering apps might let you have a list of restaurants if you link the restaurant to their app; you might be able to get a hotel feed from an OTA like Expedia, etc. Maybe Yelp has a feed??

Otherwise, you've got to find data sources and figure out how much they want, or talk to your legal team and build crawlers. I used to work at Yahoo! Travel, and we had a lot of data sources, I can't remember all of them, and was never involved in pricing discussions, but I think we tended to include attribution, if you dig into the internet archive. The base hotel feed came from Sabre, restaurants came from multiple sources (and Y!Local which had its own sources), points of interest and city information came from guide book providers like Fodors and Lonely Planet, and I think a couple others. Ski conditions came from OnTheSnow (which was a pleasure to work with).