[OSM-talk] [Imports] Import guidelines review

[Peter Wendorff]

Am 06.06.2012 12:16, schrieb Worst Fixer:
> It ist not importing, but it ist a large part of it. It should be not
> on import guide lines. Import guide lines should only cover actual
> imports.
You're right: that's not in the current written version of the import 
guidelines.
But the current written import guidelines require discussion with the 
community, and if you read past discussions for imports on the mailing 
list archives, you will see, that often the possibility of exactly this 
kind of "semi-importing" at least has been proposed, sometimes it has 
been used after that "idea" mentioned by a commenter.

On top of that you could find many examples of these "semi-imports" in 
the wiki as that has been used frequently to store and organize the 
manual work on these datasets.

Please stop referring to the import guideline as a hard law in the 
context of rewriting them to make them easier.
The written import guidelines are something like "minimum requirements": 
At least follow them, but feel free to do more, and discuss the issue 
with the community.
Semi-imports are often considered as a better solution: to fix this 
external data source availlable for mappers, but let the community 
import the data in line with local knowledge and a working human mind to 
compare with existent osm data.

IF you really want to work on making the import guidelines better, IMHO 
(and as you see, some people agree with me) the possibility of 
semi-importing in the sense of providing readable datasets is a valid, 
useful, but sometimes less known option.

regards
Peter