[Imports] Best practices for address imports

Martin Koppenhoefer dieterdreist at gmail.com
Mon Nov 25 14:31:16 UTC 2013

2013/11/24 Martin Raifer <tyr.asd at gmail.com>

> * If you had an address dataset that positions the addresses at or near to
> the respective building entrances: Wouldn't it make sense to not conflate
> the address data with building outlines? (Because by conflating the
> usefulness of the data would actually be reduced.)

This has already been answered by some mappers, and I'd like to add my +1
to it:

a) this depends on what the address represents (entrance or area) and

b) there is a tag to map an entrance: entrance=yes/main etc. so even if the
address represented an address rather than an area I'd still add the
entrance-tag to make it clear and

c) practical experience shows that those coords in the source dataset would
not necessarily be "precise" enough to just take them as they are (for
instance you'd also have to have an associated dataset with building
outlines in order to grep the right position topologically), it is (IMHO)
more important to have a good relative position (e.g. in the center of the
front side of the building) than absolute coordinates (e.g. should be in
the center but the absolute coords show them in the corner of the OSM
building because they used a different building position / outline than OSM

> * What are good ways to manage quality assurance after the import?

have an active community? If you don't have it (yet) in the area, it is all
more or less pointless, your main efforts in this case should be to create
and raise a community in the future.

> * Is there a practicable way to keep the imported data in sync with the
> source data?

as long as nobody touches it, yes (i.e. either no community or everything
was perfect ;-) ), otherwise it will be quite impossible (and it is IMHO
also not desirable to drop subsequent community refinements on imported
data in favour of updating from the original source).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20131125/3f0d8b03/attachment.html>

More information about the Imports mailing list