On Wheels App upload error status code 509

Robin_On_Wheels · 2024-10-26T18:42:44.519Z

Hi everyone,

It seems that we are having the same ‘code de status:509’ issue with our new On Wheels app.

We collect data for wheelchair users about building like restaurants, cafes, shops, … We organise teambuildings were a group of 20 people use our app to add the new accessibility tags to existing buildings. We always get this problem were OSM sends the 509 issue and people can’t upload their data and the nodes don’t show up on the map anymore. After a couple of minutes the icons show up again and we can upload again. But then it happens again.

Can anyone tell me how the frame limit works? Does it limit on the user name or on the ip address? Now all data is pulled from the OSM api to our backend and the relevant tags are send to our frontend. Then when people edit or add things our backend compares it with the existing changeset and sends everything back to OSM. Most of the time the data has been send to OSM even when we get the 509 message. We also add new nodes if the data is not know in OSM and this means that sometimes we have like 20 of the same nodes on top of each other in OSM because people keep pressing the upload button because they get the error message.

Robin_On_Wheels · 2024-10-26T18:43:11.955Z

Hi everyone,

It seems that we are having the same ‘code de status:509’ issue with our new On Wheels app.

We collect data for wheelchair users about building like restaurants, cafes, shops, … We organise teambuildings were a group of 20 people use our app to add the new accessibility tags to existing buildings. We always get this problem were OSM sends the 509 issue and people can’t upload their data and the nodes don’t show up on the map anymore. After a couple of minutes the icons show up again and we can upload again. But then it happens again.

Can anyone tell me how the frame limit works? Does it limit on the user name or on the ip address? Now all data is pulled from the OSM api to our backend and the relevant tags are send to our frontend. Then when people edit or add things our backend compares it with the existing changeset and sends everything back to OSM. Most of the time the data has been send to OSM even when we get the 509 message. We also add new nodes if the data is not know in OSM and this means that sometimes we have like 20 of the same nodes on top of each other in OSM because people keep pressing the upload button because they get the error message.

SomeoneElse · 2024-10-26T18:57:32.082Z

@Robin_On_Wheels Can you give example user names that have experienced the problem?

Edit: I merged the duplicate post into this thread too to avoid people answering twice.

SimonPoole · 2024-10-26T22:29:50.214Z

Ahmm, if you are getting a 509 response your issue has nothing to do with the rate limiting discussed here. You are being rate limited on download (not on upload, the issue discussed here), and given that you have to try -real- hard to do that, I suspect your app is broken/doing something wrong. That rate limiting is based on IP addresses AFAIK so likely you are just downloading too much from one address (which kind of seems what you are doing).

If you use an authenticated connection (that is use an OSM account to authenticate yourself with OAuth 2) to the OSM API things should be better.

PS: see API v0.6 - OpenStreetMap Wiki assuming you are using the map call for downloading the data.

Robin_On_Wheels · 2024-10-26T22:57:24.145Z

We mainly use this osm account: teambuildingonwheels | OpenStreetMap

Everyone logs in with this account (OAuth 2) so its easier to do a quality check afterwards. Can this be the problem? That this account downloads too much data? Better to use multiple accounts? If we use multiple accounts but send it through the same ip address from our backend, will osm count this as one user?

What is the limit on download? I will check with our developer and ask for more information how the app downloads and uploads data from OSM. Will be easier to find the problem.

Thanks for the answers already.

TomH · 2024-10-26T23:28:46.183Z

Yes if you’re logged in the limit is per-user while if you’re not logged in it is per IP address. That was done specifically to deal with mapping parties where lots of people were being one IP address.

Use of group accounts is heavily discouraged in any case because it means there is no record of who has actually made an edit or any way to discuss it with them.

Robin_On_Wheels · 2024-10-27T13:29:51.487Z

Ok thanks. Yes we ask people to make their own account when they want to edit locations with our app. For the teambuildings it is easier to use the same group account since we always check all edits afterwards. Before we asked people to make their own accounts during the teambuildings, but then some users received very negative emails on some edits, before we had the chance to review them and correct them. Now we receive these emails and can communicate better with the osm community.

Do you know what the limit is for 1 user? Is this per day, per hour?

Fizzie41 · 2024-10-27T22:30:38.269Z

Getting away from the rate limiting issue, you should also be following the Organised Editing guidelines: Organised Editing - OpenStreetMap Wiki

SomeoneElse · 2024-10-27T23:48:42.088Z

To be fair there was a bit of previous discussion on this.

emvee · 2024-10-28T06:27:02.444Z

Robin_On_Wheels:

Do you know what the limit is for 1 user? Is this per day, per hour?

Reading this post and if I understand the problem correctly, I would change the App so that tile are collected “anonymously”, that is without auth-cookies.