Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tile use and using this library #69

Closed
programmin1 opened this issue Mar 4, 2020 · 3 comments
Closed

Tile use and using this library #69

programmin1 opened this issue Mar 4, 2020 · 3 comments
Milestone

Comments

@programmin1
Copy link

I don't know if this has been resolved elsewhere, but where does this library stand as to the tile usage policy on https://operations.osmfoundation.org/policies/tiles/ ?

For example, "Bulk downloading is strongly discouraged. Do not download tiles unnecessarily."
My app, as well as everyone else who has build something off the example, has the cache functionality built in and is an awesome feature of this library. Is there is any required adjustment to the config, or need to register my app in addition to what work Osm GPS library does?

@dreadnought
Copy link
Contributor

I implemented some changes to make it more compliant to OSM policy in 2016 (see #47 and #48). Caching is not necessarily the same as bulk downloading. When a tile, that was downloaded while you where browsing the map, gets written to a file cache, it's actually taking load of the server. Regarding a bulk downloading feature I see the app developers responsible, not the library. That's why I implemented the user agent option, to avoid collateral damage.

@johnny-bit
Copy link
Collaborator

using user-agent property, along with proper cache management on app devs part should alleviate all problems regarding tile use and bulk download use.

I've added the user-agent property to mapviewer.c example file. Should we stress it's importance in docs?

@johnny-bit johnny-bit added this to the 1.2.0 milestone Jan 30, 2021
@johnny-bit
Copy link
Collaborator

With release 1.2.0 this won't be a problem I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants