Jan Schulte

Regarding `toilet_wheelchair` and `wheelchair_toilet`: When an API Client (iOS or Android) sends data to create a new POI they send toilet_wheelchair. The API then converts `toilet_wheelchair` to `toilets:wheelchair` for OSM.

To narrow the problem down I did the following: - Wrote some tests to ensure that `wheelchair` and `toilets:wheelchair` are actually correctly set. This works as expected. - Wrote another...

@tschob If the iOS App could use `wheelchair_toilet` that would be good, because Android also uses that identifier already. The Backend takes the value as `wheelchair_toilet` but makes sure that...

It appears to be that ead9fbb2 already smoothed the way for this change.

Steps to do here: - Migrate values from `authentication_token` over to `api_key` (has to be done once) - use `api_key` key field from now on, every time a user has...

This also might mitigate https://github.com/sozialhelden/wheelmap-privateissues/issues/42

I found out that I missed one important aspect: There are users with `api_key` already set. They probably have the wheelmap embedded somewhere. When we migrate `authentication_token` to `api_key` these...

I'm putting this on hold right now because it became much more complex than first anticipated.

I start to line up some ideas and thoughts regarding this topic. The current API cannot be touched in terms of URL structure. This would probably break behavior with all...

@Hoverbear Concerning the redirect: You mean issuing a HTTP redirect to the client then?