[Imports] UPLOADING U-WIMP project data to osm

[Stellamaris Nakacwa]

Thank you, Mike,
I understand what you are saying but am not sure I can write an
import/upload process before successfully uploading the data and this is
the last step to that.
Talking about the corrections: Since we already corrected the data, 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.
A snippet of the csv download before changes are made:
[image: image.png]

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.

Stellamaris


On Mon, Nov 7, 2022 at 2:48 PM Mike Thompson <miketho16 at gmail.com> wrote:

>
> Hello Stellamaris,
>
> On Mon, Nov 7, 2022 at 11:55 AM Stellamaris Nakacwa <sn00013 at mix.wvu.edu>
> wrote:
>
>
>> Unlike most of the imports, the data that I am about to upload was raw
>> data collected from the field using all the tools described in the wiki. We
>> collected the dataset using kobo and within kobo, I described the osm
>> language on the go. The kobo collect app had both English language and .osm
>> languages. So, the collection directly fed into Wpdx and we also had access
>> to the .osm file at once.
>>
> 1) If we had access to the original data we could see this
> 2) At the very least, you collected it with one set of OSM tags, but those
> are going to have to be translated to another set of OSM tags based on the
> discussion here (e.g. name=* becomes type=*, plus all of the suggestions
> from Frederick and others).  We should see the data both before that
> translation and after, as well as any tools/scripts used to do the
> translation.
>
> Also, again, there are no detailed instructions on how the actual import
> is going to be performed, like was provided for the Denver Buildings
> import.
>
> What happens when OSM already has an object representing the same physical
> feature that is being imported?  Will there be duplicates after the import
> (hopefully not). Will the existing data be maintained, and where
> appropriate the tags from the imported feature merged with that existing
> feature (and the imported feature discarded)?  This is desirable as it
> preserves the history in OSM.
>
> Mike
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20221107/fecd40b7/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 24299 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20221107/fecd40b7/attachment-0001.png>