[Imports] import guidelines, new rules proposal
bryce2 at obviously.com
Sat Jun 8 00:48:03 UTC 2013
On Fri, Jun 7, 2013 at 3:38 PM, Jason Remillard
<remillard.jason at gmail.com>wrote:
> A "good" import results in OSM data that is indistinguishable from
> normally mapped data.
I'll add to that: a "good" import can be tweaked later by hand, and not
result in duplicates,overwriting,
or other bad effects.
(My "osmsync" import tries to be good: for example respecting a POI shift
of 100 meters made by hand
even if the rest of the node's keys get updated by newly imported tags).
Duplicates are a bit more of a problem: I'd love to have a JOSM feature
where I could create a proposed import, then quickly cycle through each POI
and visually check for duplicates and proper positioning.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Imports