31 May 2019, 06:47 by [email protected]: > Please suggest me how I can get OSM API user id and password so that I can > pass that to authenticate. > You can register at https://www.openstreetmap.org/user/new <https://www.openstreetmap.org/user/new> but you can not use it to bypass https://operations.osmfoundation.org/policies/tiles/ <https://operations.osmfoundation.org/policies/tiles/> policy.
> Please suggest me how I can check what's wrong with > gmap.net > <http://gmap.net>> . > It is described at https://github.com/radioman/greatmaps/issues/132 <https://github.com/radioman/greatmaps/issues/132> (closed without fixing) and https://github.com/radioman/greatmaps/issues/136 <https://github.com/radioman/greatmaps/issues/136> (open as of now) It is possible that gmap.net deliberately ignores tile policy in other ways. You can review source code or capture your network traffic and review it (with for example Wireshark) to check it or wait for the developer(s) to fix it. > On Wed, 29 May 2019, 17:09 Mateusz Konieczny, <> [email protected] > <mailto:[email protected]>> > wrote: > >> Technical requirements are at >> >> https://operations.osmfoundation.org/policies/tiles/ >> <https://operations.osmfoundation.org/policies/tiles/> >> >> To check what >> gmap.net <http://gmap.net>>> is doing you need to either >> check its source code, >> capture your network traffic and review it (with for example Wireshark) >> or use program that is not maliciously violating OSM policies. >> >> 29 May 2019, 13:18 by >> [email protected] >> <mailto:[email protected]>>> : >> >>> I would appreciate if you can let me know the exact request header. >>> >> >> _______________________________________________ >> dev mailing list >> >> [email protected] <mailto:[email protected]> >> >> https://lists.openstreetmap.org/listinfo/dev >> <https://lists.openstreetmap.org/listinfo/dev> >>
_______________________________________________ dev mailing list [email protected] https://lists.openstreetmap.org/listinfo/dev
