Oh, right, I don't mean to blindly overwrite OSM data in these cases. I
mean to use good judgement and common sense, and use tools like Notes,
FIXME, or in-person checks to resolve the conflict. I'll update the wiki
page to be more clear.
Jacob
On 2022-10-12 14:34, Marc_marc wrote:
Hello,
Le 11.10.22 à 20:28, Jacob via Imports a écrit :
Use JOSM to manually handle the remaining 0.1% of conflation cases.
For these remaining issues, the deviations from reference data which
would cause problems with future updates are not marked using a
foreign key. Where necessary, perform on-the-ground checks to resolve
conflicts
In the framework of an import, I would tend to do nothing for
these objects (= don't touch them in osm) in order to treat them out
of import, if necessary by adding afterwards a note=* tag to warn
if the opendata of reference is in error or to correct osm if it is
osm which is in error.
idem if a value of your import is in conflict with a value of osm
(fictitious example: osm says red, your data says yellow...
don't overwrite osm)
thanks for taking the time to improve your import proposal,
everything else looks good to me.
I'll be happy to read the wiki page again after it's been updated,
so don't hesitate to let me know when it's up to date
Regards,
Marc
_______________________________________________
Imports mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/imports
_______________________________________________
Imports mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/imports
