[Imports] UPLOADING U-WIMP project data to osm

[Mike Thompson]

On Mon, Nov 7, 2022 at 2:44 PM Stellamaris Nakacwa <sn00013 at mix.wvu.edu>
wrote:

>  am not sure I can write an import/upload process before successfully
> uploading the data
>
The whole point is to write the process instructions *before* you start the
import/upload so the OSM community can review and provide feedback.  I
don't think these instructions have to be super complicated, and if you
learn something during the process you can augment them later with "lessons
learned"


> I will make sure that in the guide, I emphasize that for the new mappers
> as more, I am just going to simply edit my .csv and then reconvert it to a
> geojson.
>
Ok, you should share a link to the full .csv, and a link to the final
GeoJSON file after you have made the changes.  This should be done well
before the import/upload starts so that the community can review.



> I am following the normal JOSM edit guideline
> <https://toolbox.hotosm.org/pages/data-cleaning-upload-and-quality-assurance/5.1-data-cleaning-with-josm/>
> to perform the upload.  [Downlaod data in AOI, merge, validate, upload]
> My data is just water points, nothing extra. So, I do not think I have
> anything complicated.
>
 You probably can either reference those guidelines in your proposal, or
cut/paste from it.   I don't think your process will be exactly as shown in
those guidelines, so selectively cutting and pasting will probably be
best.  For one thing, you have one large file, and in the guidelines they
are starting with one file per feature.
Also,
* I believe your file is quite large, and reviewing all of those points in
one sitting in JOSM using the todo list might not be practical.  I would
suggest splitting the final file into more manageable chunks.
* Please make it clear in your instructions that if there is an existing
well or spring in OSM, that you will preserve it, copy tags from the import
data as appropriate, and delete the imported point.  You should not be
creating duplicates, nor should you be deleting existing data in favor of
the imported data.
* Are you doing this all yourself, or will there be people helping you?  It
seems like a lot of data for one person to review/import.  If you are going
to have multiple people, how are you going to keep track of who is doing
what?  The Denver building import was set up using the tasking manager,
such that when a mapper started mapping a task they automatically got both
the OSM data and the import data for that location.  This does require some
web accessible place to store the import data.
* The import should not be done under your regular OSM account, you should
create a separate account for imports (maybe you mentioned this already in
your proposal and I missed it).


Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20221107/7cc64f2c/attachment.htm>