[OSM-talk] Good practice, and should we rely on defaults?

[Minh Nguyen]

Vào lúc 03:12 2022-04-08, Richard Fairhurst đã viết:
> A machine-readable GeoJSON file with a few defaults per polygon (LHD vs 
> RHD, bikes allowed on trunk, etc.) would not necessarily be a bad thing. 
> If it was kept relatively simple then it might get widespread adoption. 
> But anything as stupidly complex as the opening hours syntax, say, is 
> not going to fly.

In case anyone is curious, some editors and data consumers do maintain 
GeoJSON files of defaults, for example:

https://github.com/Project-OSRM/osrm-backend/tree/41dda32546399f1dc12af1de41668993de44c7dc/data/
https://github.com/ideditor/country-coder/blob/main/src/data/borders.json
https://github.com/openstreetmap/iD/blob/7b0127f5e7b98214782574698c5fc8c970ed8caa/data/territory_languages.json

For every one of these files in open-source repos, you can imagine there 
are a dozen in closed-source projects, often compiled by quickly 
consulting Wikipedia. One hopes they're at least reasonably consistent 
with each other.

And then there's the wiki's attempts at achieving machine readability. 
I'm pretty sure the most recent change to the default speed limit table, 
an entry for the City of Minneapolis [1], bucks osm-default-speeds's 
expected syntax. But what is to be done about individual municipalities 
setting their own default speed limits, default U-turn restrictions [2], 
or default street parking restrictions [3]?

[1] https://wiki.openstreetmap.org/wiki/Special:Diff/2307998
[2] 
https://i1.wp.com/bikeroute.com/NationalBicycleGreenwayNews/wp-content/uploads/2013/10/Cols4CityLimits.jpg
[3] https://commons.wikimedia.org/wiki/File:MUTCD-CA_R30D.svg

-- 
minh at nguyen.cincinnati.oh.us