-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
-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
+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
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
-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
Most of the places remaining without high resolution imagery are not
high priority areas for the disease outbreak so that is why we have
not gotten better imagery.
With regards to the place=unknown thing, this was discussed on the
import list but I di
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,
can we schedule Issue triaging sometime this week?
We can try to do it on Thursday 16. October at 17:00 UTC ! [0]
Dražen
[0]
http://www.timeanddate.com/countdown/generic?p0=1440&iso=20141016T17&msg=HOT%20Projects%20issues%20triaging%20-%20itera
Hi Drazen,
That works for me.
Best,
-Kate
On Tue, Oct 14, 2014 at 10:02 AM, Dražen Odobašić
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> can we schedule Issue triaging sometime this week?
> We can try to do it on Thursday 16. October at 17:00 UTC ! [0]
>
> Dražen
>
>
>
Hi,
My apologies: solving some personal admin issues, I forgot today was the
day for the AWG monthly meeting.
Is it OK to do it next week on Tuesday, same hour as usual, to compensate?
Sincerely,
Severin
___
HOT mailing list
HOT@openstreetmap.org
https
-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
Unfortunately I'm going to miss this week's triage session ... but looking
forward to the results and the next one.
* Mikel Maron * +14152835207 @mikel s:mikelmaron
On Tuesday, October 14, 2014 1:26 PM, Kate Chapman
wrote:
>
>
>Hi Drazen,
>
>
>That works for me.
>
>
>Best,
>
>
>-Kate
>
>
12 matches
Mail list logo
