Hej alle. For nyligt blev jeg opmærksom på at StreetComplete-appen ikke tilføjer maxspeed=50 når man angiver en vej som byzone (det samme gælder for landzoner), fordi en udlænding der anvender StreetComplete ikke nødvendigvis kender trafikreglerne i et fremmed land. Som jeg forstår det bør man ikke have maxspeed:type=DK:urban eller source:maxspeed=DK:urban uden maxspeed=50 og derfor ønsker jeg at tilføjedet tag til alle veje i Aalborg Kommune som opfylder følgende:
Vejen er tagget med enten maxspeed:type=DK:urban eller source:maxspeed=DK:urban
Jeg har aldrig prøvet at foretage en automatisk rettelse på denne måde før, så jeg indskrænker mig til Aalborg Kommune, da det er der hvor jeg har mest lokalkendskab. I princippet kunne man udføre denne rettelse over hele Danmark. Jeg sætter pris på al feedback!
As I understand it, when a way is tagged with maxspeed:type=DK:urban, it is not necessary to add maxspeed=50because data users (map makers, router apps etc.) can look up what the max speed for urban areas in Denmark is, for instance here https://wiki.openstreetmap.org/wiki/Default_speed_limits The advantage of not tagging maxspeed=50is that if ever the urban area max speed in Denmark changes, all that needs to be changed is the information in the default speed limits table, not the maxspeed=*tags on all urban roads in Denmark.
I agree that this approach would be ideal, if most data consumers followed it, but I think only Osmand consumes maxspeed:type (and noone consumes the more widespread source:maxspeed). However, even if most consumers did look up the default max speed for each country, there is no harm in adding the explicit value. A router could prioritise the dynamic value if they wanted, while ignoring the fixed one.
If the default speedlimit were to change, I think it would be as simple as changing all maxspeed=50 on ways that also have maxspeed:type=DK:urban to the new default speed limit, which I don’t think is a particularly complicated edit.
In other countries it is. For example in France it is common that cities have signs at the entrance to the city, but then also inside cities have 50km/h maxspeed signs. If the maxspeed were changed presumably it would still be 50 until the physical signs were replaced.
In France they did change maxspeed:rural from 90 to 80 in 2018. But then later allowed individual departments to change it back to 90 depending on number of lanes, etc. But only on departmental roads, not national roads. IMHO that has lead to a mess, that is still being sorted out. I have driven on a lot of French roads, and done my best to set speed limits.
Anyway, I think that it makes sense that maxspeed should contain the max speed.
even if most consumers did look up the default max speed for each country, there is no harm in adding the explicit value. A router could prioritise the dynamic value if they wanted, while ignoring the fixed one.
If the default speedlimit were to change, I think it would be as simple as changing all maxspeed=50 on ways that also have maxspeed:type=DK:urban to the new default speed limit, which I don’t think is a particularly complicated edit.
(By “the dynamic value” I mean maxspeed:type=DK:urban in case that wasn’t clear)
I agree with you in principle. We should not tag exclusively for the renderer/router/whatever consumer.
Aside from the fact, that most consumers do not consume these tags, however, I don’t think your perspective on including maxspeed= is widespread/popular. Most instances of source:maxspeed=*:urban exist in combination with maxspeed=, as can be verified by checking the combinations in this taginfo list. For maxspeed:type=*:urban, about 50% are combined with maxspeed=. I suspect this difference is mostly due to StreetCompletes mode of tagging, but that’s just a guess.
On the basis of this data, I think most people think maxspeed:type= and source:maxspeed= should exist alongside maxspeed=.
I would like to know if you still think adding this “reduntant” but otherwise correct data is problematic, and if so, why?
I started my post with “As I understand it,” indicating that I’m not sure so you may very well be right. I don’t think its problematic, but possibly a waste of time to add maxspeed=50 to maxspeed:type=DK:urban
And it is not tagging for the router to tag an explicit value.
Especially when not all highways have an implicit value, and even for those that do in can be tagged in various ways (source:maxspeed, maxspeed:type etc).