When to use maxspeed:type, zone:maxspeed or source:maxspeed?

[campbelltree]

@ftrebien

Maybe, instead, we should adopt values matching default legal speed limit cases like maxspeed:type=BR:arterial, maxspeed:type=BR:collector, maxspeed:type=BR:local, maxspeed:type=BR:road, maxspeed:type=BR:single, maxspeed:type=BR:dual, etc. (or localized values such as maxspeed:type=BR:arterial, maxspeed:type=BR:coletora, maxspeed:type=BR:local, maxspeed:type=BR:estrada, maxspeed:type=BR:simples, maxspeed:type=BR:dupla).

I agree with this. Don’t tag anything as BR:urban, only use the categories that actually exist (maybe local/collector/coletora/arterial/rapido?)

@ftrebien

as source:maxspeed continues to be added at almost the same rate as maxspeed:type.

I do not think that any schema or mechanical reading implications should be imposed on source:* tags. URLs to images or the reference code of a piece of legislation should continue to be acceptable values for source:*, and they should only carry information that you can’t get from source= on a changeset.

[dieterdreist (Martin Koppenhöfer)]

@ftrebien

I am wondering if we should really add maxspeed:type=BR:urban to every urban way in Brazil that has no signage (many of which currently use source:maxspeed=implicit), from urban arterials (default speed limit of 60 km/h, real average speed close to that if not congested, corresponding to highway=secondary and highway=primary) to residential ways (default speed limit of 30 km/h, real average speed much lower than 30 km/h, corresponding to highway=residential)

if there are different default limits, you should not conflate them of course. Rather you should have 2 defaults, one for urban arterial roads, and one for residential roads, e.g. source:maxspeed=BR:urban_residential or BR:urban_arterial.
The same goes for rural roads if there are different defaults. (or better use the names you have suggested if these are closer to your legal reality).