Closed eginhard closed 2 months ago
Thank you for opening the issue! I will discuss this with @chnuessli and create a fix for the issue.
Hi @eginhard. Thank you for reporting this isse.
For me there are two issues identified in this issue.
For me, access=no is and was always for defis that are not accessible fast and free. But permissive or private are more adequate sometimes.
For the defi-form we will improve the form selection to the following via dropdown:
Access
@eginhard What do you think?
Internal Link: https://chnuessli.atlassian.net/browse/DEFI-42
@chnuessli Yes, that sounds good.
@eginhard We updated the web-ui. Can you please review and give a feedback if this is how it is expected. There is now also an info-button with more information about the different values to set for access.
Sorry for the late feedback @elektrolytmangel Yes, that looks good, thanks for updating it!
Thanks! An update for the app with similar functionality is on the way. I will update the issue as soon it is live on iOS and Android.
The feature is live on iOS and will be the next hours / days on Android.
Somebody on the OSM World Discord server noticed that a lot of defibrillators in Switzerland are tagged with
access=no
(>90% of the worldwide cases: https://overpass-turbo.eu/s/1Jda). Most of them come from the Defikarte and one related import (https://www.openstreetmap.org/changeset/134128958). Many indeed seem to be located in companies/offices, butaccess=private
would be a better fit there. Others are quite clearly meant for public access (https://www.openstreetmap.org/node/11536529969, https://www.openstreetmap.org/node/10781820605), or are even explicitly tagged that way in thedescription
(https://www.openstreetmap.org/node/11371093369, https://www.openstreetmap.org/node/10203684217, https://www.openstreetmap.org/node/7786275859).I guess this is because the Defikarte app and website form's switch for "Zugänglich/Accessible" defaults to
False
. There is no explanation at all for what this term means, so many people might just leave the default value. Providing an explicit choice between public and private access might be better here, defaulting to public (and otherwise taggingaccess=private
instead ofaccess=no
).