[OSM-dev] AND data integration

[Sander Hoentjen]

Hi,

First of all I would like to say that this is just some random rambling of
me, not based on much knowledge of the subject.

> Hello everybody!
>
> I'm Lex Tiekink, working at AND Automotive Navigation Data.

A big thank you to AND for providing the data! (and of course to everybody
that helped in making it happen)

Now on to the point of this email: How should the AND data be put into the
map?

Here are the 3 possible ways (well there might be more ways, feel free to
add), and the estimate of time they will make.
Now as i already stated i don't have muck knowledge on the subject, so
someone who is better educated should feel free to improve the estimates
9actually i just made them up, without any research, but if the estimates
are improved it might become a handy tool in deciding how the import
should take place.

At some point in the future we will know how to map AND features to OSM
features, I will call this T=0, and I expect that this will be soon.
T=1 will be one day after T=0

possibility 1) We just dump the AND data into OSM
- script have already been written to convert AND to OSM, so i expect that
this can be done before T=5
- What is left is to remove duplicate ways, and connect the "old" OSM data
that AND didn't have to the "new" OSM data that came from AND. How long
this will take is hard to estimate, but let's say 60 days, the the total
import will be finished at T=65
downsides: lot of manual work, existing work will be mostly lost, so it
can be demotivating for people that have done al lot of work already
upsides: all work is relatively easy so there are a *lot* of people that
*can* contribute to the process, starting from T=5 we will have a complete
map of NL, albeit a bit ugly because of duplicates.

possibility 2) We import only into areas where no OSM data is available
- Should be fairly easy to do, expect to finish before T=10
- What is left is to manually import AND data into places where OSM had
coverage, but AND has more ways. Also we "must" add extra (routing) info
AND has to the existing ways. I expect this to take longer then the
previous, say 80 days, so the total import will be complete at T=90
downsides: even more manual work, chance of forgetting information that
AND did have
upsides: None of the work that has been done already will be lost.

possibility 3) Like 2, only now we write awesome scripts that detect
duplicate ways, only import data not existing yet and updating existing
ways with extra information that is available
- Hard to do, expect to finish at T=100 to infinity, depending on how
perfect the script must be (there is no such thing as perfect).
- What is left is to fix up manually the few things the scripts couldn't,
totally done at > T=120
downsides: only technically skilled people can contribute and they are a
minority, it takes long, hard to decide when the scripts are "good enough"
to finally do the import
- upsides: if done properly, the scripts can be reused when new data is
given to us, no existing work is lost


Now if someone can please alter my time estimates where they are incorrect
(read as everywhere). :)

Thought are welcome,

Sander