WOF#7. Import guidelines

Posted by WorstFixer on 2 June 2012 in English (English)


Multiple persons asked me to review import guidelines. I translated pages of text into this:

Import Guide Lines

Comments? Ideas?

Comment from quantumstate on 2 June 2012 at 21:46

This generally looks good to me. I would suggest moving check license a bit higher up the list though to save wasting time converting data if it it not possible to use it.

Also it might be worth putting talk-country@ more explicitly in the Discuss section.

Comment from Gnonthgol on 2 June 2012 at 22:14

As quantiumstate writes and maybe add discussion with the local comunity with ‘check quality’. It is important to see if the import is wanted by the comunity befor you start the import process.

I do not quite like the linear path. There are no problems to start discussing an import before you check the quality, or to check the quality of the data before you transform it. But don’t upload before you have discussed the changes and given people time to go through what you intend to upload.

Otherwise this is great work. I love the nice graphical representations you make. It would make the wiki a lot better if you can document the process of importing better. It would be more worth to try and prevent people from submitting bad data then to fix bad data with with bots.

Comment from skorasaurus on 3 June 2012 at 15:40

This is a great start! Although I’ve only done one import before, I’d probably also move the license to the second step, after all, doing all of the work and then finding out that you cannot add the data would be disappointing.

Comment from compdude on 3 June 2012 at 21:50

That flowchart looks very good, though I agree with some of the suggestions that other users are making. I suggest you create a page on the OSM wiki that describes this import/upload process.

I have one question though. Why do you think that people should create a separate account for uploading the data?

Comment from Zartbitter on 4 June 2012 at 07:50

Why do you think that people should create a separate account for uploading the data?

That was mentioned as good practice at least on the mailing lists. One example: the license change. A user declines the license change, but had also imported some good data which is fine for the new license. Without an import user account is is a mess to sort things out.

Comment from LivingWithDragons on 5 June 2012 at 15:50

Some aspects/practices of importing data depend on the data (it’s size, it’s frequency of updates). If you are uploading a small area and will only do that once, then it might make more sense to do that in your existing account.

The last line “be ready to revert fast if all goes wrong” is a bad thing to state. There should be points on testing the whole import process has gone well, and test/plan (in advance) a way you will be able to revert the changes if needed.

Transform could include “break into smaller geographical chunks if appropriate/needed”

Login to leave a comment