Figure out a better solution for max speed.

[xivk]

The maxspeed values are now all explicitly defined, this is not sustainable. Perhaps we could have a maxspeed with an explicitly defined 'unit'.

[hdelva]

It's not just units though, there are also tags such as maxspeed=RO:urban and maxspeed=signal. I think the only thing we can realistically expect to do with these is to encode them with osm:hasTag. The 'cleanest' way to determine which tags have a well-defined and which ones don't (yet) seems to be a lookup table, unfortunately.

The plan was to create those maxspeed values automatically though, nobody should have to read/write the config file. The code to automate this will probably look like a clump of spaghetti, but at least it's separate from the code that generates the tiles.

[xivk]

Ok, if automating the config file is the way to go we can leaving this as is.

[hdelva]

I think you had the right idea here actually. The mapping shouldn't be an issue, but we should add the unit. Route planners can use the km/h values just fine, but there are also use cases where the original value and unit are needed - mostly user-facing stuff.

openplannerteam/routable-tiles#32 has a suggestion for a better solution. This might be a breaking change though.