Frédéric Rodrigo
Frédéric Rodrigo
Due to many issues the data is still not up to date https://osmose.openstreetmap.fr/en/issues/open?source=408822&item=xxxx&useDevItem=all https://osmose.openstreetmap.fr/en/issues/open?source=408823&item=xxxx&useDevItem=all https://osmose.openstreetmap.fr/en/issues/open?source=408824&item=xxxx&useDevItem=all https://osmose.openstreetmap.fr/en/issues/open?source=425086&item=xxxx&useDevItem=all
Data look updated. But something wrong. Look like not using the new code, or data not update but only the update the date.
1. As you propose, I think the data should be cleaned.
Removing check on node in progress 2. Welcome in PR if you want it quickly
1. Done http://osmose.openstreetmap.fr/fr/errors/graph.png?item=6040&class=802
Osmose suggest to change "Ale Wee" -> "Allée Wee" due to the country is configured with Luxembourgish French rules https://github.com/osm-fr/osmose-backend/blob/master/osmose_config.py#L619 But the whole area does not look to use french...
I suppose we cannot have a strict boundary for languages mapping area ? (We have done it in this way in Belguim with belgium_wallonia_french_community and belgium_wallonia_german_community) We can configure Luxembourg...
It may already have one. To be located.
I think there is already a check for common nodes on different layers. But this case maybe especial.
It is not miss classified. This location also include `:LocalTouristOffice`.