-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all:
Just a short update on this import.
As of 18th October, 9,072 out of 14,020 nodes (64.71%) have been
imported to OSM.
Of them,
6,652 (73.32%) are hamlet,
1,524 (16.80%) are isolated_dwelling,
489 (5.39%) are unknown,
200 (2.20%) are village
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Ralf:
I see now that I have misunderstood from the beginning what you wanted
to explain, so I beg your pardon for making you loose your time.
I've been thinking all this time that what you proposed to do was to
unify in one node several nodes wit
Hi Rafael,
"Although I answered to this before, I would add that having one single
> name in several nodes, with 1, 2, 3... or A, B, C... or I, II, III...
> added to the end to differentiate them is quite common in many
> countries in Africa. You can find many of them in Central African
> Republic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Ralf:
I've just replied a minute ago to this email in another previous
email, but I paste here again my opinion on this issue:
"Although I answered to this before, I would add that having one single
name in several nodes, with 1, 2, 3... or A, B,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf:
I comment inline some points I didn't answer, and more on the A, B,
C... point.
On 10/10/14 11:11, Ralf Stephan wrote:
> A few more observations, probably not new to fellow importers,
>
> * often when it seems UNMIL objects are placed in the m
+1 for alt_name_x
BTW there are truncated place and clan names too. Places mostly where long
names with 'Village' were truncated
to 'Vi' or 'Villa' or such (maybe a common max length?).
On 14 Oct 2014 12:37, "Rafael Avila Coya" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi, Bla
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Blake:
I had a look to this example. I also think that in these cases we
should keep both nodes, and if unsure just leave them in their
position, maybe adding a fixme tag. Both names are completely
different, so there must be a reason they are the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Blake:
I am answering some emails after long because I couldn't cope with
everything last two/three weeks.
There are 324 nodes out of the original 14,020 nodes with a / in their
name or is_in:clan tags. Maybe, based on our experience so far, we
c
First, Bopolu was an example name, I don't remember which it was actually.
On Fri, Oct 10, 2014 at 12:44 PM, Rafael Avila Coya
wrote:
> About the nodes Bopolu A, B, C..., I wouldn't condense them into one,
> as doing so we are loosing information on different settlements, or
> parts of the same
Hi Ralf:
About the nodes Bopolu A, B, C..., I wouldn't condense them into one,
as doing so we are loosing information on different settlements, or
parts of the same whole settlement.
I would better leave them as such, and maybe (that should be
discussed) tag them as place=neighbourhood, leaving t
A few more observations, probably not new to fellow importers,
- often when it seems UNMIL objects are placed in the mid of the jungle,
there is an isolated dwelling somewhere
- often when I encounter very different GNS vs. UNMIL place names in a
hamlet area it's worthwhile to look far
Rafael,
I for one am fine with these natural rules.
On Sat, Sep 27, 2014 at 11:00 AM, Rafael Avila Coya
wrote:
> ..
> . I am more for
> changing the '&' to "and" in general, but surely they need to have an
> space both sides.
> ...
>
> So "Marbo #2"
> would be correct, and "Marbo # 2" incorr
Hi,
One other comment I would make on the process now that I have done a
several hundred nodes is that what looks like two names on one
settlement could very well be two separate names for two different
locations in the same village.
For example:
https://www.openstreetmap.org/#map=18/6.4232
I am pretty sure that names with / in them are really a list of
different names or alt_names as well call them.
I was thinking maybe after the initial placement is over we might
consider going through and moving the / names into the alt_name_ fields.
Blake
On 9/27/2014 3:07 AM, Ralf Steph
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Ralf:
There are 39 nodes that include an "&" in their names. I am more for
changing the '&' to "and" in general, but surely they need to have an
space both sides.
There are 196 nodes with a "#", most of them in the name tag, but some
others in th
Another improvement to the workflow document I would like to propose, is
that the doc talks about treatment of names containing "/" (which should
have spaces around the character). Can we assume the same for "&", "#", and
parentheses? Should any of them be treated differently, e.g. " And " for
"&"?
Hamlets can have farm names too as it seems. People add buildings, I
suspect.
On 25 Sep 2014 03:32, "Rafael Avila Coya" wrote:
> Hi Ralf.
> A farm could be isolated_dwelling?
> About unmil:id nobody noticed that. I would quite do id1;id2 and add it to
> the workflow wiki.
> Still travelling for a
Hi Ralf.
A farm could be isolated_dwelling?
About unmil:id nobody noticed that. I would quite do id1;id2 and add it to
the workflow wiki.
Still travelling for a few days in a row, so answering with my phone
whenever I get a wifi spot, so sorry for the brevity.
Cheers,
Rafael.
El 24/09/2014 23:28,
Hello,
I would like to share some thoughts and experiences on this import task.
- Landsat-8 imagery can only sometimes prove existence of a hamlet.
This may be due to the small size of UNMIL sourced places in general, but
there are also resolution issues. so there is quite some number
Hi, Ralf:
Thanks for contributing.
I've added both usernames to the list of allowed users. Let me know if you
still have problems.
Cheers,
Rafael.
El 23/09/2014 16:08, "Ralf Stephan" escribió:
> On Tue, Sep 23, 2014 at 6:53 AM, Rafael Avila Coya
> wrote:
> > But it's actually a bit better if
On Tue, Sep 23, 2014 at 6:53 AM, Rafael Avila Coya wrote:
> But it's actually a bit better if we
> access with our import account instead of the regular one, as that way the
> import account will be the one that will appear in the stats, and therefore
> making it more clear/less confusing.
Hi Raf
;)
El 23/09/2014 12:59, "Manfred A. Reiter" escribió:
> 2014-09-23 6:53 GMT+02:00 Rafael Avila Coya :
>
> [...]
>
>> I didn't comment it because I am now in a long distance bus, only with
>> my cellphone.
>>
> Have a nice and safe trip, my friend. ;-)
> sorry for that OT comment
>
> Manfred
>
__
2014-09-23 6:53 GMT+02:00 Rafael Avila Coya :
[...]
> I didn't comment it because I am now in a long distance bus, only with my
> cellphone.
>
Have a nice and safe trip, my friend. ;-)
sorry for that OT comment
Manfred
___
HOT mailing list
HOT@openstr
Yes. I was aware that it wasn't needed to use the import account to access
the job tasks and their data. I didn't comment it because I am now in a
long distance bus, only with my cellphone. But it's actually a bit better
if we access with our import account instead of the regular one, as that
way t
Hi Rafael,
I realize adding my import user name to the HOT TM2 project was not
needed was it?
It only matters that we use the proper OSM login info for JOSM, checkout
the task can be under our regular OSM login. First time I had to use an
alternate login so I got a little confused :)
Sorry
Done. Cheers,
Rafael
El 23/09/2014 09:22, "Blake Girardot" escribió:
>
>
> On 9/21/2014 1:42 AM, Rafael Avila Coya wrote:
>
>> I've added to the job the same users that were contributing to the GNS
>> merging job [3] + myself.
>>
>> If anyone else is interested in participating in this import, p
On 9/21/2014 1:42 AM, Rafael Avila Coya wrote:
I've added to the job the same users that were contributing to the GNS
merging job [3] + myself.
If anyone else is interested in participating in this import, please
reply to this list to have your name added.
Hi Rafael,
Can you please add my u
Cheers Rafael.
Pierre
De : Rafael Avila Coya
À : "hot@openstreetmap.org"
Envoyé le : Dimanche 21 septembre 2014 7h42
Objet : [HOT] [Ebola] Import of 14, 020 United Nations Mission in Liberia place
nodes
-BEGIN PGP SIGNED MESSAGE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all:
The Tasking Manager job to import [1] these set of places has being
discussed in the imports list, issues have been addressed and the
wikis have been written, with a detailed workflow [2] to secure a
consistent import process.
This job will g
29 matches
Mail list logo
