Re: [OSM-talk-fr] 118 valeur de surface=* en français à traduire :)

[Eric SIBERT]

A Madagascar, il y a les ponts où il n'y a que des madriers dans le sens 
de la longueur. Vélo ou moto, tu ne passes pas mais, avec un peu de 
chance, il y a un gué à côté.


Il y a aussi les ponts il faut amener soit-même ses madriers...

https://wiki.openstreetmap.org/wiki/FR:Highway_Tag_Africa#Travers%C3%A9e_de_rivi%C3%A8re

Eric


Le 04/04/2023 à 00:02, Marc_marc a écrit :


- la voie contient des revêtements différent dans sa largeur.
je pense surtout à concrete:lanes
pour le moment il n'y a pas de moyen de renseigner proprement
le revêtement entre les bandes oü roulent les pneus gauches
et droites des véhicules à 4 roues. c'est un manque pour
les vélos cargos où le vélo roule fatalement au milieu.
j'ai vu des asphalt-grass-asphalt qui représente probablement
la même chose.

si du monde est motivé, nous pourrions déjà diminuer
les 2 premiers cas puisqu'ils sont résoluble

Cordialement,
Marc



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



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

Re: [OSM-talk-fr] 118 valeur de surface=* en français à traduire :)

[Marc_marc]

Le 04.04.23 à 00:02, Marc_marc a écrit :

- la voie contient des revêtements différent dans sa largeur.
je pense surtout à concrete:lanes
pour le moment il n'y a pas de moyen de renseigner proprement
le revêtement entre les bandes oü roulent les pneus gauches
et droites des véhicules à 4 roues. c'est un manque pour
les vélos cargos où le vélo roule fatalement au milieu.
j'ai vu des asphalt-grass-asphalt qui représente probablement
la même chose.


en cherchannt dans tagino, je viens de trouver surface:middle
https://wiki.openstreetmap.org/wiki/Key%3Asurface%3Amiddle

les 3 cas "connus" sont résoluble :)



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

Re: [OSM-talk-fr] 118 valeur de surface=* en français à traduire :)

[Marc_marc]

Bonsoir,

Le 03.04.23 à 21:06, George Kaplan a écrit :

on devrait éviter les valeurs multiples.
pour qui une valeur multiple serait utile ?


je vois 3 cas pour lequel cela arrive :

- le voie change de surface -> il faut améliorer/éviter les valeurs 
multiples en découpant le chemin à chaque changement de surface,

du moins si ces changements concernent une "certaine" distance

- la voie comportent plusieurs matériaux mélangés -> c'est souvent
un mauvais choix de valeur. exemple gravel;sand -> cela pourrait
être compacted (ou autre choix possible, c'est un exemple)

- la voie contient des revêtements différent dans sa largeur.
je pense surtout à concrete:lanes
pour le moment il n'y a pas de moyen de renseigner proprement
le revêtement entre les bandes oü roulent les pneus gauches
et droites des véhicules à 4 roues. c'est un manque pour
les vélos cargos où le vélo roule fatalement au milieu.
j'ai vu des asphalt-grass-asphalt qui représente probablement
la même chose.

si du monde est motivé, nous pourrions déjà diminuer
les 2 premiers cas puisqu'ils sont résoluble

Cordialement,
Marc



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

Re: [OSM-talk-fr] 118 valeur de surface=* en français à traduire :)

[George Kaplan]

Merci Marc_marc,

J’ai vu dans la liste des propositions des valeurs cibles multiples comme par 
ex "ground;asphalt ». AMHA, on devrait éviter les valeurs multiples.

Les moteurs d’itinéraires utilisent cette donnée. Ils doivent donc analyser les 
différentes valeurs et en choisir la pire pour attribuer le coût du segment de 
route. Si un moteur ne sait pas gérer les valeurs multiples, il va probablement 
appliquer une valeur par défaut. Au final, il vaut mieux en tant que 
contributeur d’affecter une valeur unique à cette clé, quitte à découper plus 
finement le way en question.
Même remarque pour les quelques rendus qui dessinent le way différemment 
suivant la valeur de cette clé.

A part ces 2 exemples, vous connaissez d’autres consommateurs de cette clé ? Et 
pour qui une valeur multiple serait utile ?

George


> Le 3 avr. 2023 à 14:32, Marc_marc  a écrit :
> 
> Bonjour,
> 
> Le 28.03.23 à 23:57, Marc_marc a écrit :
>> j'ai finis par faire une liste de 118 valeurs en français
>> https://mensuel.framapad.org/p/osm-surface-a-traduire
> 
> Merci à tous ceux qui y ont participé
> j'ai transmis à Mateusz
> Je referrai une 2ieme passe quand son bot
> sera passé corriger tout cela
> 
> Cordialement,
> Marc
> 
> 
> 
> ___
> 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] JOSM version stable 18700 traduction du Journal des modification

[leni]

JOSM vient de passer à la version stable 18700

Voici la traduction en français du Journal des modifications 
https://josm.openstreetmap.de/wiki/Fr%3AChangelog?version=164#a2023-04-03:VersionStable1870023.03(le 
lien vers l’original anglais est en haut à droite du Journal des 
modifications)


cordialement

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

[Talk-bd] AMA Session on OSMBD Membership Drive Campaign 2023

[Sawan Shariar]

Great News!
OSM Bangladesh Membership Working Group is hosting a session on
AskMeAnything (AMA) on OSMBD MEMBERSHIP DRIVE CAMPAIGN 2023 in
collaboration with YouthMappers Bangladesh Community on April 06, 2023 at
3PM (Bangladesh Time). If you have any queries regarding that, please ask
us in the session. To attend the session and get the session platform link,
please join ou telegram channel at https://t.me/+YB1mYu2bmzUwZWNl

Please prepare your list and see you soon.

Thanks
#OSMBD #MembershipWG




দারুণ খবর!
আগামী ৬ এপ্রিল বিকাল ৩ টায় ওএসএম বাংলাদেশ মেম্বারশিপ ওয়ার্কিং গ্রুপ, ইয়ুথ
ম্যাপারস বাংলাদেশ কমিটির সহযোগিতায় "AskMeAnything (AMA) on OSMBD Membership
Drive Campaign 2023" শিরোনামে একটি সেশনের আয়োজন করতে যাচ্ছে। যদি আপনাদের এই
বিষয়ের উপর কোনো প্রশ্ন থাকে দয়া করে অনুষ্ঠানে উত্থাপন করতে অনুরোধ করা
যাচ্ছে।
অনুষ্ঠানে অংশ নেওয়ার জন্য আমাদের টেলিগ্রাম গ্রুপে যোগ দিতে অনুরোধ করছি।
টেলিগ্রাম চ্যানেল লিংক- https://t.me/+YB1mYu2bmzUwZWNl

খুব দ্রুত দেখা হচ্ছে, তাত সময় আপনাদের প্রশ্নসমুহ তৈরী করুন।

ধন্যবাদ
ওএসএম বাংলাদেশ মেম্বারশিপ ওয়ার্কিং গ্রুপ
___
Talk-bd mailing list
Talk-bd@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-bd

[Talk-it-lazio] Incontro dei mappatori romani e laziali - 26 aprile 2023

[Flaminia Tumino]

Ciao a tutt*,
con le temperature miti ricominciamo a mappare in giro!
Malgrado Monti sia abbastanza mappato, all'ultimo mapping party abbiamo
trovato che ci sono tanti cambiamenti che non sono stati riportati su
openStreetMap, quindi continuiamo in quella zona.
Appuntamento come al solito ai piedi della fontana in piazzetta alle 19.30
Qui sotto il link dell'evento:

https://osmcal.org/event/2019/

 A presto,
Flaminia
___
Talk-it-lazio mailing list
Talk-it-lazio@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it-lazio

Re: [OSM-talk] edits made by National Trust staff

[Volker Schmidt]

An interesting discussion, which I think is not specific or limited to the
NT in the UK. The correct handling of proposed, planned, or
under-condtruction features is for example something that I have
encountered with cycle routes in Italy. So please keep on this list.


On Mon, 3 Apr 2023, 13:17 ,  wrote:

> Send talk mailing list submissions to
> talk@openstreetmap.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.openstreetmap.org/listinfo/talk
> or, via email, send a message with subject or body 'help' to
> talk-requ...@openstreetmap.org
>
> You can reach the person managing the list at
> talk-ow...@openstreetmap.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of talk digest..."
>
>
> Today's Topics:
>
>1. Re: edits made by National Trust staff (was: Talk-GB Digest,
>   Vol 197, Issue 27) (Marc_marc)
>
>
> --
>
> Message: 1
> Date: Mon, 3 Apr 2023 11:43:34 +0200
> From: Marc_marc 
> To: talk@openstreetmap.org
> Subject: Re: [OSM-talk] edits made by National Trust staff (was:
> Talk-GB Digest, Vol 197, Issue 27)
> Message-ID: 
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Hello,
>
> Le 27.03.23 ? 14:51, Ragone, Olivia via talk a ?crit?:
> > We tend to use a standard changeset comment as it would be very
> > difficult to capture details of every change
>
> the comment is not to actually describe what you did but why. e.g.
> "added a path that was just created" will avoid the contributor
> wondering why they can't see it on the satellite view
>
> I invite you to continue the conversation with the local community
> by subscribing to talk-gb
> https://lists.openstreetmap.org/listinfo/talk-gb
> and then replace the recipient of your email
> with talk...@openstreetmap.org
>
> Regards,
> Marc
>
>
>
>
>
> --
>
> Subject: Digest Footer
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
> --
>
> End of talk Digest, Vol 224, Issue 5
> 
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk-fr] 118 valeur de surface=* en français à traduire :)

[Marc_marc]

Bonjour,

Le 28.03.23 à 23:57, Marc_marc a écrit :

j'ai finis par faire une liste de 118 valeurs en français
https://mensuel.framapad.org/p/osm-surface-a-traduire


Merci à tous ceux qui y ont participé
j'ai transmis à Mateusz
Je referrai une 2ieme passe quand son bot
sera passé corriger tout cela

Cordialement,
Marc



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

Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)

[Marc_marc]

Le 29.03.23 à 14:21, Mateusz Konieczny via talk a écrit :


Mar 29, 2023, 00:15 by marc_m...@mailo.com:

Le 28.03.23 à 19:38, Mateusz Konieczny via talk a écrit :

If someone speaking French would prepare pairs from-to they
confirmed to be basically 100% reliable pairs

I'll translate the list, it's not that the issue


here is the list (thanks for the crow work via talk-fr)

it might be more resilient to new cases to treat multiple
values separately, case insensitive, and
to replace "_et_" " et ""/" with ";"

value_in_french corrected_value
terre earth
herbe grass
cailloux gravel
gazon_ras short_grass
goudron asphalt
sable sand
bitume asphalt
terre_battue clay for tennis pitch, earth for others
pierre gravel
bois wood
macadam asphalt
sable_et_terre earth;sand
gazon_tres_ras grass
sol earth
pavés paving_stones or sett
pelouse grass
Terre earth
resine acrylic
gravier gravel
gazon grass
charbon coal
béton_poreux concrete + smoothness=good
béton_bitumineux asphalt
béton concrete
terre_et_sable earth;sand
synthétique artificial_turf (for leisure=pitch)
synthetique artificial_turf (for leisure=pitch)
herbe_synthétique artificial_turf (for leisure=pitch)
gazon_synthétique artificial_turf
parquet wood
multiple multi
herb grass
ciment concrete
calcaire rock
cailloux_et_galets pebblestone
terre_goudron ground;asphalt
terre_et_herbe earth;grass
terre,_cailloux ground;gravel
plastique plastic
pierres gravel
Herbe_et_cailloux grass;gravel
graviers gravel
gravier0 gravel
carrelage tiles
brique paving_stones
boue mud
bitumen asphalt
béton_désactivé concrete
banc_de_sable sand
terr_et_pierre ground;gravel
terre_touvenant ground
terre/sable ground;sand
terre_roche rock
terre_pierres ground;gravel
terre_naturelle,_argileuse ground
terre_humide mud
terre;herbe ground
terre_goudrons ground;asphalt
terre_et_rochers ground;rock
terre_et_pierres ground;gravel
terre_et_pierre ground;gravel
terre_et_gravier ground;gravel
terre_cailloux ground;gravel
terre_boue mud
terre,_boue mud
terre_batue clay
terre2 ground
terrain_synthétique tartan
terrain_en_herbe grass
tere ground
Sable sand
rocheux/felsig rock
rochers rock
rocher rock
polyuréthane acrylic
plastique plastic
planches wood
pierres_sèches rock
pierre_et_terre ground;gravel
pelouse_naturelle grass
pelouse_et_terre grass;ground
neige snow
Mousse moss
métal metal
liège cork
herbe_naturel grass
herbe_et_sable grass;sand
gravillons,_béton concrete;gravel
gravillons gravel
gravillon gravel
graviers_et_terre ground;gravel
gourdon asphalt
goudronné asphalt
enrobes asphalt
enrobé asphalt
empierrée pebblestone
diverses multi
compact1ée compacted
chemin_galet pebblestone
chemin_en_terre ground
chemin_de_terre_et_herbe ground
chemin_de_terre_et_graviers ground;gravel
chemin_de_terre ground
"champs,_herbe" grass
caoutchouc rubber
cailloux_et_terre ground;gravel
bois_et_goudron/plastique asphalt;plastic;wood
blocs_de_roche rock
béton_bois concrete;wood
béton_bitumimeux asphalt



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

Re: [OSM-talk] Proposed automatic replacements of multiple surface values - the third edition (review welcomed!)

[Mateusz Konieczny via talk]

I am not planning to propose automatically migrating ones where situation 
remains unclear.


Mar 27, 2023, 13:21 by dieterdre...@gmail.com:

>
>
> Am Mo., 27. März 2023 um 10:32 Uhr schrieb David Haberthür <> 
> em...@davidhaberthuer.ch> >:
>
>>
>> Ciao
>>
>>
>>> I added
>>>     # translating German
>>>     'holz': 'wood',
>>>     'schotter': 'gravel',
>>>     'Gras_Laub': 'grass',
>>> to candidate list for the next one
>>>
>>
>> I’m my (Swiss German) opinion "Schotter" is much bigger than gravel, which 
>> is translated to "Kies".
>> Gravel might be passable by bike, Schotter is the foundation under railways 
>> tracks.
>> I wouldn’t want to ride my bike over Schotter!
>>
>
>
> there was a discussion recently about several of these terms, including 
> pebbles and gravel. 
> The term "Kies" usually means rounded, natural pebbles as can be found in 
> rivers, while there is also "gebrochener Kies" which means crushed stone. 
> "Schotter" also means crushed stone. You correctly point out that the largest 
> grain size is very relevant for usability, you can't cycle on 63mm Schotter, 
> but you can on 16mm (still not desirable, but a huge difference to 63mm). 
> There are various terms, and they are sometimes colloquially used with a 
> different meaning than the definition used by specialists, and they may be 
> imprecise without adding the grain sizes, so there will probably never be an 
> unambiguous translation in a single word.
>

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

Re: [OSM-talk] edits made by National Trust staff (was: Talk-GB Digest, Vol 197, Issue 27)

[Marc_marc]

Hello,

Le 27.03.23 à 14:51, Ragone, Olivia via talk a écrit :
We tend to use a standard changeset comment as it would be very 
difficult to capture details of every change


the comment is not to actually describe what you did but why. e.g. 
"added a path that was just created" will avoid the contributor 
wondering why they can't see it on the satellite view


I invite you to continue the conversation with the local community
by subscribing to talk-gb
https://lists.openstreetmap.org/listinfo/talk-gb
and then replace the recipient of your email
with talk...@openstreetmap.org

Regards,
Marc



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

Re: [OSM-talk] Talk-GB Digest, Vol 197, Issue 27

[Dave F via talk]

Could admin transfer this to Talk-GB please.

DaveF

On 27/03/2023 13:51, Ragone, Olivia via talk wrote:


Thank you for providing feedback on some of the edits made by National 
Trust staff as part of our organised editing activity, on the 
representation of paths. We’d like to apologise that it has taken some 
time to provide a response.  We are always open to constructive 
feedback that helps us to add value to OSM for the benefit of all.


The aim of the National Trust’s organised editing activity is to 
capture and accurately tag the access rights of all paths on or near 
National Trust managed land. In doing so, we hope to use it as the 
basis for enhancing access and the management of paths, to improve 
visitor experience.


We are trying to be consistent in how ways are tagged / represented in 
OpenStreetMap. A standard schema and internally developed guidance are 
being utilised to help map commonly occurring scenarios. This schema 
can be found on the OSM Wiki page (link). We currently have 5 staff 
members conducting remote mapping sessions with local rangers to gain 
their on-the-ground insight. We believe that working with the 
on-the-ground staff provides our best available source of local 
knowledge, but we acknowledge there may be situations where there are 
differing opinions on path representation. The Trust invite feedback 
from OSM mappers, but it may take some time to review each situation.


In the time available, we are focusing on the existence of the path 
(ie. location and connectivity) and the legal right (ie. access tags). 
In the future, we hope to look at other attributes to represent the 
characteristics of the path. Following the initial data capture, we 
plan to hand over OSM updates to the ranger teams; we are currently 
refining the guidance material to support this. Feedback from the OSM 
community to help ensure we are providing appropriate guidance is 
welcome.


We tend to use a standard changeset comment as it would be very 
difficult to capture details of every change. However, since receiving 
feedback on the Talk-GB mailing list, we have amended our standard 
comment to be more representative of the type of changes that have 
been made on individual properties. As part of the process, we have a 
monitoring tool that looks at the weekly changes to paths in OSM on 
land managed by the National Trust. This could be made publicly 
available as an Esri Open Data WMS if it would provide further 
transparency. We accept in the time that we have, occasional errors 
will be made. After our first round of data capture, we have allocated 
time to analyse and assure the quality of changes by our team.


Overall, we expect that the changes will improve the representation of 
paths on OSM, but we are very keen to improve our process by utilising 
the wealth of knowledge and experience in the OSM community.


National Trust Paths & Trails Team.



*GIS Data Officer (Paths) *

*National Trust*

*Email:*olivia.rag...@nationaltrust.org.uk 



nationaltrust.org.uk 



-- The National Trust is a registered charity no. 205846. Our 
registered office is Heelis, Kemble Drive, Swindon, Wiltshire SN2 2NA. 
The views expressed in this email are personal and may not necessarily 
reflect those of the National Trust unless explicitly stated 
otherwise. This email and any files transmitted with it are 
confidential and intended solely for the use of the individual or 
entity to whom they are addressed. If you have received this email in 
error, please notify me immediately. If you are not the intended 
recipient of this email, you should not copy it for any purpose, or 
disclose its contents to any other person. Senders and recipients of 
email should be aware that, under the Data Protection Act 2018, the 
contents may have to be disclosed. The National Trust has scanned this 
email for security issues. However the National Trust cannot accept 
liability for any form of malware that may be in this email and we 
recommend that you check all emails with an appropriate security tool.


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