date:20171111


> MB can be  vague nowadays, sometimes people use it when they mean
> 1000^2, and sometimes it means 1024^2.  MiB is explicitly 1024^2.
> (lowercase mb is even more vague as it could also mean Mega-bit,
> which
> is 256 bytes).
> 

Sorry, 131072 bytes.

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

It has something to do with the difference between 10**3 and 2**10

2017-11-11 23:21 GMT+01:00 john whelan :

> >but it is not widely acknowledged within the industry or media.
>
> That probably explains why in fifty years of working with computers I
> hadn't come across the term.
>
> Cheerio John
>
> On 11 Nov 2017 5:03 pm, "Daniel Koć"  wrote:
>
>> W dniu 11.11.2017 o 22:55, john whelan pisze:
>>
>> >17MiB
>>
>> Interesting file size.  What is a MiB?
>>
>>
>> https://en.wikipedia.org/wiki/Mebibyte
>>
>> --
>> "My method is uncertain/ It's a mess but it's working" [F. Apple]
>>
>>
>> ___
>> talk mailing list
>> talk@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk
>>
>>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

On Sat, 2017-11-11 at 22:57 +0100, mmd wrote:
> I can reproduce this locally on JOSM 13106. According to 
> cpu jvisualvm
> profiling (on Oracle JDK), most time is spent in method
> org.openstreetmap.josm.data.tagging.ac.AutoCompletionSet.add.
> 
> Best bet would be to create an issue on
> https://josm.openstreetmap.de/newticket

Thank you! So it's autocomplete as I suspected. I will file a ticket.
Is there a way to disable autocomplete in the meantime?

On Sat, 2017-11-11 at 22:27 +0100, Jo wrote:
> When working with public transport, the PT_Assistant plugin might be
> interesting for you. On the other hand, it might cause additional
> overhead.

Seems useful!

On Sat, 2017-11-11 at 23:09 +0100, Jan Martinec wrote:
> You can download somewhat-recent JOSM versions from https://josm.
> openstreetmap.de/download/ , I do see 12921 there. Also josm-latest,
> which
> is the testing version (currently 13101).

Thank you.

> Interesting file size.  What is a MiB?
> 
> If you are working with large file sizes and using the results
> elsewhere
> you should be using ECC memory.  Anything else and you stand a chance
> of
> corruption.
> 
> How much memory does your laptop have?

MiB is practically the same as MB in for the needs of this
conversation.

MB can be  vague nowadays, sometimes people use it when they mean
1000^2, and sometimes it means 1024^2.  MiB is explicitly 1024^2.
(lowercase mb is even more vague as it could also mean Mega-bit, which
is 256 bytes).

I am not working with astronomically huge memory, just a mundane
Overpass fetch-edit*-upload cycle. But perhaps it's all been smooth
because the dataset is entirely nodes, and no ways or relations. The
laptop is 4 GiB. Pretty average hardware.

*The edit is actually several custom GTFS scripts followed by some
manual touches but that's irrelevant for the performance issue. For
anyone interested in what I do with 30k stops:
https://wiki.openstreetmap.org/wiki/User:SafwatHalaby/scripts/gtfs

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

>but it is not widely acknowledged within the industry or media.

That probably explains why in fifty years of working with computers I
hadn't come across the term.

Cheerio John

On 11 Nov 2017 5:03 pm, "Daniel Koć"  wrote:

> W dniu 11.11.2017 o 22:55, john whelan pisze:
>
> >17MiB
>
> Interesting file size.  What is a MiB?
>
>
> https://en.wikipedia.org/wiki/Mebibyte
>
> --
> "My method is uncertain/ It's a mess but it's working" [F. Apple]
>
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

2017-11-11 Thread James

have you tried with wireframe mode(ctrl+w)?

On Nov 11, 2017 5:11 PM, "Jan Martinec"  wrote:

> You can download somewhat-recent JOSM versions from
> https://josm.openstreetmap.de/download/ , I do see 12921 there. Also
> josm-latest, which is the testing version (currently 13101).
>
> Cheers,
> Honza "Piškvor" Martinec
>
> Dne 11. 11. 2017 22:15 napsal uživatel "john whelan" <
> jwhelan0...@gmail.com>:
>
> If you give it more memory sometimes that compensates on the CPU side by
> not requiring so much disk reading and writing.  Also there are almost
> certainly internal tables which work better in memory.  JAVA is a strange
> world of its own and with so many contributors and plugins I'm not sure
> anyone has a clear idea of exactly how JOSM works with in it.
>
> Not guaranteed but worth a try.
>
> Cheerio John
>
> On 11 November 2017 at 16:03, Safwat Halaby  wrote:
>
>> More details:
>>
>> JOSM 12712 has no issues.
>> Latest JOSM 13053 has issues.
>> Not sure how to download the intermediate version (12921).
>> It's a CPU starvation issue and not a memory overuse issue. (Core at
>> 100% for 10-30 seconds).
>>
>> Test case:
>>
>> Open up the attached file, try editing the ref or name of a stop.
>>
>> 12712 works flawlessly.
>> 13053 hangs for 10-30 seconds.
>
>
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

2017-11-11 Thread Jan Martinec

You can download somewhat-recent JOSM versions from https://josm.
openstreetmap.de/download/ , I do see 12921 there. Also josm-latest, which
is the testing version (currently 13101).

Cheers,
Honza "Piškvor" Martinec

Dne 11. 11. 2017 22:15 napsal uživatel "john whelan" :

If you give it more memory sometimes that compensates on the CPU side by
not requiring so much disk reading and writing.  Also there are almost
certainly internal tables which work better in memory.  JAVA is a strange
world of its own and with so many contributors and plugins I'm not sure
anyone has a clear idea of exactly how JOSM works with in it.

Not guaranteed but worth a try.

Cheerio John

On 11 November 2017 at 16:03, Safwat Halaby  wrote:

> More details:
>
> JOSM 12712 has no issues.
> Latest JOSM 13053 has issues.
> Not sure how to download the intermediate version (12921).
> It's a CPU starvation issue and not a memory overuse issue. (Core at
> 100% for 10-30 seconds).
>
> Test case:
>
> Open up the attached file, try editing the ref or name of a stop.
>
> 12712 works flawlessly.
> 13053 hangs for 10-30 seconds.

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

2017-11-11 Thread Daniel Koć


W dniu 11.11.2017 o 22:55, john whelan pisze:

>17MiB

Interesting file size.  What is a MiB?


https://en.wikipedia.org/wiki/Mebibyte

--
"My method is uncertain/ It's a mess but it's working" [F. Apple]

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-cz] jednosměrka

2017-11-11 Thread Pavel Machek

On Sat 2017-11-11 20:40:17, Michal Fabík wrote:
> On 11.11.2017 13:59, Zbyněk Datinský wrote:
> >Rád bych jen připomenul, že přenosné, pevně neinstalované, dopravní
> >značení se nemapuje.
> 
> Ahoj, to mně zas přijde dost kategorické. Když si policajti takhle někde
> postaví nějakou značku víceméně podle nálady a po šichtě ji zase sbalí a
> odvezou, tak ji pochopitelně mapovat nebudu, ale třeba i některé dlouhodobé
> dopravní uzavírky jsou běžně značené přenosnými značkami. Přitom přes celou
> ulici je pět metrů hluboká jáma a vedle stojí cedule Termín dokončení
> stavby, cojávim, září 2019. Jako jo, označím příslušnou ulici jako stavbu,
> ale to nemusí vždycky řešit všechny související omezení (objízdé trasy,
> změny jednosměrek v okolních ulicích, omezení počtu pruhů apod.).

Ne, prenosne znaceni se bezne nemapuje. Na druhou stranu tohle neni
uplne bezna situace, takze ... bych to asi zmapoval.
Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) 
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html


signature.asc
Description: Digital signature
___
Talk-cz mailing list
Talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz

Re: [Talk-es] ¡Ayuda! Error al renombrar la página wiki traducida

2017-11-11 Thread dcapillae

Si la página está en español, las referencias a otras páginas del wiki
(enlaces internos) deben dirigir a páginas en español, siempre que éstas
existan. Usa [[ES:Título-en-inglés]] o [[ES:Título-en-español]] para crear
los enlaces. Si no existe traducción al español de la página destino, los
enlaces deben dirigir a la versión de referencia, normalmente la versión en
inglés.

Existe una plantilla que automáticamente detecta si la página de destino
existe en el idioma correspondiente a la página actual. Es una plantilla muy
útil cuando estás traduciendo. Así, por ejemplo, si traduces una página con
múltiples referencias a otras páginas que aún no están traducidas, usando
esta plantilla en los enlaces internos te aseguras que cuando esas páginas
existan (porque alguien más adelante las traduzca a su vez) las referencias
de tu página dirigirán automáticamente a la versión en español.

La plantilla en cuestión es  Template:LL
  , y su uso es muy
sencillo. Simplemente tienes que añadir como argumento el título de la
página de referencia en inglés, por ejemplo, un enlace interno construido
con esta plantilla podría ser [[{{LL|Tagging for the renderer}}]]. Si la
página tiene una traducción en español, el enlace dirigirá automáticamente a
la versión en español, y si no existe, a la versión en inglés. En el futuro,
si alguien traduce la página de destino, los enlaces de tu página detectarán
automáticamente que existe una versión en español y redigirán a dicha
versión.

Si sabes que existe la página en español, evita usar la plantilla, pon
directamente el nombre de la página [[ES:Título-en-inglés]] o bien
[[ES:Título-en-español]]. Usar muchas plantilla afecta al rendimiento de la
página.

Un cordial saludo.



-
Daniel Capilla
OSM user: dcapillae 
--
Sent from: http://gis.19327.n8.nabble.com/Spain-f5409873.html

___
Talk-es mailing list
Talk-es@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-es

Re: [OSM-talk] Serious JOSM performance degradation

2017-11-11 Thread mmd

Am 11.11.2017 um 22:25 schrieb Safwat Halaby:
> Apparently one of my messages did not get through due to a huge file.
> Here it is once more:
> 
> More details:
> 
> JOSM 12712 has no issues.
> Latest JOSM 13053 has issues.
> Not sure how to download the intermediate version (12921).
> It's a CPU starvation issue and not a memory overuse issue. (Core at
> 100% for 10-30 seconds).
> 
> Test case:
> Open up the attached file, try editing the ref or name of a stop.
> 12712 works flawlessly.
> 13053 hangs for 10-30 seconds.
> 

I can reproduce this locally on JOSM 13106. According to jvisualvm cpu
profiling (on Oracle JDK), most time is spent in method
org.openstreetmap.josm.data.tagging.ac.AutoCompletionSet.add.

Best bet would be to create an issue on
https://josm.openstreetmap.de/newticket


-- 


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

>17MiB

Interesting file size.  What is a MiB?

If you are working with large file sizes and using the results elsewhere
you should be using ECC memory.  Anything else and you stand a chance of
corruption.

How much memory does your laptop have?

Thanks John

On 11 Nov 2017 4:48 pm, "Safwat Halaby"  wrote:

> That's interestingly low. I'm talking about a 17MiB file here, and it
> was never slugish before this bug. My laptop is an average thinkpad...
>
> On Sat, 2017-11-11 at 15:52 -0500, john whelan wrote:
> > java -Xmx821000 -jar G:\josm\josm-tested.jar
> >
> > in a .bat file seems to be happy with 2Mb files.  It can be sluggish
> > though
> > so I try to keep it below 250kb for best performance.
> >
> > Cheerio John
> >
> > On 11 November 2017 at 15:43, Safwat Halaby 
> > wrote:
> >
> > > I deal with a huge dataset (about 30k bus stops nodes) almost
> > > daily.
> > > This was never a problem before, but since recently (I cannot
> > > pinpoint
> > > the exact version), JOSM often hangs when I edit the bus stop tags.
> > > Waiting for a few seconds (can be up to ~30) always resolves this.
> > >
> > > I suspect it has to do with JOSM's autocomplete, because it seems
> > > to
> > > happen when editing massively used keys. For instance, all stops
> > > have a
> > > "ref" key, and when I click "edit" on a single stop's "ref", JOSM
> > > stalls. A similar issue occurs when adding "description" to
> > > changeset
> > > uploads. Description is also used by all stops.
> > >
> > > Any tips or pointers?
> > >
> > > ___
> > > talk mailing list
> > > talk@openstreetmap.org
> > > https://lists.openstreetmap.org/listinfo/talk
> > >
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

That's interestingly low. I'm talking about a 17MiB file here, and it
was never slugish before this bug. My laptop is an average thinkpad...

On Sat, 2017-11-11 at 15:52 -0500, john whelan wrote:
> java -Xmx821000 -jar G:\josm\josm-tested.jar
> 
> in a .bat file seems to be happy with 2Mb files.  It can be sluggish
> though
> so I try to keep it below 250kb for best performance.
> 
> Cheerio John
> 
> On 11 November 2017 at 15:43, Safwat Halaby 
> wrote:
> 
> > I deal with a huge dataset (about 30k bus stops nodes) almost
> > daily.
> > This was never a problem before, but since recently (I cannot
> > pinpoint
> > the exact version), JOSM often hangs when I edit the bus stop tags.
> > Waiting for a few seconds (can be up to ~30) always resolves this.
> > 
> > I suspect it has to do with JOSM's autocomplete, because it seems
> > to
> > happen when editing massively used keys. For instance, all stops
> > have a
> > "ref" key, and when I click "edit" on a single stop's "ref", JOSM
> > stalls. A similar issue occurs when adding "description" to
> > changeset
> > uploads. Description is also used by all stops.
> > 
> > Any tips or pointers?
> > 
> > ___
> > talk mailing list
> > talk@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk
> > 

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

When working with public transport, the PT_Assistant plugin might be
interesting for you. On the other hand, it might cause additional overhead.

Jo

2017-11-11 22:23 GMT+01:00 Safwat Halaby :

> I don't know what these are.
>
> The test described below was done without plugins, by the way.
>
> On Sat, 2017-11-11 at 22:14 +0100, Jo wrote:
> > Did you start using PT_Assistant? Or a MapCSS style dedicated to PT?
> >
> > Polyglot
> >
> > 2017-11-11 22:10 GMT+01:00 john whelan :
> >
> > > If you give it more memory sometimes that compensates on the CPU
> > > side by
> > > not requiring so much disk reading and writing.  Also there are
> > > almost
> > > certainly internal tables which work better in memory.  JAVA is a
> > > strange
> > > world of its own and with so many contributors and plugins I'm not
> > > sure
> > > anyone has a clear idea of exactly how JOSM works with in it.
> > >
> > > Not guaranteed but worth a try.
> > >
> > > Cheerio John
> > >
> > > On 11 November 2017 at 16:03, Safwat Halaby 
> > > wrote:
> > >
> > > > More details:
> > > >
> > > > JOSM 12712 has no issues.
> > > > Latest JOSM 13053 has issues.
> > > > Not sure how to download the intermediate version (12921).
> > > > It's a CPU starvation issue and not a memory overuse issue. (Core
> > > > at
> > > > 100% for 10-30 seconds).
> > > >
> > > > Test case:
> > > >
> > > > Open up the attached file, try editing the ref or name of a stop.
> > > >
> > > > 12712 works flawlessly.
> > > > 13053 hangs for 10-30 seconds.
> > >
> > >
> > >
> > > ___
> > > talk mailing list
> > > talk@openstreetmap.org
> > > https://lists.openstreetmap.org/listinfo/talk
> > >
> > >
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

Apparently one of my messages did not get through due to a huge file.
Here it is once more:

More details:

JOSM 12712 has no issues.
Latest JOSM 13053 has issues.
Not sure how to download the intermediate version (12921).
It's a CPU starvation issue and not a memory overuse issue. (Core at
100% for 10-30 seconds).

Test case:
Open up the attached file, try editing the ref or name of a stop.
12712 works flawlessly.
13053 hangs for 10-30 seconds.

original message ends here.

As for the file, I cannot attach it, but use this Overpass query to
obtain the same dataset:

[out:xml][timeout:90][bbox:29.4013195,33.8818359,33.4131022,36.0791016]
;
(
area(3601473946); // Israel
area(3601803010); // Judea and Samaria district
)->.a;
(
  node["highway"="bus_stop"](area.a);
  way["highway"="bus_stop"](area.a);
)->.b;
(rel(bw.b);rel(bn.b))->.routes;
(.b;way(bn.b);)->.b;
(.b;node(w.b);)->.b;
(.b;.routes;);
out meta;

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

I don't know what these are.

The test described below was done without plugins, by the way.

On Sat, 2017-11-11 at 22:14 +0100, Jo wrote:
> Did you start using PT_Assistant? Or a MapCSS style dedicated to PT?
> 
> Polyglot
> 
> 2017-11-11 22:10 GMT+01:00 john whelan :
> 
> > If you give it more memory sometimes that compensates on the CPU
> > side by
> > not requiring so much disk reading and writing.  Also there are
> > almost
> > certainly internal tables which work better in memory.  JAVA is a
> > strange
> > world of its own and with so many contributors and plugins I'm not
> > sure
> > anyone has a clear idea of exactly how JOSM works with in it.
> > 
> > Not guaranteed but worth a try.
> > 
> > Cheerio John
> > 
> > On 11 November 2017 at 16:03, Safwat Halaby 
> > wrote:
> > 
> > > More details:
> > > 
> > > JOSM 12712 has no issues.
> > > Latest JOSM 13053 has issues.
> > > Not sure how to download the intermediate version (12921).
> > > It's a CPU starvation issue and not a memory overuse issue. (Core
> > > at
> > > 100% for 10-30 seconds).
> > > 
> > > Test case:
> > > 
> > > Open up the attached file, try editing the ref or name of a stop.
> > > 
> > > 12712 works flawlessly.
> > > 13053 hangs for 10-30 seconds.
> > 
> > 
> > 
> > ___
> > talk mailing list
> > talk@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk
> > 
> > 

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

Did you start using PT_Assistant? Or a MapCSS style dedicated to PT?

Polyglot

2017-11-11 22:10 GMT+01:00 john whelan :

> If you give it more memory sometimes that compensates on the CPU side by
> not requiring so much disk reading and writing.  Also there are almost
> certainly internal tables which work better in memory.  JAVA is a strange
> world of its own and with so many contributors and plugins I'm not sure
> anyone has a clear idea of exactly how JOSM works with in it.
>
> Not guaranteed but worth a try.
>
> Cheerio John
>
> On 11 November 2017 at 16:03, Safwat Halaby  wrote:
>
>> More details:
>>
>> JOSM 12712 has no issues.
>> Latest JOSM 13053 has issues.
>> Not sure how to download the intermediate version (12921).
>> It's a CPU starvation issue and not a memory overuse issue. (Core at
>> 100% for 10-30 seconds).
>>
>> Test case:
>>
>> Open up the attached file, try editing the ref or name of a stop.
>>
>> 12712 works flawlessly.
>> 13053 hangs for 10-30 seconds.
>
>
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

If you give it more memory sometimes that compensates on the CPU side by
not requiring so much disk reading and writing.  Also there are almost
certainly internal tables which work better in memory.  JAVA is a strange
world of its own and with so many contributors and plugins I'm not sure
anyone has a clear idea of exactly how JOSM works with in it.

Not guaranteed but worth a try.

Cheerio John

On 11 November 2017 at 16:03, Safwat Halaby  wrote:

> More details:
>
> JOSM 12712 has no issues.
> Latest JOSM 13053 has issues.
> Not sure how to download the intermediate version (12921).
> It's a CPU starvation issue and not a memory overuse issue. (Core at
> 100% for 10-30 seconds).
>
> Test case:
>
> Open up the attached file, try editing the ref or name of a stop.
>
> 12712 works flawlessly.
> 13053 hangs for 10-30 seconds.
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-es] ¡Ayuda! Error al renombrar la página wiki traducida

2017-11-11 Thread Ibai Gurrutxaga


Gracias por la explicación.

Mi problema era que no sabía como llegar a la última versión en inglés, 
pero leyendo tu explicación lo he intuido y ya lo he encontrado a través 
del historial de la página.


Aprovecho el mensaje para preguntar otra cosa relacionada. De momento 
estoy traduciendo algunas páginas que se referencian desde "ES:Buenas 
prácticas", como "Página principal" (por ejemplo, "ES:Verificabilidad" y 
la página en cuestión, "ES:Una característica, un elemento OSM").


He pensado que lo adecuado sería actualizar las referencias en 
"ES:Buenas prácticas" para que ahora apunten a las nuevas versiones 
traducidas, en lugar de a las versiones en inglés. El problema es que he 
comprobado que hay referencias a otras páginas como "Tagging for the 
renderer" o "Good changeset comments" que referencian a la versión en 
inglés, habiendo ya una versión en castellano de ellas.


¿Es simplemente que no están actualizadas o hay alguna razón para que 
esto sea así?


Un saludo y gracias otra vez,
Ibai.


On 11/11/17 20:41, dcapillae wrote:

Te indico cómo lo he resuelto por si te pasa otra vez y quieres resolverlo
por ti mismo:

1º) He copiado tu traducción a la página «Una característica, un elemento
OSM», para luego renombrarla añadiéndole el prefijo de idiomas: «ES:Una
característica, un elemento OSM».

2ª) En lugar de revertir tus cambios en «One feature, one OSM element», he
buscado la última versión en inglés y la he copiado en su lugar.

Por último, sólo queda asegurarte de que en la plantilla {{Languages}} de la
página traducida, «ES:Una característica, un elemento OSM», figura como
página de referencia el título de la página original en inglés, «One
feature, one OSM element». Así la barra interlingüística funcionará bien y
se puedrá cambiar entre las distintas traducciones, incluida tu traducción
en español.

Un cordial saludo.



-
Daniel Capilla
OSM user: dcapillae
--
Sent from: http://gis.19327.n8.nabble.com/Spain-f5409873.html

___
Talk-es mailing list
Talk-es@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-es



___
Talk-es mailing list
Talk-es@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-es

Re: [OSM-talk] Serious JOSM performance degradation

java -Xmx821000 -jar G:\josm\josm-tested.jar

in a .bat file seems to be happy with 2Mb files.  It can be sluggish though
so I try to keep it below 250kb for best performance.

Cheerio John

On 11 November 2017 at 15:43, Safwat Halaby  wrote:

> I deal with a huge dataset (about 30k bus stops nodes) almost daily.
> This was never a problem before, but since recently (I cannot pinpoint
> the exact version), JOSM often hangs when I edit the bus stop tags.
> Waiting for a few seconds (can be up to ~30) always resolves this.
>
> I suspect it has to do with JOSM's autocomplete, because it seems to
> happen when editing massively used keys. For instance, all stops have a
> "ref" key, and when I click "edit" on a single stop's "ref", JOSM
> stalls. A similar issue occurs when adding "description" to changeset
> uploads. Description is also used by all stops.
>
> Any tips or pointers?
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Serious JOSM performance degradation

On Sat, 2017-11-11 at 22:43 +0200, Safwat Halaby wrote:
> I deal with a huge dataset (about 30k bus stops nodes) almost daily.
> This was never a problem before, but since recently (I cannot
> pinpoint
> the exact version), JOSM often hangs when I edit the bus stop tags.
> Waiting for a few seconds (can be up to ~30) always resolves this.
> 
> I suspect it has to do with JOSM's autocomplete, because it seems to
> happen when editing massively used keys. For instance, all stops have
> a
> "ref" key, and when I click "edit" on a single stop's "ref", JOSM
> stalls. A similar issue occurs when adding "description" to changeset
> uploads. Description is also used by all stops.
> 
> Any tips or pointers?
> 
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk

I will soon test this out with various versions.

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

[OSM-talk] Serious JOSM performance degradation

I deal with a huge dataset (about 30k bus stops nodes) almost daily.
This was never a problem before, but since recently (I cannot pinpoint
the exact version), JOSM often hangs when I edit the bus stop tags.
Waiting for a few seconds (can be up to ~30) always resolves this.

I suspect it has to do with JOSM's autocomplete, because it seems to
happen when editing massively used keys. For instance, all stops have a
"ref" key, and when I click "edit" on a single stop's "ref", JOSM
stalls. A similar issue occurs when adding "description" to changeset
uploads. Description is also used by all stops.

Any tips or pointers?

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-cz] Strava Heatmap

2017-11-11 Thread Marián Kyral

No všiml jsem si, že to tady jeden kolega začal více používat, tak jsem
to dneska zkusil a je to brutální změna. Docela dost se podle toho dá
mapovat.

Marián

Dne 11.11.2017 v 21:19 Milan Cerny napsal(a):
> Jen pro zajímavost, po dlouhé době došlo na aktualizaci Strava Heatmap, někdy 
> se to celkem hodí.
> https://medium.com/strava-engineering/the-global-heatmap-now-6x-hotter-23fc01d301de?_branch_match_id=457982050159408399
>
> https://labs.strava.com/heatmap/#10.37/14.57074/49.98286/hot/all
>
> Milan
>
> ___
> Talk-cz mailing list
> Talk-cz@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-cz


___
Talk-cz mailing list
Talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz

[Talk-cz] Strava Heatmap

2017-11-11 Thread Milan Cerny

Jen pro zajímavost, po dlouhé době došlo na aktualizaci Strava Heatmap, někdy 
se to celkem hodí.
https://medium.com/strava-engineering/the-global-heatmap-now-6x-hotter-23fc01d301de?_branch_match_id=457982050159408399

https://labs.strava.com/heatmap/#10.37/14.57074/49.98286/hot/all

Milan

___
Talk-cz mailing list
Talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz

Re: [Talk-es] ¡Ayuda! Error al renombrar la página wiki traducida

2017-11-11 Thread dcapillae

Te indico cómo lo he resuelto por si te pasa otra vez y quieres resolverlo
por ti mismo:

1º) He copiado tu traducción a la página «Una característica, un elemento
OSM», para luego renombrarla añadiéndole el prefijo de idiomas: «ES:Una
característica, un elemento OSM». 

2ª) En lugar de revertir tus cambios en «One feature, one OSM element», he
buscado la última versión en inglés y la he copiado en su lugar.

Por último, sólo queda asegurarte de que en la plantilla {{Languages}} de la
página traducida, «ES:Una característica, un elemento OSM», figura como
página de referencia el título de la página original en inglés, «One
feature, one OSM element». Así la barra interlingüística funcionará bien y
se puedrá cambiar entre las distintas traducciones, incluida tu traducción
en español.

Un cordial saludo.



-
Daniel Capilla
OSM user: dcapillae 
--
Sent from: http://gis.19327.n8.nabble.com/Spain-f5409873.html

___
Talk-es mailing list
Talk-es@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-es

Re: [Talk-cz] jednosměrka

2017-11-11 Thread Michal Fabík


On 11.11.2017 13:59, Zbyněk Datinský wrote:
Rád bych jen připomenul, že přenosné, pevně neinstalované, dopravní 
značení se nemapuje.


Ahoj, to mně zas přijde dost kategorické. Když si policajti takhle někde 
postaví nějakou značku víceméně podle nálady a po šichtě ji zase sbalí a 
odvezou, tak ji pochopitelně mapovat nebudu, ale třeba i některé 
dlouhodobé dopravní uzavírky jsou běžně značené přenosnými značkami. 
Přitom přes celou ulici je pět metrů hluboká jáma a vedle stojí cedule 
Termín dokončení stavby, cojávim, září 2019. Jako jo, označím příslušnou 
ulici jako stavbu, ale to nemusí vždycky řešit všechny související 
omezení (objízdé trasy, změny jednosměrek v okolních ulicích, omezení 
počtu pruhů apod.).


--
Michal Fabík

___
Talk-cz mailing list
Talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz

Re: [Talk-it] Feature Proposal - RFC - (Fire Hydrant Extensions (part 2)

2017-11-11 Thread Alberto

> Mi piace molto! Voterò positivamente. Per quanto riguarda invece il tag
> poposto "Attacco di mandata"
> https://wiki.openstreetmap.org/wiki/Proposed_features/Dry_riser_inlet
> quando verrà votato?
> Bubix

Dovresti contattare l'autore (che mi pare sia Martin), io non me ne sto 
occupando.
Alcuni tag sarebbero da allineare con quelli degli idranti, tipo diameter=*, 
couplings=*, couplings:type=*, couplings:diameters=*, ...
Alberto


---
Questa e-mail è stata controllata per individuare virus con Avast antivirus.
https://www.avast.com/antivirus


___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [Talk-es] ¡Ayuda! Error al renombrar la página wiki traducida

2017-11-11 Thread Ibai Gurrutxaga


No sé cómo lo has hecho, pero ¡muchas gracias!

Procuraré ser más cuidadoso la próxima vez...

Ibai Gurrutxaga.


On 11/11/17 19:58, dcapillae wrote:

¡Solucionado!

Gracias por tus traducciones. ¡Buen trabajo!



-
Daniel Capilla
OSM user: dcapillae
--
Sent from: http://gis.19327.n8.nabble.com/Spain-f5409873.html

___
Talk-es mailing list
Talk-es@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-es



___
Talk-es mailing list
Talk-es@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-es

[Talk-in] Fwd: [FSFTN] OSM Geography Awareness Week Mapathon in TamilNadu

2017-11-11 Thread Balaji Ravichandran

-- Forwarded message --
From: Survesh Jones <123surv...@gmail.com>
Date: 11 November 2017 at 23:54
Subject: [FSFTN] OSM Geography Awareness Week Mapathon in TamilNadu
To: Announcement and Discussion mailing list 


Hi there,

FSFTN  is organizing a Mapjam Activity as a part of
*OSM
Geography Awareness Week* , where people around the
world join together to celebrate geography and make maps with
*OpenStreetMap* , the free and openly
editable map of the world. This event is a week-long mapathon, that is
from *Nov
12th* to *Nov 17th*. Participants will contribute to OpenStreetMap for this
whole week (by finding names of roads, speed limits, pincodes and more in
the app "StreetComplete") and their contributions will be tracked in our
leaderboard.

This event is open to all people, so if you want to join in the fun follow
the steps below.

*Steps to Participate :- *

   - Register an account at OSM here  (If not
   before)
   - Register for the FSFTN Mapathon here 
   - Start Contributing
   - Check your position on the leaderboard here
   

*Note:- Only Contributions from Nov 12th to Nov 17th (2017) will be taken
into account*

*Steps to Contribute:-*

   - Install *F-Droid* from here 
   - Install *StreetComplete* app from the F-Droid repository or Download
   here 
   - Link your account using your OSM Credentials
   - Start Contributing by marking places in the go. Upload the
   contributions to your OSM account


Share your contributions in Social Media with the hashtag *#osmgeoweek
#fsftn #fsftnmap2017*
*For more details, questions and doubts :- *

Contact - 9043475346
Email - *a...@fsftn.org *

Happy Mapping 
Also Follow us on Facebook

to be periodically updated about the event
___
FSFTN mailing list
Website : https://fsftn.org/
Discuss : https://discuss.fsftn.org/
Contact : https://fsftn.org/blog/contact/
General info : https://mailman.fsftn.org/mailman/listinfo/mailinglist_
fsftn.org
To Unsubscribe : https://mailman.fsftn.org/mailman/options/mailinglist_
fsftn.org



-- 
Best Regards,
Balaji Ravichandran
___
Talk-in mailing list
Talk-in@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-in

Re: [Talk-es] ¡Ayuda! Error al renombrar la página wiki traducida

2017-11-11 Thread dcapillae

¡Solucionado!

Gracias por tus traducciones. ¡Buen trabajo!



-
Daniel Capilla
OSM user: dcapillae 
--
Sent from: http://gis.19327.n8.nabble.com/Spain-f5409873.html

___
Talk-es mailing list
Talk-es@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-es

Re: [Talk-it] Relazione route multiuso

2017-11-11 Thread liste DOT girarsi AT posteo DOT eu


Il 11/11/2017 19:45, liste DOT girarsi AT posteo DOT eu ha scritto:
Ho guardato le due relazioni, una Ãš con tre tag, e l'altra Ãš con un 
tag route=*, e vabbÃš, poi ci sta il network=*, e qui casca l'asino 
perchÃš lasci il valore "lcn" che vale solo per le biciclette (local 
cycle network), sicchÃš dovresti mettre piÃ¹ valori anche sul network, 
ovvero (lcn, lwn- visto che MTB resta sempre cycle).


Pre me tre relazioni sono il minimo sindacale, piÃ¹ manutenibili, piÃ¹ 
fruibili da software/siti dedicati, piÃ¹ gestibili anche dalla wiki come 
pagine dedicate, altrimenti tanto vale fare un'unica pagina lunga per 
tutto l'ambaradan.


Poi quanto detto da Volker sulla ciclopedonale, mi pare diversa da 
questa situazione, in quanto in quella sua situazione si parla di corsie 
dedicate sullo stesso tracciato e segnalate con segnaletica sia 
verticale che orrizzontale, mentre qui si tratta solo di usare lo stesso 
tracciato per piÃ¹ tipologie di "mezzi", passatemi il termine, cambia 
solo la **superfiche** del terreno e pericolositÃ .


Capisco che sono una scocciatura tre relazioni, perÃ², sinceramente con 
josm Ãš possibile copiare a stessa relazione, modificando la copia, 
adattandola al caso specifico, cosa che alla fine modifica due tag e si 
"perde meno tempo", secono me.


Anche perchÃš se il tracciato ad un certo punto, esempio, viene solo 
consentito ai pedoni su un tratto ed il resto no, che si fÃ , si 
modifica la relazione come, intendo quella con tag multipli?


Oppure, c'Ãš una deviazione per sole MTB, che si fÃ  con la relazione? 
si creano bivi?


Vedo e prevedo un gran porcaio sinceramente.

Poi, quante volte si mette mano ad una singola relazione una volta 
fatta? capisco che ci vuole tempo alle volte, ma lo ritengo ben speso, 
molto piÃ¹ della poca voglia a metterci mano.



My 2 cents.






Perdonate la parola super, messa in evidenza sopra con **, ma nella 
fretta, questa cosa, seppur bella, resta oniricachiedo scusa 
ancora.


--
_|_|_|_|_|_|_|_|_|_
|_|_|_|_|_|_|_|_|_|_|
Simone Girardelli

___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [Talk-it] Relazione route multiuso

2017-11-11 Thread liste DOT girarsi AT posteo DOT eu

Ho guardato le due relazioni, una è con tre tag, e l'altra è con un tag 
route=*, e vabbè, poi ci sta il network=*, e qui casca l'asino perchè 
lasci il valore "lcn" che vale solo per le biciclette (local cycle 
network), sicchè dovresti mettre più valori anche sul network, ovvero 
(lcn, lwn- visto che MTB resta sempre cycle).


Pre me tre relazioni sono il minimo sindacale, più manutenibili, più 
fruibili da software/siti dedicati, più gestibili anche dalla wiki come 
pagine dedicate, altrimenti tanto vale fare un'unica pagina lunga per 
tutto l'ambaradan.


Poi quanto detto da Volker sulla ciclopedonale, mi pare diversa da 
questa situazione, in quanto in quella sua situazione si parla di corsie 
dedicate sullo stesso tracciato e segnalate con segnaletica sia 
verticale che orrizzontale, mentre qui si tratta solo di usare lo stesso 
tracciato per più tipologie di "mezzi", passatemi il termine, cambia 
solo la superfiche del terreno e pericolosità.


Capisco che sono una scocciatura tre relazioni, però, sinceramente con 
josm è possibile copiare a stessa relazione, modificando la copia, 
adattandola al caso specifico, cosa che alla fine modifica due tag e si 
"perde meno tempo", secono me.


Anche perchè se il tracciato ad un certo punto, esempio, viene solo 
consentito ai pedoni su un tratto ed il resto no, che si fà, si modifica 
la relazione come, intendo quella con tag multipli?


Oppure, c'è una deviazione per sole MTB, che si fà con la relazione? si 
creano bivi?


Vedo e prevedo un gran porcaio sinceramente.

Poi, quante volte si mette mano ad una singola relazione una volta 
fatta? capisco che ci vuole tempo alle volte, ma lo ritengo ben speso, 
molto più della poca voglia a metterci mano.



My 2 cents.



--
_|_|_|_|_|_|_|_|_|_
|_|_|_|_|_|_|_|_|_|_|
Simone Girardelli

___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [OSM-talk-fr] Toilettes pas publiques

2017-11-11 Thread Philippe Verdy

C'est exactement la proposition que j'ai faite ci-dessus avec "room=*"
(bien que là ce n'est pas une simple pièce, mais un petit "building"
extérieur). Il reste que le problème ne se réduit pas aux seules toilettes
(on peut penser à toutes sortes de locaux techniques présents au milieu
d'une zone accessible au publique mais non accessibles au public et
affichant un panneau "accès réservé au personnel" ou similaire.

Maintenant si c'est privé, je ne vois pas l'intérêt de détailler plus ce
qui se trouve à l'intérieur (est-ce vraiment des toilettes? ou un placard à
balais? ou un espace de stockage ou un local technique?). Je me
contenterais juste de baliser ce qui est visible: la plaque, le panneau ou
l'inscription mentionnant l'accès réservé (qui n'est pas vraiment privé non
plus: "access=personnal" semble plus approprié, le personnel ou les
personnes habilitées par leur mission n'est ni propriétaire ni locataire et
reste tenu de respecter la propriété privée à qui on lui a donné un accès
autorisé).

Je pense donc que taguer ces toilettes comme telles n'a pas sa place du
tout dans OSM. La seule chose qui compte c'est l'accès public interdit et
on n'a pas à entrer dans le détail de ce qui est privé sauf si un
panneau/un affichage l'indique clairement (même chose que pour les panneaux
de propriété privées indiquant une zone de chasse, ou une surveillance par
caméra ou la présence de chiens de garde à l'intérieur: on n'ira pas
vérifier à l'intérieur, seul le panneau public compte pour OSM).

Bref je pense à un tag du type "barrier=*" (pour le panneau ou
l'inscription, avec possibilité de copier le texte affiché dans un
"inscription=*") puis le reste derrière seulement identifié comme une zone
"access=private" (ou landuse=military) et rien de plus. On ne tague que ce
qu'on voit légalement depuis l'espace public ou le ciel, mais rien du tout
dans les zones intérieures fermées puisque c'est invérifiable légalement.

Le 11 novembre 2017 à 13:22, JB  a écrit :

> Je pense que j'aurais plutôt eu tendance à reprendre le tag utilisé pour
> l'indoor (mais j'ai un trou de mémoire, room=toilets?), qui indique un WC,
> mais pas des toilettes accessibles/publiques.
> JB.
>
> Le 11.11.2017 07:06, Christian Quest a écrit :
>
> Si le wiki est sans équivoque sur le fait de ne pas mapper les toilettes
> non publiques, il faut le respecter.
>
> Je conserverai l'objet dans OSM afin qu'il ne soit pas recréé par un autre
> contributeur, mais avec un tag du genre: private:amenity=toilets ou quelque
> chose qu'un outil qui se base sur amenity=toilets n'utilisera pas mais
> compréhensible par un contributeur.. ça pourrait même être un simple
> note=private toilets, not to map as amenity=toilets according to the wiki
>
>
> Le 10 novembre 2017 à 22:38, marc marc  a
> écrit :
>
>> Le 10. 11. 17 à 22:23, David Crochet a écrit :
>> > Le 10/11/2017 à 21:49, Romain MEHUT a écrit :
>> >> Je vois que dans le wiki, le tag access=private est rayé. Sur le fond,
>> >> je comprends la logique mais si je retire le tag amenity que
>> >> mettriez-vous à la place ?
>> > Pour moi la règle est simple :
>> > Que voit-je : je vois des toilettes, j'ajoute dans OSM des toilettes
>>
>> la règle est simple mais je comprend tout a fait l'auteur de la note.
>> une amenity qui n'est pas accessible, détruite, hors d'usage ou qui a
>> changé d'usage n'est plus une amenity.
>> D'ailleurs la page wiki concernée demande de ne pas maper les toilettes
>> privées.
>>
>> Autre exemple : j'ai rencontré un coin ou quelqu'un a créé un tag
>> parking pour chaque place de parking privé associé à un immeuble.
>> résultat le plan est inutilisable tant visuellement que par recherche.
>> faut-il changer le rendu et tous les outils ?
>> ou préfixer la fonction qui n'existe pas avec no: ?
>> je n'ai pas encore fait les modifs (parce qu'ils y a + urgent à cet
>> endroit) mais je ne vois que la 2ieme solution comme réaliste.
>>
>> De même il y a déjà un consensus pour dire qu'un équipement d'urgence
>> qui ne fonctionne plus n'est plus un équipement d'urgence (on le prefix
>> par disused: généralement).
>> cela me semble tout aussi valable et non contradictoire avec la règle
>> "mapper ce qu'on voit".
>>
>> Cordialement,
>> Marc
>> ___
>> Talk-fr mailing list
>> Talk-fr@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-fr
>>
>
>
>
> --
> Christian Quest - OpenStreetMap France
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>
>
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

[Talk-dk] Hjælp til rep af relation

2017-11-11 Thread Lars Gravengaard

Hej Alle

Da jeg var ved at opdater Hirtshals Havn ifølge de nye Opdaterede Luftfotos
fra SDFE.

Ødelage jeg denne Relation: E 39 Trondheim - Ålborg

https://www.openstreetmap.org/relation/56555#map=8/56.634/11.305

Håber at der er en der vil fikse den da det vist er bedst at jeg ikke
"fiksker" mere i den :-)

/Lars
___
Talk-dk mailing list
Talk-dk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-dk

[Talk-es] ¡Ayuda! Error al renombrar la página wiki traducida

2017-11-11 Thread Ibai Gurrutxaga


Hola.

He querido entrar poco a poco en la traducción de la wiki y he traducido 
un par de páginas. El problema es que acabo de meter la pata por partida 
doble y no soy capaz de solucionarlo. Por favor, que alguien con más 
experiencia me ayude.


El caso es que he traducido la página "One feature, one OSM_element" del 
inglés al castellano. Todo ha ido bien y he querido renombrar la página. 
En este movimiento he hecho el primer error ya que lo he renombrado como 
"Una característica, un elemento OSM", sin el código "ES:" inicial. Como 
no he conseguido deshacer el cambio, he pensado en volver a renombrarlo 
al nombre original ("ES:One feature, one OSM_element" para ver si esto 
lo deshacía.


Y aquí ha venido el segundo error ya que lo he renombrado a "One 
feature, one OSM_element", ¡otra vez sin el código "ES:"! El resultado 
es que ahora en la versión inglesa aparece mi traducción y que no sé 
cómo deshacer el cambio.


Por favor, que alguien me eche una mano.

Gracias y perdón por la metedura de pata.
Ibai Gurrutxaga.


___
Talk-es mailing list
Talk-es@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-es

[OSM-talk] MapContrib 1.9


MapContrib version 1.9 is released with some improvements:

- the eagerly awaited opportunity to share the administration of a 
theme. In General Setup, you can add any OSM contributor who has 
contributed at least once!
- a little less expected but practical:) each time there is a reference 
to opening_hours, an icon appears allowing you to go to the Yohours 
website, facilitating the entry / http://projets.pavie.info/yohours/

- some inevitable bug fixes and other unexpected little stuff,

Thanks to Adrets (http://www.adrets-asso.fr/) and to the "Libres 
Géographes" (supported by the International Organisation of La 
Francophonie - OIF) who participate in the financing of the developments!


--
Vincent Bergeot


___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-GB] Importing Shell fuel stations

2017-11-11 Thread Rory McCann

On 06/11/17 16:45, Andy Mabbett wrote:
> Some years ago, we had a data donation, here in the United Kingdom, of
> data on cycle shops. These were imported into a tool which (if memory
> serves) enabled users to compare them to existing entries, and import
> the data to them if useful, or add new objects if necessary. I recall
> that it didn't take long for the UK community to process them.
> 
> Can that tool not be repurposed, and thereby avoid the friction that
> imports like this seem sadly to cause?

I have come across this tool which is designed for "merging" in 3rd
party data into OSM in a semi-manual manner. But it's a bit rough around
the edges, with no way to add new datasets (I think)

 http://poichecker.com/en



___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [OSM-talk-fr] MapContrib 1.9

2017-11-11 Thread PanierAvide


Bravo pour tout le boulot qui est fait sur MapContrib :-)

Adrien.


Le 11/11/2017 à 18:21, Vincent Bergeot a écrit :


Bonjour,

la version 1.9 de MapContrib est sortie avec quelques améliorations :

  * la très attendue possibilité de partager l'administration d'un
thème. Dans Configuration générale, vous pouvez ajouter tous
contributeur OSM ayant contribué au moins une fois !
  * un peu moins attendue mais pratique :) à chaque fois qu'il est
fait référence à opening_hours, une icône apparait permettant de
se rendre sur le site Yohours, facilitant la saisie /
http://projets.pavie.info/yohours/
  * quelques inévitables corrections de bugs et autres petits trucs
non attendus,


Merci à l'Adrets (http://www.adrets-asso.fr/) et aux Libres Géographes 
(soutenus par l’Organisation Internationale de la Francophonie - OIF) 
qui participent au financement des développements !


Bonne journée

--
Vincent Bergeot


___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr



--
PanierAvide
Géomaticien & développeur

___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

[OSM-talk-fr] MapContrib 1.9


Bonjour,

la version 1.9 de MapContrib est sortie avec quelques améliorations :

 * la très attendue possibilité de partager l'administration d'un
   thème. Dans Configuration générale, vous pouvez ajouter tous
   contributeur OSM ayant contribué au moins une fois !
 * un peu moins attendue mais pratique :) à chaque fois qu'il est fait
   référence à opening_hours, une icône apparait permettant de se
   rendre sur le site Yohours, facilitant la saisie /
   http://projets.pavie.info/yohours/
 * quelques inévitables corrections de bugs et autres petits trucs non
   attendus,


Merci à l'Adrets (http://www.adrets-asso.fr/) et aux Libres Géographes 
(soutenus par l’Organisation Internationale de la Francophonie - OIF) 
qui participent au financement des développements !


Bonne journée

--
Vincent Bergeot

___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [OSM-talk-fr] Utilisation du tag 'name' avec les langues régionales


Le 11/11/2017 à 12:30, marc marc a écrit :

Bonjour,

Le 11. 11. 17 à 12:02, Vincent Bergeot a écrit :

Est-il envisageable de l’empêcher d'éditer ? et si oui comment ?

bis répétita :
- faire un commentaire public sur un changeset problématique


désolé, il semble que j'ai raté quelques autres messages.
Donc fait ici : http://www.openstreetmap.org/changeset/53672431

et par @trial ici : http://www.openstreetmap.org/changeset/53646881




- apràs un temps raisonnable (qui est peut-être déjà écoulé si le point
précédent a été fait... mais personne n'a donné le lien), écrire au DWG
en demandant au miminum le revert de tout les names en france et le
revert de tout les names:fr (y compris de l'autre de la frontière)


ok, attendons donc :)

merci Marc,




Cordialement,
Marc
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr



--
Vincent Bergeot


___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

[OSM-talk-fr] cartographier toujours plus haut

2017-11-11 Thread osm . sanspourriel

http://www.sciencemag.org/news/2017/11/glacier-mapping-drone-soars-nearly-5000-meters-setting-record
Ou comment cartographier tranquillement depuis son salon.  Oui il faut en 
général quelqu'un à proximité du drone !


___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Wochennotiz Nr. 381 31.10.2017–06.11.2017

2017-11-11 Thread Wochennotizteam

Hallo,

die Wochennotiz Nr. 381 mit vielen wichtigen Neuigkeiten aus der 
OpenStreetMap-Welt ist da:

http://blog.openstreetmap.de/blog/2017/11/wochennotiz-nr-381/

Viel Spaß beim Lesen!
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de

Wochennotiz Nr. 381 31.10.2017–06.11.2017

2017-11-11 Thread Wochennotizteam

Hallo,

die Wochennotiz Nr. 381 mit vielen wichtigen Neuigkeiten aus der 
OpenStreetMap-Welt ist da:

http://blog.openstreetmap.de/blog/2017/11/wochennotiz-nr-381/

Viel Spaß beim Lesen!
___
Talk-at mailing list
Talk-at@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-at

[Talk-ca] Integrating the statistical and geospatial data with ECLAC, United Nations

2017-11-11 Thread Javier Carranza

Hi there,

I wanted to share with you guys that we are preparing together with many
other grassroot and mapping communities  a statement
on
the integration of statistical and geospatial data - portraying the civil
society standpoint - to all national statistics offices, including Stats
Can, all of which will gather in  Aguascalientes, Mexico under the Conference
of the Statistics for the Americas

umbrella
next week.

This is totally related to the #osmgeoweek, where at least in Canada and
Mexico  , we will be working
to demonstrate it is possible to map all buildings of the territory in a
census modality, i.e. covering the whole country.

For those who don't know us, we are a geo hackers community from Colombia
and neighbouring countries  working on open
geospatial data  in several countries in the region of central america and
northern south america. We are partnering in several global events like the
Geo Awareness Week, the World Data Forum

and usually lecture at the SotM US on statistical and geospatial projects
 .

Please let us know , if you agree with the above statement, so we can count
on board with OSM CA for supporting our statement , visualizing your name
and identifiers together with other National Latin American base
communities .

All best
[image: geocensos]
*Javier Carranza** Tresoldi** CEO*

*, GeoCensos@geocensos*Skype: javiercarranza
https://www.youtube.com/watch?v=9cfdYdQHZVY
Colombia Mobile:(57) 314-3244540
Panama Mobile: (507) 688 - 04892
www.geocensos.com
*Lets map together a better world*
 [image: Twitter]
 [image: LinkedIn]


"La información aquí contenida es para uso exclusivo de la persona o
entidad de destino. Está estrictamente prohibida su utilización, copia,
descarga, distribución, modificación y/o reproducción total o parcial, sin
el permiso expreso del representante legal de Fundación Geocensos, pues su
contenido puede ser de carácter confidencial y/o contener material
privilegiado. Si usted recibió esta información por error, por favor
contacte en forma inmediata a quien la envió y borre este material de su
computador. La Fundación GeoCensos no es responsable por la información
contenida en esta comunicación, el directo responsable es quien la firma o
el autor de la misma."
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca

Re: [Talk-cz] Fwd: [OpenStreetMap] Mateusz Konieczny okomentoval jednu z vašich sad změn

2017-11-11 Thread Jan Martinec

No, maják to byl kdysi dávno, teď už je to jen věž. Případně by se dala
otagovat výška, typ konstrukce, a tak, ale maják leda s historic: prefixem.

Zdar,
Honza Piškvor Martinec

Dne 11. 11. 2017 16:22 napsal uživatel "Marek Janata" :

> Ahoj,
>
> myslite ze oprava na tower je ok?
>
> M
>
> -- Forwarded message -
> From: OpenStreetMap 
> Date: so 11. 11. 2017 15:48
> Subject: [OpenStreetMap] Mateusz Konieczny okomentoval jednu z vašich sad
> změn
> To: 
>
>
> [image: OpenStreetMap]  *OpenStreetMap*
> 
>
> Dobrý den, uživateli Lopux,
>
> *Mateusz Konieczny*
>  zanechal komentář
> na jedné z vašich sad změn, vytvořené 2017-11-11 14:48:48 UTC. s komentářem
> „*add some POI*“
> [image: Mateusz Konieczny]
> 
>
> I fixed tagging of http://www.openstreetmap.org/node/4018439411#map=19/49.
> 63527/15.69424=N - it is man_made=tower, not man_made=lighthouse
>
> Více informací o této sadě změn lze nalézt na
> http://www.openstreetmap.org/changeset/37354113.
>
> Pro odhlášení z aktualizací této sady změn jděte na
> http://www.openstreetmap.org/changeset/37354113 a klikněte na „Zrušit
> odebírání“.
>
> OpenStreetMap 
>
> ___
> Talk-cz mailing list
> Talk-cz@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-cz
>
>
___
Talk-cz mailing list
Talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz

[Talk-cz] Fwd: [OpenStreetMap] Mateusz Konieczny okomentoval jednu z vašich sad změn

2017-11-11 Thread Marek Janata

Ahoj,

myslite ze oprava na tower je ok?

M

-- Forwarded message -
From: OpenStreetMap 
Date: so 11. 11. 2017 15:48
Subject: [OpenStreetMap] Mateusz Konieczny okomentoval jednu z vašich sad
změn
To: 

[image: OpenStreetMap]  *OpenStreetMap*

Dobrý den, uživateli Lopux,

*Mateusz Konieczny* 
zanechal komentář na jedné z vašich sad změn, vytvořené 2017-11-11 14:48:48
UTC. s komentářem „*add some POI*“
[image: Mateusz Konieczny]

I fixed tagging of
http://www.openstreetmap.org/node/4018439411#map=19/49.63527/15.69424=N
- it is man_made=tower, not man_made=lighthouse

Více informací o této sadě změn lze nalézt na
http://www.openstreetmap.org/changeset/37354113.

Pro odhlášení z aktualizací této sady změn jděte na
http://www.openstreetmap.org/changeset/37354113 a klikněte na „Zrušit
odebírání“.

OpenStreetMap 
___
Talk-cz mailing list
Talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz

Re: [OSM-talk-be] intersection looks very wrong

2017-11-11 Thread Gerard Vanderveken

In Streetview it looks the same.
I see this of a typical case of willing to map too much.
By that I mean every turn (or shortcut) from one lane to all possible
others.

The crossing should look in its basic form like a #.
Is it needed to represent every lane as separate roads?
I don't think so.
Only when there is a real division in the form of a physical separation,
other then a simple white line, such as a sideway, traffic island,
arched surface, ..., additional trunks should be mapped.
For all other things tagging Lanes
and Turning indications
per lane

should be sufficient to map this crossing.

A lot of cleanup is needed here, starting with the 2 trunks 214506429
and 115952062

Regards,
Gerard.

Jakka wrote:

The middle intersection looks very wrong. Want to redesign it. There
for need to know if the aerial image on "Wallononmap" are still
corresponding with what is out there ? Or are there other images ?
The same with intersection north and south of it I need to connect
directly good on those also.

Check this in editor:
1)
https://www.openstreetmap.org/#map=19/50.543085562147645/5.4872411965277195

Check a routeplanner
2)
https://www.mapcat.com/directions/car#map=18.9/50.54324/5.48770=50.54312,5.48745;50.54332,5.48772

check aerial image I want to work with. No Mapillary image yet.
3)
http://geoportail.wallonie.be/walonmap#SHARE=5DB543FAA0BC7C61E053D0AFA49DE388#CTX=DDB

___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [OSM-talk-fr] Toilettes pas publiques

2017-11-11 Thread marc marc

c'est une très bonne suggestion
https://taginfo.openstreetmap.org/tags/room=toilets

quitte à combiner les 2 :
room=toilets
access=private
+ note ou private:amenity=toilets

Le 11. 11. 17 à 13:22, JB a écrit :
> Je pense que j'aurais plutôt eu tendance à reprendre le tag utilisé pour 
> l'indoor (mais j'ai un trou de mémoire, room=toilets?), qui indique un 
> WC, mais pas des toilettes accessibles/publiques.
> JB.
> 
> Le 11.11.2017 07:06, Christian Quest a écrit :
> 
>> Si le wiki est sans équivoque sur le fait de ne pas mapper les 
>> toilettes non publiques, il faut le respecter.
>> Je conserverai l'objet dans OSM afin qu'il ne soit pas recréé par un 
>> autre contributeur, mais avec un tag du genre: private:amenity=toilets 
>> ou quelque chose qu'un outil qui se base sur amenity=toilets 
>> n'utilisera pas mais compréhensible par un contributeur.. ça pourrait 
>> même être un simple note=private toilets, not to map as 
>> amenity=toilets according to the wiki
>>
>> Le 10 novembre 2017 à 22:38, marc marc a écrit :
>>
>> Le 10. 11. 17 à 22:23, David Crochet a écrit :
>> > Le 10/11/2017 à 21:49, Romain MEHUT a écrit :
>> >> Je vois que dans le wiki, le tag access=private est rayé. Sur
>> le fond,
>> >> je comprends la logique mais si je retire le tag amenity que
>> >> mettriez-vous à la place ?
>> > Pour moi la règle est simple :
>> > Que voit-je : je vois des toilettes, j'ajoute dans OSM des toilettes
>>
>> la règle est simple mais je comprend tout a fait l'auteur de la note.
>> une amenity qui n'est pas accessible, détruite, hors d'usage ou qui a
>> changé d'usage n'est plus une amenity.
>> D'ailleurs la page wiki concernée demande de ne pas maper les
>> toilettes
>> privées.
>>
>> Autre exemple : j'ai rencontré un coin ou quelqu'un a créé un tag
>> parking pour chaque place de parking privé associé à un immeuble.
>> résultat le plan est inutilisable tant visuellement que par recherche.
>> faut-il changer le rendu et tous les outils ?
>> ou préfixer la fonction qui n'existe pas avec no: ?
>> je n'ai pas encore fait les modifs (parce qu'ils y a + urgent à cet
>> endroit) mais je ne vois que la 2ieme solution comme réaliste.
>>
>> De même il y a déjà un consensus pour dire qu'un équipement d'urgence
>> qui ne fonctionne plus n'est plus un équipement d'urgence (on le
>> prefix
>> par disused: généralement).
>> cela me semble tout aussi valable et non contradictoire avec la règle
>> "mapper ce qu'on voit".
>>
>> Cordialement,
>> Marc
>> ___
>> Talk-fr mailing list
>> Talk-fr@openstreetmap.org 
>> https://lists.openstreetmap.org/listinfo/talk-fr
>> 
>>
>>
>>
>> -- 
>> Christian Quest - OpenStreetMap France
>>
>> ___
>> Talk-fr mailing list
>> Talk-fr@openstreetmap.org 
>> https://lists.openstreetmap.org/listinfo/talk-fr
> 
> 
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
> 

___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

[OSM-talk-fr] [CDL2017] Participants stand

2017-11-11 Thread orhygine

Salut,

Pour le stand OSM du week-end prochain au Capitole du Libre, l'organisation
me demande de transmettre les noms des participants pour les badges.

Se sont déjà manifestés Laurent C., Jean-Guilhem C., Sébastien D., Vincent
P.

D'autres ?

a+
Christophe

-- 
Christophe aka orhygine | http://orhyginal.free.fr |
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [Talk-cz] jednosměrka

2017-11-11 Thread Zbyněk Datinský

Rád bych jen připomenul, že přenosné, pevně neinstalované, dopravní značení se nemapuje. A myslím, že na tom nemění nic ani fakt, že se na místě vyskytuje pravidelně dle sněhu.Dne 11. 11. 2017 12:38 napsal uživatel marek :A jak označím směr jednosměrky za sněhu?

Marek Polák

__
> Od: Pavel Machek 
> Komu: OpenStreetMap Czech Republic 
> Datum: 10.11.2017 23:46
> Předmět: Re: [Talk-cz] jednosměrka
>

On Thu 2017-11-09 21:30:49, Miroslav Suchý wrote:
 > Dne 9.11.2017 v 21:26 marek napsal(a):
 > > Právě, že to nemá datum. Napadne sníh a policajti tam dají jednosměrku a
 > > vybírají pokuty. Sníh sleze a už to je zase obousměrná.
 > 
 > oneway:conditional=yes @ (snow)
 > 
 > Je to na te wiki popsano "road condition".

 No... "oneway:conditional=yes @ (snow)" by bylo "je tam cedule
 jednosmerky, s dodatkem ze plati jen kdyz je snih". Jestli tam
 policajti davaji jednosmerku a pak ji zase odnesou, tak je to malicko
 jina situace...

 ...i kdyz bych to tak asi taky oznacil ;-).
 Pavel
 -- 
 (english) http://www.livejournal.com/~pavelmachek
 (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

 --

 ___
 Talk-cz mailing list
 Talk-cz@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/talk-cz

___
Talk-cz mailing list
Talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz

[OSM-talk-be] intersection looks very wrong

2017-11-11 Thread Jakka




The middle intersection looks very wrong. Want to redesign it. There for 
need to know if the aerial image on "Wallononmap" are still 
corresponding with what is out there ? Or are there other images ?
The same with intersection north and south of it I need to connect 
directly good on those also.

Check this in editor:
1) 
https://www.openstreetmap.org/#map=19/50.543085562147645/5.4872411965277195

Check a routeplanner
2) 
https://www.mapcat.com/directions/car#map=18.9/50.54324/5.48770=50.54312,5.48745;50.54332,5.48772

check aerial image I want to work with. No Mapillary image yet.
3) 
http://geoportail.wallonie.be/walonmap#SHARE=5DB543FAA0BC7C61E053D0AFA49DE388#CTX=DDB



___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Re: [Talk-it] Relazione route multiuso

penso che se fai:
“route=mtb;hiking;bicycle”

non é reconosciuto e poi non é verificato (skipped)

Jo

2017-11-11 13:02 GMT+01:00 carlo folini :

> Ho provato ad analizzare con relation analyzer
> http://ra.osmsurround.org/searchRelation?name=sentiero+
> valtellina=
>
> La cosa 'stana' è che la relazione route=bicycle restituisce un "internal
> error" (ho scritto per capire la causa dell'errore)
> Quella con route=mtb;hiking;bicycle dice che la relazione va bene.
>
> Diciamo che il primo step è positivo. Quindi funziona per OSM, Relation
> analyzer, WayMarkedTrail, OpenTopoMap
> .
> Su taginfo non sono molte le istanze di questo tipo.
>
> Cercando con overpass-turbo con la query
> /*
> This has been generated by the overpass-turbo wizard.
> The original search was:
> “route=mtb;hiking;bicycle”
> */
> [out:json][timeout:25];
> // gather results
> (
>   // query part for: “route="mtb;hiking;bicycle"”
>   relation["route"~";"]({{bbox}});
> );
> // print results
> out body;
> >;
> out skel qt;
>
> se ne trovano poche in giro per l'italia, zona Vicenza, Milano, Novara,
> Torino
> http://www.openstreetmap.org/relation/3088663
> http://www.openstreetmap.org/relation/2827085
>
>
> 
>  Mail
> priva di virus. www.avast.com
> 
> <#m_-3912852951900430660_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> Il giorno 10 novembre 2017 19:06, Marco  ha
> scritto:
>
>> Grazie a tutti e tre per le risposte, quindi il tag route con più valori
>> non è sbagliato, è solo più scomodo da manutenere nel caso cambi il
>> percorso, ho capito bene?! Comunque va bene, ne creerò una per ogni
>> "disciplina" (mtb, hiking, cycling)
>>
>>
>> ___
>> Talk-it mailing list
>> Talk-it@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-it
>>
>
>
>
> --
> Carlo Folini
> mailto:carlo.fol...@gmail.com
>
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it
>
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [OSM-talk-fr] Toilettes pas publiques

2017-11-11 Thread JB

Je pense que j'aurais plutôt eu tendance à reprendre le tag utilisé pour
l'indoor (mais j'ai un trou de mémoire, room=toilets?), qui indique un
WC, mais pas des toilettes accessibles/publiques.
JB. 

Le 11.11.2017 07:06, Christian Quest a écrit :

> Si le wiki est sans équivoque sur le fait de ne pas mapper les toilettes non 
> publiques, il faut le respecter. 
> Je conserverai l'objet dans OSM afin qu'il ne soit pas recréé par un autre 
> contributeur, mais avec un tag du genre: private:amenity=toilets ou quelque 
> chose qu'un outil qui se base sur amenity=toilets n'utilisera pas mais 
> compréhensible par un contributeur.. ça pourrait même être un simple 
> note=private toilets, not to map as amenity=toilets according to the wiki  
> 
> Le 10 novembre 2017 à 22:38, marc marc  a écrit :
> 
>> Le 10. 11. 17 à 22:23, David Crochet a écrit :
>>> Le 10/11/2017 à 21:49, Romain MEHUT a écrit :
 Je vois que dans le wiki, le tag access=private est rayé. Sur le fond,
 je comprends la logique mais si je retire le tag amenity que
 mettriez-vous à la place ?
>>> Pour moi la règle est simple :
>>> Que voit-je : je vois des toilettes, j'ajoute dans OSM des toilettes
>> 
>> la règle est simple mais je comprend tout a fait l'auteur de la note.
>> une amenity qui n'est pas accessible, détruite, hors d'usage ou qui a
>> changé d'usage n'est plus une amenity.
>> D'ailleurs la page wiki concernée demande de ne pas maper les toilettes
>> privées.
>> 
>> Autre exemple : j'ai rencontré un coin ou quelqu'un a créé un tag
>> parking pour chaque place de parking privé associé à un immeuble.
>> résultat le plan est inutilisable tant visuellement que par recherche.
>> faut-il changer le rendu et tous les outils ?
>> ou préfixer la fonction qui n'existe pas avec no: ?
>> je n'ai pas encore fait les modifs (parce qu'ils y a + urgent à cet
>> endroit) mais je ne vois que la 2ieme solution comme réaliste.
>> 
>> De même il y a déjà un consensus pour dire qu'un équipement d'urgence
>> qui ne fonctionne plus n'est plus un équipement d'urgence (on le prefix
>> par disused: généralement).
>> cela me semble tout aussi valable et non contradictoire avec la règle
>> "mapper ce qu'on voit".
>> 
>> Cordialement,
>> Marc
>> 
>> ___
>> Talk-fr mailing list
>> Talk-fr@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-fr [1]
> 
> -- 
> 
> Christian Quest - OpenStreetMap France 
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
 

Links:
--
[1] https://lists.openstreetmap.org/listinfo/talk-fr___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [Talk-it] Relazione route multiuso

2017-11-11 Thread carlo folini

Ho provato ad analizzare con relation analyzer
http://ra.osmsurround.org/searchRelation?name=sentiero+valtellina=

La cosa 'stana' è che la relazione route=bicycle restituisce un "internal
error" (ho scritto per capire la causa dell'errore)
Quella con route=mtb;hiking;bicycle dice che la relazione va bene.

Diciamo che il primo step è positivo. Quindi funziona per OSM, Relation
analyzer, WayMarkedTrail, OpenTopoMap
.
Su taginfo non sono molte le istanze di questo tipo.

Cercando con overpass-turbo con la query
/*
This has been generated by the overpass-turbo wizard.
The original search was:
“route=mtb;hiking;bicycle”
*/
[out:json][timeout:25];
// gather results
(
  // query part for: “route="mtb;hiking;bicycle"”
  relation["route"~";"]({{bbox}});
);
// print results
out body;
>;
out skel qt;

se ne trovano poche in giro per l'italia, zona Vicenza, Milano, Novara,
Torino
http://www.openstreetmap.org/relation/3088663
http://www.openstreetmap.org/relation/2827085


Mail
priva di virus. www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Il giorno 10 novembre 2017 19:06, Marco  ha scritto:

> Grazie a tutti e tre per le risposte, quindi il tag route con più valori
> non è sbagliato, è solo più scomodo da manutenere nel caso cambi il
> percorso, ho capito bene?! Comunque va bene, ne creerò una per ogni
> "disciplina" (mtb, hiking, cycling)
>
>
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it
>



-- 
Carlo Folini
mailto:carlo.fol...@gmail.com
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [Talk-cz] jednosměrka

2017-11-11 Thread Miroslav Suchý

Dne 11.11.2017 v 12:38 marek napsal(a):
> A jak označím směr jednosměrky za sněhu?

Smerem te cesty. Kazda cesta ma smer. I kdyz to neni jednosmerka.
Napriklad u srazu (cliff) znaci smer cesty kde je vrsek a kde spodek srazu.

Mirek

___
Talk-cz mailing list
Talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz

Re: [Talk-cz] jednosměrka

2017-11-11 Thread marek


A jak označím směr jednosměrky za sněhu?
 
Marek Polák
 
__

Od: Pavel Machek 
Komu: OpenStreetMap Czech Republic 
Datum: 10.11.2017 23:46
Předmět: Re: [Talk-cz] jednosměrka


On Thu 2017-11-09 21:30:49, Miroslav Suchý wrote:
> Dne 9.11.2017 v 21:26 marek napsal(a):
> > Právě, že to nemá datum. Napadne sníh a policajti tam dají jednosměrku a
> > vybírají pokuty. Sníh sleze a už to je zase obousměrná.
> 
> oneway:conditional=yes @ (snow)
> 
> Je to na te wiki popsano "road condition".


No... "oneway:conditional=yes @ (snow)" by bylo "je tam cedule
jednosmerky, s dodatkem ze plati jen kdyz je snih". Jestli tam
policajti davaji jednosmerku a pak ji zase odnesou, tak je to malicko
jina situace...

...i kdyz bych to tak asi taky oznacil ;-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek 

(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html 



--

___
Talk-cz mailing list
Talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz 


___
Talk-cz mailing list
Talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz

Re: [OSM-talk-fr] Utilisation du tag 'name' avec les langues régionales

2017-11-11 Thread marc marc

Bonjour,

Le 11. 11. 17 à 12:02, Vincent Bergeot a écrit :
> Est-il envisageable de l’empêcher d'éditer ? et si oui comment ?

bis répétita :
- faire un commentaire public sur un changeset problématique
- apràs un temps raisonnable (qui est peut-être déjà écoulé si le point 
précédent a été fait... mais personne n'a donné le lien), écrire au DWG 
en demandant au miminum le revert de tout les names en france et le 
revert de tout les names:fr (y compris de l'autre de la frontière)

Cordialement,
Marc
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [OSM-talk-fr] Utilisation du tag 'name' avec les langues régionales

2017-11-11 Thread Philippe Verdy

visiblement il passe par un bot qui crée un changeset par nom modifié, ce
qui alourdit sérieusement les annulations multiples de ce qu'il fait.
A signaler au DWG donc pour bloquer son compte. Il a édéjà été averti
plusieurs fois, reverté plusieurs fois.

Le 11 novembre 2017 à 12:02, Vincent Bergeot  a écrit :

> Bonjour,
>
> Le 17/10/2017 à 12:55, Vincent Bergeot a écrit :
>
>> Au regard des multiples discussions, je ne sais pas comment les
>> contacter, du moins pour le nouveau http://www.openstreetmap.org/u
>> ser/Baxe%20Nafarroa
>>
>> Pour lui : http://www.openstreetmap.org/node/1690923675/history on
>> rentre dans la bataille d'édition je pense ! Je viens de renvoyer un mot en
>> proposant de réfléchir plutôt au rendu cartographique qu'au changement de
>> contenu du "name".
>>
>
> cela continue :
>
> http://www.openstreetmap.org/node/1826708933/history#map=19/
> 43.39876/-1.45656
>
> http://www.openstreetmap.org/node/388577606/history
>
> Izpura continue à ajouter des noms basques sur le format "name = nom en
> français - noms en basque", pas de réponse de sa part et c'est un peu en
> mode je fais ma vie j'ai l'impression : http://www.openstreetmap.org/u
> ser/izpura
>
> Ce n'est pas seulement les noms de villages, j'ai l'impression que c'est
> également d'autres objets, type caserne de pompiers :
> http://www.openstreetmap.org/way/522188195
>
> Est-il envisageable de l’empêcher d'éditer ? et si oui comment ?
>
> Cordialement
>
> PS : je reconnais volontiers que la photo de profil et le caractère
> patriotico-nationalo-je montre un drapeau n'aide pas le regard sur ce que
> fait ce bonhomme !
>
> --
> Vincent Bergeot
>
>
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [OSM-talk-fr] Utilisation du tag 'name' avec les langues régionales


Bonjour,

Le 17/10/2017 à 12:55, Vincent Bergeot a écrit :
Au regard des multiples discussions, je ne sais pas comment les 
contacter, du moins pour le nouveau 
http://www.openstreetmap.org/user/Baxe%20Nafarroa


Pour lui : http://www.openstreetmap.org/node/1690923675/history on 
rentre dans la bataille d'édition je pense ! Je viens de renvoyer un 
mot en proposant de réfléchir plutôt au rendu cartographique qu'au 
changement de contenu du "name".


cela continue :

http://www.openstreetmap.org/node/1826708933/history#map=19/43.39876/-1.45656

http://www.openstreetmap.org/node/388577606/history

Izpura continue à ajouter des noms basques sur le format "name = nom en 
français - noms en basque", pas de réponse de sa part et c'est un peu en 
mode je fais ma vie j'ai l'impression : 
http://www.openstreetmap.org/user/izpura


Ce n'est pas seulement les noms de villages, j'ai l'impression que c'est 
également d'autres objets, type caserne de pompiers : 
http://www.openstreetmap.org/way/522188195


Est-il envisageable de l’empêcher d'éditer ? et si oui comment ?

Cordialement

PS : je reconnais volontiers que la photo de profil et le caractère 
patriotico-nationalo-je montre un drapeau n'aide pas le regard sur ce 
que fait ce bonhomme !


--
Vincent Bergeot


___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

semanarioOSM Nº 381 2017-10-31-2017-11-07

Hola, el semanario Nº 381, el sumario de todo lo que está ocurriendo en el 
mundo de openstreetmap está en línea en *español*:

http://www.weeklyosm.eu/es/archives/9621/

¡Disfruta!

semanarioOSM? 
¿Dónde?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
¿Quién?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-es mailing list
Talk-es@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-es

semanarioOSM Nº 381 2017-10-31-2017-11-07

Hola, el semanario Nº 381, el sumario de todo lo que está ocurriendo en el 
mundo de openstreetmap está en línea en *español*:

http://www.weeklyosm.eu/es/archives/9621/

¡Disfruta!

semanarioOSM? 
¿Dónde?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
¿Quién?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-cu mailing list
Talk-cu@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cu

semanarioOSM Nº 381 2017-10-31-2017-11-07

Hola, el semanario Nº 381, el sumario de todo lo que está ocurriendo en el 
mundo de openstreetmap está en línea en *español*:

http://www.weeklyosm.eu/es/archives/9621/

¡Disfruta!

semanarioOSM? 
¿Dónde?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
¿Quién?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-cl mailing list
Talk-cl@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cl

semanarioOSM Nº 381 2017-10-31-2017-11-07