Re: [Talk-it] Vecchi sentieri CAI

[Danilo via Talk-it]

Concordo TOTALMENTE con quanto esposto da IvoDaniloIl 27 Set 2020 23:36, Ivo Reano  ha scritto:Giusto per fare almeno una verifica formale, potresti segnalarci qualcuno di questi sentieri "ex CAI"?Grazie.Ivo, Jrachi
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [Talk-us] Recent Trunk road edits

[Jack Burke]

Clifford,

If I'm going to name names, I may as well include a few relevant links, too.

The editor in question is "floridaeditor"
https://www.openstreetmap.org/user/floridaeditor and he has a diary
entry about what he's doing (in addition to what he has on his profile
page about it).  He changed *every single* trunk road in Georgia to
primary, and from what I can tell, in Florida, too.  I haven't yet
expanded my examination into other states yet.

One example changeset comment can be found here:
https://www.openstreetmap.org/changeset/87987046
Another (where he reverted someone's reversal of his edits) is:
https://www.openstreetmap.org/changeset/88299504

I myself haven't added any comments to some of his changesets yet
because of his borderline belligerent attitude in his remarks.  He
essentially sets himself up as the judge and jury about whether or not
he will "accept" any requests for a change back to trunk.  A few other
people have (one of whom did so in a less than helpful manner, even
though he's local and from what I can tell, should likely be familiar
with the roads in question), but I'm just being an observer on that
for now.

I'm on Slack, and I originally posted a comment about this editor on
some roads in Florida (that I'm familiar with), but the responses I
saw seemed to be somewhat "meh" so I didn't pursue it.  If there's
another thread about it there, I'd love to read it, because (1) I
missed it, and (2) if it's about the same person, y'all weren't very
successful in reverting the changes.

--jack

On Sun, Sep 27, 2020 at 10:21 PM Clifford Snow  wrote:
>
> Jack,
> First off - lets name names. Who is this person? We did have a discussion on 
> Slack a while back about an editor changing trunk to something other than 
> trunk. As far as I know we were successful in reverting many of those.
>
> Not everyone is comfortable using Slack and I understand. However, they 
> should respond to changeset comments. Especially from someone familiar with 
> the road. If they ignore you, then I would recommend involving DWG. If they 
> just want to argue then but won't join Slack, then I'd invite them to to this 
> mailing list discuss why they feel a particular road should be changed from 
> trunk to primary.
>
> Best,
> Clifford
>
> On Sun, Sep 27, 2020 at 6:35 PM Jack Burke  wrote:
>>
>> Hi all,
>>
>> Recently, someone has taken it on himself to downgrade most (all?)
>> highway=trunk roads in the eastern U.S. to just primary.  The odd
>> thing is that the very wiki page he cites as his reason fully supports
>> keeping them as trunk.  Many of them I'm personally familiar with, and
>> even absent the wiki's definition, they actually make more sense as
>> trunk from a driving perspective.
>>
>> A few other editors have been getting involved in discussions with
>> him, some helpfully, others not quite.  He was specifically invited to
>> join this mailing list (and tagging), to discuss things, but as far as
>> I can tell hasn't done so yet.  Andy from DWG also suggested that he
>> join the OSMUS Slack channel, but I can't tell that he's done that,
>> either.
>>
>> Of particular concern to me isn't just his downgrades, but his
>> attitude about them.  Some of his changeset comments basically tell
>> anyone who disagrees with him to appeal his decision to him, and he'll
>> decide if the appellant is right or not, and if he catches anyone
>> reversing his changes, he'll just revert it back.  Given his
>> already-posted attitude about his edits, I'm not sure that trying to
>> message him privately will do much good.
>>
>> I'm going to go ahead and put out here that I've gone ahead and
>> changed some of them back to highway=trunk anyway, because as I said,
>> they just make more sense that way, *and* meet the wiki's definition.
>> And I'm quite sure that he'll revert them as soon as he notices.
>>
>> Does anyone have any suggestions, comments, questions, jokes, etc.,
>> about the situation?
>>
>> Regards,
>> Jack
>>
>> ___
>> Talk-us mailing list
>> Talk-us@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-us
>
>
>
> --
> @osm_washington
> www.snowandsnow.us
> OpenStreetMap: Maps with a human touch

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

Re: [Talk-us] Recent Trunk road edits

[Clifford Snow]

Jack,
First off - lets name names. Who is this person? We did have a discussion
on Slack a while back about an editor changing trunk to something other
than trunk. As far as I know we were successful in reverting many of those.

Not everyone is comfortable using Slack and I understand. However, they
should respond to changeset comments. Especially from someone familiar with
the road. If they ignore you, then I would recommend involving DWG. If they
just want to argue then but won't join Slack, then I'd invite them to to
this mailing list discuss why they feel a particular road should be changed
from trunk to primary.

Best,
Clifford

On Sun, Sep 27, 2020 at 6:35 PM Jack Burke  wrote:

> Hi all,
>
> Recently, someone has taken it on himself to downgrade most (all?)
> highway=trunk roads in the eastern U.S. to just primary.  The odd
> thing is that the very wiki page he cites as his reason fully supports
> keeping them as trunk.  Many of them I'm personally familiar with, and
> even absent the wiki's definition, they actually make more sense as
> trunk from a driving perspective.
>
> A few other editors have been getting involved in discussions with
> him, some helpfully, others not quite.  He was specifically invited to
> join this mailing list (and tagging), to discuss things, but as far as
> I can tell hasn't done so yet.  Andy from DWG also suggested that he
> join the OSMUS Slack channel, but I can't tell that he's done that,
> either.
>
> Of particular concern to me isn't just his downgrades, but his
> attitude about them.  Some of his changeset comments basically tell
> anyone who disagrees with him to appeal his decision to him, and he'll
> decide if the appellant is right or not, and if he catches anyone
> reversing his changes, he'll just revert it back.  Given his
> already-posted attitude about his edits, I'm not sure that trying to
> message him privately will do much good.
>
> I'm going to go ahead and put out here that I've gone ahead and
> changed some of them back to highway=trunk anyway, because as I said,
> they just make more sense that way, *and* meet the wiki's definition.
> And I'm quite sure that he'll revert them as soon as he notices.
>
> Does anyone have any suggestions, comments, questions, jokes, etc.,
> about the situation?
>
> Regards,
> Jack
>
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>


-- 
@osm_washington
www.snowandsnow.us
OpenStreetMap: Maps with a human touch
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

[Talk-us] Recent Trunk road edits

[Jack Burke]

Hi all,

Recently, someone has taken it on himself to downgrade most (all?)
highway=trunk roads in the eastern U.S. to just primary.  The odd
thing is that the very wiki page he cites as his reason fully supports
keeping them as trunk.  Many of them I'm personally familiar with, and
even absent the wiki's definition, they actually make more sense as
trunk from a driving perspective.

A few other editors have been getting involved in discussions with
him, some helpfully, others not quite.  He was specifically invited to
join this mailing list (and tagging), to discuss things, but as far as
I can tell hasn't done so yet.  Andy from DWG also suggested that he
join the OSMUS Slack channel, but I can't tell that he's done that,
either.

Of particular concern to me isn't just his downgrades, but his
attitude about them.  Some of his changeset comments basically tell
anyone who disagrees with him to appeal his decision to him, and he'll
decide if the appellant is right or not, and if he catches anyone
reversing his changes, he'll just revert it back.  Given his
already-posted attitude about his edits, I'm not sure that trying to
message him privately will do much good.

I'm going to go ahead and put out here that I've gone ahead and
changed some of them back to highway=trunk anyway, because as I said,
they just make more sense that way, *and* meet the wiki's definition.
And I'm quite sure that he'll revert them as soon as he notices.

Does anyone have any suggestions, comments, questions, jokes, etc.,
about the situation?

Regards,
Jack

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

[Talk-at] (Halb-)mechanischer Edit von Ärztenamen in Tirol

[Stefan Tauner]

Hi,

mir ist aufgefallen, dass die Namen von Ärzten und Arztpraxen in Tirol
einem ungewöhnlichen Schema folgen, nämlich "Dr  ()".
Das geht auf den intensiven Einsatz von fs_LT zurück, welcher sie in
dieser Form über die Zeit eingetragen hat. Das betrifft lt. folgendem
Query knappe 900 Objekte. Das inkludiert aber nur die, die von fs_LT
als letztes geändert (und vmtl. in ~100% der Fälle auch angelegt)
wurden. Wenn man diese User-Beschränkung aufhebt sind es ca. 1200.
https://overpass-turbo.eu/s/YrY

Da dieses Schema für den deutschen Sprachraum unüblich ist, würde ich
das gerne auf "Dr.  " ändern (bzw. wäre ich natürlich
auch nicht böse, wenn das jemand anderer hackt ;)
Ich würde das ggf. per Overpass laden, exportieren in einem Texteditor,
mit sed oder vl. auch etwas OSM-spezifischen (Vorschläge?) ändern und
wieder hochladen. Allerdings wird es auf Grund von Doppelnamen und
anderen Uneindeutigkeiten ohne eine manuelle Überprüfung ohnehin kaum
gehen. Da fs_LT nichts dagegen hat, seh ich aber keine grundsätzlichen
Probleme. Trotzdem stelle ich das hier mal zur Diskussion, bevor ich
mich um die Details zu automated edits kümmere.

CS-Diskussion (die aber wenig weitere Information beinhaltet):
https://www.openstreetmap.org/changeset/88331474

-- 
Kind regards/Mit freundlichen Grüßen, Stefan Tauner

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

Re: [Talk-at] Mapper A* beschädigt reihenweise Relationen

[Robert Grübler]

Die DWG hab ich informiert (Ticket#202009111326). 
In der Zwischenzeit sind mir 3 weitere CS mit beschädigten Relationen 
aufgefallen.
Heute der CS https://www.openstreetmap.org/changeset/88237088 mit 10 
beschädigten Relationen (alles Wander- und Radrouten).

Tut mir leid, mir ist das zuviel, ich räum den Scherbenhaufen nicht weiter auf.

LG Robert


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

Re: [OSM-talk-fr] Simplification représentation "Cédez-le-passage cycliste au feu"

[Eric SIBERT via Talk-fr]

À Grenoble, on a les panneaux vélo-super-power :

https://www.mapillary.com/map/im/qAFGJjDNEmcMO5BL-gBfIg

Au feu rouge, les vélos peuvent aller partout en cédant le passage.

Donc, dans le schéma d'origine que je découvre, il faudrait trois relations.

Eric

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

Re: [Talk-it] Vecchi sentieri CAI

[Ivo Reano]

Giusto per fare almeno una verifica formale, potresti segnalarci qualcuno
di questi sentieri "ex CAI"?
Grazie.
Ivo, Jrachi
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [Talk-it] Vecchi sentieri CAI

[Ivo Reano]

Il giorno dom 27 set 2020 alle ore 22:45 MicheleOSM3 
ha scritto:

> Grazie a tutti delle risposte.
>
> Credo di non essere stato chiarissimo, pertanto chiedo scusa e faccio
> una premessa.
>
> Premesso che:
> Se faccio una modifica in OSM per un certo sentiero, ho già verificato
> se è CAI o no, sia perché ho già controllato la segnaletica di persona,
> sia perché ho già controllato il sito CAI-FVG, a volte ho anche chiesto
> info ad altre persone.
> Quando nella mia domanda iniziale scrivo: "sentieri che una volta erano
> sentieri CAI ma che adesso non sono più CAI", intendo dire che non sono
> più gestiti dal CAI, e pertanto il CAI ha rimosso (o avrebbe dovuto
> rimuovere) i relativi cartelli e segnavia e ha rimosso (o avrebbe dovuto
> rimuovere) dal suo sito i riferimeti al sentiero.
> Pertanto non sto parlando di sfalciature e altra la manutenzione che fa
> il CAI su sentieri CAI , sto parlando solo di sentieri ex-CAI.
> Questi sentieri ex-CAI a volte sono hanno ancora parti con tracce molto
> visibili altre volte le tracce non si vedono più, alle volte sono
> franati, a volte sono percorsi saltuariamente da escursionisti molto
> esperti e avventurosi, insomma ci sono varie situazioni.
>
> Premesso tutto questo, la mi domanda è molto semplice:
> Dato che ho trovato su OSM sentieri mappati come CAI ma che in realtà
> sono ex-CAI, ho iniziato a correggere queste situazioni e per farlo ho
> visto cosa hanno fatto altri prima di me e ho copiato un po' le loro
> tecniche.
> Volevo sapere se la tecnica che hanno usato altri prima di me è valida o
> se avete delle tecniche migliori.
>
Premesso che io vivo una situazione , forse, diversa dal FVG, Piemonte.
Anche se sono quasi 20 anni che partecipo attivamente alla manutenzione dei
sentieri della nostra zona, le Valli di Lanzo, anche come ricerca per il
recupero di vecchi tracciati, e rilevatore della rete sentieristica
regionale, ed, infine credo di avere una certa esperienza delle "cose" del
CAI; ho sempre sentito con fastidio la designazione di "sentiero CAI".
I sentieri come vie di comunicazione rurale, che siano mantenuti nella
segnaletica, verticale, o solo orizzontale, oppure siano semplicemente
usati, non sono di proprietà di nessuno, possono essere su terreno privato,
ma il loro uso è pubblico!

La tecnica è molto semplice, usare il prefisso disused su 3 tag, come
> nell'esempio:
>  disused:operator=Club Alpino Italiano
>  disused:osmc:name=651
>  disused:osmc:symbol=red:red:white_stripe:651:black
> A me sembra valida, sia perché credo che descriva la realtà, sia perché
> le visualizzazioni appaiono corrette.
>
Mi sembra una inutile complicazione.
Se l'operator era "CAI" mentre in effetti la sezione locale non se ne
occupa, credo sia semplicemente da correggere con il nuovo o reale operator
e se nessuno si dichiara responsabile si toglie il tag come errato.
Piccola parentesi: (non sono sicuro della validità nazionale) la
responsabilità civile della viabilità rurale è il comune nella figura del
sindaco. Se qualcuno si fa male su un sentiero e la colpa è di una
insufficiente manutenzione, o mancanza di segnalazione di un effettivo
pericolo il responsabile è il sindaco del comune pertinente. Ma io stesso
non metterò mai una figura operator se non sono sicuro che vi sia una
persona o un indirizzo e-mail a cui inviare la segnalazione di problemi su
un sentiero. Chiudendo la parentesi: nelle valli di Lanzo, Ceronda, Ceronda
e Casternone e anche  Val Malone potete inviare segnalazioni su
problematiche a i...@cailanzo.it
Se sul percorso non esistono segni col numero e le bandierine a vernice si
sono dissolte col tempo si devono togliere i rispettivi  tag dalla
relazione del percorso.
L'ultima precisazione è riferita al fatto che tu segnali tag senza
specificare che quelli che proponi possono essere solo sulla relazione di
un percorso escursionistico e non sul tratto di sentiero.

grazie a chi mi vorrà rispondere.
> ciao
>
Ciao
Ivo, Jrachi
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [Talk-it] Vecchi sentieri CAI

[Martin Koppenhoefer]

sent from a phone

> On 27. Sep 2020, at 22:45, MicheleOSM3  wrote:
> 
> La tecnica è molto semplice, usare il prefisso disused su 3 tag, come 
> nell'esempio:
> disused:operator=Club Alpino Italiano
> disused:osmc:name=651
> disused:osmc:symbol=red:red:white_stripe:651:black


premesso che in OpenStreetMap ci sono sia sentieri (highway=path etc.) che 
sentieri (relazioni con tag type=route, route=hiking), suppongo che ti 
riferisci ad entrambi i casi?

Penso che in generale le modifiche proposte da te vanno bene, hanno senso 
(aiutano nell’interpretazione di qualche segnavia ancora sul campo, nonché di 
altre mappe (superate)), e sono in sintonia con il concetto di life cycle 
prefix. Potresti anche mettere “abandoned” invece di disused.

https://wiki.openstreetmap.org/wiki/Lifecycle_prefix

Ciao Martin 

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

Re: [OSM-talk-fr] Choisir le bon name pour les trajets de bus

[osm . sanspourriel]

Le 27/09/2020 à 18:02, deuzeffe - opensm@deuzeffe.org a écrit :


Le 27/09/2020 à 16:46, Gad Jo a écrit :

Bonjour a tous,


Bonjour,


Bonjour aussi.


Sur les trajets desservant des communes différentes j'ai ajouter le
nom des communes + arrêt. Problème ça commence à être sacrement
illisible.

Sur ton exemple on reste dans la même commune.

> Auriez vous des propositions à me faire ? À moins que des règles
existent et j'applique... Je serait tenté de placer que le nom de
l'arrêt


J'ai peut-être été hétérodoxe, mais pour les lignes de bus de
l'intercommunalité voisine et celles du département, j'ai "bêtement"
repris les dénominations officielles du réseau, de terminus à terminus.


Ça semble assez logique : un réseau de transport public doit savoir
comment s'adresser au public pour lequel les transports s'adressent.
Certains arrêts n'ont pas le même nom suivant la ligne. Style Mairie ou
Trifouillis-les-Oies Mairie.

Ça pourra donner des Mairie - Cimetière pour une ligne de
Trifouillis-les-Oies mais Trifouillis-les-Oies Mairie -
Brie-Compte-Robert Église pour une autre.

Note : je mets en name le nom affiché (source:name
=sign)
et official_name pour celui des trajets (source:official_name=timetable).

Jean-Yvon




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

Re: [OSM-talk-fr] Web-SIG du Pays Terres de Lorraine

[pepilepi...@ovh.fr]

Le 27/09/2020 à 21:17, osm.sanspourr...@spamgourmet.com a écrit :
> Le 27/09/2020 à 14:21, Romain MEHUT - romain.me...@mailo.com a écrit :
>> J'en viens donc à vous, auriez-vous connaissance de web-SIG grand
>> public où les données OSM seraient exploitées pour justement éviter
>> cet écueil ? Tony peut être avec la CCPRO ?
>
> GéoBretagne avec ÇaResteOuvert par exemple :
>
> https://cms.geobretagne.fr/content/commerces-de-premiere-necessite-ouverts
>
> 
>
>
> Avec les débits de boisson sur Marseille, CRO ferme.
>
> En fait non, ne va-t-il pas falloir réactiver CRO ? :-(
CRO ou Kro ?
>
> Mais avant il faut sans doute nettoyer ce qui est encore présent.
>
> Jean-Yvon
>
>
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr


-- 


Si ma réponse n'a pas résolu ton problème, c'est que tu n'as pas posé la
bonne question.

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

Re: [Talk-it] Vecchi sentieri CAI

[MicheleOSM3]

Grazie a tutti delle risposte.

Credo di non essere stato chiarissimo, pertanto chiedo scusa e faccio 
una premessa.


Premesso che:
Se faccio una modifica in OSM per un certo sentiero, ho già verificato 
se è CAI o no, sia perché ho già controllato la segnaletica di persona, 
sia perché ho già controllato il sito CAI-FVG, a volte ho anche chiesto 
info ad altre persone.
Quando nella mia domanda iniziale scrivo: "sentieri che una volta erano 
sentieri CAI ma che adesso non sono più CAI", intendo dire che non sono 
più gestiti dal CAI, e pertanto il CAI ha rimosso (o avrebbe dovuto 
rimuovere) i relativi cartelli e segnavia e ha rimosso (o avrebbe dovuto 
rimuovere) dal suo sito i riferimeti al sentiero.
Pertanto non sto parlando di sfalciature e altra la manutenzione che fa 
il CAI su sentieri CAI , sto parlando solo di sentieri ex-CAI.
Questi sentieri ex-CAI a volte sono hanno ancora parti con tracce molto 
visibili altre volte le tracce non si vedono più, alle volte sono 
franati, a volte sono percorsi saltuariamente da escursionisti molto 
esperti e avventurosi, insomma ci sono varie situazioni.


Premesso tutto questo, la mi domanda è molto semplice:
Dato che ho trovato su OSM sentieri mappati come CAI ma che in realtà 
sono ex-CAI, ho iniziato a correggere queste situazioni e per farlo ho 
visto cosa hanno fatto altri prima di me e ho copiato un po' le loro 
tecniche.
Volevo sapere se la tecnica che hanno usato altri prima di me è valida o 
se avete delle tecniche migliori.
La tecnica è molto semplice, usare il prefisso disused su 3 tag, come 
nell'esempio:

    disused:operator=Club Alpino Italiano
    disused:osmc:name=651
    disused:osmc:symbol=red:red:white_stripe:651:black
A me sembra valida, sia perché credo che descriva la realtà, sia perché 
le visualizzazioni appaiono corrette.


grazie a chi mi vorrà rispondere.
ciao


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

Re: [OSM-talk-fr] Simplification représentation "Cédez-le-passage cycliste au feu"

[osm . sanspourriel]

En deux mots : simple mais pas pris en compte par les outils. Devrait
donc passer par une proposition officielle notant cela.

Sauf que si tu mets ça sur un point, comment savoir de quelle route tu
parles si la voie piétonne est autorisée aux cycles.

De plus les cyclistes ne doivent la priorité que si le feu est rouge ou
orange.

Mais ce problème est le même qu'avec la relation.

Je doute que le cas des feux sur appel piéton soit la majorité des cas.
Sinon il faudra distinguer left/right/forward.

Jean-Yvon

Le 27/09/2020 à 19:02, Axel Listes - axe...@broman.fr a écrit :

Une proposition du type :

highway=traffic_signals
traffic_signals:direction=forward
highway:bicycle=give_way

Qu'en pensez-vous ?



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

Re: [OSM-talk-fr] tag bmo:type

[osm . sanspourriel]

Bonjour,

Comme indiqué distingue ls bâti léger du bâti en dur (donc a priori
différent du wall=no du cadastre).

J'ai failli supprimer certains mais justement ce n'est pas exactement
wall=no. Hier je suis tombé sur deux "trucs" légers qui n'étaient pas
des wall=no.

Je parle de la version Brest Métropole (old_name=Brest Métropole Océane
;-)).

Émilie Laffray se fera un plaisir d'éclairer notre lanterne puisqu'elle
fait partie de la dream team de l'époque :

https://wiki.openstreetmap.org/wiki/BMO


Jean-Yvon

Le 27/09/2020 à 21:02, Georges Dutreix via Talk-fr -
talk-fr@openstreetmap.org a écrit :


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

Re: [OSM-talk-fr] Choisir le bon name pour les trajets de bus

[lejun]

J'ai récemment mis à jour l'intégralité du réseau à Besançon
(https://wiki.openstreetmap.org/wiki/Besan%C3%A7on/Ginko) et ai été
confronté à la question. À ce sujet le wiki semble clair, le PTv2
(dernière proposition validée) préconise le format :
< vehicle type > < reference number >: < initial stop > => < terminal stop >
Dans ton exemple le résultat (en supposant que les deux arrêts sont dans
la même commune) devrait donc être :
Bus 12bis: Montredon Pôle d'Échange => Clos des Ormeaux

J'ai des réserves sur le format mais si c'est ce qui a été validé par la
communauté alors je l'applique en attendant d'avoir l'occasion de
m'exprimer à ce sujet. Je préférerais également le nom officiel donné
par la compagnie, actuellement les informations sont redondantes avec
les attributs "type", "ref", "from" et "to".

Le 27/09/2020 à 20:57, Gad Jo a écrit :

Avec le recul c'était une mauvaise idée rendant la lecture complexe sur
certains trajets.
J'attends quelques jours au cas où un avis contraire me le déconseille
mais je pense opter pour placer uniquement le depart et terminus sans le
nom des communes.

Le September 27, 2020 4:02:31 PM UTC, deuzeffe 
a écrit :

Le 27/09/2020 à 16:46, Gad Jo a écrit :

Bonjour a tous,


Bonjour,

Un point que j'ai mis de côté en me promettant de le régler est le
format pour le nom des trajets (1 ligne, plusieurs trajets)

Sur les trajets desservant des communes différentes j'ai ajouter
le nom
des communes + arrêt. Problème ça commence à être sacrement
illisible.

Auriez vous des propositions à me faire ? À moins que des règles

existent et j'applique... Je serait tenté de placer que le nom
de l'arrêt


J'ai peut-être été hétérodoxe, mais pour les lignes de bus de
l'intercommunalité voisine et celles du département, j'ai "bêtement"
repris les dénominations officielles du réseau, de terminus à terminus.
Bon, j'avoue, les données sont en LO, c'est plus facile :) Aucune idée
si ta collectivité a publié des données surhttps://transport.data.gouv.fr/

Ça donne un truc comme ça :

https://wiki.openstreetmap.org/wiki/Limoges/Transports_en_commun#R.C3.A9seau_STCLM
(WIP) ou ça :

https://wiki.openstreetmap.org/wiki/Haute-Vienne/Transports_en_commun#R.C3.A9seau_Moohv87
(WIP aussi)

Et pour les terminus hors grosse ville, parfois le réseau précise
l'arrêt parfois non. Donc, je fais pareil ;)


--
Lejun - Groupe Local OpenStreetMap Bourgogne-Franche-Comté

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

Re: [OSM-talk-fr] Web-SIG du Pays Terres de Lorraine

[osm . sanspourriel]

Le 27/09/2020 à 14:21, Romain MEHUT - romain.me...@mailo.com a écrit :

J'en viens donc à vous, auriez-vous connaissance de web-SIG grand
public où les données OSM seraient exploitées pour justement éviter
cet écueil ? Tony peut être avec la CCPRO ?


GéoBretagne avec ÇaResteOuvert par exemple :

https://cms.geobretagne.fr/content/commerces-de-premiere-necessite-ouverts


Avec les débits de boisson sur Marseille, CRO ferme.

En fait non, ne va-t-il pas falloir réactiver CRO ? :-(

Mais avant il faut sans doute nettoyer ce qui est encore présent.

Jean-Yvon



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

[OSM-talk-fr] tag bmo:type

[Georges Dutreix via Talk-fr]

Bonjour,

je viens de tomber sur ce tag bmo:type. A priori beaucoup de bâtiments 
dans le quartier ont ce bidule.
Comme ça date de 2009, je me demandais si un nettoyage en masse ne 
serait pas judicieux.
En fouillant un peu, je vois des références à un import Brest Métropole 
Océane (https://forum.openstreetmap.fr/viewtopic.php?t=5311).
Mais peut-être cette étiquette est-elle très utile ? Est-ce le cas 
encore en 2020 ?


https://www.openstreetmap.org/way/42521903/history


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

Re: [OSM-talk-fr] Choisir le bon name pour les trajets de bus

[Gad Jo]

Pour l'instant rien n'a été publié sur transport data gouv. 
Quand j'ai commencé à créé les trajets je pensai plutôt à mettre en avant la 
commune de départ et d'arrivée + nom des arrêts. Quand on ne sait pas quelle 
ligne prendre ça peut aider.

Avec le recul c'était une mauvaise idée rendant la lecture complexe sur 
certains trajets.
J'attends quelques jours au cas où un avis contraire me le déconseille mais je 
pense opter pour placer uniquement le depart et terminus sans le nom des 
communes.

Le September 27, 2020 4:02:31 PM UTC, deuzeffe  a 
écrit :
>Le 27/09/2020 à 16:46, Gad Jo a écrit :
>> Bonjour a tous,
>
>Bonjour,
>
>> Un point que j'ai mis de côté en me promettant de le régler est le 
>> format pour le nom des trajets (1 ligne, plusieurs trajets)
>> 
>> Sur les trajets desservant des communes différentes j'ai ajouter le
>nom 
>> des communes + arrêt. Problème ça commence à être sacrement
>illisible.
>> > Auriez vous des propositions à me faire ? À moins que des règles
>> existent et j'applique... Je serait tenté de placer que le nom de
>l'arrêt
>
>J'ai peut-être été hétérodoxe, mais pour les lignes de bus de 
>l'intercommunalité voisine et celles du département, j'ai "bêtement" 
>repris les dénominations officielles du réseau, de terminus à terminus.
>
>Bon, j'avoue, les données sont en LO, c'est plus facile :) Aucune idée 
>si ta collectivité a publié des données sur
>https://transport.data.gouv.fr/
>
>Ça donne un truc comme ça : 
>https://wiki.openstreetmap.org/wiki/Limoges/Transports_en_commun#R.C3.A9seau_STCLM
>
>(WIP) ou ça : 
>https://wiki.openstreetmap.org/wiki/Haute-Vienne/Transports_en_commun#R.C3.A9seau_Moohv87
>
>(WIP aussi)
>
>Et pour les terminus hors grosse ville, parfois le réseau précise 
>l'arrêt parfois non. Donc, je fais pareil ;)
>
>-- 
>deuzeffe
>
>
>___
>Talk-fr mailing list
>Talk-fr@openstreetmap.org
>https://lists.openstreetmap.org/listinfo/talk-fr

-- 
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [Talk-GB] Listed status / scheduled monument

[Jez Nicholson]

I believe that the Listed Buildings refs are fairly old. The whole thing
might warrant a revisit, and perhaps a Quarterly Project?

I would be happy for a new-style ref:GB:he (or similar) and an automated
edit. After discussion obviously.

On Sat, 26 Sep 2020, 20:57 Dave Dunford,  wrote:

> The most logical and consistent scheme would seem to me to be - contrary
> to Key:listed_status
>  and
> established consensus:
>
> <*heritage*_status=Scheduled Monument> (which would also work for
> , etc.)
>  (in line with other numeric referencing systems; my
> understanding is that HE don't use any other number systems, though you
> sometimes see their pre-NHLE numbers quoted, which could be tagged
> appropriately)
>
>  feels internally contradictory.
>  is inconsistent with other referencing schemes.
>
> But it's an awfully well-established consensus...
>
> Incidentally, some structures are both Listed Buildings and Scheduled
> Monuments (notably crosses and bridges, in my experience), or you get
> Listed Buildings (defined by HE as a single point) within scheduled
> monuments (defined by HE as an area). Yours is a case in point: the Priory
> building is a Grade I listed building (
> https://historicengland.org.uk/listing/the-list/list-entry/1062210) and
> the Priory Farmhouse is Grade II (
> https://historicengland.org.uk/listing/the-list/list-entry/1360390) and
> both are within the area defined as a scheduled monument.
>
> Third observation - whatever we do, we should t call them "Scheduled
> Monuments" as HE do, rather than the dated "Scheduled Ancient Monuments"
> (quite a lot of them - e.g. Victorian lead mines in my part of the world -
> aren't that ancient).
>
> Dave 
>
> On 26/09/2020 13:43, Edward Bainton wrote:
>
> Hi all
>
> I'd like to map St Leonard's Priory, Stamford, Lincs:
> https://historicengland.org.uk/listing/the-list/list-entry/1007690
>
> This is a 'scheduled monument'.
>
>1. The wiki is a bit inconsistent on *how to tag* this.
>   1. Key:listed_status
>   
>   suggests I should tag it .
>   2. The table at Key:HE_ref
>    would suggest that
>   may not be the right tag, as  is only given for listed
>   buildings - a different legal category.
>   3. I've found plenty of the former in the map, so I'm assuming
>   that's correct and the table at HE_ref needs amplifying
>
>   2. I've also got a puzzle about *how to give the ref. number*.
>   1. Key:listed_status
>    invites
>   me to use .
>   2. Key:heritage
>    invites
>   me to use 
>
>   I've tried using overpass-turbo to get relative frequencies of
>   those two tags. I get the following (for most but not all of England, so
>   ymmv: north of ~Barnard Castle not in my bounding box, but that wasn't a
>   political decision...).
>
>   I can't interpret it fully, but it looks like ref:he may be worth
>   deleting from the wiki as obsolete?
>
>   *HE_ref=**
>   Loaded – nodes: 46397, ways: 5541, relations: 124
>   Displayed – pois: 591, lines: 634, polygons: 4770
>
>   *ref:he=**
>   Loaded – nodes: 2274, ways: 176, relations: 1
>   Displayed – pois: 31, lines: 10, polygons: 166
>
> Thanks for any help.
>
> Edward / eteb3
>
> ___
> Talk-GB mailing 
> listTalk-GB@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/talk-gb
>
>
> ___
> Talk-GB mailing list
> Talk-GB@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-gb
>
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [Talk-GB] Hello world and automated change proposal: Add missing URL scheme on UK's Pubs websites

[Andrew Hain]

Keep Right flags web links that have gone offline.

--
Andrew

From: Philip Barnes 
Sent: 27 September 2020 18:49
To: talk-gb@openstreetmap.org 
Subject: Re: [Talk-GB] Hello world and automated change proposal: Add missing 
URL scheme on UK's Pubs websites

On Sun, 2020-09-27 at 16:28 +0100, Rodrigo Díez Villamuera wrote:
Hi all,

First of all, I would like to introduce myself on this email list and to thank 
you all for your contributions to OSM. Great work!

After some time using OSM as a user, I decided to make my first step as a 
contributor, hence this email and the proposal inside.

Please bear in mind that this is my first attempt to contribute with a proposal 
and, although I have done my best reading the community conventions and best 
practices, I am sure I have made some mistakes on the way. Be merciful! :P

To the point now.

I am importing a subset of nodes from UK (those tagged with amenity:pub) for a 
pet project.

When analysing the data I realised that some of these nodes contain a website: 
tag that does not contain an appropriate URL schema (http/https).

Ie: www.mypub.com rather than http://www.mypub.com or 
https://www.mypub.com

This goes in contradiction with the Wiki documentation for 
website.

I created a proposal for a one-off, scoped, automated edit for these nodes to 
find the appropiate scheme for the existing URL and retag the nodes.

I added the proposal to the Automated edits log. You can read it 
here.

Just wanted to share the proposal with the UK community, gather your feedback, 
comments and advises on how to proceed from here

One issue I can think of with pubs and websites is that they need checking to 
ensure they are still current.

The defacto method most pubs use to communicate with customers is facebook.

A more general fix of urls missing http(s)://, why only pubs?.  is probably a 
maproulette quest.

Phil (trigpoint)

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

Re: [Talk-GB] Hello world and automated change proposal: Add missing URL scheme on UK's Pubs websites

[Philip Barnes]

On Sun, 2020-09-27 at 16:28 +0100, Rodrigo Díez Villamuera wrote:
> Hi all,
> 
> First of all, I would like to introduce myself on this email list and
> to thank you all for your contributions to OSM. Great work!
> 
> After some time using OSM as a user, I decided to make my first step
> as a contributor, hence this email and the proposal inside.
> 
> Please bear in mind that this is my first attempt to contribute with
> a proposal and, although I have done my best reading the community
> conventions and best practices, I am sure I have made some mistakes
> on the way. Be merciful! :P
> 
> To the point now.
> 
> I am importing a subset of nodes from UK (those tagged with
> amenity:pub) for a pet project.
> 
> When analysing the data I realised that some of these nodes contain a
> website: tag that does not contain an appropriate URL schema
> (http/https).
> 
> Ie: www.mypub.com rather than http://www.mypub.com or 
> https://www.mypub.com
> 
> This goes in contradiction with the Wiki documentation for website.
> 
> I created a proposal for a one-off, scoped, automated edit for these
> nodes to find the appropiate scheme for the existing URL and retag
> the nodes.
> 
> I added the proposal to the Automated edits log. You can read it
> here.
> 
> Just wanted to share the proposal with the UK community, gather your
> feedback, comments and advises on how to proceed from here
> 
One issue I can think of with pubs and websites is that they need
checking to ensure they are still current. 

The defacto method most pubs use to communicate with customers is
facebook.

A more general fix of urls missing http(s)://, why only pubs?.  is
probably a maproulette quest.

Phil (trigpoint)


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

Re: [Talk-us] [Tagging] Large fire perimeter tagging?

[Clifford Snow]

On Sun, Sep 27, 2020 at 7:24 AM Clifford Snow 
wrote:

>
>
> On Sun, Sep 27, 2020 at 12:46 AM Mateusz Konieczny via Tagging <
> tagg...@openstreetmap.org> wrote:
>
>> landuse=forest is used to tag tree covered area, not for how land is used
>>
>
> I don't believe everyone around here will agree with that interpretation.
> I live in an area with significant logging. Typically I will see logging
> trucks bringing in just cut timber to be milled  when I'm out for just a
> short drive. Timber production is a big industry in Alaska, British
> Columbia, Washington, Oregon, and California.
>

I did a check of Washington and saw that there are a number of
landuse=forest that should be natural=trees. I suspect that it's also
happening elsewhere.

>
>> It is also basically universally interpreted this way by various data
>> consumers.
>>
>
> That may be for cartographic interpretation. But researchers may have a
> different opinion. A researcher just interested in potential wildfire areas
> may not be interested in the difference, but someone looking at how much
> land is being used for forestry products may have a different opinion. Or
> in mountainous states where clear cutting often causes landslides. I know
> our state studies where it's dangerous to clear cut because the area is so
> steep.
>
> The wiki on landuse=forest does need some help. We shouldn't be offering a
> tag with such unclear use cases as landuse=forest currently is written.
>

I'm not sure there would be a consensus agreement to revise the wiki to
indicate landuse=forest should be used for timber production.  Thoughts?

>
>
> --
@osm_washington
www.snowandsnow.us
OpenStreetMap: Maps with a human touch
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [OSM-talk-nl] Importing trees in Utrecht

[Sebastiaan Couwenberg]

On 9/27/20 6:44 PM, Pieter van Mill via Talk-nl wrote:
> If there are any comments I would love to hear them,

More mappers are active on the forum, you'll get more feedback there.

 https://forum.openstreetmap.org/viewforum.php?id=12

Since you only talk about importing, also think about how the data will
be updated.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

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

Re: [OSM-talk-fr] Fontaine...

[Jacques Lavignotte]

Le 27/09/2020 à 18:45, Water-Map a écrit :


amenity = fountain
drinking_water = no


Pile-poil !

https://www.openstreetmap.org/node/7946142457

Merci, J.

--
GnuPg : 156520BBC8F5B1E3 Because privacy matters.
« Quand est-ce qu'on mange ? » AD (c) (tm)

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

[OSM-talk-fr] Simplification représentation "Cédez-le-passage cycliste au feu"

[Axel Listes]

Bonjour,

Depuis plusieurs années je représente les cédez-le-passage créé via des
panonceaux sur les feux de circulation, destinées exclusivement aux
vélos, en créant des relations comme indiqué sur la page wiki dédié.
https://wiki.openstreetmap.org/wiki/FR:Bicycle#Panonceaux_de_C.C3.A9dez-le-passage_cycliste_au_feu

J'ai toujours trouvé cette façon de faire relativement lourde, mais les
contributions étant effectuées ponctuellement, je ne me suis jamais
vraiment posé la question de trouver des alternatives.

Localement, la métropole dans laquelle je contribue principalement a
fait poser ce type de panneau en masse sur le territoire (des
centaines), juste avant le premier tour des élections municipale.
Aujourd’hui, l'idée est de les insérer progressivement dans la base,
mais j'aimerais éventuellement utiliser une variante plus simple pour
certains cas qui peuvent se passer de relation.

Imaginez, parfois vous avez des feux qui ne font que réguler un passage
piétons, d'autres fois les possibilités au carrefour d’emprunter des
directions sont déjà intégralement recouvert par les directions
affichées sur les panonceaux.

Cet exemple qui représente un aller tout droit, qui est de toutes façons
la seule direction possible pour les cyclistes :
https://www.mapillary.com/map/im/eAaLPasL2dPva8sKAwjP8w

Une proposition du type :

highway=traffic_signals
traffic_signals:direction=forward
highway:bicycle=give_way

Qu'en pensez-vous ?

-- 

"Un peuple prêt à sacrifier un peu de liberté pour un peu de sécurité ne
mérite ni l'une ni l'autre, et finit par perdre les deux."
Citation de Benjamin Franklin.

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

Re: [OSM-talk-fr] Fontaine...

[Water-Map]

Salut,

Nous sommes des simples utilisateurs des données ..

Je tagguerais personnellement la fontaine dans la photo comme déjà proposée
et j'ajouterais la photo au wiki :)

amenity = fountain
drinking_water = no

Voici le wiki en anglais ..

https://wiki.openstreetmap.org/wiki/Tag:amenity%3Dfountain
Et une fontaine qui n'est pas si différente de la tienne ..
https://wiki.openstreetmap.org/wiki/File:Trento-fountain_in_vicolo_beato_Stefano_Bellesini.jpg



On Sun, 27 Sep 2020 at 18:16, deuzeffe  wrote:

> Le 27/09/2020 à 18:03, Jacques Lavignotte a écrit :
>
> Hello,
>
> > Le 27/09/2020 à 17:47, ades a écrit :
> >> Ah bon ?
> >
> >>  pour
> >> une fontaine (potable ou non)."
> >
> > mais rien qui ressemble à ma fontaine :
> >
> > https://i.postimg.cc/CxTLyS41/IMG-20200926-184649.jpg
> >
> > Donc pas de fountain=*
>
> Bah, si tu ne la trouves pas là :
> https://wiki.openstreetmap.org/wiki/Key:fountain ça va être compliqué de
> lui attribuer un sous-type.
>
> Faut demander aux spécialistes de https://water-map.org/ ;)
>
> --
> deuzeffe
>
> ___
> 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-nl] Importing trees in Utrecht

[Pieter van Mill via Talk-nl]

Hello everyone,

I would like to start a project to import trees in the city of Utrecht, The 
Netherlands. 

The wiki page of this project can be found here: 
https://wiki.openstreetmap.org/wiki/Utrecht_tree_import

Before I do more work on this project I would like to see if this is a good 
project to do. The data that could be imported can be found on this map: 
https://gemu.maps.arcgis.com/apps/webappviewer/index.html?id=53c67672c1fa46e5bef555a611b58301

The license for the dataset is CC-0 which makes it compatible with the ODbL 
license.

If there are any comments I would love to hear them,

Pieter (pcmill)

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

Re: [OSM-talk-fr] Fontaine...

[deuzeffe]

Le 27/09/2020 à 18:03, Jacques Lavignotte a écrit :

Hello,


Le 27/09/2020 à 17:47, ades a écrit :

Ah bon ?


 pour 
une fontaine (potable ou non)."


mais rien qui ressemble à ma fontaine :

https://i.postimg.cc/CxTLyS41/IMG-20200926-184649.jpg

Donc pas de fountain=*


Bah, si tu ne la trouves pas là : 
https://wiki.openstreetmap.org/wiki/Key:fountain ça va être compliqué de 
lui attribuer un sous-type.


Faut demander aux spécialistes de https://water-map.org/ ;)

--
deuzeffe

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

Re: [OSM-talk-fr] Fontaine...

[JB]

amenity = fountain + drinking_water = no / conditional (eau non 
surveillée, parfois indiquée « non potable »)


Le 27/09/2020 à 15:47, Jacques Lavignotte a écrit :

Bonjour,

https://i.postimg.cc/CxTLyS41/IMG-20200926-184649.jpg

ne semble pas être une amenity=fountain selon le Saint Wiki..

Mais c'est quoi donc que ça se tagge ?

J.





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

Re: [OSM-talk-fr] Fontaine...

[Jacques Lavignotte]

Le 27/09/2020 à 17:47, ades a écrit :

Ah bon ?


 pour une 
fontaine (potable ou non)."


mais rien qui ressemble à ma fontaine :

https://i.postimg.cc/CxTLyS41/IMG-20200926-184649.jpg

Donc pas de fountain=*

J.

--
GnuPg : 156520BBC8F5B1E3 Because privacy matters.
« Quand est-ce qu'on mange ? » AD (c) (tm)

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

Re: [OSM-talk-fr] Choisir le bon name pour les trajets de bus

[deuzeffe]

Le 27/09/2020 à 16:46, Gad Jo a écrit :

Bonjour a tous,


Bonjour,

Un point que j'ai mis de côté en me promettant de le régler est le 
format pour le nom des trajets (1 ligne, plusieurs trajets)


Sur les trajets desservant des communes différentes j'ai ajouter le nom 
des communes + arrêt. Problème ça commence à être sacrement illisible.

> Auriez vous des propositions à me faire ? À moins que des règles
existent et j'applique... Je serait tenté de placer que le nom de l'arrêt


J'ai peut-être été hétérodoxe, mais pour les lignes de bus de 
l'intercommunalité voisine et celles du département, j'ai "bêtement" 
repris les dénominations officielles du réseau, de terminus à terminus. 
Bon, j'avoue, les données sont en LO, c'est plus facile :) Aucune idée 
si ta collectivité a publié des données sur https://transport.data.gouv.fr/


Ça donne un truc comme ça : 
https://wiki.openstreetmap.org/wiki/Limoges/Transports_en_commun#R.C3.A9seau_STCLM 
(WIP) ou ça : 
https://wiki.openstreetmap.org/wiki/Haute-Vienne/Transports_en_commun#R.C3.A9seau_Moohv87 
(WIP aussi)


Et pour les terminus hors grosse ville, parfois le réseau précise 
l'arrêt parfois non. Donc, je fais pareil ;)


--
deuzeffe


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

Re: [OSM-talk-fr] Fontaine...

[ades]

Ah bon ? 
"amenity =fountain 
 pour une 
fontaine (potable ou non)."
maintenant pour fontaine : 
l’académie Fçaise : " Construction qui permet l’écoulement d’une source, la 
distribution des eaux, et sert souvent d’ornement »
cf ici aussi : 
http://stella.atilf.fr/Dendien/scripts/tlfiv5/visusel.exe?13;s=1086321930;r=1;nat=;sol=2;
et littré : "Édifice public qui verse l’eau »



> Le 27 sept. 2020 à 15:47, Jacques Lavignotte  a écrit 
> :
> 
> Bonjour,
> 
> https://i.postimg.cc/CxTLyS41/IMG-20200926-184649.jpg
> 
> ne semble pas être une amenity=fountain selon le Saint Wiki..
> 
> Mais c'est quoi donc que ça se tagge ?
> 
> J.
> -- 
> GnuPg : 156520BBC8F5B1E3 Because privacy matters.
> « Quand est-ce qu'on mange ? » AD (c) (tm)
> 
> ___
> 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-GB] Hello world and automated change proposal: Add missing URL scheme on UK's Pubs websites

[Rodrigo Díez Villamuera]

Hi all,

First of all, I would like to introduce myself on this email list and to
thank you all for your contributions to OSM. Great work!

After some time using OSM as a user, I decided to make my first step as a
contributor, hence this email and the proposal inside.

Please bear in mind that this is my first attempt to contribute with a
proposal and, although I have done my best reading the community
conventions and best practices, I am sure I have made some mistakes on the
way. Be merciful! :P

To the point now.

I am importing a subset of nodes from UK (those tagged with amenity:pub)
for a pet project.

When analysing the data I realised that some of these nodes contain a
website: tag that does not contain an appropriate URL schema (http/https).

Ie: www.mypub.com rather than http://www.mypub.com or https://www.mypub.com

This goes in contradiction with the Wiki documentation for website.


I created a proposal for a one-off, scoped, automated edit for these nodes
to find the appropiate scheme for the existing URL and retag the nodes.

I added the proposal to the Automated edits log. You can read it here

.

Just wanted to share the proposal with the UK community, gather your
feedback, comments and advises on how to proceed from here

Thanks in advance!








--
Rodrigo Díez Villamuera

w: http://rodrigodiez.io
t: @rodrigodiez_pro
p: 00 44 7513 638225
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

[OSM-talk-fr] Choisir le bon name pour les trajets de bus

[Gad Jo]

Bonjour a tous,


J'avance à grand pas vers la fin d'un vieux projet commencé en 2012 : 
cartographier les lignes de bus sur Narbonne

Un point que j'ai mis de côté en me promettant de le régler est le format pour 
le nom des trajets (1 ligne, plusieurs trajets)

Sur les trajets desservant des communes différentes j'ai ajouter le nom des 
communes + arrêt. Problème ça commence à être sacrement illisible.

Exemple extrême (y aura pas pire que ça) : Bus 12 bis : Montredon-des-Corbières 
- Montredon Pôle d’échanges → Montredon-des-Corbières - Clos des Ormeaux 
(Désolé le copier-coller sur l'application ajoute le format)
Relation concernée : https://www.openstreetmap.org/relation/11674315

Plus d'exemple sur la page de suivi :
https://wiki.openstreetmap.org/w/index.php?title=Narbonne/Transports_en_commun#Lignes_P.C3.A9riurbaines

Auriez vous des propositions à me faire ? À moins que des règles existent et 
j'applique... Je serait tenté de placer que le nom de l'arrêt

Ps : si vous avez des suggestions sur le contenu de la page de suivi je suis 
preneur. Je compte la communiquer à l'Agglo
-- 
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [Talk-us] Large fire perimeter tagging?

[Mateusz Konieczny via Talk-us]

I am a bit dubious about value of updating fire=perimeter

It is something that changes extremely quickly, we should
not encourage people to survey perimeter of ACTIVE fire,
OSM is doomed to be strictly worse source of fire perimeter
than alternative sources

> fire has absolutely enormous impact to what we do and might map here,
both present and future.  The aftermath of this fire (>85,000 acres this fire 
alone)
will last for decades, and for OSM to not reflect this in the map

Obviously, we should (try to) update map where situation changed.

Delete building that will not be rebuild (mark them as destroyed:building=*
until aerial imagery will update)
[deleting buildings and remapping them as they get reconstructed may
be viable in cases of heavy mapper presence]

Delete other permanently destroyed objects and so on.

> Do we have landcover tags which could replace landuse=forest
or natural=wood with something like natural=fire_scarred?

AFAIK nothing established, see
https://lists.openstreetmap.org/pipermail/tagging/2018-March/035435.html
for related discussion about wind damage.

Sep 24, 2020, 23:30 by stevea...@softworkers.com:

> I didn't get a single reply on this (see below), which I find surprising, 
> especially as there are currently even larger fires that are more widespread 
> all across the Western United States.
>
> I now ask if there are additional, appropriate polygons with tags I'm not 
> familiar with regarding landcover that might be added to the map (as 
> "landuse=forest" might be strictly true now only in a 'zoning' sense, as many 
> of the actual trees that MAKE these forests have sadly burned down, or 
> substantially so).
>
> Considering that there are literally millions and millions of acres of 
> (newly) burned areas (forest, scrub, grassland, residential, commercial, 
> industrial, public, private...), I'm surprised that OSM doesn't have some 
> well-pondered and actual tags that reflect this situation.  My initial 
> tagging of this (simply tagged, but enormous) polygon as "fire=perimeter" was 
> coined on my part, but as I search wiki, taginfo and Overpass Turbo queries 
> for similar data in the map, I come up empty.
>
> First, do others think it is important that we map these?  I say yes, as this 
> fire has absolutely enormous impact to what we do and might map here, both 
> present and future.  The aftermath of this fire (>85,000 acres this fire 
> alone) will last for decades, and for OSM to not reflect this in the map 
> (somehow, better bolstered than a simple, though huge, polygon tagged with 
> fire=perimeter, start_date and end_date) seems OSM "cartographically misses 
> something."  I know that HOT mappers map the "present- and aftermath-" of 
> humanitarian disasters, I've HOT-participated myself.  So, considering the 
> thousands of structures that burned (most of them homes), tens of thousands 
> of acres which are burn-scarred and distinctly different than their 
> landcover, millions of trees (yes, really) and even landuse is now currently 
> tagged, I look for guidance — beyond the simple tag of fire=perimeter on a 
> large polygon.
>
> Second, if we do choose to "better" map these incidents and results (they are 
> life- and planet-altering on a grand scale) how might we choose to do that?  
> Do we have landcover tags which could replace landuse=forest or natural=wood 
> with something like natural=fire_scarred?  (I'm making that up, but it or 
> something like it could work).  How and when might we replace these with 
> something less severe?  On the other hand, if it isn't appropriate that we 
> map any of this, please say so.
>
> Thank you, especially any guidance offered from HOT contributors who have 
> worked on post-fire humanitarian disasters,
>
> SteveA
> California (who has returned home after evacuation, relatively safe now that 
> this fire is 100% contained)
>
>
> On Aug 29, 2020, at 7:20 PM, stevea  wrote:
>
>> Not sure if crossposting to talk-us is correct, but it is a "home list" for 
>> me.
>>
>> I've created a large fire perimeter in OSM from public sources, 
>> http://www.osm.org/way/842280873 .  This is a huge fire (sadly, there are 
>> larger ones right now, too), over 130 square miles, and caused the 
>> evacuation of every third person in my county (yes).  There are hundreds, 
>> perhaps thousands of structures, mostly residential homes, which have burned 
>> down and the event has "completely changed" giant redwoods in and the 
>> character of California's oldest state park (Big Basin).
>>
>> This perimeter significantly affects landuse, landcover and human patterns 
>> of movement and activity in this part of the world for a significant time to 
>> come.  It is a "major disaster."  I'm curious how HOT teams might delineate 
>> such a thing (and I've participated in a HOT fire team, mapping barns, water 
>> sources for helicopter dips and other human structures during a large fire 
>> near me), I've simply made a polygon tagged 

Re: [Talk-us] [Tagging] Large fire perimeter tagging?

[Mateusz Konieczny via Talk-us]

landuse=forest is used to tag tree covered area, not for how land is used

It is also basically universally interpreted this way by various data consumers.

Sep 25, 2020, 00:05 by cliff...@snowandsnow.us:

> Steve,
> Just a reminder, landuse is to tag what the land is used for. landuse=forest 
> is for areas that have harvestable wood products, ie trees. Just because 
> there was a fire doesn't mean the landuse changes. Landcover is a better tag 
> for burnt areas as well as areas just clearcut. 
>
>
>
> On Thu, Sep 24, 2020 at 2:31 PM stevea <> stevea...@softworkers.com> > wrote:
>
>> I didn't get a single reply on this (see below), which I find surprising, 
>> especially as there are currently even larger fires that are more widespread 
>> all across the Western United States.
>>  
>>  I now ask if there are additional, appropriate polygons with tags I'm not 
>> familiar with regarding landcover that might be added to the map (as 
>> "landuse=forest" might be strictly true now only in a 'zoning' sense, as 
>> many of the actual trees that MAKE these forests have sadly burned down, or 
>> substantially so).
>>  
>>  Considering that there are literally millions and millions of acres of 
>> (newly) burned areas (forest, scrub, grassland, residential, commercial, 
>> industrial, public, private...), I'm surprised that OSM doesn't have some 
>> well-pondered and actual tags that reflect this situation.  My initial 
>> tagging of this (simply tagged, but enormous) polygon as "fire=perimeter" 
>> was coined on my part, but as I search wiki, taginfo and Overpass Turbo 
>> queries for similar data in the map, I come up empty.
>>  
>>  First, do others think it is important that we map these?  I say yes, as 
>> this fire has absolutely enormous impact to what we do and might map here, 
>> both present and future.  The aftermath of this fire (>85,000 acres this 
>> fire alone) will last for decades, and for OSM to not reflect this in the 
>> map (somehow, better bolstered than a simple, though huge, polygon tagged 
>> with fire=perimeter, start_date and end_date) seems OSM "cartographically 
>> misses something."  I know that HOT mappers map the "present- and 
>> aftermath-" of humanitarian disasters, I've HOT-participated myself.  So, 
>> considering the thousands of structures that burned (most of them homes), 
>> tens of thousands of acres which are burn-scarred and distinctly different 
>> than their landcover, millions of trees (yes, really) and even landuse is 
>> now currently tagged, I look for guidance — beyond the simple tag of 
>> fire=perimeter on a large polygon.
>>  
>>  Second, if we do choose to "better" map these incidents and results (they 
>> are life- and planet-altering on a grand scale) how might we choose to do 
>> that?  Do we have landcover tags which could replace landuse=forest or 
>> natural=wood with something like natural=fire_scarred?  (I'm making that up, 
>> but it or something like it could work).  How and when might we replace 
>> these with something less severe?  On the other hand, if it isn't 
>> appropriate that we map any of this, please say so.
>>  
>>  Thank you, especially any guidance offered from HOT contributors who have 
>> worked on post-fire humanitarian disasters,
>>  
>>  SteveA
>>  California (who has returned home after evacuation, relatively safe now 
>> that this fire is 100% contained)
>>  
>>  
>>  On Aug 29, 2020, at 7:20 PM, stevea <>> stevea...@softworkers.com>> > wrote:
>>  > Not sure if crossposting to talk-us is correct, but it is a "home list" 
>> for me.
>>  > 
>>  > I've created a large fire perimeter in OSM from public sources, >> 
>> http://www.osm.org/way/842280873>>  .  This is a huge fire (sadly, there are 
>> larger ones right now, too), over 130 square miles, and caused the 
>> evacuation of every third person in my county (yes).  There are hundreds, 
>> perhaps thousands of structures, mostly residential homes, which have burned 
>> down and the event has "completely changed" giant redwoods in and the 
>> character of California's oldest state park (Big Basin).
>>  > 
>>  > This perimeter significantly affects landuse, landcover and human 
>> patterns of movement and activity in this part of the world for a 
>> significant time to come.  It is a "major disaster."  I'm curious how HOT 
>> teams might delineate such a thing (and I've participated in a HOT fire 
>> team, mapping barns, water sources for helicopter dips and other human 
>> structures during a large fire near me), I've simply made a polygon tagged 
>> fire=perimeter, a name=* tag and a start_date.  I don't expect rendering, 
>> it's meant to be an "up to right about here" (inside the polygon is/was a 
>> burning fire, outside was no fire).  I wouldn't say it is more accurate than 
>> 20 to 50 meters on any edge, an "across a wide street" distance to be "off" 
>> is OK with me, considering this fire's size, but if a slight skew jiggles 
>> the whole thing into place better, feel 

Re: [Talk-us] [Tagging] Large fire perimeter tagging?

[Clifford Snow]

On Sun, Sep 27, 2020 at 12:46 AM Mateusz Konieczny via Tagging <
tagg...@openstreetmap.org> wrote:

> landuse=forest is used to tag tree covered area, not for how land is used
>

I don't believe everyone around here will agree with that interpretation.
I live in an area with significant logging. Typically I will see logging
trucks bringing in just cut timber to be milled  when I'm out for just a
short drive. Timber production is a big industry in Alaska, British
Columbia, Washington, Oregon, and California.

>
> It is also basically universally interpreted this way by various data
> consumers.
>

That may be for cartographic interpretation. But researchers may have a
different opinion. A researcher just interested in potential wildfire areas
may not be interested in the difference, but someone looking at how much
land is being used for forestry products may have a different opinion. Or
in mountainous states where clear cutting often causes landslides. I know
our state studies where it's dangerous to clear cut because the area is so
steep.

The wiki on landuse=forest does need some help. We shouldn't be offering a
tag with such unclear use cases as landuse=forest currently is written.

Best,
Clifford


-- 
@osm_washington
www.snowandsnow.us
OpenStreetMap: Maps with a human touch
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

[Talk-us] weeklyOSM #531 2020-09-15-2020-09-21

[weeklyteam]

The weekly round-up of OSM news, issue # 531,
is now available online in English, giving as always a summary of a lot of 
things happening in the openstreetmap world:

 https://www.weeklyosm.eu/en/archives/13784/

Enjoy! 

Did you know that you can also submit messages for the weeklyOSM? Just log in 
to https://osmbc.openstreetmap.de/login with your OSM account. Read more about 
how to write a post here: 
http://www.weeklyosm.eu/this-news-should-be-in-weeklyosm 

weeklyOSM? 
who: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

[OSM-talk-fr] Serveur Discord créé

[Emilie Laffray]

 Bonjour tout le monde,

juste un petit passage pour signaler que quelqu'un a créé un serveur
discord pour la communauté OpenStreetMap Fr.
L'utilisateur s'appelle Khryashch#1881.
Voila le lien https://discord.gg/wxNGfdT

Pour ceux qui ne connaissent pas Discord, c'est une sorte de IRC moderne
avec persistance des discussions et la possibilité de faire du vocal/vidéo
facilement.
C'est surtout utilisé à la base pour faciliter les communaute de gamers et
ca touche a des gens un peu plus jeune généralement pour qui IRC est un
truc un peu abscon :)

Voila voila,
Emilie Laffray
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

[OSM-talk-fr] Fontaine...

[Jacques Lavignotte]

Bonjour,

https://i.postimg.cc/CxTLyS41/IMG-20200926-184649.jpg

ne semble pas être une amenity=fountain selon le Saint Wiki..

Mais c'est quoi donc que ça se tagge ?

J.
--
GnuPg : 156520BBC8F5B1E3 Because privacy matters.
« Quand est-ce qu'on mange ? » AD (c) (tm)

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

Re: [Talk-gb-london] Question about London's habit of mapping

[Philip Barnes]

On Wed, 2020-09-23 at 10:15 +0100, Corentin Furet wrote:
> Hello everybody,
> 
> 
> I am new in London (and in the UK in general) and I started mapping
> around me. I have some questions about local habit of mapping.
> 
Welcome to the UK.

This list is very quiet, your messgaes will be seen by far more UK
mappers on the UK wide talk-gb list.

https://lists.openstreetmap.org/listinfo/talk-gb

Cheers 
Phil (trigpoint)




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

Re: [OSM-talk-fr] Web-SIG du Pays Terres de Lorraine

[Romain MEHUT]

Oui je sais très bien mais rien n'empêche chaque territoire d'avoir son 
propre web-SIG d'où ma question.


Je ferai remonter aussi le manque d'attribution.

Romain

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

Bonjour,

C'est ce que fait la démo qui est ici
http://demo.openstreetmap.fr/

Au passage le web Sig utilise les tuiles OSM de GeoGrandEst sans 
attribution.


Frédéric.


Le 27/09/2020 à 11:40, Romain MEHUT a écrit :

Bonjour,

Il y a un peu plus d'une semaine, j'étais en rendez-vous avec le 
président (politique) et le directeur du Pays Terres de Lorraine 
http://www.terresdelorraine.org/fr/la-gouvernance.html.


Ce rendez-vous plusieurs fois reportés faisait suite à mes 
sollicitations d'accès aux données du territoire en particulier pour 
faire le lien avec "Ça reste ouvert". J'ai donc pu expliquer le 
fonctionnement d'OpenStreetMap et ses atouts pour la constitution 
d'un bien commun numérique... Le message que j'ai souhaité faire 
passer était donc que la collectivité exploite les données OSM.


Depuis le "Pays" a mis en ligne un web-SIG grand public 
https://cartographie.terresdelorraine.org/portail C'est déjà un pas 
avant que la collectivité publie ces informations mais en l'état on 
ne peut les télécharger et elles sont pour certains items pas à jour 
ou incomplètes à l'inverse d'OSM.


J'en viens donc à vous, auriez-vous connaissance de web-SIG grand 
public où les données OSM seraient exploitées pour justement éviter 
cet écueil ? Tony peut être avec la CCPRO ?


Merci par avance.

Romain




___
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-gb-london] Question about London's habit of mapping

[Philip Barnes]

On Wed, 2020-09-23 at 22:02 +0100, Inan Hira via Talk-gb-london wrote:
> 
> Along with an in person survey, borough websites/maps could be a good
> reference. Also check Royal Mail's postcode finder [3] to see if
> you're
> missing any building numbers or names.
> 
> [3]: https://www.royalmail.com/find-a-postcode
> 
Please don't do that, the Royal Mail postcode checker is copyright and
we do not have permission to use it.

Phil (trigpoint)


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

[Talk-ca] hebdoOSM Nº 531 2020-09-15-2020-09-21

[theweekly . osm]

Bonjour,

Le résumé hebdomadaire n° 531 de l'actualité OpenStreetMap vient de paraître 
*en français*. Un condensé à retrouver sur :

https://www.weeklyosm.eu/fr/archives/13784/

Bonne lecture !

Saviez-vous que vous pouvez vous aussi soumettre des messages pour la note 
hebdomadaire sans être membre ? Il vous suffit de vous connecter sur 
https://osmbc.openstreetmap.de/login avec votre compte OSM. Pour en savoir plus 
sur la rédaction d'un article, cliquez ici: 
http://www.weeklyosm.eu/fr/this-news-should-be-in-weeklyosm

hebdoOSM ? 
Qui : https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Où : 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca

Re: [Talk-ht] hebdoOSM Nº 531 2020-09-15-2020-09-21

[John Trilik]

Unsubscribe

Get Outlook for iOS

From: theweekly@gmail.com 
Sent: Sunday, September 27, 2020 6:04:18 AM
To: talk-ht@openstreetmap.org 
Subject: [Talk-ht] hebdoOSM Nº 531 2020-09-15-2020-09-21

Bonjour,

Le résumé hebdomadaire n° 531 de l'actualité OpenStreetMap vient de paraître 
*en français*. Un condensé à retrouver sur :

https://www.weeklyosm.eu/fr/archives/13784/

Bonne lecture !

Saviez-vous que vous pouvez vous aussi soumettre des messages pour la note 
hebdomadaire sans être membre ? Il vous suffit de vous connecter sur 
https://osmbc.openstreetmap.de/login avec votre compte OSM. Pour en savoir plus 
sur la rédaction d'un article, cliquez ici: 
http://www.weeklyosm.eu/fr/this-news-should-be-in-weeklyosm

hebdoOSM ?
Qui : https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages
Où : 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-ht mailing list
Talk-ht@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ht
Notez! Vous pouvez utiliser Google Translate (http://translate.google.com) pour 
traduire les messages.
___
Talk-ht mailing list
Talk-ht@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ht
Notez! Vous pouvez utiliser Google Translate (http://translate.google.com) pour 
traduire les messages.

[OSM-talk-fr] hebdoOSM Nº 531 2020-09-15-2020-09-21

[theweekly . osm]

Bonjour,

Le résumé hebdomadaire n° 531 de l'actualité OpenStreetMap vient de paraître 
*en français*. Un condensé à retrouver sur :

https://www.weeklyosm.eu/fr/archives/13784/

Bonne lecture !

Saviez-vous que vous pouvez vous aussi soumettre des messages pour la note 
hebdomadaire sans être membre ? Il vous suffit de vous connecter sur 
https://osmbc.openstreetmap.de/login avec votre compte OSM. Pour en savoir plus 
sur la rédaction d'un article, cliquez ici: 
http://www.weeklyosm.eu/fr/this-news-should-be-in-weeklyosm

hebdoOSM ? 
Qui : https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Où : 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

[Talk-de] weeklyOSM #531 2020-09-15-2020-09-21

[weeklyteam]

Die Wochennotiz Ausgabe Nr. # 531, ist nun verfügbar - 
wie immer mit vielen Nachrichten aus dem OSM-Universium:

https://www.weeklyosm.eu/de/archives/13784/

Viel Spaß beim Lesen.  

Euer Wochennotizteam

Wusstet ihr, dass ihr auch selbst Meldungen für die Wochennotiz
einreichen könnt? Einfach auf https://osmbc.openstreetmap.de/ 
mit eurem OSM-Benutzerkonto anmelden und dann den Gastzugang benutzen. 

weeklyOSM? 
who: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de

[Talk-ht] hebdoOSM Nº 531 2020-09-15-2020-09-21

[theweekly . osm]

Bonjour,

Le résumé hebdomadaire n° 531 de l'actualité OpenStreetMap vient de paraître 
*en français*. Un condensé à retrouver sur :

https://www.weeklyosm.eu/fr/archives/13784/

Bonne lecture !

Saviez-vous que vous pouvez vous aussi soumettre des messages pour la note 
hebdomadaire sans être membre ? Il vous suffit de vous connecter sur 
https://osmbc.openstreetmap.de/login avec votre compte OSM. Pour en savoir plus 
sur la rédaction d'un article, cliquez ici: 
http://www.weeklyosm.eu/fr/this-news-should-be-in-weeklyosm

hebdoOSM ? 
Qui : https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Où : 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-ht mailing list
Talk-ht@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ht
Notez! Vous pouvez utiliser Google Translate (http://translate.google.com) pour 
traduire les messages.

[Talk-it] weeklyOSM #531 2020-09-15-2020-09-21

[weeklyteam]

Il settimanale di notizie su OSM, numero # 531, è ora disponibile online in 
italiano, 
fornendo come sempre un riassunto di molte cose che accadono nel mondo 
OpenStreetMap: 

https://www.weeklyosm.eu/it/archives/13784/

Buona lettura! 

Sai che possono anche inviare messaggi per il weeklyOSM? Basta effettuare il 
login 
su https://osmbc.openstreetmap.de/login con il tuo account OSM. 

Per saperne di più su come scrivere un messaggio, leggi qui: 
http://www.weeklyosm.eu/this-news-should-be-in-weeklyosm 
weeklyOSM? 

chi: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
dove?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

[Talk-africa] hebdoOSM Nº 531 2020-09-15-2020-09-21

[theweekly . osm]

Bonjour,

Le résumé hebdomadaire n° 531 de l'actualité OpenStreetMap vient de paraître 
*en français*. Un condensé à retrouver sur :

https://www.weeklyosm.eu/fr/archives/13784/

Bonne lecture !

Saviez-vous que vous pouvez vous aussi soumettre des messages pour la note 
hebdomadaire sans être membre ? Il vous suffit de vous connecter sur 
https://osmbc.openstreetmap.de/login avec votre compte OSM. Pour en savoir plus 
sur la rédaction d'un article, cliquez ici: 
http://www.weeklyosm.eu/fr/this-news-should-be-in-weeklyosm

hebdoOSM ? 
Qui : https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Où : 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-africa mailing list
Talk-africa@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-africa

[Talk-br] semanárioOSM Nº 531 2020-09-15-2020-09-21

[theweekly . osm]

Bom dia,

O semanárioOSM Nº 531, o resumo de tudo o que acontece no mundo OpenStreetMap, 
está publicado *em português* : 

https://www.weeklyosm.eu/pb/archives/13784/

Aproveite!

Você sabia que também pode enviar mensagens para o OSM semanal/semanárioOSMſ 
sem ser membro? Basta fazer login em https://osmbc.openstreetmap.de/login com 
sua conta OSM e usar a conta de convidado. Leia mais sobre como escrever um 
post aqui: http://www.weeklyosm.eu/this-news-should-be-in-weeklyosm

semanarioOSM? 
Quem?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Onde?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-br mailing list
Talk-br@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-br

[Talk-pt] semanárioOSM Nº 531 2020-09-15-2020-09-21

[theweekly . osm]

Bom dia,

O semanárioOSM Nº 531, o resumo de tudo o que acontece no mundo OpenStreetMap, 
está publicado *em português* : 

https://www.weeklyosm.eu/pb/archives/13784/

Aproveite!

Você sabia que também pode enviar mensagens para o OSM semanal/semanárioOSMſ 
sem ser membro? Basta fazer login em https://osmbc.openstreetmap.de/login com 
sua conta OSM e usar a conta de convidado. Leia mais sobre como escrever um 
post aqui: http://www.weeklyosm.eu/this-news-should-be-in-weeklyosm

semanarioOSM? 
Quem?: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
Onde?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-pt mailing list
Talk-pt@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-pt

[Talk-cl] semanarioOSM Nº 531 2020-09-15-2020-09-21

[theweekly . osm]

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

https://www.weeklyosm.eu/es/archives/13784/

¡Disfruta!

¿Sabías que también puedes enviar mensajes para la nota semanal sin ser 
miembro? Simplemente ingresa a https://osmbc.openstreetmap.de/login con tu 
cuenta de OSM. Lee más sobre cómo escribir una publicación aquí: 
http://www.weeklyosm.eu/es/this-news-should-be-in-weeklyosm 

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

[Talk-es] semanarioOSM Nº 531 2020-09-15-2020-09-21

[theweekly . osm]

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

https://www.weeklyosm.eu/es/archives/13784/

¡Disfruta!

¿Sabías que también puedes enviar mensajes para la nota semanal sin ser 
miembro? Simplemente ingresa a https://osmbc.openstreetmap.de/login con tu 
cuenta de OSM. Lee más sobre cómo escribir una publicación aquí: 
http://www.weeklyosm.eu/es/this-news-should-be-in-weeklyosm 

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

[Talk-cu] semanarioOSM Nº 531 2020-09-15-2020-09-21

[theweekly . osm]

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

https://www.weeklyosm.eu/es/archives/13784/

¡Disfruta!

¿Sabías que también puedes enviar mensajes para la nota semanal sin ser 
miembro? Simplemente ingresa a https://osmbc.openstreetmap.de/login con tu 
cuenta de OSM. Lee más sobre cómo escribir una publicación aquí: 
http://www.weeklyosm.eu/es/this-news-should-be-in-weeklyosm 

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

[OSM-co] semanarioOSM Nº 531 2020-09-15-2020-09-21

[theweekly . osm]

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

https://www.weeklyosm.eu/es/archives/13784/

¡Disfruta!

¿Sabías que también puedes enviar mensajes para la nota semanal sin ser 
miembro? Simplemente ingresa a https://osmbc.openstreetmap.de/login con tu 
cuenta de OSM. Lee más sobre cómo escribir una publicación aquí: 
http://www.weeklyosm.eu/es/this-news-should-be-in-weeklyosm 

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-co mailing list
Talk-co@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-co

[Talk-ca] weeklyOSM #531 2020-09-15-2020-09-21

[weeklyteam]

The weekly round-up of OSM news, issue # 531,
is now available online in English, giving as always a summary of a lot of 
things happening in the openstreetmap world:

 https://www.weeklyosm.eu/en/archives/13784/

Enjoy! 

Did you know that you can also submit messages for the weeklyOSM? Just log in 
to https://osmbc.openstreetmap.de/login with your OSM account. Read more about 
how to write a post here: 
http://www.weeklyosm.eu/this-news-should-be-in-weeklyosm 

weeklyOSM? 
who: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca

[Talk-GB] weeklyOSM #531 2020-09-15-2020-09-21

[weeklyteam]

The weekly round-up of OSM news, issue # 531,
is now available online in English, giving as always a summary of a lot of 
things happening in the openstreetmap world:

 https://www.weeklyosm.eu/en/archives/13784/

Enjoy! 

Did you know that you can also submit messages for the weeklyOSM? Just log in 
to https://osmbc.openstreetmap.de/login with your OSM account. Read more about 
how to write a post here: 
http://www.weeklyosm.eu/this-news-should-be-in-weeklyosm 

weeklyOSM? 
who: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

[OSM-talk] weeklyOSM #531 2020-09-15-2020-09-21

[weeklyteam]

The weekly round-up of OSM news, issue # 531,
is now available online in English, giving as always a summary of a lot of 
things happening in the openstreetmap world:

 https://www.weeklyosm.eu/en/archives/13784/

Enjoy! 

Did you know that you can also submit messages for the weeklyOSM? Just log in 
to https://osmbc.openstreetmap.de/login with your OSM account. Read more about 
how to write a post here: 
http://www.weeklyosm.eu/this-news-should-be-in-weeklyosm 

weeklyOSM? 
who: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

[OSM-talk-ie] weeklyOSM #531 2020-09-15-2020-09-21

[weeklyteam]

The weekly round-up of OSM news, issue # 531,
is now available online in English, giving as always a summary of a lot of 
things happening in the openstreetmap world:

 https://www.weeklyosm.eu/en/archives/13784/

Enjoy! 

Did you know that you can also submit messages for the weeklyOSM? Just log in 
to https://osmbc.openstreetmap.de/login with your OSM account. Read more about 
how to write a post here: 
http://www.weeklyosm.eu/this-news-should-be-in-weeklyosm 

weeklyOSM? 
who: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-ie mailing list
Talk-ie@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ie

[talk-ph] weeklyOSM #531 2020-09-15-2020-09-21

[weeklyteam]

The weekly round-up of OSM news, issue # 531,
is now available online in English, giving as always a summary of a lot of 
things happening in the openstreetmap world:

 https://www.weeklyosm.eu/en/archives/13784/

Enjoy! 

Did you know that you can also submit messages for the weeklyOSM? Just log in 
to https://osmbc.openstreetmap.de/login with your OSM account. Read more about 
how to write a post here: 
http://www.weeklyosm.eu/this-news-should-be-in-weeklyosm 

weeklyOSM? 
who: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
talk-ph mailing list
talk-ph@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ph

[Talk-bo] semanarioOSM Nº 531 2020-09-15-2020-09-21

[theweekly . osm]

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

https://www.weeklyosm.eu/es/archives/13784/

¡Disfruta!

¿Sabías que también puedes enviar mensajes para la nota semanal sin ser 
miembro? Simplemente ingresa a https://osmbc.openstreetmap.de/login con tu 
cuenta de OSM. Lee más sobre cómo escribir una publicación aquí: 
http://www.weeklyosm.eu/es/this-news-should-be-in-weeklyosm 

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-bo mailing list
Talk-bo@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-bo

[Talk-africa] weeklyOSM #531 2020-09-15-2020-09-21

[weeklyteam]

The weekly round-up of OSM news, issue # 531,
is now available online in English, giving as always a summary of a lot of 
things happening in the openstreetmap world:

 https://www.weeklyosm.eu/en/archives/13784/

Enjoy! 

Did you know that you can also submit messages for the weeklyOSM? Just log in 
to https://osmbc.openstreetmap.de/login with your OSM account. Read more about 
how to write a post here: 
http://www.weeklyosm.eu/this-news-should-be-in-weeklyosm 

weeklyOSM? 
who: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages 
where?: 
https://umap.openstreetmap.fr/en/map/weeklyosm-is-currently-produced-in_56718#2/8.6/108.3
___
Talk-africa mailing list
Talk-africa@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-africa

Re: [OSM-talk-fr] Web-SIG du Pays Terres de Lorraine

[Frédéric Rodrigo]

Bonjour,

C'est ce que fait la démo qui est ici
http://demo.openstreetmap.fr/

Au passage le web Sig utilise les tuiles OSM de GeoGrandEst sans 
attribution.


Frédéric.


Le 27/09/2020 à 11:40, Romain MEHUT a écrit :

Bonjour,

Il y a un peu plus d'une semaine, j'étais en rendez-vous avec le 
président (politique) et le directeur du Pays Terres de Lorraine 
http://www.terresdelorraine.org/fr/la-gouvernance.html.


Ce rendez-vous plusieurs fois reportés faisait suite à mes 
sollicitations d'accès aux données du territoire en particulier pour 
faire le lien avec "Ça reste ouvert". J'ai donc pu expliquer le 
fonctionnement d'OpenStreetMap et ses atouts pour la constitution d'un 
bien commun numérique... Le message que j'ai souhaité faire passer 
était donc que la collectivité exploite les données OSM.


Depuis le "Pays" a mis en ligne un web-SIG grand public 
https://cartographie.terresdelorraine.org/portail C'est déjà un pas 
avant que la collectivité publie ces informations mais en l'état on ne 
peut les télécharger et elles sont pour certains items pas à jour ou 
incomplètes à l'inverse d'OSM.


J'en viens donc à vous, auriez-vous connaissance de web-SIG grand 
public où les données OSM seraient exploitées pour justement éviter 
cet écueil ? Tony peut être avec la CCPRO ?


Merci par avance.

Romain




___
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] Web-SIG du Pays Terres de Lorraine

[Romain MEHUT]

Bonjour,

Il y a un peu plus d'une semaine, j'étais en rendez-vous avec le 
président (politique) et le directeur du Pays Terres de Lorraine 
http://www.terresdelorraine.org/fr/la-gouvernance.html.


Ce rendez-vous plusieurs fois reportés faisait suite à mes 
sollicitations d'accès aux données du territoire en particulier pour 
faire le lien avec "Ça reste ouvert". J'ai donc pu expliquer le 
fonctionnement d'OpenStreetMap et ses atouts pour la constitution d'un 
bien commun numérique... Le message que j'ai souhaité faire passer était 
donc que la collectivité exploite les données OSM.


Depuis le "Pays" a mis en ligne un web-SIG grand public 
https://cartographie.terresdelorraine.org/portail C'est déjà un pas 
avant que la collectivité publie ces informations mais en l'état on ne 
peut les télécharger et elles sont pour certains items pas à jour ou 
incomplètes à l'inverse d'OSM.


J'en viens donc à vous, auriez-vous connaissance de web-SIG grand public 
où les données OSM seraient exploitées pour justement éviter cet écueil 
? Tony peut être avec la CCPRO ?


Merci par avance.

Romain




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

Re: [OSM-talk-fr] Colloque IGN, 5-9 octobre

[Yves P.]

> Je me permets de signaler 2 conférences dont certains mots clés (collaboratif 
> pour la première et OpenStreetMap pour la deuxième) m'ont fait envoyer ce 
> courriel :
> 
Le thème de l'Intelligence artificiel devrait intéresser aussi quelques 
personnes :

Retour d’expériences INRIA sur l’IA. Guillaume CHARPIAT, chargé de recherche 
INRIA Saclay.
Retour d’expérience de la recherche IGN sur l’IA au service de l’information 
géographique. Frank FUCHS, Délégué scientifique et technique de l’IGN. 
Olivier JAMET, Délégué scientifique et technique adjoint de l’IGN.
L’apprentissage profond au service de la télédétection. Camille PARISEL, 
chef de département d’appui à l’innovation IGN.

__
Yves


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

[OSM-talk-fr] Osmose - Demande d'aide pour les écoles en France

[Frédéric Rodrigo]

Bonjour,

La liste des signalements de dysfonctionnement d'Osmose à propos des 
écoles en France ne fait que s'allonger. Mais personne ne traite le sujet.


https://github.com/osm-fr/osmose-backend/issues

Le sujet de l'éducation intéresse ici du monde. Si quelqu’un veut bien 
regarder ça. Il faut faire le point sur les issues dans github et les 
analyses Osmose. Puis proposer les corrections qui vont bien dans les 
analyses Osmose (modification du code ou au moins signaler quoi changer où).


Merci.

Frédéric.



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

[OSM-talk-fr] Colloque IGN, 5-9 octobre

[Vincent Bergeot]

Bonjour,

Je me permets de signaler 2 conférences dont certains mots clés 
(collaboratif pour la première et OpenStreetMap pour la deuxième) m'ont 
fait envoyer ce courriel :


 * Projet LandSense : quel potentiel du collaboratif pour la mise à
   jour de l’OCS-Grande Échelles ? le 7 octobre 11-12h
 * Évaluation de la qualité de données d’OpenStreetMap à partir
   d’indicateurs intrinsèques. le 9 octobre 11h-12h

Tout le programme ici : 
http://chatconference.com/files/ign-jr2020/data/livret-jrign2020.pdf


Inscription libre et gratuite si j'ai tout suivi : 
http://recherche.ign.fr/jr/jr20.php


Bonne journée

--

Vincent Bergeot

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

[Talk-it] R: Cambio licenza mappe catastali

[canfe]

Confermo con orrore.
Non volevo crederci ma anche questa strada provinciale non è accatastata.
https://www.openstreetmap.org/way/680286866 

-Messaggio originale-
Da: Federico Cortese [mailto:cortese...@gmail.com] 
Inviato: sabato 26 settembre 2020 16:30
A: openstreetmap list - italiano
Oggetto: Re: [Talk-it] Cambio licenza mappe catastali

On Sat, Sep 26, 2020 at 3:42 PM Martin Koppenhoefer
 wrote:
>
> lo scopo non � quello di poter registrare la suddivisione ed i proprietari 
> dei terreni? Mi sembra strano che nemmeno le geometrie delle particelle sono 
> affidabili.
> Al meno la versione online mi sembra di non riportare tutte le suddivisioni 
> con sufficiente dettaglio per poter registrare i proprietari (parlo proprio 
> dei vicini miei, dove conosco bene la situazione)

Per quanto riguarda le suddivisioni delle particelle, quelle sono
indicative nel senso che la mappa non ha valore metrico ma solo
descrittivo.
Dal punto di vista metrico quello che fa fede sono gli atti di
frazionamento presentati dalle parti.
Se non vedi le suddivisioni sulla mappa pu� essere che si tratta di
particelle urbane e che le pertinenze scoperte siano divise
nell'elaborato planimetrico urbano.
A parte questi dettagli non � per nulla strano che una scuola che
esiste da decenni non sia accatastata o che una strada statale a
quattro corsie costruita 60 anni fa non sia ancora frazionata.

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-london] Question about London's habit of mapping

[Inan Hira via Talk-gb-london]

Hi

> Ok, I wasn't clear. I wanted to say I noticed that very often buildings
> have the tags "addr:housenumber=*" and "add:street=*" to indicate their
> address. And with the continuation of your message it seems to be what
> you are doing.

Everything's clear now. I hoped various examples would give some ideas.

> The point I wanted to highlight is that very often the 22 Royal Road (it
> will be my example for this message) designates the entrance which lead
> to the flats at and above the level of the road, and 22A Royal Road the
> entrance of the flat in the basement. And I barely never see the
> basement flat's address indicated in OSM. Therefore I was wondering if I
> missed something. (such as a local convention of not mapping the house
> number of the basement if it is the same as the house above it + "A".
> Indeed when we attribute the tags "addr:housenumber=22" and
> "add:street=Royal Road" to a building, and not using the way with an
> additional node with the tag "addr:housenumber=22" and a relation:street
> (https://wiki.openstreetmap.org/wiki/Relation:street) it is not possible
> to have 2 different house numbers for the same building, so I could have
> been possible that basement's numbering have been drop for simplicity.)

I don't think we can tag a building with two different
`addr:housenumber` tags apart from setting the value of this as a range
or mix of ranges and other values (22-24 or 22;22A). I'm sure there
isn't a convention to omit the basements or other numbers. So I'd guess
that's a case of lack of information. But in the UK instance of taginfo,
I can see that `addr:flats` is used in combination with `entrance`,
`addr:street` and `addr:housenumber`[0].

[0]:
https://taginfo.openstreetmap.org.uk/keys/?key=addr%3Aflats#combinations

> As you said in your message there is the possibility to add two
> "entrance" nodes, one for the basement and one for the other part of the
> building.
> However I like to keep this option for building where the two entrances
> are spatially separated. In this case the basement's door and the "main
> entrance"'s door are nearly on top of each other. With no other
> indication that the doors are not on the same level it could be
> confusing to understand the map I think.
> And mapping building with the tags "addr:housenumber=22" and
> "add:street=Royal Road", and in addition an other node with
> "entrance=yes" and "addr:housenumber=22A" for the basement seems strange
> for me.

Have you seen the recommendations under Entrances and addresses section
of the `key=entrance` [1] wiki page? They recommend a similar
combination. If the doors are on top of each other in vertical
alignment, I guess we can just move one slightly to next to the other.

[1]:
https://wiki.openstreetmap.org/wiki/Key:entrance#Entrances_and_addresses

> Where do you find borough's plan and records? I looked for the
> Kensington and Chelsea one without success.
> Are they uploaded with an OSM-compatible licensing?

Borough websites have plans, maps etc. Kensington and Chelsea lists
bunch of plans but they are not detailed. Perhaps it could be useful to
confirm some other notes that you take about land use, amenities etc.
Most of the time they don't have free licences as they are usually using
Ordnance Survey data. I just compare them with my notes to detect
discrepancies, OS data can have some significant errors anyway. Postcode
checker is useful to see if I am missing building numbers as not every
number plate is clearly visible.

Best regards,
Inan

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