[Talk-ca] Imported frustrations

[James Ewen]

On Thu, Oct 6, 2011 at 12:45 PM, Harald Kliems
<harald.kliems at mail.mcgill.ca> wrote:

> Finding and fixing these errors has been a huge timesuck and not much fun.

Wow, using the tool you just showed me made the job of finding and
correcting the errors in my local community a very quick and easy
task... trying to find duplicate ways is pretty tough just going by
what you can see. Finding unconnected ways is a little easier as they
show up visibly.

I just cleaned up about 20 square miles of area in about 10 minutes.

There's an even bigger issue where the canvec imports stop well shy of
the existing roads, or issues like this:

http://tools.geofabrik.de/osmi/debug.html?view=routing_non_eu&lon=-112.55995&lat=53.71582&zoom=13&opacity=0.98

I was thinking that it might be an idea where instead of dropping the
close match CanVec Imports, that if they were imported, but marked
such that they would be easily found and deleted if not desired, or
the existing road could be deleted, and the CanVec import modified to
make it the new way.

Such as in the case above where the CanVec way was left out of the
import in deference to the existing road, it would be very easy to
just modify the CanVec way to make it part of the database, and delete
the less accurate hand drawn way. It's more of a pain to have to go
and find the CanVec ways again, and import them so you can delete the
hand drawn way.

If there were a way to have the CanVec ways that were determined to be
duplicates shown on a map (kind of like showing roads under
construction), one could easily compare the two ways, and with a
simple edit and delete combination, make the CanVec way the one to
keep, or a simple delete to remove the CanVec way.

Speaking of CanVec imports... anyone going to tackle importing roads
into Saskatchewan some day? It gets pretty bleak on that side of the
border in a hurry!

http://www.openstreetmap.org/?lat=52.091&lon=-109.473&zoom=9&layers=O

-- 
James
VE6SRV