For who still remembers www.OSMgo.org or even uses it:
Loading was slow due to the many rather suboptimal Overpass API calls. This has now been replaced by the direct OSM API and works.
Hopefully that’s ok given the “many” hits. The OSM server only sees the user’s IP. I can’t give out a client ID, can I?
My hoster changed the PHP version. At least multiuser mode is currently not possible: todo
Wer sich noch an www.OSMgo.org erinnert oder es gar nutzt:
Das Laden hakte wegen der vielen eher un-optimalen Overpass-API-Calls. Das ist jetzt durch das direkte OSM-API ersetzt worden und flutscht.
Hoffentlich ist das von den “vielen” Zugriffen ok so. Der OSM-Server sieht ja jeweils nur die IP des Verwenders. Irgendwie eine Client-Kennung kann ich nicht mitgeben, oder?
Mein Hoster hat die PHP-Version geändert. Zumindest Multiuser-Mode geht derzeit nicht: todo
The editing API is provided in order to edit the map data, not for read-only purposes or projects. Clients may be blocked without notice if they are affecting the service level for others or causing data corruption.
The main editing API is intended for editing only. Don’t be surprised if your application is blocked.
That’s what I was afraid of. But what could I do correctly, what API could I use? Is there a mirror service?
I don’t expect much traffic to do any harm (In the browser trace I see a minimal increasing delay of the request answers) But that could be checked!
And I am just curious: How could it be detected? Not by the IP cause will be the IP of each users browser. I could add &client=OSMgo to mark it.
