Re: [Talk-et] [Imports] Ethiopia POI Import

2022-05-08 Thread Alex (AddisMap.com)
Hi Claire, Hi Imre,

Thanks for your responses.

Claire Halleux wrote:
> Regarding crowdsourced importing tools, HOTOSM tasking manager coupled to the 
> OSMSharp service developed by Ben Abelshausen (and recently added to HOTOSM) 
> works well for reviewing multiple objects within a bbox. It easily loads the 
> objects for review in a separate layer. Alternatively, for checking one 
> object at a time, MapRoulette is a great option.

I searched for OSMSharp and found only a low-level C# implementation
for OSM. Where can I check how this works coupled to HOTOSM tasking
manager? Would this work on smartphones? Because at the end of the
day, the POIs need to be verified on the ground. In the best case,
this would be as simple as on StreetComplete.

Thanks Imre for the thorough analysis.

Imre Samu wrote:
> based on  https://en.wikipedia.org/wiki/Subdivisions_of_Ethiopia
> - "woredas" (districts) --->  addr:district ?
> - "kebele" (wards)  --->  addr:ward ?

Yes it might absolutely make sense to map those.

> 2.)  I have found strange house numbers;  Is it valid numbers?
> $ osmium tags-count  AddisMapPOI.osm '*housenumber=*' | head
> 3845 "addr:housenumber" "New"

Most of those tags can probably be cleared. But there are actually
houses with the number sign "New", when a house number was not yet
assigned.

> 3.)  I have found some strange POI names.
> $ osmium tags-count  AddisMapPOI.osm '*=*losed*' | head -n 30
> 143 "name" "Closed Sook"

probably this should be converted to a disused:shop:kiosk tag and
would also need manual verification.

> $ osmium tags-count  AddisMapPOI.osm '*=+251*'  | head
> 3441 "contact:phone" "+251 "
> 20 "contact:phone" "+251 AV"
> 10 "contact:phone" "+251 NA"

We can safely remove such tags ...

> 7.)  The elimination of duplicates - so harder ;
> for example -  this will be imported:

Probably this needs lots of manual work, as due to the transliteration
there are often different spellings. Wondering if there are scripts
which use a fuzzy search for identifying such cases and make the
manual duplicate check more efficient.


Regards,

Alexander


Am So., 8. Mai 2022 um 02:13 Uhr schrieb Imre Samu :
>
> Hi Alexander!
>
> Thank you for opening the data! :-)
>
> Quick feedback about AddisMapPOI.osm.bz2
> - Probably some issues/comments are related.
> - need some data cleaning / re-tagging ..
> - and de-duplicates is a key!
>
> my suggestion:
> - split/partition the data by POI type ..
> - and let's first focus on the more stable POI types
> --  Diplomatic, Banks, College, ...
>
>
> details:
> 1.) Addresses:  is it possible to clean the tags?  most of them are not 
> documented in the osm wiki; so not usable for most of the programs.
>
> $  osmium tags-count AddisMapPOI.osm | grep addr
> 33260 "addr:subcity"
> 33088 "addr:woreda"
> 29356 "addr:description"
> 24033 "addr:housenumber"
> 21120 "addr:street"
> 176 "addr:city"
> 11 "addr:postcode"
> 10 "addr:kebele"
> 7 "addr:Kebele"
> 7 "addr:housename"
> 5 "addr:buildingname"
> 4 "addr:p.o.box"
> 2 "addr:floor"
> 2 "addr:full"
> 2 "addr:wereda"
> 1 "addr:country"
> 1 "addr:mobilephone"
>
> based on  https://en.wikipedia.org/wiki/Subdivisions_of_Ethiopia
> - "woredas" (districts) --->  addr:district ?
> - "kebele" (wards)  --->  addr:ward ?
>
>
> 2.)  I have found strange house numbers;  Is it valid numbers?
>
> $ osmium tags-count  AddisMapPOI.osm '*housenumber=*' | head
> 3845 "addr:housenumber" "New"
> 655 "addr:housenumber" "new"
> 531 "addr:housenumber" "NA"
> 451 "addr:housenumber" "AV"
> 141 "addr:housenumber" "1"
> 133 "addr:housenumber" "shed"
> 108 "addr:housenumber" "2"
> 95 "addr:housenumber" "Shed"
> 91 "addr:housenumber" "4"
> 79 "addr:housenumber" "3"
>
> 3.)  I have found some strange POI names.
>
> $ osmium tags-count  AddisMapPOI.osm '*=*losed*' | head -n 30
> 143 "name" "Closed Sook"
> 72 "owner" "Closed"
> 22 "name" "Sook (closed)"
> 20 "name" "Sook(closed)"
> 19 "owner" "Closed Sook"
> 13 "name" "Closed"
> 12 "name" "(closed)Sook"
> 9 "name" "(Closed)Sook"
> 7 "name" "Sook (Closed)"
> 6 "name" "Sook(Closed)"
> 5 "owner" "No Information/closed"
> 4 "name" "Closed Café"
> 4 "name" "Sook Closed"
> 3 "name" "Closed Bar"
> 3 "name" "Closed Grocery"
> 3 "name" "Closed SOOK"
> 3 "owner" "(closed)"
> 2 "name" "Abdela Sook(closed)"
> 2 "name" "Abeba Sook Closed"
> 2 "name" "Closed Chat Bet"
> 2 "name" "Closed Wholesaler"
> 2 "name" "Kurs Bet Closed"
> 2 "name" "Pepsi Sook(closed)"
> 2 "owner" "(Closed)"
> 2 "owner" "Closed Café"
> 1 "contact:phone" "+251 Closed"
> 1 "name" "(Closed Sook)"
> 1 "name" "(Closed)Grocery"
> 1 "name" "(closed Chatbet"
> 1 "name" "(closed) Grocery"
>
>
> 4.)  I have found some strange phone numbers:
>
> $ osmium tags-count  AddisMapPOI.osm '*=+251*'  | head
> 3441 "contact:phone" "+251 "
> 20 "contact:phone" "+251 AV"
> 10 "contact:phone" "+251 NA"
> 4 "contact:phone" "+251 911"
> 4 "contact:phone" "+251 N.A"
> 3 "contact:phone" "+251 115510694"
> 3 "contact:phone" "+251 115529979"
> 3 

Re: [Talk-et] [Imports] Ethiopia POI Import

2022-05-07 Thread Claire Halleux via Talk-ET
Hi Alex,

Having personally seen Addis Ababa changing so much between 2007 and 2019,
I think that sounds like a good strategy.

Regarding crowdsourced importing tools, HOTOSM tasking manager coupled to
the OSMSharp service developed by Ben Abelshausen (and recently added to
HOTOSM) works well for reviewing multiple objects within a bbox. It easily
loads the objects for review in a separate layer. Alternatively, for
checking one object at a time, MapRoulette is a great option.

Claire

On Sat, May 7, 2022 at 1:09 PM Alex (AddisMap.com) 
wrote:

> Hi,
>
> I have been in touch with Binyam of the Ethiopian OSM Community on th
> OpenStreetMap Ethiopia Telegram group and a short call.
>
> > the gathered datasets between 2010-2016 are considered valuable. even
> though,  it is not that recent
> > I also noticed some points overlapping with the existing features. Maybe
> as you said checking the data on a small aerial to get and idea of how many
> percent still could be valid is a good idea.
>
> So we will basically try to go ahead with this import, in cooperation
> with the local community.
>
> The next step will be to evaluate which percentage of the points in
> some sample areas are still existing and how many overlaps are there.
> Then we will decide on how to go forward.
>
> In the meantime I am wondering if there are any existing tools / apps
> / workflows to verify this data and import the verified data to OSM.
> We are thinking about using the HOTOSM Tasking manager to subdivide
> the area and then check on the ground. We are not sure yet how apps
> like Vespucci can be used here to make this most efficient.
>
> Kind Regards,
>
> Alexander
>
> ___
> Imports mailing list
> impo...@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/imports
>
___
Talk-ET mailing list
Talk-ET@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-et


Re: [Talk-et] [Imports] Ethiopia POI Import

2022-05-07 Thread roptat
My personal favorite method is to get a GPX file of the points in the area I'm 
going to map and import it in osmand. They will look like favorites, but you 
can change the color of the whole group which is nice. Then, just travel to 
these points and take a note of which ones are there, not there or simply off 
by a few meters.

For most POIs, osmand also has a contribution plugin that will work nicely. I 
don't use it often, I prefer to take a picture instead and work from home as I 
don't like editing osm on my phone.

I've been using this method to integrate power substation data in France, using 
opendata. It works very well for me. I got the GPX extracts from osmose, but 
I'm sure you'll find a way to extract the data even without osmose :) If this 
is opendata and the community already uses osmose, maybe you could use it too?

HTH!

On May 7, 2022 2:05:01 PM GMT+02:00, "Alex (AddisMap.com)"  
wrote:
>Hi,
>
>I have been in touch with Binyam of the Ethiopian OSM Community on th
>OpenStreetMap Ethiopia Telegram group and a short call.
>
>> the gathered datasets between 2010-2016 are considered valuable. even 
>> though,  it is not that recent
>> I also noticed some points overlapping with the existing features. Maybe as 
>> you said checking the data on a small aerial to get and idea of how many 
>> percent still could be valid is a good idea.
>
>So we will basically try to go ahead with this import, in cooperation
>with the local community.
>
>The next step will be to evaluate which percentage of the points in
>some sample areas are still existing and how many overlaps are there.
>Then we will decide on how to go forward.
>
>In the meantime I am wondering if there are any existing tools / apps
>/ workflows to verify this data and import the verified data to OSM.
>We are thinking about using the HOTOSM Tasking manager to subdivide
>the area and then check on the ground. We are not sure yet how apps
>like Vespucci can be used here to make this most efficient.
>
>Kind Regards,
>
>Alexander
>
>___
>Imports mailing list
>impo...@openstreetmap.org
>https://lists.openstreetmap.org/listinfo/imports
___
Talk-ET mailing list
Talk-ET@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-et