date:20200111


Ciao Francesco,

On 12/01/20 08:14, Francesco Ansanelli wrote:
mi sembra che hai dato per scontato che il esistano 2 tag per i 
cellulari...
Dalla discussione precedente non è ancora chiaro se "phone:mobile" è 
effettivamente uguale a "contact:mobile".
L'esempio "strano" che avevi citato è un caso particolarissimo 
praticamente non utilizzato. A me pare che i due tag siano usati 
assolutamente allo stesso modo.
Inoltre la votazione era a favore dello schema più usato e non è 
passata, magari possiamo fare il contrario per vedere se fosse 
preferito l'altro schema.


La votazione era stata fatta per deprecare uno schema in ambito 
internazionale.


La mia domanda era ristretta alla possibilità di concordare a livello 
nazionale su una delle due possibilità...


Ale


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

Re: [Talk-it] Numero di cellulare in OSM

Notare solo che è stato solo discusso l'uso di

contact:phone:IT

che sarebbe un terzo tag per i numeri di telefono, da usare per i numeri
verdi (800) e inserire senza prefisso internazionale (in quanto non possono
essere chiamati da estero).


Il dom 12 gen 2020, 07:47 Edoardo Yossef Marascalchi <
e.marascal...@gmail.com> ha scritto:

> penso ad esempio a
> contact:facebook
> contact:skype
> contact: whatsapp
> contact:pigeon
> contact:owl
> contact:strllettera
> 
>
> Il dom 12 gen 2020, 8:44 AM Edoardo Yossef Marascalchi <
> e.marascal...@gmail.com> ha scritto:
>
>> detto che nessuno di noi è in grado di distinguere un numero fisso
>> straniera da un cellulare, negli USA non hanno neppure prefissi diversi e
>> fino a qualche anno fa, per questo, il costo della chiamata era condiviso
>> tra chiamato e chiamante (ora credo sian cambiate le cose ma non be posso
>> essere certo).
>>
>> io, personalmente, preferisco la tassonimia contact: dove è facilmente e
>> intelligibilmente raggruppabile qualsiasi tag odierno o futuro
>>
>>
>>
>> Il dom 12 gen 2020, 7:55 AM canfe  ha scritto:
>>
>>> +1
>>>
>>>
>>>
>>> --
>>> Sent from: http://gis.19327.n8.nabble.com/Italy-General-f5324174.html
>>>
>>> ___
>>> 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
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [Talk-it] Numero di telefono in Italia: phone/contact:phone

Il dom 12 gen 2020, 07:03 Alessandro Sarretta 
ha scritto:

> Ciao a tutti,
>
> provo a riprendere il thread sul numero di cellulare con un cambio di
> oggetto e una proposta.
>
> Chiedo in particolar modo ai più esperti e veterani: anche se a livello
> internazionale non c'è un accordo nella scelta tra lo schema di tagging
> "phone" o "contact:phone", potremmo, come comunità italiana, decidere
> invece di sceglierne uno per semplificarci la vita almeno "qui da noi"?
>
> Se consideriamo la possibilità di mantenere la differenziazione del mobile
> (io sarei d'accordo, ma potremmo decide anche altrimenti), le variabili
> principali non sono molte in realtà, mi pare siano essenzialmente 4:
> *phone* / *phone:mobile *e *contact:phone* / *contact:mobile*.
>
> Guardando al database taginfo in Italia (grazie Martin per aver fatto
> girare la notizia recentemente), vedo questi numeri:
> phone 60681 [1]
> phone:mobile 897 [2]
> contact:phone 10858 [3]
> contact:mobile 1120 [4]
>
> Se volessimo mantenere lo schema più usato, potremmo concordare su phone e
> phone:mobile.
>
> Cosa ne dite?
>
Ciao,

mi sembra che hai dato per scontato che il esistano 2 tag per i cellulari...
Dalla discussione precedente non è ancora chiaro se "phone:mobile" è
effettivamente uguale a "contact:mobile".

Forse è anche per questo che qualcuno ha usato "mobile"?

https://taginfo.openstreetmap.org/keys/mobile

Tag evidentemente anche esso mai documentato...

Inoltre la votazione era a favore dello schema più usato e non è passata,
magari possiamo fare il contrario per vedere se fosse preferito l'altro
schema.

Ale
>
>
> [1] https://taginfo.geofabrik.de/europe/italy/keys/phone
>
> [2] https://taginfo.geofabrik.de/europe/italy/keys/phone%3Amobile
>
> [3] https://taginfo.geofabrik.de/europe/italy/keys/contact%3Aphone
>
> [4] https://taginfo.geofabrik.de/europe/italy/keys/contact%3Amobile
> ___
> 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: [Talk-it] Numero di cellulare in OSM

2020-01-11 Per discussione Edoardo Yossef Marascalchi

penso ad esempio a
contact:facebook
contact:skype
contact: whatsapp
contact:pigeon
contact:owl
contact:strllettera


Il dom 12 gen 2020, 8:44 AM Edoardo Yossef Marascalchi <
e.marascal...@gmail.com> ha scritto:

> detto che nessuno di noi è in grado di distinguere un numero fisso
> straniera da un cellulare, negli USA non hanno neppure prefissi diversi e
> fino a qualche anno fa, per questo, il costo della chiamata era condiviso
> tra chiamato e chiamante (ora credo sian cambiate le cose ma non be posso
> essere certo).
>
> io, personalmente, preferisco la tassonimia contact: dove è facilmente e
> intelligibilmente raggruppabile qualsiasi tag odierno o futuro
>
>
>
> Il dom 12 gen 2020, 7:55 AM canfe  ha scritto:
>
>> +1
>>
>>
>>
>> --
>> Sent from: http://gis.19327.n8.nabble.com/Italy-General-f5324174.html
>>
>> ___
>> 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: [Talk-it] Numero di cellulare in OSM

2020-01-11 Per discussione Edoardo Yossef Marascalchi

detto che nessuno di noi è in grado di distinguere un numero fisso
straniera da un cellulare, negli USA non hanno neppure prefissi diversi e
fino a qualche anno fa, per questo, il costo della chiamata era condiviso
tra chiamato e chiamante (ora credo sian cambiate le cose ma non be posso
essere certo).

io, personalmente, preferisco la tassonimia contact: dove è facilmente e
intelligibilmente raggruppabile qualsiasi tag odierno o futuro



Il dom 12 gen 2020, 7:55 AM canfe  ha scritto:

> +1
>
>
>
> --
> Sent from: http://gis.19327.n8.nabble.com/Italy-General-f5324174.html
>
> ___
> 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: [talk-au] Way has been simplified...

2020-01-11 Per discussione Andrew Davidson


On 12/1/20 12:37 pm, Sebastian S. wrote:
When using OSMAnd for routing I came across the following note: "way has 
been simplified using a error criteria of 3m" it is usually in green text.

Does anyone know what this means


It indicates that the number of points in the lines has been reduced by 
removing the unnecessary ones, while keeping the simplified line within 
3 m of the original.


, why do we need the note?

It is a requirement under the CC-BY 4.0 license to indicate if you 
modified the licensed material.


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

[Talk-it] Numero di telefono in Italia: phone/contact:phone


Ciao a tutti,

provo a riprendere il thread sul numero di cellulare con un cambio di 
oggetto e una proposta.


Chiedo in particolar modo ai più esperti e veterani: anche se a livello 
internazionale non c'è un accordo nella scelta tra lo schema di tagging 
"phone" o "contact:phone", potremmo, come comunità italiana, decidere 
invece di sceglierne uno per semplificarci la vita almeno "qui da noi"?


Se consideriamo la possibilità di mantenere la differenziazione del 
mobile (io sarei d'accordo, ma potremmo decide anche altrimenti), le 
variabili principali non sono molte in realtà, mi pare siano 
essenzialmente 4: /phone/ / /phone:mobile /e /contact:phone/ / 
/contact:mobile/.


Guardando al database taginfo in Italia (grazie Martin per aver fatto 
girare la notizia recentemente), vedo questi numeri:


phone 60681 [1]
phone:mobile 897 [2]
contact:phone 10858 [3]
contact:mobile 1120 [4]

Se volessimo mantenere lo schema più usato, potremmo concordare su phone 
e phone:mobile.


Cosa ne dite?

Ale


[1] https://taginfo.geofabrik.de/europe/italy/keys/phone

[2] https://taginfo.geofabrik.de/europe/italy/keys/phone%3Amobile

[3] https://taginfo.geofabrik.de/europe/italy/keys/contact%3Aphone

[4] https://taginfo.geofabrik.de/europe/italy/keys/contact%3Amobile

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

Re: [Talk-it] Numero di cellulare in OSM

2020-01-11 Per discussione canfe

+1



--
Sent from: http://gis.19327.n8.nabble.com/Italy-General-f5324174.html

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

Re: [Talk-it] violazione di licenza ?


Ciao Volker, vado subito alla domanda finale

On 11/01/20 22:22, Volker Schmidt wrote:

Ma è una mancata attribuzione?


Secondo me assolutamente sì.

Ti suggerirei di scrivere e farglielo notare (chiedendo una conferma di 
quanto hai ipotizzato/verificato).


Ale


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

Re: [talk-au] NPWS landing sites task

2020-01-11 Per discussione Graeme Fitzpatrick

& done!

Thanks

Graeme


On Sun, 12 Jan 2020 at 10:14, Graeme Fitzpatrick 
wrote:

>
> Thanks fellas!
>
> Back to it, then :-)
>
> Graeme
>
>
> On Sat, 11 Jan 2020 at 22:08, Sebastian S.  wrote:
>
>> I use a node for most.
>> Only if there is a distinct clearing in the middle of nowhere or a marked
>> helipad then I use an area.
>>
>> On 11 January 2020 8:56:01 pm AEDT, Andrew Harvey <
>> andrew.harv...@gmail.com> wrote:
>>>
>>> On Sat, 11 Jan 2020 at 17:56, Graeme Fitzpatrick 
>>> wrote:
>>>
 Question re this Map Roulette task, thanks.

 I take it these details have come from a NPWS list of some form that
 says there is a landing site at "this" spot.

>>>
>>> Yes that's right.
>>>
>>>
 So, even if it shows as just a patch of bare ground, we tag it as a
 landing site?

>>>
>>> This dataset is saying that the patch of bare ground is a landing site,
>>> either an emergency one or actual helipad. Remember we're not just mapping
>>> any available patch of bare ground as an emergency landing site, only those
>>> which NPWS have designated as emergency landing sites.
>>>
>>>

 Node or area?

>>>
>>> Up to you both are fine, but unless there is some kind of boundary you
>>> can see I'd just go with a node.
>>>
>>>

 Of the few I've looked at, one was a very discernible flattened out
 square of dirt which I tagged as an area, another was just a clearing in
 the forest so I put a node there, while the third was just a spot in an
 open paddock.

 & it would appear that emergency=landing_site doesn't render in any way
 - does that matter?

>>>
>>> That's okay, typically something only starts getting rendered by maps
>>> and apps once it has some usage, so actually mapping it helps justify
>>> getting it into maps and apps.
>>>
>>
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au

Re: [OSM-talk] Too subjective & problematic Re: no-go-areas

2020-01-11 Per discussione Paul Johnson

On Sat, Jan 11, 2020 at 2:25 PM Martin Trautmann via talk <
talk@openstreetmap.org> wrote:

> On 20-01-02 12:23, pangoSE wrote:
>
> > A map cannot solve a lack of general awareness when visiting a
> > new/unknown place. Going to the mountains to hike can also be dangerous
> > if you are not well prepared. This is of course not marked on the map!
>
> I agree that I don't know any non-subjective way how to identify such an
> area.
>

OK, too subjective for OSM then.

> But a good map is for people who do NOT know this area.
> People who know about neither need a map nor a warning.
>

Not our problem, we map the objective.
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [talk-au] Way has been simplified...

2020-01-11 Per discussione David Wales

By default OSMAnd shows things which may be of interest to mappers.

If you don't want to see these notes, you can turn the feature off.

On 12 January 2020 1:18:42 pm AEDT, Warin <61sundow...@gmail.com> wrote:
>On 12/1/20 12:37 pm, Sebastian S. wrote:
>> When using OSMAnd for routing I came across the following note: "way 
>> has been simplified using a error criteria of 3m" it is usually in 
>> green text.
>> Does anyone know what this means, why do we need the note? What 
>> purpose does it serve?
>
>
>This is usually from an import of data. The data may have many points 
>(nodes in OSM) that lead to data bloat.
>
>JOSM has a tool that reduces the number of nodes such that any error 
>will be less than 3 meters from the original information, 'simplify
>way'.
>
>
>It may be better to have these as 'comment=*' rather than 'note=*'?
>They 
>should only be for other mappers to see if they have some concern with 
>the data.
>
>
>___
>Talk-au mailing list
>Talk-au@openstreetmap.org
>https://lists.openstreetmap.org/listinfo/talk-au
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au

Re: [talk-au] Way has been simplified...

2020-01-11 Per discussione Warin


On 12/1/20 12:37 pm, Sebastian S. wrote:
When using OSMAnd for routing I came across the following note: "way 
has been simplified using a error criteria of 3m" it is usually in 
green text.
Does anyone know what this means, why do we need the note? What 
purpose does it serve?



This is usually from an import of data. The data may have many points 
(nodes in OSM) that lead to data bloat.


JOSM has a tool that reduces the number of nodes such that any error 
will be less than 3 meters from the original information, 'simplify way'.



It may be better to have these as 'comment=*' rather than 'note=*'? They 
should only be for other mappers to see if they have some concern with 
the data.



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

[talk-au] Way has been simplified...

When using OSMAnd for routing I came across the following note: "way has been 
simplified using a error criteria of 3m" it is usually in green text.
Does anyone know what this means, why do we need the note? What purpose does it 
serve?___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au

Re: [talk-au] NPWS landing sites task

2020-01-11 Per discussione Graeme Fitzpatrick

Thanks fellas!

Back to it, then :-)

Graeme


On Sat, 11 Jan 2020 at 22:08, Sebastian S.  wrote:

> I use a node for most.
> Only if there is a distinct clearing in the middle of nowhere or a marked
> helipad then I use an area.
>
> On 11 January 2020 8:56:01 pm AEDT, Andrew Harvey <
> andrew.harv...@gmail.com> wrote:
>>
>> On Sat, 11 Jan 2020 at 17:56, Graeme Fitzpatrick 
>> wrote:
>>
>>> Question re this Map Roulette task, thanks.
>>>
>>> I take it these details have come from a NPWS list of some form that
>>> says there is a landing site at "this" spot.
>>>
>>
>> Yes that's right.
>>
>>
>>> So, even if it shows as just a patch of bare ground, we tag it as a
>>> landing site?
>>>
>>
>> This dataset is saying that the patch of bare ground is a landing site,
>> either an emergency one or actual helipad. Remember we're not just mapping
>> any available patch of bare ground as an emergency landing site, only those
>> which NPWS have designated as emergency landing sites.
>>
>>
>>>
>>> Node or area?
>>>
>>
>> Up to you both are fine, but unless there is some kind of boundary you
>> can see I'd just go with a node.
>>
>>
>>>
>>> Of the few I've looked at, one was a very discernible flattened out
>>> square of dirt which I tagged as an area, another was just a clearing in
>>> the forest so I put a node there, while the third was just a spot in an
>>> open paddock.
>>>
>>> & it would appear that emergency=landing_site doesn't render in any way
>>> - does that matter?
>>>
>>
>> That's okay, typically something only starts getting rendered by maps and
>> apps once it has some usage, so actually mapping it helps justify getting
>> it into maps and apps.
>>
>
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au

Re: [OSM-talk] Too subjective & problematic Re: no-go-areas

2020-01-11 Per discussione Dave F via talk


On 11/01/2020 20:22, Martin Trautmann via talk wrote:


But a good map is for people who do NOT know this area.
People who know about neither need a map nor a warning.


Which those with more accurate, regularly updated data, such a emergency 
services & governmental authorities, can provide by overlaying it onto OSM.


DaveF

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

Re: [OSM-talk] [Tagging] nomoj de internaciaj objektoj / nazwy obiektów międzynarodowych / names of international objects

2020-01-11 Per discussione Tomek

W dniu 20-01-12 o 00:04, stevea pisze:
>> Se vi parolas Esperanton, kial vi ĝin ne uzas?
> Because this is an English-language list.
>
>> Kial mi devas uzi
>> elektronikan tradukilon por kompreni vian mesaĝon, kaj vi postulas por
>> skribi en via gepatra lingvo? Mi ne devigas al aliaj homoj lerni mian
>> lingvon (la polan). Kiu estas fanatikulo tie ĉi?
> I speak some Polish, too.  Yet, I don't wish to fight with you.
>
> I will continue to use English here, though I will not continue to answer you 
> when you write to the list in Esperanto (or Polish).  Why?  I repeat myself 
> (as do others here):  because this is an English-language list.
>
> Peace,
> SteveA
EO
Listoj por uzantoj de angla lingvo:
https://lists.openstreetmap.org/listinfo/talk-gb
https://lists.openstreetmap.org/listinfo/talk-us
Tie ĉi estas ĝenerala internacia listo pri OSM-etikedoj.

PL
Listy dla użytkowników języka angielskiego:
https://lists.openstreetmap.org/listinfo/talk-gb
https://lists.openstreetmap.org/listinfo/talk-us
Tutaj jest ogólna lista odnośnie znaczników OSM.
<>___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Fwd: [Tagging] Tagging the local language

2020-01-11 Per discussione Joseph Eisenberg

> a change in the urban structure (urban confuguration, architectural style, 
> living standards, socially / ownerstructure, etc.). can mark a border very 
> strongly in some instances

Right, that's why we can map landuse=residential, landuse=industrial,
landuse=commercial and landuse=retail as areas with clear boundaries.

- Joseph Eisenberg

On 1/12/20, Martin Koppenhoefer  wrote:
> Am Sa., 11. Jan. 2020 um 01:30 Uhr schrieb Joseph Eisenberg <
> joseph.eisenb...@gmail.com>:
>
>> On Sat, Jan 11, 2020 at 2:49 AM Mateusz Konieczny
>> 
>> wrote:
>>
>>> or to use tricks like the “place=neighbourhood” one (which is based on
>>> POIs rather than polygons)?
>>>
>>> It is certainly wrong to do this.
>>>
>>
>> I think the “trick” here is referring to the stand at practice of mapping
>> all place= features as nodes, including neighborhoods, because their
>> boundaries are usually fuzzy (and precise boundaries can be mapped with
>> boundary=administrative or another boundary= tag).
>>
>
>
>
> mostly I agree, although it should be mentioned that neighbourhood (or
> other place boundaries like quarter and suburb) may be very clear although
> they aren't officially declared: when they are hard "natural" borders like
> railroads, rivers, motorways, etc. Also a change in the urban structure
> (urban confuguration, architectural style, living standards, socially /
> ownerstructure, etc.). can mark a border very strongly in some instances,
> without it having to be an administrative boundary.
>
> Cheers
> Martin
>

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

Re: [OSM-talk] [Tagging] nomoj de internaciaj objektoj / nazwy obiektów międzynarodowych / names of international objects

2020-01-11 Per discussione stevea

> Se vi parolas Esperanton, kial vi ĝin ne uzas?

Because this is an English-language list.

> Kial mi devas uzi
> elektronikan tradukilon por kompreni vian mesaĝon, kaj vi postulas por
> skribi en via gepatra lingvo? Mi ne devigas al aliaj homoj lerni mian
> lingvon (la polan). Kiu estas fanatikulo tie ĉi?

I speak some Polish, too.  Yet, I don't wish to fight with you.

I will continue to use English here, though I will not continue to answer you 
when you write to the list in Esperanto (or Polish).  Why?  I repeat myself (as 
do others here):  because this is an English-language list.

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

Re: [OSM-talk] [Tagging] nomoj de internaciaj objektoj / nazwy obiektów międzynarodowych / names of international objects

2020-01-11 Per discussione Tomek

W dniu 20-01-11 o 23:20, stevea pisze:
> On Jan 11, 2020, at 2:12 PM, Tomek  wrote:
>> EN
>> English fanatics, please read the text: 
>> http://sylvanzaft.org/verkaro/Esperanto-A_Language_for_a_Global_Village.pdf
> No thank you.  I am not a "fanatic" of my mother tongue, I simply use it 
> along with hundreds of millions or billions of others — um, not all of them 
> HERE, of course, but there are enough English speakers here, and there have 
> been since Day 1, to make it an interesting and informative place to have 
> conversations like this.  Not to mention I am multilingual (though my 
> Esperanto is 35-year-old-rusty).
>
> What I would much rather do is continue discussion on this list in English, 
> as we always have.  It is good discussion, but I don't appreciate being 
> name-called ("fanatic") or told to "go learn a new language."  I mentioned 
> that I was a founding member of my university's Esperanto Club, so I know the 
> reasoning behind why people might want to learn the language.  But I don't 
> believe it was ever meant to be rammed down anybody's throat.  (Which is what 
> that felt like).
>
> Opinions are mine.
>
> Thanks for your understanding and peace to you,
> SteveA
Se vi parolas Esperanton, kial vi ĝin ne uzas? Kial mi devas uzi
elektronikan tradukilon por kompreni vian mesaĝon, kaj vi postulas por
skribi en via gepatra lingvo? Mi ne devigas al aliaj homoj lerni mian
lingvon (la polan). Kiu estas fanatikulo tie ĉi?


W dniu 20-01-11 o 23:24, Steve Doerr pisze:
> Please post in English if you want people to understand what you are
> trying to say. Otherwise, feel free to talk to yourself in Esperanto.
https://translate.google.pl/
https://www.bing.com/translator/
https://translate.yandex.com/
<>

signature.asc
Description: OpenPGP digital signature
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] [Tagging] nomoj de internaciaj objektoj / nazwy obiektów międzynarodowych / names of international objects

2020-01-11 Per discussione Steve Doerr

Please post in English if you want people to understand what you are 
trying to say. Otherwise, feel free to talk to yourself in Esperanto.

Steve

On 11/01/2020 22:12, Tomek wrote:

EO
W dniu 20-01-07 o 08:27, Mateusz Konieczny pisze:

Yes, but using it for a pragmatic reasons
for an international communication is
usually not imperialism.

I can try to communicate with group of  people
from different countries in Polish,
Latin, Sindarin or Esperanto.

But except rare cases using English is likely
to result in more efficient communication.
Vi povas paroli en la pola, kiu estas mia denaska lingvo. Mi ne miras, 
ke vi malsukcesis komunikadi per fikcia/arta lingvo kreita por 
prezenti mondon de hobitoj kaj elfoj. Latino taŭgas por nomi speciojn 
kaj por estroj de katolika eklezio. Esperanto fakte estas la plej 
efika maniero por komunikadi kaj ne diskriminacias iun ajn.

W dniu 20-01-07 o 02:32, Joseph Eisenberg pisze:

This will not work, because local mappers will constantly be adding
back "name=*" tags to get the feature to appear in their favorite map
style. If you want to define that a feature has no default language,
it would be good to use a new tag like "default:language=none" or
something similar, but it will be hard to determine when to use such a
tag.
Kiuj lokalaj mapigistoj? Ni parolas pri nomoj de Suda Oceano kaj 
insuloj proksime de Antarkto!

W dniu 20-01-07 o 13:28, Paul Allen pisze:
On Tue, 7 Jan 2020 at 12:21, ael > wrote:

On Mon, Jan 06, 2020 at 10:59:35PM +0100, Tom Pfeifer wrote:
> On 06.01.2020 21:32, Tomek wrote:
> > Exactly, does a buoy with the inscription "Baltic Sea" swim
at 56° N18°
> > E? No, there is simply water that Poles call the "Morze
Bałtyckie",
> > Germans "Ostsee", etc.
>
>
> > Please support (vote) my proposal or write a reason why not.
>
> For the count, +1 against.
And another +1, against.

Bringing back memories of AOL, me too.  +1 against.

--
Paul

Voĉoj sen klarigo (kaj sen proponita solvo) ne enkalkulas.
-3

PL
W dniu 20-01-07 o 08:27, Mateusz Konieczny pisze:

Yes, but using it for a pragmatic reasons
for an international communication is
usually not imperialism.

I can try to communicate with group of  people
from different countries in Polish,
Latin, Sindarin or Esperanto.

But except rare cases using English is likely
to result in more efficient communication.
Możesz pisać w języku polskim, który jest moim językiem. Nie dziwię 
się, że nie zdołałeś się porozumieć używając fikcyjneko/artystycznego 
języka prezentującego świat hobbitów i elfów. Łacina nadaje się tylko 
do nazywania gatunków i dla szefów Kościoła katolickiego. Esperanto w 
rzeczywistości jest najbardziej efektywnym sposobem na komunikację i 
nie dyskryminuje kogokolwiek. Polecam tekst (pisany przez anglika): 
https://eduinf.waw.pl/esp/util/espglobal/

W dniu 20-01-07 o 02:32, Joseph Eisenberg pisze:

This will not work, because local mappers will constantly be adding
back "name=*" tags to get the feature to appear in their favorite map
style. If you want to define that a feature has no default language,
it would be good to use a new tag like "default:language=none" or
something similar, but it will be hard to determine when to use such a
tag.
Którzy lokalni mapowicze? Mówimy o nazwach mórz Oceanu Południowego i 
wysp w pobliżu Antarktydy!

W dniu 20-01-07 o 13:28, Paul Allen pisze:
On Tue, 7 Jan 2020 at 12:21, ael > wrote:

On Mon, Jan 06, 2020 at 10:59:35PM +0100, Tom Pfeifer wrote:
> On 06.01.2020 21:32, Tomek wrote:
> > Exactly, does a buoy with the inscription "Baltic Sea" swim
at 56° N18°
> > E? No, there is simply water that Poles call the "Morze
Bałtyckie",
> > Germans "Ostsee", etc.
>
>
> > Please support (vote) my proposal or write a reason why not.
>
> For the count, +1 against.
And another +1, against.

Bringing back memories of AOL, me too.  +1 against.

--
Paul
Głosy bez wyjaśnienia (i bez zaproponowanego rozwiązania) nie wliczają 
się.

-3

EN
English fanatics, please read the text: 
http://sylvanzaft.org/verkaro/Esperanto-A_Language_for_a_Global_Village.pdf

___
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] [Tagging] nomoj de internaciaj objektoj / nazwy obiektów międzynarodowych / names of international objects

2020-01-11 Per discussione stevea

On Jan 11, 2020, at 2:12 PM, Tomek  wrote:
> EN
> English fanatics, please read the text: 
> http://sylvanzaft.org/verkaro/Esperanto-A_Language_for_a_Global_Village.pdf

No thank you.  I am not a "fanatic" of my mother tongue, I simply use it along 
with hundreds of millions or billions of others — um, not all of them HERE, of 
course, but there are enough English speakers here, and there have been since 
Day 1, to make it an interesting and informative place to have conversations 
like this.  Not to mention I am multilingual (though my Esperanto is 
35-year-old-rusty).

What I would much rather do is continue discussion on this list in English, as 
we always have.  It is good discussion, but I don't appreciate being 
name-called ("fanatic") or told to "go learn a new language."  I mentioned that 
I was a founding member of my university's Esperanto Club, so I know the 
reasoning behind why people might want to learn the language.  But I don't 
believe it was ever meant to be rammed down anybody's throat.  (Which is what 
that felt like).

Opinions are mine.

Thanks for your understanding and peace to you,
SteveA
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-GB] Map with AI comes to the UK

2020-01-11 Per discussione Steve Doerr


On 11/01/2020 12:41, Rob Nickerson wrote:


In JOSM add it using:

wmts:https://api.mapbox.com/styles/v1/robjn/ck59jksa71nym1co31kr8mulb/wmts?access_token=pk.eyJ1Ijoicm9iam4iLCJhIjoid0dYNkY1QSJ9.A-0lzQOawGYICYPfURsjDA

And in iD Editor add it using:

https://api.mapbox.com/styles/v1/robjn/ck59jksa71nym1co31kr8mulb/tiles/256/{zoom}/{x}/{y}?access_token=pk.eyJ1Ijoicm9iam4iLCJhIjoid0dYNkY1QSJ9.A-0lzQOawGYICYPfURsjDA



And Potlatch?

--
Steve


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

Re: [OSM-talk] [Tagging] nomoj de internaciaj objektoj / nazwy obiektów międzynarodowych / names of international objects

2020-01-11 Per discussione Tomek

EO
W dniu 20-01-07 o 08:27, Mateusz Konieczny pisze:
> Yes, but using it for a pragmatic reasons
> for an international communication is
> usually not imperialism.
>
> I can try to communicate with group of  people
> from different countries in Polish,
> Latin, Sindarin or Esperanto.
>
> But except rare cases using English is likely
> to result in more efficient communication.
Vi povas paroli en la pola, kiu estas mia denaska lingvo. Mi ne miras,
ke vi malsukcesis komunikadi per fikcia/arta lingvo kreita por prezenti
mondon de hobitoj kaj elfoj. Latino taŭgas por nomi speciojn kaj por
estroj de katolika eklezio. Esperanto fakte estas la plej efika maniero
por komunikadi kaj ne diskriminacias iun ajn.

W dniu 20-01-07 o 02:32, Joseph Eisenberg pisze:
> This will not work, because local mappers will constantly be adding
> back "name=*" tags to get the feature to appear in their favorite map
> style. If you want to define that a feature has no default language,
> it would be good to use a new tag like "default:language=none" or
> something similar, but it will be hard to determine when to use such a
> tag.
Kiuj lokalaj mapigistoj? Ni parolas pri nomoj de Suda Oceano kaj insuloj
proksime de Antarkto!

W dniu 20-01-07 o 13:28, Paul Allen pisze:
> On Tue, 7 Jan 2020 at 12:21, ael  > wrote:
>
> On Mon, Jan 06, 2020 at 10:59:35PM +0100, Tom Pfeifer wrote:
> > On 06.01.2020 21:32, Tomek wrote:
> > > Exactly, does a buoy with the inscription "Baltic Sea" swim at
> 56° N18°
> > > E? No, there is simply water that Poles call the "Morze
> Bałtyckie",
> > > Germans "Ostsee", etc.
> >
> >
> > > Please support (vote) my proposal or write a reason why not.
> >
> > For the count, +1 against.
> And another +1, against.
>
>
> Bringing back memories of AOL, me too.  +1 against.
>
> -- 
> Paul
Voĉoj sen klarigo (kaj sen proponita solvo) ne enkalkulas.
-3



PL
W dniu 20-01-07 o 08:27, Mateusz Konieczny pisze:
> Yes, but using it for a pragmatic reasons
> for an international communication is
> usually not imperialism.
>
> I can try to communicate with group of  people
> from different countries in Polish,
> Latin, Sindarin or Esperanto.
>
> But except rare cases using English is likely
> to result in more efficient communication.
Możesz pisać w języku polskim, który jest moim językiem. Nie dziwię się,
że nie zdołałeś się porozumieć używając fikcyjneko/artystycznego języka
prezentującego świat hobbitów i elfów. Łacina nadaje się tylko do
nazywania gatunków i dla szefów Kościoła katolickiego. Esperanto w
rzeczywistości jest najbardziej efektywnym sposobem na komunikację i nie
dyskryminuje kogokolwiek. Polecam tekst (pisany przez anglika):
https://eduinf.waw.pl/esp/util/espglobal/

W dniu 20-01-07 o 02:32, Joseph Eisenberg pisze:
> This will not work, because local mappers will constantly be adding
> back "name=*" tags to get the feature to appear in their favorite map
> style. If you want to define that a feature has no default language,
> it would be good to use a new tag like "default:language=none" or
> something similar, but it will be hard to determine when to use such a
> tag.
Którzy lokalni mapowicze? Mówimy o nazwach mórz Oceanu Południowego i
wysp w pobliżu Antarktydy!

W dniu 20-01-07 o 13:28, Paul Allen pisze:
> On Tue, 7 Jan 2020 at 12:21, ael  > wrote:
>
> On Mon, Jan 06, 2020 at 10:59:35PM +0100, Tom Pfeifer wrote:
> > On 06.01.2020 21:32, Tomek wrote:
> > > Exactly, does a buoy with the inscription "Baltic Sea" swim at
> 56° N18°
> > > E? No, there is simply water that Poles call the "Morze
> Bałtyckie",
> > > Germans "Ostsee", etc.
> >
> >
> > > Please support (vote) my proposal or write a reason why not.
> >
> > For the count, +1 against.
> And another +1, against.
>
>
> Bringing back memories of AOL, me too.  +1 against.
>
> -- 
> Paul
Głosy bez wyjaśnienia (i bez zaproponowanego rozwiązania) nie wliczają się.
-3



EN
English fanatics, please read the text:
http://sylvanzaft.org/verkaro/Esperanto-A_Language_for_a_Global_Village.pdf

<>

signature.asc
Description: OpenPGP digital signature
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

[Talk-it] violazione di licenza ?

2020-01-11 Per discussione Volker Schmidt

Ho per caso scoperto uno strano giro  di informazione.
Un sito A di una ditta a Vicenza pubblica dei tour in bicicletta nella zona
con foto e descrizione e una Mappa Google con un tracciato. Il tracciato è
scaricabile in formato kmz.
Mi sono incuriosito quando ho visto che il tracciato non combaciava con la
geometria delle vie su Gmaps. Ho messo il puntatore sulla traccia e appare
un link a una trccia sul sito Alltrails.com. Alltrails è uno dei tanti siti
per progettazione di percorsi in bici e a piedi ecc., Clicco sul link - mi
da 404.
Scarico la traccia kmz e la sovrappongo sulla mappa OSM (utilizzata da
Alltrails) e, bingo, è OSM in assoluta precisione.
Mi sembra ovvio che la ditta A ha utilizzato il sito Alltrails per la
progettazione del percorso (e non ha registrato il percorso con un GPS) e
poi ha eliminato la traccia dal sito Alltrails, cosa non tanto corretta, mi
sembra. Le condizioni Alltrails dicono: " You must not use any part of the
materials used in or on the Products for commercial purposes without
obtaining a written license to do so from us", ma non è chiaro se il fatto
che la ditta A ti vende la traccia al prezzo di €0 sia una violazione...
Ma poi la traccia che pubblicano come kmz su una mappa Google è stato
prodotto con dati OSM. Mi piace ancora meno. Non c'è nessun accenno ne a
Alltrails ne OSM.
Ma è una mancata attribuzione?

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

[Talk-ca] FW: Re: Importing buildings in Canada

2020-01-11 Per discussione Daniel @jfd553

By the way, have a look at

https://wiki.openstreetmap.org/wiki/Canada_Building_Import

https://wiki.openstreetmap.org/wiki/The_Open_Database_of_Buildings
Cheers

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

Re: [OSM-talk] Too subjective & problematic Re: no-go-areas

2020-01-11 Per discussione stevea


> On Jan 11, 2020, at 12:22 PM, Martin Trautmann via talk 
> 
> and
> On 20-01-02 12:23, pangoSE wrote what they wrote.

To be clear, the hazards I'm hazily identifying are naturally-occurring or are 
human-made real-life hazards that can cause you real harm if you approach them 
and are not careful to avoid them, not "stay out of that neighborhood" kinds of 
"hazards."  Things like an area which is radioactive, has a "falling hazard" 
(such as a pit, though I think we have "adit" for mine shafts — and we do have 
natural=cliff, which I agree suffices for what it is) and other unusual hazards 
like places which have a propensity to be repeatedly struck by lightning 
(that's a weird one, and kind of controversial, I know).

As before, I doubt "hazard" or "no-go" will get more traction than it has (here 
and now), I simply make that clarification.

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

Re: [Talk-ca] Importing buildings in Canada

2020-01-11 Per discussione Daniel @jfd553

Updates about the ODB import proposal
Documentation:
All the content regarding the current import has been moved to the Open 
Database of Building (ODB) wiki page [1]. The purpose of the page is now 
twofold. Provide a detailed procedure on how to import the data and to keep an 
inventory of what has been done/remains to do.
The Canada Building Import wiki page [2] will keep the same name but its 
content has been modified to serve as a hub for all building imports, previous 
and current. I also added a section to describe what best practices are when 
importing/editing buildings (to be developed).
Import:
Regarding the import, I proposed the import to be done using the task manager 
on a Municipal basis for all the reasons mentioned here [3]. In order to make 
it work properly, the OSMCanada task manager [4] needs to be set up for a given 
municipality only after a contributor has identified himself as the local 
import manager. We also know that the task manager us totally customizable [5].

Now we need to discuss, amongst other things, of ...

* Who will be in charge of setting up the task manager?

* What optimal task manager's parameters should be to ease the import?

* What parameters are required to review what has already been imported?

* How to proceed when pre-processing is required?
Proposals or suggestions? Let's discuss
Daniel

[1] https://wiki.openstreetmap.org/wiki/The_Open_Database_of_Buildings

[2] https://wiki.openstreetmap.org/wiki/Canada_Building_Import

[3] https://lists.openstreetmap.org/pipermail/talk-ca/2020-January/009541.html

[4] http://tasks.osmcanada.ca/

[5] https://lists.openstreetmap.org/pipermail/talk-ca/2020-January/009553.html


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

Re: [OSM-talk] Too subjective & problematic Re: no-go-areas

2020-01-11 Per discussione Martin Trautmann via talk

On 20-01-02 12:23, pangoSE wrote:

> A map cannot solve a lack of general awareness when visiting a
> new/unknown place. Going to the mountains to hike can also be dangerous
> if you are not well prepared. This is of course not marked on the map!

I agree that I don't know any non-subjective way how to identify such an
area.

But a good map is for people who do NOT know this area.
People who know about neither need a map nor a warning.

Schönen Gruß
Martin

signature.asc
Description: OpenPGP digital signature
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk-fr] sites OSM down

2020-01-11 Per discussione Philippe Verdy

Bon c'est revenu (site web, API, tuiles ok)

Le sam. 11 janv. 2020 à 18:38, Philippe Verdy  a écrit :

> Connexion impossible à OSM (même en consultation). Visiblement un proxy ne
> répond plus du tout.
> Après un long timeout, pas de connexion TCP du tout, même pas un statut
> HTTP, aucune réponse, la session TCP est fermée après un long délai.
>
> Hier et avant-hier c'était super lent, mais là plus rien du tout. Tout est
> fermé (site principal, API, serveurs de tuiles...)
>
> Visiblement un changement malencontreux sur le DNS d'openstreetmap.org
> (mauvaise adresse IP) ou rupture de liaison Internet. Ou alors un sérieux
> problème d'attaque externe.
>
> Suis-je le seul ?
>
>
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

[OSM-talk-fr] sites OSM down

2020-01-11 Per discussione Philippe Verdy

Connexion impossible à OSM (même en consultation). Visiblement un proxy ne
répond plus du tout.
Après un long timeout, pas de connexion TCP du tout, même pas un statut
HTTP, aucune réponse, la session TCP est fermée après un long délai.

Hier et avant-hier c'était super lent, mais là plus rien du tout. Tout est
fermé (site principal, API, serveurs de tuiles...)

Visiblement un changement malencontreux sur le DNS d'openstreetmap.org
(mauvaise adresse IP) ou rupture de liaison Internet. Ou alors un sérieux
problème d'attaque externe.

Suis-je le seul ?
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

[OSM-talk-fr] Non attribution

2020-01-11 Per discussione Eric

Bonjour,

Le site "https://cartepatrimoine.ladrome.fr/carte#; propose un fond de
carte qui est basé sur OSM (je reconnais des contribution).
Les tuiles sont issues du serveur :
https://maps.wikimedia.org
(par exemple https://maps.wikimedia.org/osm-intl/18/134593/94591.png)
et je ne vois nulle part d'attribution. Est-ce que dois leur signaler ?

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

Re: [OSM-talk] Fwd: [Tagging] Tagging the local language

Am Sa., 11. Jan. 2020 um 01:30 Uhr schrieb Joseph Eisenberg <
joseph.eisenb...@gmail.com>:

> On Sat, Jan 11, 2020 at 2:49 AM Mateusz Konieczny 
> wrote:
>
>> or to use tricks like the “place=neighbourhood” one (which is based on
>> POIs rather than polygons)?
>>
>> It is certainly wrong to do this.
>>
>
> I think the “trick” here is referring to the stand at practice of mapping
> all place= features as nodes, including neighborhoods, because their
> boundaries are usually fuzzy (and precise boundaries can be mapped with
> boundary=administrative or another boundary= tag).
>

mostly I agree, although it should be mentioned that neighbourhood (or
other place boundaries like quarter and suburb) may be very clear although
they aren't officially declared: when they are hard "natural" borders like
railroads, rivers, motorways, etc. Also a change in the urban structure
(urban confuguration, architectural style, living standards, socially /
ownerstructure, etc.). can mark a border very strongly in some instances,
without it having to be an administrative boundary.

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

[OSM-talk] New Telegram chat for OSM + LGBTQIA*

2020-01-11 Per discussione Rory McCann


Hello all,

A new Telegram group has been set up: “RainbOSM”. A chat about LGBTQIA* 
issues and OpenStreetMap. 


Join here: https://t.me/joinchat/BDLI7xMzuF5TRZ5lwLYxkA

--
R

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

[Diversity-talk] New Telegram chat for OSM + LGBTQIA*

2020-01-11 Per discussione Rory McCann


Hello all,

A new Telegram group has been set up: “RainbOSM”. A chat about LGBTQIA* 
issues and OpenStreetMap. 


Join here: https://t.me/joinchat/BDLI7xMzuF5TRZ5lwLYxkA

--
R

___
Diversity-talk mailing list
Code of Conduct: 
https://wiki.openstreetmap.org/wiki/Diversity/MailingList/CodeOfConduct
Contact the mods (private): diversity-talk-ow...@openstreetmap.org

Re: [OSM-talk] JOSM: hover-Coordinate by easy click into clipboard?

2020-01-11 Per discussione Oleksiy Muzalyev

It is interesting as an exercise in Regular Expressions.

I would prefer to have under
Geo URI
geo:47.8329,36.8763?z=16

just the coordinates themselves:
Geo coordinates
47.8329, 36.8763

where coordinates would be in a read-only input box with the "copy"
clickable icon which allows to copy the coordinates in one(!) click.

As it is now I have to select the whole string, right-click, select
copy, then click paste without formatting, select again the coordinates,
and so on and so forth.

The JavaScript function to copy in one click is like three lines of
code. And there is an empty space under: Geo URI

Best regards,
O.

On 1/11/20 13:50, Jo wrote:

Would this help?
https://pythex.org/?regex=(%5Cd%2B.%5Cd%2B%2C%5Cd%2B.%5Cd%2B)_string=geo%3A42.2010%2C20.7331%3Fz%3D14=0=0=0=0

Probably still more involved than what you would like.

On Sat, Jan 11, 2020, 10:51 Oleksiy Muzalyev
mailto:oleksiy.muzal...@bluewin.ch>> wrote:

On MacOS it is Command+Shift+C.

I wish there were such a feature on the OSM.org map. Now it is
also possible to copy the coordinates of a place,
but one has to copy a long string and then to extract the
coordinates from it. But is JOSM one gets them directly in the
proper format, something like: 47.7549028, 36.8379178

Sometimes, when adding a photo to Wikimedia Commons which has got
the coordinates in its JPG's EXIF properties, still for some
reason the coordinates do not resurface in the location's latitude
and longitude fields of the page. So, usually in such a case, I
return to the OSM.org page, copy the long string and then extract
the coordinates from it manually.

Maybe there is such a feature on the OSM.org page, but I just did
not notice it yet. Perhaps, I can also point a cursor to a place
and do some keyboard combination and only the coordinates are copied.

Best regards,
Oleksiy

On 1/8/20 05:52, Erwin Olario wrote:

In JOSM, on an active layer, while a node is selected, you can
press CTRL+SHIFT+C and it will copy its coordinates to memory.

On Tue, Jan 7, 2020, 09:43 tshrub
mailto:my-email-confirmat...@online.de>> wrote:

hi,

in JOSM's status bar the mouse position is constantly running
as a
coordinate. Is there any easy way to get it, may be by
keyboard into the
clipboard?
I want to edit GPS data from, or better: add GPS-data to
trackless
photos - I want to place them like this with JOSM' sat-pictures.

bella saluti

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

Re: [OSM-talk-fr] Source : les cartes IGN, c'est bien proscrit ?

2020-01-11 Per discussione deuzeffe


Le 11/01/2020 à 09:24, ades a écrit :

En posant la question autrement, les source "Open Licence / licence ouverte » 
Etalab sont utilisables ou pas ?


Les questions de Vincent portait sur les cartes IGN (pas en OL/LO, donc) 
où sont indiqués les lieux-dits. Pas autre chose, il me semble.


--
deuzeffe - pas confondre avec YOLO


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

Re: [OSM-talk-fr] Padza [Mayotte]

2020-01-11 Per discussione marc marc

Le 11.01.20 à 07:36, Waxy via Talk-fr a écrit :
> https://fr.wikipedia.org/wiki/Padza
> natural=bare_rock

cela me semble bien.

> surface=ground

bof, wikipedia a dit que c'est de la roche et non de la terre


> natural=stone

c'est pour un rocher individuel

> natural=sand (parfois avec surface=ground)

celai pourrait décrire que la zone rocheuse est devenue du sable.
mais à mon avis il faudra choisir entre les 2
selon l'état : soit c'est encore un rocher, soit c'est du sable

> Les name=Padza sont à enlever

ou à migrer en description

> clé geological=outcrop

ca pourrait être un bon complément pour décrire le comment
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [Talk-it] Numero di cellulare in OSM

Ciao,

ma lo usi per i cellulari?

Grazie
Francesco

Il giorno sab 11 gen 2020 alle ore 14:32 Andreas Lattmann <
andrea.lattm...@ga-2.it> ha scritto:

> Anch'io uso phone:mobile e credo sia utile.
>
> Il 11 gennaio 2020 09:53:41 CET, Federico Cortese 
> ha scritto:
> >On Sat, Jan 11, 2020 at 9:09 AM Martin Koppenhoefer
> > wrote:
> >>
> >> Io uso “phone” per tutti i primi numeri, e solo quando ci sono più
> >tipi di numeri per lo stesso POI metto phone:mobile. Invece contact:*
> >non lo metto mai, perché è solo più da digitare, ma non aggiunge niente
> >di utile (a mio parere), al meno per phone.
> >>
> >
> >Esattamente quello che faccio anche io:
> >-phone=* per un solo contatto telefonico;
> >-phone:mobile=* se oltre al telefono fisso è indicato anche un
> >cellulare, per tenerli in due tag separati.
> >-contact:phone=* mai usato (ho votato anche a favore del deprecare
> >contact:phone qui
> >
> https://wiki.openstreetmap.org/wiki/Discussions/tagging/contact:phone_or_phone
> ,
> >anche se hanno vinto i contrari)
> >-contact:mobile=* fino a poco tempo fa non sapevo nemmeno esistesse :-)
> >
> >Ciao,
> >Federico
> >
> >___
> >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
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [Talk-it] Numero di cellulare in OSM

Il sab 11 gen 2020, 10:17 Martin Koppenhoefer  ha
scritto:

>
>
> sent from a phone
>
> > On 11. Jan 2020, at 09:22, Francesco Ansanelli 
> wrote:
> >
> > Sul telefonino posso mandare un SMS se trovo occupato, potrei avere un
> piano che prevede costi differenti tra fissi e mobili...
>
>
> OpenStreetMap però è un progetto per il presente ed il futuro. Negli anni
> novanta era sicuramente molto più importante capire la tipologia di numero
> che si stava chiamando, ma oramai, soprattutto in Italia, hanno quasi tutti
> piani tariffari che prevedono chiamate illimitate (o minu  sufficienti)
> verso tutti.
>
>
>
> > Chi usa il dato da OSM, se lo trova già diviso, ha un servizio in più...
> Che a noi costa poco dare!
>
>
> in realtà costa per chi deve usare i dati, perché deve cercare in tanti
> chiavi diversi, e fare il merge. Invece se tutti usassero “phone” (e forse
> “contact:phone”), trovare un numero sarebbe molto più facile.
>

Infatti, abbiamo 3 tag (oltre alle varianti) in cui scrivere un numero...
Magari iniziamo a deprecarne qualcuno... Avevo votato a favore quando si
era proposto di togliere lo schema contact, ma se si facesse una votazione
per deprecare phone voterei sempre a favore.


> Qualcuno potrebbe avere un piano che comporta vantaggi per chiamare numeri
> Wind? Allora phone:mobile:Wind=...
>
> Forse le compagnie che usano la rete Telefònica di ex-E-Plus  hanno
> vantaggi chiamandosi nella stessa rete?
> Visto? Finché parliamo di reti italiane (che conosciamo tutti), sembra
> tutto logico e facile, ma quando non conosci più i dettagli diventa
> incomprensibile, e diventa complicato trovare i numeri telefonici, perché
> sono distribuiti su vari tag.
>

Creare tag come "phone:IT:eplus" mi sembra controverso... Sono d'accordo



> Ciao Martin
> ___
> 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: [Talk-it] Numero di cellulare in OSM

2020-01-11 Per discussione Andreas Lattmann

Anch'io uso phone:mobile e credo sia utile.

Il 11 gennaio 2020 09:53:41 CET, Federico Cortese  ha 
scritto:
>On Sat, Jan 11, 2020 at 9:09 AM Martin Koppenhoefer
> wrote:
>>
>> Io uso “phone” per tutti i primi numeri, e solo quando ci sono più
>tipi di numeri per lo stesso POI metto phone:mobile. Invece contact:*
>non lo metto mai, perché è solo più da digitare, ma non aggiunge niente
>di utile (a mio parere), al meno per phone.
>>
>
>Esattamente quello che faccio anche io:
>-phone=* per un solo contatto telefonico;
>-phone:mobile=* se oltre al telefono fisso è indicato anche un
>cellulare, per tenerli in due tag separati.
>-contact:phone=* mai usato (ho votato anche a favore del deprecare
>contact:phone qui
>https://wiki.openstreetmap.org/wiki/Discussions/tagging/contact:phone_or_phone,
>anche se hanno vinto i contrari)
>-contact:mobile=* fino a poco tempo fa non sapevo nemmeno esistesse :-)
>
>Ciao,
>Federico
>
>___
>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: [Talk-GB] Map with AI comes to the UK

2020-01-11 Per discussione Rob Nickerson

Hi all,

A quick update on the MapWithAI stuff. Kaart have developed a plugin for
JOSM:
https://www.openstreetmap.org/user/the_node_less_traveled/diary/391863
https://josm.openstreetmap.de/wiki/Help/Plugin/MapWithAI

Also, but slightly less relevant now, I have thrown this data into Mapbox
studio tilesets so that you can add as a background to JOSM/ID.

The process I use is to add the layer in JOSM, pan around until I find
something that needs adding, then use the JOSM plugin to add (and adjust)
it.

Raster tiles
In JOSM add it using:

wmts:
https://api.mapbox.com/styles/v1/robjn/ck59jksa71nym1co31kr8mulb/wmts?access_token=pk.eyJ1Ijoicm9iam4iLCJhIjoid0dYNkY1QSJ9.A-0lzQOawGYICYPfURsjDA

And in iD Editor add it using:

https://api.mapbox.com/styles/v1/robjn/ck59jksa71nym1co31kr8mulb/tiles/256/{zoom}/{x}/{y}?access_token=pk.eyJ1Ijoicm9iam4iLCJhIjoid0dYNkY1QSJ9.A-0lzQOawGYICYPfURsjDA

Thank you,
*Rob*


On Thu, 2 Jan 2020 at 22:08, Rob Nickerson 
wrote:

> Hi all,
>
> I just spotted that Facebook have pushed an update to their map with AI
> project:
>
> "For our final release of 2019, we have released 84 new countries for our
> AI road data with new coverage in the remainder of Europe, Asia, and
> Oceania! AI roads are now available nearly globally."
> Source:
> https://github.com/facebookmicrosites/Open-Mapping-At-Facebook/blob/master/WHATSNEW.md
>
> For those who don't know what MapWithAI is check out https://mapwith.ai
>
> And to try it out in their RapID version of the iD editor:
> https://mapwith.ai/rapid#background=Bing_features=boundaries=18.60/53.40625/-2.13801
>
> Just roads at the moment and not that easy to find a suggestion that is
> worth adding (at least near me where roads are well mapped) but this does
> demonstrate what is possible. Let us know if you have a good or bad
> experience with this.
>
> Would be great to see this extended to buildings but we may have to wait
> for Microsoft for that.
>
> P.S. A happy new year to all!
>
> Thank you,
> *Rob*
>
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [talk-au] NPWS landing sites task

I use a node for most.
Only if there is a distinct clearing in the middle of nowhere or a marked 
helipad then I use an area.

On 11 January 2020 8:56:01 pm AEDT, Andrew Harvey  
wrote:
>On Sat, 11 Jan 2020 at 17:56, Graeme Fitzpatrick
>
>wrote:
>
>> Question re this Map Roulette task, thanks.
>>
>> I take it these details have come from a NPWS list of some form that
>says
>> there is a landing site at "this" spot.
>>
>
>Yes that's right.
>
>
>> So, even if it shows as just a patch of bare ground, we tag it as a
>> landing site?
>>
>
>This dataset is saying that the patch of bare ground is a landing site,
>either an emergency one or actual helipad. Remember we're not just
>mapping
>any available patch of bare ground as an emergency landing site, only
>those
>which NPWS have designated as emergency landing sites.
>
>
>>
>> Node or area?
>>
>
>Up to you both are fine, but unless there is some kind of boundary you
>can
>see I'd just go with a node.
>
>
>>
>> Of the few I've looked at, one was a very discernible flattened out
>square
>> of dirt which I tagged as an area, another was just a clearing in the
>> forest so I put a node there, while the third was just a spot in an
>open
>> paddock.
>>
>> & it would appear that emergency=landing_site doesn't render in any
>way -
>> does that matter?
>>
>
>That's okay, typically something only starts getting rendered by maps
>and
>apps once it has some usage, so actually mapping it helps justify
>getting
>it into maps and apps.
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au

Re: [OSM-talk] JOSM: hover-Coordinate by easy click into clipboard?

2020-01-11 Per discussione Jo

Would this help?
https://pythex.org/?regex=(%5Cd%2B.%5Cd%2B%2C%5Cd%2B.%5Cd%2B)_string=geo%3A42.2010%2C20.7331%3Fz%3D14=0=0=0=0

Probably still more involved than what you would like.

Jo

On Sat, Jan 11, 2020, 10:51 Oleksiy Muzalyev 
wrote:

> On MacOS it is Command+Shift+C.
>
> I wish there were such a feature on the OSM.org map. Now it is also
> possible to copy the coordinates of a place,
> but one has to copy a long string and then to extract the coordinates from
> it. But is JOSM one gets them directly in the proper format, something
> like: 47.7549028, 36.8379178
>
> Sometimes, when adding a photo to Wikimedia Commons which has got the
> coordinates in its JPG's EXIF properties, still for some reason the
> coordinates do not resurface in the location's latitude and longitude
> fields of the page. So, usually in such a case, I return to the OSM.org
> page, copy the long string and then extract the coordinates from it
> manually.
>
> Maybe there is such a feature on the OSM.org page, but I just did not
> notice it yet. Perhaps, I can also point a cursor to a place and do some
> keyboard combination and only the coordinates are copied.
>
> Best regards,
> Oleksiy
>
> On 1/8/20 05:52, Erwin Olario wrote:
>
> In JOSM, on an active layer, while a node is selected, you can press
> CTRL+SHIFT+C and it will copy its coordinates to memory.
>
> On Tue, Jan 7, 2020, 09:43 tshrub  wrote:
>
>> hi,
>>
>> in JOSM's status bar the mouse position is constantly running as a
>> coordinate. Is there any easy way to get it, may be by keyboard into the
>> clipboard?
>> I want to edit GPS data from, or better: add GPS-data to trackless
>> photos - I want to place them like this with JOSM' sat-pictures.
>>
>> bella saluti
>>
>>
>> ___
>> talk mailing list
>> talk@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk
>>
>
> ___
> talk mailing 
> listtalk@openstreetmap.orghttps://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-fr] Source : les cartes IGN, c'est bien proscrit ?

2020-01-11 Per discussione ades

sorry… je voulais juste préciser que certaines productions de l'IGN (dont des 
cartes) sont utilisables…
;-)



> Le 11 janv. 2020 à 10:26, Vincent Bergeot  a écrit :
> 
> Le 11/01/2020 à 09:24, ades a écrit :
>> En posant la question autrement, les source "Open Licence / licence ouverte 
>> » Etalab sont utilisables ou pas ? 
> c'est plutôt une autre question, dont la réponse est oui les ressources sous 
> LO sont utilisable dans OSM
> Et à ma question des cartes IGN (en particuliers les cartes papiers par 
> exemple) sans licence LO, non ce n'est pas utilisable et donc une source à 
> retirer.
> Merci pour les divers retours
> -- 
> 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] Osmose a pris son week-end...

2020-01-11 Per discussione Jacques Lavignotte


Rien d'urgent de mon coté.

Merci Frédéric,  J.


Le 11/01/2020 à 11:50, Frédéric Rodrigo a écrit :

Le 11/01/2020 à 11:37, Jacques Lavignotte a écrit :

C'est moi ou bien ?

Salutations,   Jacques



Non, c'est justement le weekend que Osmose travaille.

Une mise à jour récente sur l'introduction d'uuid (stabilité et unicité 
des identifiants de signalements) a introduite de mauvaises données dans 
la base de données.


La corrections de la base de données est en cours, mais ça a gros impact 
sur les performances du serveur.







--
GnuPg : 156520BBC8F5B1E3 Because privacy matters.
On mangera ? (c) (tm)

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

Re: [OSM-talk-fr] Osmose a pris son week-end...

2020-01-11 Per discussione Frédéric Rodrigo


Le 11/01/2020 à 11:37, Jacques Lavignotte a écrit :

C'est moi ou bien ?

Salutations,   Jacques



Non, c'est justement le weekend que Osmose travaille.

Une mise à jour récente sur l'introduction d'uuid (stabilité et unicité 
des identifiants de signalements) a introduite de mauvaises données dans 
la base de données.


La corrections de la base de données est en cours, mais ça a gros impact 
sur les performances du serveur.





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

[OSM-talk-fr] Osmose a pris son week-end...

2020-01-11 Per discussione Jacques Lavignotte


C'est moi ou bien ?

Salutations,   Jacques

--
GnuPg : 156520BBC8F5B1E3 Because privacy matters.
On mangera ? (c) (tm)

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

Re: [talk-au] NPWS landing sites task

2020-01-11 Per discussione Andrew Harvey

On Sat, 11 Jan 2020 at 17:56, Graeme Fitzpatrick 
wrote:

> Question re this Map Roulette task, thanks.
>
> I take it these details have come from a NPWS list of some form that says
> there is a landing site at "this" spot.
>

Yes that's right.

> So, even if it shows as just a patch of bare ground, we tag it as a
> landing site?
>

This dataset is saying that the patch of bare ground is a landing site,
either an emergency one or actual helipad. Remember we're not just mapping
any available patch of bare ground as an emergency landing site, only those
which NPWS have designated as emergency landing sites.

>
> Node or area?
>

Up to you both are fine, but unless there is some kind of boundary you can
see I'd just go with a node.

>
> Of the few I've looked at, one was a very discernible flattened out square
> of dirt which I tagged as an area, another was just a clearing in the
> forest so I put a node there, while the third was just a spot in an open
> paddock.
>
> & it would appear that emergency=landing_site doesn't render in any way -
> does that matter?
>

That's okay, typically something only starts getting rendered by maps and
apps once it has some usage, so actually mapping it helps justify getting
it into maps and apps.
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au

Re: [OSM-talk] JOSM: hover-Coordinate by easy click into clipboard?

2020-01-11 Per discussione Oleksiy Muzalyev


On MacOS it is Command+Shift+C.

I wish there were such a feature on the OSM.org map. Now it is also 
possible to copy the coordinates of a place,
but one has to copy a long string and then to extract the coordinates 
from it. But is JOSM one gets them directly in the proper format, 
something like: 47.7549028, 36.8379178


Sometimes, when adding a photo to Wikimedia Commons which has got the 
coordinates in its JPG's EXIF properties, still for some reason the 
coordinates do not resurface in the location's latitude and longitude 
fields of the page. So, usually in such a case, I return to the OSM.org 
page, copy the long string and then extract the coordinates from it 
manually.


Maybe there is such a feature on the OSM.org page, but I just did not 
notice it yet. Perhaps, I can also point a cursor to a place and do some 
keyboard combination and only the coordinates are copied.


Best regards,
Oleksiy

On 1/8/20 05:52, Erwin Olario wrote:
In JOSM, on an active layer, while a node is selected, you can press 
CTRL+SHIFT+C and it will copy its coordinates to memory.


On Tue, Jan 7, 2020, 09:43 tshrub > wrote:


hi,

in JOSM's status bar the mouse position is constantly running as a
coordinate. Is there any easy way to get it, may be by keyboard
into the
clipboard?
I want to edit GPS data from, or better: add GPS-data to trackless
photos - I want to place them like this with JOSM' sat-pictures.

bella saluti


___
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: [talk-au] A nice website for a bush fire over view

2020-01-11 Per discussione Andrew Harvey

There is no requirement. They can be anonymous if they prefer, best option
is whois data, but like many sites this one is by proxy so that doesn't
reveal anything.

On Sat, 11 Jan 2020 at 19:16, Sebastian S.  wrote:

> I often wonder who puts these pages together.
> Is there no requirement to give contact or responsible person details by
> law in Australia?
>
> On 10 January 2020 1:30:06 pm AEDT, Warin <61sundow...@gmail.com> wrote:
>>
>> Bush fire site for Vic/NSW with OSM attribution.. but data from other 
>> sources too...
>>
>> https://bushfire.io
>>
>> Pity our federal government cannot do the same for all of Australia, could 
>> help stop those trolls.
>>
>>
>> ___
> Talk-au mailing list
> Talk-au@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-au
>
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au

Re: [OSM-talk-fr] Source : les cartes IGN, c'est bien proscrit ?

2020-01-11 Per discussione Vincent Bergeot


Le 11/01/2020 à 09:24, ades a écrit :
En posant la question autrement, les source "Open Licence / licence 
ouverte » Etalab sont utilisables ou pas ?


c'est plutôt une autre question, dont la réponse est oui les ressources 
sous LO sont utilisable dans OSM


Et à ma question des cartes IGN (en particuliers les cartes papiers par 
exemple) *sans* licence LO, non ce n'est pas utilisable et donc une 
source à retirer.


Merci pour les divers retours

--
Vincent Bergeot

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

Re: [Talk-it] Numero di cellulare in OSM

sent from a phone

> On 11. Jan 2020, at 09:22, Francesco Ansanelli  wrote:
> 
> Sul telefonino posso mandare un SMS se trovo occupato, potrei avere un piano 
> che prevede costi differenti tra fissi e mobili...

OpenStreetMap però è un progetto per il presente ed il futuro. Negli anni 
novanta era sicuramente molto più importante capire la tipologia di numero che 
si stava chiamando, ma oramai, soprattutto in Italia, hanno quasi tutti piani 
tariffari che prevedono chiamate illimitate (o minu  sufficienti) verso tutti.

> Chi usa il dato da OSM, se lo trova già diviso, ha un servizio in più... Che 
> a noi costa poco dare!

in realtà costa per chi deve usare i dati, perché deve cercare in tanti chiavi 
diversi, e fare il merge. Invece se tutti usassero “phone” (e forse 
“contact:phone”), trovare un numero sarebbe molto più facile.

Qualcuno potrebbe avere un piano che comporta vantaggi per chiamare numeri 
Wind? Allora phone:mobile:Wind=...

Forse le compagnie che usano la rete Telefònica di ex-E-Plus  hanno vantaggi 
chiamandosi nella stessa rete? 
Visto? Finché parliamo di reti italiane (che conosciamo tutti), sembra tutto 
logico e facile, ma quando non conosci più i dettagli diventa incomprensibile, 
e diventa complicato trovare i numeri telefonici, perché sono distribuiti su 
vari tag.

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

Re: [Talk-it] Numero di cellulare in OSM

Il sab 11 gen 2020, 09:55 Martin Koppenhoefer  ha
scritto:

>
>
> sent from a phone
>
> > On 11. Jan 2020, at 08:59, Francesco Ansanelli 
> wrote:
> >
> > phone:FR:mobile:SFR=3000 for standard toll free call only from the SFR
> mobile network (operator in France)
>
>
>  non è un tag di OpenStreetMap (non è utilizzato nemmeno una volta)
>

Però se è documentato è un tag Essendo l'unico posto dove è menzionato
phone:mobile, immagino sia nato per un significato e ne abbia assunto un
altro...
Déjà vu!

> Ciao Martin
> ___
> 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: [Talk-it] Numero di cellulare in OSM



sent from a phone

> On 11. Jan 2020, at 08:59, Francesco Ansanelli  wrote:
> 
> phone:FR:mobile:SFR=3000 for standard toll free call only from the SFR mobile 
> network (operator in France)


 non è un tag di OpenStreetMap (non è utilizzato nemmeno una volta)

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

Re: [Talk-it] Numero di cellulare in OSM

2020-01-11 Per discussione Federico Cortese

On Sat, Jan 11, 2020 at 9:09 AM Martin Koppenhoefer
 wrote:
>
> Io uso “phone” per tutti i primi numeri, e solo quando ci sono più tipi di 
> numeri per lo stesso POI metto phone:mobile. Invece contact:* non lo metto 
> mai, perché è solo più da digitare, ma non aggiunge niente di utile (a mio 
> parere), al meno per phone.
>

Esattamente quello che faccio anche io:
-phone=* per un solo contatto telefonico;
-phone:mobile=* se oltre al telefono fisso è indicato anche un
cellulare, per tenerli in due tag separati.
-contact:phone=* mai usato (ho votato anche a favore del deprecare
contact:phone qui
https://wiki.openstreetmap.org/wiki/Discussions/tagging/contact:phone_or_phone,
anche se hanno vinto i contrari)
-contact:mobile=* fino a poco tempo fa non sapevo nemmeno esistesse :-)

Ciao,
Federico

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

Re: [Talk-it] Numero di cellulare in OSM

Ciao Andrea,

Il sab 11 gen 2020, 09:22 Andrea Musuruane  ha scritto:

> Ciao,
> la discussione è nata su un changeset dove mi sono accorto delle
> modifiche fatte da Francesco:
> https://www.openstreetmap.org/changeset/79310026
>
> Giustamente, Francesco ha spostato in ML la discussione.
>
> Faccio notare che questo è un edit semi automatico e come tale sarebbe
> dovuto essere discusso prima di eseguire i vari commit.
> https://wiki.openstreetmap.org/wiki/Automated_edits
>


In realtà è stato un lavoro manuale di svariate ore!


> Sulla wiki c'è un unico riferimento al significato della chiave
> phone:mobile, ed è in una pagina in italiano:
> https://wiki.openstreetmap.org/wiki/IT:Glossario_OSM
>
> Mentre nella pagina della chiave phone è presente questo esempio:
> *phone:FR:mobile:SFR=3000 for standard toll free call only from the SFR
> mobile network (operator in France)*
>
> La mia opinione in merito è che è inutile avere due tag distinti per
> specificare il tipo di numero di telefono. Se si vuole capire se è un fisso
> o mobile (o un numero verde o un numero di emergenza, ecc), lo si può
> capire direttamente dalla sintassi del numero stesso.
>
> La chiave contact:mobile è deprecata per lo stesso motivo: *"mobile phone
> number. The more general tag contact:phone
> =* should be
> preferred"*
> https://wiki.openstreetmap.org/wiki/Key:contact
>
> Quindi sarebbe utile continuare a usare solo phone (o contact:phone che mi
> è sempre sembrato un tag con una semantica migliore). Questo inoltre
> facilita la vita anche ai consumatori dei dati e non mi sembra un aspetto
> trascurabile.
>
> Ciao,
>
> Andrea
>
>
>
>
>
> On Sat, Jan 11, 2020 at 7:37 AM Francesco Ansanelli 
> wrote:
>
>> Buongiorno lista,
>>
>> C'è un problema con il tag "phone:mobile" in quanto in una pagina¹ è
>> indicato espressamente che si tratta di "numero di cellulare", mentre da un
>> esempio nella pagina Phone² pare che serva per indicare il numero per chi
>> chiama da rete mobile (con possibilità di indicare anche operatore e
>> nazione del chiamante).
>> Ovviamente c'è una bella differenza!
>>
>> Ho passato qualche ora ad aggiornare il formato dei numeri di telefono in
>> Piemonte, spostando anche sul tag cellulare quando necessario... Essendoci
>> questa ambiguità ovviamente il lavoro che ho fatto potrebbe essere stato in
>> parte inutile.
>> Visto che è una procedura piuttosto meccanica vorrei fare un edit e
>> cambiare tutti i tag "phone:mobile" in "contact:mobile", in quanto lo
>> schema "contact:*" prevede "mobile" con il significato che avevo inteso
>> anche io. Posso farlo solo sugli oggetti modificati da me oppure su tutta
>> Italia (dato che è un problema di pagina wiki in italiano)?
>> Oppure dovrei fare revert e tornare su "phone"?
>>
>> Visto che ci siamo, infine, vorrei sapere se per voi è corretto fare la
>> distinzione tra numeri fissi e mobili, oppure, se "phone" (o
>> "contact:phone") dovrebbe essere il calderone dove finisce tutto,
>> eventualmente separato dal simbolo punto e virgola?
>> In questo caso preferirei usare 2 tag diversi, visto che mi sembra
>> un'utile distinzione. Voi cosa pensate?
>>
>> Anche in base ai commenti, vorrei aggiornare le due pagine in questione:
>> per prima cosa, togliendo dalla pagina del glossario il riferimento al
>> cellulare o cambiando il tag indicando quello dello schema "contact:*" e,
>> successivamente, la pagina "phone" aggiungendo che i numeri di cellulare
>> vanno inseriti seguendo un altro schema oppure messi nel tag phone.
>>
>> Grazie mille
>> Francesco
>>
>> ¹ https://wiki.openstreetmap.org/wiki/IT:Glossario_OSM
>> ² https://wiki.openstreetmap.org/wiki/Key:phone
>>
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [OSM-talk-fr] Source : les cartes IGN, c'est bien proscrit ?

2020-01-11 Per discussione Christian Quest

En posant la question autrement, les source "Open Licence / licence 
ouverte » Etalab sont utilisables ou pas ?

Ch. Quest avait l’air de dire que oui dans un post récent.



Je n'ai pas "l'air de dire", ça a toujours été le cas.

Je ne comprends pas pourquoi certains se posent la question depuis 
quelques temps et mettent en doute quelque chose de clair: la LO est 
compatible avec l'ODbL, l'inverse ne l'est pas.


La LO qui n'est qu'une traduction "claire" de la loi, est heureusement 
compatible avec l'usage pour OSM, sinon cela voudrait dire que toutes 
les données mises en opendata en France ne le seraient pas !



Nous avons une couche Route500 sur les serveurs OSM depuis des années, 
Admin-Express y est aussi intégré.


L'orthohr nous l'utilisons depuis plusieurs années

Le reste est d'une qualité dégradée qui rend les données sans intérêt 
pour nous.



Les cartes IGN détaillées (le 1:25000) ne sont pas en LO, c'est pour 
cela qu'on ne peut pas les utiliser.



--
Christian Quest - OpenStreetMap France


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

Re: [OSM-talk-fr] {Disarmed} Re: SPAM, Mentions légales

2020-01-11 Per discussione Christian Quest


Mail envoyé... à suivre

Le 10/01/2020 à 23:08, Thomas Gratier a écrit :

Salut,

Pour http://www.inforoute04.fr/ et https://www.inforoutefrance.fr/, 
 le problème est plutôt qu'ils ont 
caché "volontairement" (pour des raisons de "look" souvent) 
l'attribution parce que pour OpenLayers par défaut, tu testes 
http://openlayers.org/en/latest/doc/quickstart.html ou tu vas sur 
https://openlayers.org/en/latest/examples/simple.html pour voir que 
l'attribution est bien respectée par défaut.


J'ai récemment répondu à des c... qui insistent pour te planquer par 
défaut l'attribution *MailScanner soupçonne le lien suivant d'être une 
tentative de fraude de la part de "twitter.com" * 
https://twitter.com/ThomasG77/status/12142053007498199https://twitter.com/ThomasG77/status/1214205300749819905 
 
en particulier les gens de chez M...x qui persistent et signent depuis 
plusieurs années...
Il faut noter qu'ils font un peu moins pire que d'autres acteurs car 
l'attribution bien que "planqué" par défaut est présente contrairement 
à d'autres qui prennent la peine de la supprimer, la renommer à leur 
nom ("Copyright MyCompany all rights reserved, fuck the OSM 
contributors"), oublient de l'ajouter, la mettent en police 6 en bas 
de leur page crédits,...
La discussion initiale que j'ai attrapée est 
https://twitter.com/allan_mustard/status/1214022912895787009 
https://twitter.com/allan_mustard/status/1214022912895787009et là, 
j'ai bien dû "allumer" parce que les "Maurice poussaient le bouchon 
trop loin"



Thomas

https://twitter.co 



--
Christian Quest - OpenStreetMap France

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

Re: [Talk-it] Numero di cellulare in OSM

On 11/01/20 08:58, Francesco Ansanelli wrote:

> C'è un problema con il tag "phone:mobile" in quanto in una
pagina¹ è
> indicato espressamente che si tratta di "numero di cellulare",
mentre
> da un esempio nella pagina Phone² pare che serva per indicare il
> numero per chi chiama da rete mobile (con possibilità di indicare
> anche operatore e nazione del chiamante).
Non ho trovato questo riferimento. Puoi esplicitare per favore la
frase
dalla quale derivi questo significato?

Non c'è! Però l'unico riferimento è questo esempio:

phone:FR:mobile:SFR=3000 for standard toll free call only from the SFR 
mobile network (operator in France)

La riga che hai copiato è nella sezione "Support for multiple 
countries": 
https://wiki.openstreetmap.org/wiki/Key:phone#Support_for_multiple_countries

Da quello che capisco, gli esempi sono delle ulteriori specificazioni 
per indicare numeri particolari per chi chiama da uno stato specifico. I 
numeri sono phone::*

Io interpreto che l'esempio [contact:]phone:FR:mobile:SFR=3000 sia molto 
specifico e non confligga con un generico phone:mobile (o il 
corrispondente contact:mobile). Ho trovato solamente 23 elementi taggati 
con uno schema simile...

Ale

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

[OSM-talk-fr] Source : les cartes IGN, c'est bien proscrit ?

2020-01-11 Per discussione ades

En posant la question autrement, les source "Open Licence / licence ouverte » 
Etalab sont utilisables ou pas ? 

Ch. Quest avait l’air de dire que oui dans un post récent.

Dans ce cas les sources ign sous ‘Open licence/licence ouverte’ le seraient 
également. Maintenant pour la toponymie…
soit (d’après http://www.ign.fr/institut/activites/lign-lopen-data 
) : 


Sont téléchargeables sur l'Espace professionnel de l'IGN et utilisables 
gratuitement sous licence ouverte Etalab (liste à jour au 30 avril 2018)

ADMIN EXPRESS 
BD ALTI®  aux pas de 75 m et 250 m
ROUTE 500® 
ROUTE 120® 
Le thème hydrographique de la BD TOPO 

BD ORTHO® 50 cm  
sur certains départements
ORTHO HR®  sur certains départements
BD ORTHO® 5 m 
FranceRaster ® 
 du 1 : 100 000 au 1 : 8 000 000
Contours... IRIS® 
Sont téléchargeables sur la plateforme ouverte des données publiques françaises 
et utilisables gratuitement sous licence ouverte Etalab

Répertoire de données de référence géodésiques et des codelists ISO 19115 

Sont téléchargeables sur le site Éducation de l'IGN et utilisables gratuitement 
sous licence ouverte Etalab

Fonds de carte  « image »
Sont téléchargeables sur le site de l'inventaire forestier et utilisables 
gratuitement sous licence ouverte Etalab

Données de l'inventaire forestier 
 (données brutes, 
résultats standards et personnalisés)
Sont téléchargeables sur le site de la géodésie et utilisables gratuitement 
sous licence ouverte Etalab

Fiches géodésiques et de nivellement 

Est téléchargeable sur le portail de l'information géographique maritime et 
littorale du Service hydrographique et océanographique de la marine (SHOM) et 
utilisable gratuitement sous licence ouverte Etalab

Litto3D® (coproduction SHOM/IGN) sur data.shom.fr 
Sont téléchargeables sur le service « Remonter le temps 
 » et utilisables gratuitement

Prises de vues aériennes (PVA)
Cartes anciennes numérisées

> Le 9 janv. 2020 à 16:53, François Lacombe  a écrit 
> :
> 
> Bonjour
> 
> Une issue a été ouverte relativement à ce problème, avec un extrait sur la 
> commune de Saint-Christo en Jarez.
> https://github.com/Project-OSRM/osrm-backend/issues/5644 
> 
> 
> Par ailleurs et malgré les id de longueur importante, le routage se fait 
> correctement et les routes sont bien renvoyées.
> 
> N'hésitez pas à commenter ou constater ce que je remonte, pour être sur que 
> je ne fasse pas d'erreur
> 
> François
> 
> Le mer. 8 janv. 2020 à 22:58, François Lacombe  > a écrit :
> 
> Le mer. 8 janv. 2020 à 22:04, Julien Coupey  > a écrit :
> Il y a quand même pas mal de gens qui 
> continuent à utiliser OSRM et tout ce petit monde a intérêt à ce que ça 
> fonctionne. ;-)
> 
> Je n'en doute pas vu le nombre de forks sur le dépôt du backend c'est 
> impressionnant.
> 
> A la base, j'en suis arrivé à cette solution (utiliser annotations=nodes) 
> parce qu'il y avait ce soucis-là sur lequel personne n'a jamais réagit
> https://github.com/Project-OSRM/osrm-backend/issues/5190 
> 
> 
> Il n'y a pas de jeu de données d'entrée en effet, il faudra que je vois si je 
> ne peux pas sortir un extract dans ce coin également.
> Mais il faut aussi fournir les profils utilisés pour produire la réduction et 
> je n'y suis pas autorisé
> 
> Bonne soirée
> 
> François
> ___
> 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: [Talk-it] Numero di cellulare in OSM

2020-01-11 Per discussione Andrea Musuruane

Ciao,
la discussione è nata su un changeset dove mi sono accorto delle
modifiche fatte da Francesco:
https://www.openstreetmap.org/changeset/79310026

Giustamente, Francesco ha spostato in ML la discussione.

Faccio notare che questo è un edit semi automatico e come tale sarebbe
dovuto essere discusso prima di eseguire i vari commit.
https://wiki.openstreetmap.org/wiki/Automated_edits

Sulla wiki c'è un unico riferimento al significato della chiave
phone:mobile, ed è in una pagina in italiano:
https://wiki.openstreetmap.org/wiki/IT:Glossario_OSM

Mentre nella pagina della chiave phone è presente questo esempio:
*phone:FR:mobile:SFR=3000 for standard toll free call only from the SFR
mobile network (operator in France)*

La mia opinione in merito è che è inutile avere due tag distinti per
specificare il tipo di numero di telefono. Se si vuole capire se è un fisso
o mobile (o un numero verde o un numero di emergenza, ecc), lo si può
capire direttamente dalla sintassi del numero stesso.

La chiave contact:mobile è deprecata per lo stesso motivo: *"mobile phone
number. The more general tag contact:phone
=* should be
preferred"*
https://wiki.openstreetmap.org/wiki/Key:contact

Quindi sarebbe utile continuare a usare solo phone (o contact:phone che mi
è sempre sembrato un tag con una semantica migliore). Questo inoltre
facilita la vita anche ai consumatori dei dati e non mi sembra un aspetto
trascurabile.

Ciao,

Andrea





On Sat, Jan 11, 2020 at 7:37 AM Francesco Ansanelli 
wrote:

> Buongiorno lista,
>
> C'è un problema con il tag "phone:mobile" in quanto in una pagina¹ è
> indicato espressamente che si tratta di "numero di cellulare", mentre da un
> esempio nella pagina Phone² pare che serva per indicare il numero per chi
> chiama da rete mobile (con possibilità di indicare anche operatore e
> nazione del chiamante).
> Ovviamente c'è una bella differenza!
>
> Ho passato qualche ora ad aggiornare il formato dei numeri di telefono in
> Piemonte, spostando anche sul tag cellulare quando necessario... Essendoci
> questa ambiguità ovviamente il lavoro che ho fatto potrebbe essere stato in
> parte inutile.
> Visto che è una procedura piuttosto meccanica vorrei fare un edit e
> cambiare tutti i tag "phone:mobile" in "contact:mobile", in quanto lo
> schema "contact:*" prevede "mobile" con il significato che avevo inteso
> anche io. Posso farlo solo sugli oggetti modificati da me oppure su tutta
> Italia (dato che è un problema di pagina wiki in italiano)?
> Oppure dovrei fare revert e tornare su "phone"?
>
> Visto che ci siamo, infine, vorrei sapere se per voi è corretto fare la
> distinzione tra numeri fissi e mobili, oppure, se "phone" (o
> "contact:phone") dovrebbe essere il calderone dove finisce tutto,
> eventualmente separato dal simbolo punto e virgola?
> In questo caso preferirei usare 2 tag diversi, visto che mi sembra
> un'utile distinzione. Voi cosa pensate?
>
> Anche in base ai commenti, vorrei aggiornare le due pagine in questione:
> per prima cosa, togliendo dalla pagina del glossario il riferimento al
> cellulare o cambiando il tag indicando quello dello schema "contact:*" e,
> successivamente, la pagina "phone" aggiungendo che i numeri di cellulare
> vanno inseriti seguendo un altro schema oppure messi nel tag phone.
>
> Grazie mille
> Francesco
>
> ¹ https://wiki.openstreetmap.org/wiki/IT:Glossario_OSM
> ² https://wiki.openstreetmap.org/wiki/Key:phone
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [Talk-it] Numero di cellulare in OSM

Il sab 11 gen 2020, 09:09 Martin Koppenhoefer  ha
scritto:

>
>
> sent from a phone
>
> > On 11. Jan 2020, at 08:26, canfe  wrote:
> >
> > Chiamare qualcuno ad ora tarda sul fisso o sul cellulare fa una bella
> > differenza!
>
>
> bo, per me non c’è questa bella differenza. La piccola differenza dei miei
> numeri: spengo il cellulare a mano mentre il fisso si spegne in automatico
> col timer. Qui comunque stiamo parlando di numeri pubblici, non di numeri
> di persone private, e quindi quando chiami fuori orari avranno normalmente
> una segreteria automatica.
>
> Io uso “phone” per tutti i primi numeri, e solo quando ci sono più tipi di
> numeri per lo stesso POI metto phone:mobile. Invece contact:* non lo metto
> mai, perché è solo più da digitare, ma non aggiunge niente di utile (a mio
> parere), al meno per phone.
>

Sul telefonino posso mandare un SMS se trovo occupato, potrei avere un
piano che prevede costi differenti tra fissi e mobili...
Chi usa il dato da OSM, se lo trova già diviso, ha un servizio in più...
Che a noi costa poco dare!
Se c'è il punto e virgola deve pure dividerli per poterli chiamare.

>
>
> Ciao Martin
> ___
> 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: [talk-au] A nice website for a bush fire over view

I often wonder who puts these pages together.
Is there no requirement to give contact or responsible person details by law in 
Australia?

On 10 January 2020 1:30:06 pm AEDT, Warin <61sundow...@gmail.com> wrote:
>Bush fire site for Vic/NSW with OSM attribution.. but data from other 
>sources too...
>
>https://bushfire.io
>
>Pity our federal government cannot do the same for all of Australia,
>could help stop those trolls.
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au

Re: [Talk-it] Numero di cellulare in OSM

sent from a phone

> On 11. Jan 2020, at 08:26, canfe  wrote:
> 
> Chiamare qualcuno ad ora tarda sul fisso o sul cellulare fa una bella
> differenza!

bo, per me non c’è questa bella differenza. La piccola differenza dei miei 
numeri: spengo il cellulare a mano mentre il fisso si spegne in automatico col 
timer. Qui comunque stiamo parlando di numeri pubblici, non di numeri di 
persone private, e quindi quando chiami fuori orari avranno normalmente una 
segreteria automatica.

Io uso “phone” per tutti i primi numeri, e solo quando ci sono più tipi di 
numeri per lo stesso POI metto phone:mobile. Invece contact:* non lo metto mai, 
perché è solo più da digitare, ma non aggiunge niente di utile (a mio parere), 
al meno per phone.

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

Re: [talk-au] JOSM problem