On 22/8/23 14:32, Ben Ritter wrote:
Doing small targeted mechanical edits like this sounds like a good
workflow to me.
My recommendation would be to structure the program in two steps:
1. The first script calculates all of the changes that it wants to
make, and writes it to CSV, with all of the details required for step 2.
2. The second script reads the CSV and prepares the edit.
The primary benefit is that you can inspect the proposed edits in
Excel and post them on a wiki page for others to see.
There are more steps than that now...
Run the render .. that generates a number of error files in text format.
Select the general error file you want to work on and put it into
'excell' (or libreoffice cal) and convert the text to columns
Remove the errors you are not targeting this time, Get the
nodes/ways/relations into a single sheet and save that as .csv
Now open JOSM and download the nodes/ways from that csv data .. This
gives you the complete OSM data for the things you want to change. Save
that .. it is an .osm file
Now open the .osm file make the changes and change the node/way/ header
to signify that these are to be chang4ed - save that flie as the change
file and save the one that the program is not changing to another file
for checking and possible manual change..
Now open JOSM and open the change .osm file and download to OSM...
That is 5 steps .. checking can be done using JOSM. Looking at them from
the csv file only gives you the osm reference number nothing else...
you'd need to refer that number to the osm data base to see the full data.
_______________________________________________
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au
