date:20200303

Re: [Talk-it] [Talk-it-cai] Tags per percorsi MTB ufficiali con standard CAI (su Georesq)

2020-03-03 Thread solitone

Personalmente per gradare le singole way ho sempre usato i tag mtb:scale=*, 
mtb:scale:uphill=* e incline=*, che sono i più diffusi e utilizzano il sistema 
singletrail-skala.de. La scala CAI non è del tutto equivalente a 
singletrail-skala.de e potrebbe avere senso aggiungere ulteriori tag per questa.

Mi allaccio a questa discussione per segnalare che c’è un ulteriore tag molto 
importante per la pratica della MTB: surface=*. Purtroppo non sempre vedo dei 
valori veramente convincenti per differenziare in maniera precisa i diversi 
tipi di superficie che si trovano sui sentieri in montagna. Due esempi che non 
so come etichettare sono le pietre mobili (arrotondate o spigolose) e la roccia 
fissa (placconate).

Attualmente su taginfo vedo alcuni valori che sembrano simili, in ordine di 
popolarità: stone, rock, rocky, rocks, stones. Che differenze ci saranno? Anni 
fa avevo posto una domanda su help, ma non ne avevo cavato 
molto:https://help.openstreetmap.org/questions/10175/keysurface-stones-boulders-and-rocky-surface


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

[Talk-us] Whole-US Garmin Map update - 2020-03-01

2020-03-03 Thread Dave Hansen

These are based off of Lambertus's work here:

http://garmin.openstreetmap.nl

If you have questions or comments about these maps, please feel
free to ask.  However, please do not send me private mail.  The
odds are, someone else will have the same questions, and by
asking on the talk-us@ list, others can benefit.

Downloads:

http://daveh.dev.openstreetmap.org/garmin/Lambertus/2020-03-01

Map to visualize what each file contains:


http://daveh.dev.openstreetmap.org/garmin/Lambertus/2020-03-01/kml/kml.html


FAQ



Why did you do this?

I wrote scripts to joined them myself to lessen the impact
of doing a large join on Lambertus's server.  I've also
cut them in large longitude swaths that should fit conveniently
on removable media.  

http://daveh.dev.openstreetmap.org/garmin/Lambertus/2020-03-01

Can or should I seed the torrents?

Yes!!  If you use the .torrent files, please seed.  That web
server is in the UK, and it helps to have some peers on this
side of the Atlantic.

Why is my map missing small rectangular areas?

There have been some missing tiles from Lambertus's map (the
red rectangles),  I don't see any at the moment, so you may
want to update if you had issues with the last set.

Why can I not copy the large files to my new SD card?

If you buy a new card (especially SDHC), some are FAT16 from
the factory.  I had to reformat it to let me create a >2GB
file.

Does your map cover Mexico/Canada?

Yes!!  I have, for the purposes of this map, annexed Ontario
in to the USA.  Some areas of North America that are close
to the US also just happen to get pulled in to these maps.
This might not happen forever, and if you would like your
non-US area to get included, let me know. 

-- Dave


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

[OSM-talk] Please be gentle with newbies

2020-03-03 Thread john whelan

These days I'm retired and use my old age pensioner bus pass to grab a free
coffee.  Often there are strings attached like a group of politicans or
journalists etc. floating around.

Today I got cornered by one who had been on the receiving end of a
communication from a mapper saying they had made a mistake on their first
attempt at mapping.

It was a couple of years ago and the message was a little on the aggressive
side.  The receiver still remembers it clearly and in their mind OSM was a
well this not the place to use those sort of words.

When you send a message to a mapper you don't know who they are.  You are
representing OpenStreetMap when you send a message so please put your
passion to one side and be gentle with the poor things if only so I can
enjoy my free coffee in peace.

I do sympathize, I've come across a lot of suboptimal mapping in my time
and mentally expressed exactly the same thoughts that were expressed but I
do try to count to ten before sending a polite note that says did you
really mean to map this this way?  Have you read the wiki here which gives
guidance?

And yes I know those who read this mailing list would always be polite but
I couldn't think where else to post it.

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

Re: [OSM-talk-fr] [SANTé MENTALE][CMP] [HDJ]

2020-03-03 Thread Jacques Lavignotte





Nœud : CMP de Chauvigny (7248478979 
)



C’est pour adultes ou enfants et adolescents ? ;)


Les deux dans le même bâtiment. En fait (je crois  bien que) c'est le 
même local (même bureau) qui sert aux deux. 1 ou 2 jour/semaine.


Je préfère mettre l’abréviation parce que soignants et patients 
l’utilisent


Toutafé

> que c’est court et plus lisible sur la carte.

Dans le cas du CMP de Chauvigny je mettrais :


   * name=CMP
   * alt_name=Centre médico-psychologique antenne de Chauvigny


Les puristes mettront :


   * name=Centre médico-psychologique
   * short_name=CMP
   * official_name=Antenne du Centre médico-psychologique enfants et
 adolescents de Chauvigny ???

C'est le CMP du CH Laborit à Chauvigny.



Dans le cas du CSAPA de l’ADLCA de Lons-le-Saunier :




   * name=CSAPA Jura-Sud
   * short_name=CSAPA
   * alt_name=Centre de soins, d'accompagnement et de prévention en
 addictologie


Dans le cas du CSAPA de Passerelle 39 de Lons-le-Saunier :


   * name=Passerelle 39
   * short_name=CSAPA
   * alt_name=Centre de soins, d'accompagnement et de prévention en
 addictologie
   * operator=Passerelle 39

Tout ça me convient.


On aurait un tag explicit pour chaque établissement médico-social, 


Les hospitaliers vont te dire qu'un CMP/CATTP c'est *médical* et non 
*médico-social* Même si les CH gèrent du médico-social (ESAT catégorie 
FINESS [246] par ex.)



éviterait de « bricoler » avec les clés *_name.


La  catégorie FINESS [246/156/292] ??

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] Hack Weekend, Toulouse, 4-5 avril 2020, soutien aux déplacements

2020-03-03 Thread Vincent Bergeot


Bonjour à toutes et tous, (copie sur talk-fr, tech, dev-fr et association@)

un *hack weekend OSM se déroule à Toulouse les 4 et 5 avril 2020*. 
Toutes les infos ici : 
https://wiki.openstreetmap.org/wiki/Toulouse_Hack_Weekend_April_2020.


OpenStreetMap France souhaite faciliter la venue à ce hack weekend et 
*prend donc en charge les frais de déplacements des participants en 
faisant la demande* !


Alors n'hésitez pas et contacter tresore...@openstreetmap.fr (prévoyez 
un RIB et un petit formulaire à compléter 
https://nextcloud.openstreetmap.fr/index.php/s/ZmTWX6pdibPJY5L)


Pour l'hébergement il y a quelques places de disponible chez des 
contributeurs locaux. Demandez si besoin !


--

Vincent Bergeot
pour l'association OSM-FR

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

Re: [OSM-talk-fr] Mise à jour BANO

2020-03-03 Thread Vincent de Château-Thierry



Le 03/03/2020 à 19:39, Pierre-Yves Mevel via Talk-fr a écrit :

Merci Vincent pour cette réponse.

Donc, ça finira bien par revenir. Je ne me sens pas les compétences pour 
aller tripatouiller sur Github, mais si je peux être utile à quoi que ce 
soit, n'hésite pas à me faire signe.


Si tu es partant pour beta-tester les fichiers d'Ille-et-Vilaine en v2 
dès leur dispo, moi ça me va :)


vincent

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

Re: [OSM-talk-be] #equalstreetnames

2020-03-03 Thread Karel Adams

Just for the fun of speculating: is way 225291488 named politically
correct, or not? ;)

On 2020-03-03 19:30, Marc Gemis wrote:

Hello Seppe

thanks a lot for sharing this information.
I do like the project (despite my comments on obtaining the data
before the start) because:

- it uses my 2 favourite crowd-sourced open data projects
- it really requires both projects to create the map
- Open Street Maps (sic) is not only used as background nor for navigation
- it brought together 60 people. I do hope they will somehow continue
to contribute to OSM and/or Wikidata
- It gave OSM and Wikidata some publicity

As for the criticism on participating in an event that tries to gather
data on gender inequality in street names.
I do not see any political statement in that. After all, OSM and
Wikidata are very natural sources for such events, as, you might have
guessed it, are open data. If one makes a political statement with
that, mapping bicycle parking could be seen as supporting anti-car
policies as well.

I assume mappers are often activists or at least passionate for
certain features, be it slow roads, airfields, AEDs, historical
buildings, power infrastructure etc. We are often open data and open
source activists as well.
Recently, on the tagging mailing list, you see requests for tags to
map free drinking water, free refills, object sharing, food sharing,
etc. All those are somehow driven by activism. Is that wrong? Not in
my opinion, it enriches the OSM project. If we would only try to mimic
Google Maps by focussing on navigation and shops (for advertising), we
could as well stop now.

So thank you for setting up the project and let's hope it will hellp
OSM grow further in the future.

regards

On Tue, Mar 3, 2020 at 12:39 PM Santens Seppe wrote:

Hi all,

Today, #equalstreetnames was launched, something Open Knowledge / OSM Belgium
(among others) can be very proud of if you ask me. The project combines OSM and
Wikidata (+ extra data crowdsourced during a workshop) to make this map:
https://equalstreetnames.brussels/ (stunning isn’t it?). More info on why an
how can be found in this blogpost:
https://be.okfn.org/2020/03/03/equalstreetnames-brussels-launch-of-open-data-visualisation/

The project already got some nice media coverage, e.g.
https://www.bruzz.be/samenleving/nauwelijks-brusselse-straten-naar-vrouwen-vernoemd-trage-inhaalbeweging-2020-03-03
and
https://www.rtbf.be/info/dossier/les-grenades/detail_combattre-le-sexisme-en-rebaptisant-les-rues-de-bruxelles?id=10446433

Of course, you can help spread the word, e.g. by sharing

https://www.facebook.com/OpenKnowledgeBE/photos/a.376589912722798/1030439804004469/?type=3

https://twitter.com/OpenKnowledgeBE/status/1234754767756386304

https://www.linkedin.com/posts/open-knowledge-belgium_opendata-activity-6640521647684100096-GvRU

Best regards,

Seppe

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

Re: [OSM-talk-be] RFC: explicit tagging of 'Jaagpaden'

2020-03-03 Thread Marc Gemis

As we map what is on the ground, we do not have to care about that,  I
would assume. Let someone else fight with the people that place the signs.

m

Op di 3 mrt. 2020 20:10 schreef Steven Clays :

> To make it more complex, not every signposted towpath in Flanders is
> legally a towpath. Check
> http://www.start2boat.be/vaaropleiding/downloads/reglementen/Bijzondere%20reglementen.pdf
>
> Op di 3 mrt. 2020 om 19:38 schreef Stijn Rombauts via Talk-be <
> talk-be@openstreetmap.org>:
>
>> Hi,
>>
>> 'Jaagpaden' are not always paved roads. Often compacted, gravel, earthen,
>> grassy, ... roads/tracks and then highway=track seems a better choice.
>> Sometimes the only thing that's left is just a path. Then the tag
>> service=towpath is rather odd. I use description=jaagpad.
>> And what about similar roads which usually have the same access
>> restrictions but are called 'haven' or 'havengebied' instead of 'jaagpad'?
>>
>> Regards,
>>
>> StijnRR
>>
>>
>> Op dinsdag 3 maart 2020 16:28:46 CET schreef Pieter Vander Vennet <
>> pieterv...@posteo.net>:
>>
>>
>> Hey Marc,
>>
>> Thanks for your response.
>>
>> IMHO all towpaths are indeed peculiar service roads, thus
>> 'highway=service' + 'service=towpath'. The wiki even mentions explicitly
>> that it should be a service road.
>>
>> The examples you sent are excellent examples where the legal signposting
>> didn't catch up with the historic usage. These clearly used to be
>> towpath but they didn't gain the legal recognition of a 'jaagpad'.
>> Personally, I would tag those with 'service=towpath' (reflecting the
>> historic usage) but not with 'towpath=yes', but this is very subject to
>> change. We might even consider `towpath=no` (with a note clarifying this
>> is legally _not_ a 'jaagpad') or `legal:towpath=no` or something similar.
>>
>> Another thought: if we are about using 'towpath=yes' to reflect the
>> legal status, I'm doubting that there is no better tag scheme for this.
>>
>>
>> Kind regards, Pieter
>>
>>
>> On 03.03.20 16:12, Marc Gemis wrote:
>> > I'm fine with explicitly mapping them.
>> > Isn't service=towpath strange on a way that is not tagged as
>> > highway=service? (but you know that I think they should have been
>> > mapped as highway=service in the first place, but this is not the
>> > case)
>> >
>> > So it's meant for all those that are explicitly signed as "Jaagpad"
>> > and not for any others? So this
>> > https://www.mapillary.com/map/im/3T0U_uBJxNXHfrgwdztQDQ is not a
>> > Jaagpad? (a bit further
>> >
>> https://www.mapillary.com/app/?lat=51.05439739997222=4.4334043=17=photo=cmVJ5z_VXnZqwsdrEK0aHw
>> > , but that still does not make it a Jaadpad?)
>> >
>> > m.
>> >
>> > On Tue, Mar 3, 2020 at 2:14 PM Pieter Vander Vennet
>> >  wrote:
>> >> Hello everyone,
>> >>
>> >> Even though the legal restrictions of 'Jaagpaden' (towpaths in proper
>> English) is already described in detail on the wiki, it would still be
>> useful to reflect the special status explicitly, in our case to give a
>> comfort bonus in cycling route planning but also for historical purposes.
>> >>
>> >> For context, a 'jaagpad', 'trekpad' or towing path is a path that used
>> to be used to (literally) tow boats through the canals, either with
>> manpower or horsepower and a rope attached to the boat - hence there are
>> never trees between a towpath.
>> >>
>> >> With the rise of cheap and powerful combustion engines, this practice
>> became disused and towpaths became service roads and cycleways.
>> >>
>> >> As stated, these often are excellent and heavily preferred by
>> cyclists. Normally, they are wide, asphalted, there are very few cars and
>> especially: there is the very nice scenery of the canal.
>> >>
>> >> Therefore, I would propose to introduce tagging in Belgium to tag
>> towpaths.
>> >>
>> >>
>> >> There are two ways to achieve this:
>> >>
>> >> - A towpath is typically a specific type of service road, so we can
>> add `service=towpath`
>> >>
>> >> - In the UK, the towpaths are tagged with `towpath=yes`
>> >>
>> >> Note that towpaths in Flanders are mostly signposted with an official
>> sign, even though that this is a bit of a legal remnant of a previous era.
>> However, it makes it very explicit and thus unambiguous to map.
>> >>
>> >> But now, for the serious questions:
>> >>
>> >> - what are your thoughts of mapping them somehow? IMHO it is an added
>> value and I'm quite in favour of them.
>> >>
>> >> - What is the best way of mapping them? I'm a bit on the edge of the
>> options above: `service=towpath` is IMHO semantically the most correct
>> form, as it indicates that it is a service road originally built for
>> towing. `towpath=yes` reeks more of the legal status (i.e. having a formal
>> road sign indicating 'jaagpad'). The latter has the advantage of already
>> being in use in the UK with over 3500 instances according to taginfo.
>> service=towpath is not in use at the moment.
>> >>
>> >>
>> >> PS: fun etymological fact: the English verb 'to tow' is

Re: [OSM-talk-be] RFC: explicit tagging of 'Jaagpaden'

2020-03-03 Thread Marc Gemis

Hgw=service can be unpacked and tracks can be paved.  The difference is the
function,  not the surface

m

Op di 3 mrt. 2020 19:38 schreef Stijn Rombauts via Talk-be <
talk-be@openstreetmap.org>:

> Hi,
>
> 'Jaagpaden' are not always paved roads. Often compacted, gravel, earthen,
> grassy, ... roads/tracks and then highway=track seems a better choice.
> Sometimes the only thing that's left is just a path. Then the tag
> service=towpath is rather odd. I use description=jaagpad.
> And what about similar roads which usually have the same access
> restrictions but are called 'haven' or 'havengebied' instead of 'jaagpad'?
>
> Regards,
>
> StijnRR
>
>
> Op dinsdag 3 maart 2020 16:28:46 CET schreef Pieter Vander Vennet <
> pieterv...@posteo.net>:
>
>
> Hey Marc,
>
> Thanks for your response.
>
> IMHO all towpaths are indeed peculiar service roads, thus
> 'highway=service' + 'service=towpath'. The wiki even mentions explicitly
> that it should be a service road.
>
> The examples you sent are excellent examples where the legal signposting
> didn't catch up with the historic usage. These clearly used to be
> towpath but they didn't gain the legal recognition of a 'jaagpad'.
> Personally, I would tag those with 'service=towpath' (reflecting the
> historic usage) but not with 'towpath=yes', but this is very subject to
> change. We might even consider `towpath=no` (with a note clarifying this
> is legally _not_ a 'jaagpad') or `legal:towpath=no` or something similar.
>
> Another thought: if we are about using 'towpath=yes' to reflect the
> legal status, I'm doubting that there is no better tag scheme for this.
>
>
> Kind regards, Pieter
>
>
> On 03.03.20 16:12, Marc Gemis wrote:
> > I'm fine with explicitly mapping them.
> > Isn't service=towpath strange on a way that is not tagged as
> > highway=service? (but you know that I think they should have been
> > mapped as highway=service in the first place, but this is not the
> > case)
> >
> > So it's meant for all those that are explicitly signed as "Jaagpad"
> > and not for any others? So this
> > https://www.mapillary.com/map/im/3T0U_uBJxNXHfrgwdztQDQ is not a
> > Jaagpad? (a bit further
> >
> https://www.mapillary.com/app/?lat=51.05439739997222=4.4334043=17=photo=cmVJ5z_VXnZqwsdrEK0aHw
> > , but that still does not make it a Jaadpad?)
> >
> > m.
> >
> > On Tue, Mar 3, 2020 at 2:14 PM Pieter Vander Vennet
> >  wrote:
> >> Hello everyone,
> >>
> >> Even though the legal restrictions of 'Jaagpaden' (towpaths in proper
> English) is already described in detail on the wiki, it would still be
> useful to reflect the special status explicitly, in our case to give a
> comfort bonus in cycling route planning but also for historical purposes.
> >>
> >> For context, a 'jaagpad', 'trekpad' or towing path is a path that used
> to be used to (literally) tow boats through the canals, either with
> manpower or horsepower and a rope attached to the boat - hence there are
> never trees between a towpath.
> >>
> >> With the rise of cheap and powerful combustion engines, this practice
> became disused and towpaths became service roads and cycleways.
> >>
> >> As stated, these often are excellent and heavily preferred by cyclists.
> Normally, they are wide, asphalted, there are very few cars and especially:
> there is the very nice scenery of the canal.
> >>
> >> Therefore, I would propose to introduce tagging in Belgium to tag
> towpaths.
> >>
> >>
> >> There are two ways to achieve this:
> >>
> >> - A towpath is typically a specific type of service road, so we can add
> `service=towpath`
> >>
> >> - In the UK, the towpaths are tagged with `towpath=yes`
> >>
> >> Note that towpaths in Flanders are mostly signposted with an official
> sign, even though that this is a bit of a legal remnant of a previous era.
> However, it makes it very explicit and thus unambiguous to map.
> >>
> >> But now, for the serious questions:
> >>
> >> - what are your thoughts of mapping them somehow? IMHO it is an added
> value and I'm quite in favour of them.
> >>
> >> - What is the best way of mapping them? I'm a bit on the edge of the
> options above: `service=towpath` is IMHO semantically the most correct
> form, as it indicates that it is a service road originally built for
> towing. `towpath=yes` reeks more of the legal status (i.e. having a formal
> road sign indicating 'jaagpad'). The latter has the advantage of already
> being in use in the UK with over 3500 instances according to taginfo.
> service=towpath is not in use at the moment.
> >>
> >>
> >> PS: fun etymological fact: the English verb 'to tow' is derived from
> the Dutch word for rope: 'touw'
> >>
> >> --
> >> Met vriendelijke groeten,
> >> Pieter Vander Vennet
> >>
> >> ___
> >> Talk-be mailing list
> >> Talk-be@openstreetmap.org
> >> https://lists.openstreetmap.org/listinfo/talk-be
> > ___
> > Talk-be mailing list
> > Talk-be@openstreetmap.org
> >

Re: [OSM-talk-be] RFC: explicit tagging of 'Jaagpaden'

2020-03-03 Thread s8evq

Hi Pieter,

So to be clear, you want to tag the historic usage of a road as a towpath? 

As a way of finding pleasant cycle ways, it's probably mostly valid. Two things 
I think about:

For example, this (https://www.mapillary.com/map/im/r1iBEQmaUlqv0BHGmDoIGw) 
would also classify as historic tow path. There is no cycle lane and cars can 
drive 50. (even 70 on the other side of the canal, before the crossroad).

On the other hand, the paths along the Albertkanaal wouldn't fit under a 
historic definition of towpath, as the canal was finished 1946 and the paths 
were most likely not used or intended to tow boats by.

What would be the criteria for this kind of road? Be parallel along a canal 
that historically had tow boats traffic?


On Tue, 3 Mar 2020 16:28:15 +0100, Pieter Vander Vennet  
wrote:

> Hey Marc,
> 
> Thanks for your response.
> 
> IMHO all towpaths are indeed peculiar service roads, thus
> 'highway=service' + 'service=towpath'. The wiki even mentions explicitly
> that it should be a service road.
> 
> The examples you sent are excellent examples where the legal signposting
> didn't catch up with the historic usage. These clearly used to be
> towpath but they didn't gain the legal recognition of a 'jaagpad'.
> Personally, I would tag those with 'service=towpath' (reflecting the
> historic usage) but not with 'towpath=yes', but this is very subject to
> change. We might even consider `towpath=no` (with a note clarifying this
> is legally _not_ a 'jaagpad') or `legal:towpath=no` or something similar.
> 
> Another thought: if we are about using 'towpath=yes' to reflect the
> legal status, I'm doubting that there is no better tag scheme for this.
> 
> 
> Kind regards, Pieter
> 
> 
> On 03.03.20 16:12, Marc Gemis wrote:
> > I'm fine with explicitly mapping them.
> > Isn't service=towpath strange on a way that is not tagged as
> > highway=service? (but you know that I think they should have been
> > mapped as highway=service in the first place, but this is not the
> > case)
> >
> > So it's meant for all those that are explicitly signed as "Jaagpad"
> > and not for any others? So this
> > https://www.mapillary.com/map/im/3T0U_uBJxNXHfrgwdztQDQ is not a
> > Jaagpad? (a bit further
> > https://www.mapillary.com/app/?lat=51.05439739997222=4.4334043=17=photo=cmVJ5z_VXnZqwsdrEK0aHw
> > , but that still does not make it a Jaadpad?)
> >
> > m.
> >
> > On Tue, Mar 3, 2020 at 2:14 PM Pieter Vander Vennet
> >  wrote:
> >> Hello everyone,
> >>
> >> Even though the legal restrictions of 'Jaagpaden' (towpaths in proper 
> >> English) is already described in detail on the wiki, it would still be 
> >> useful to reflect the special status explicitly, in our case to give a 
> >> comfort bonus in cycling route planning but also for historical purposes.
> >>
> >> For context, a 'jaagpad', 'trekpad' or towing path is a path that used to 
> >> be used to (literally) tow boats through the canals, either with manpower 
> >> or horsepower and a rope attached to the boat - hence there are never 
> >> trees between a towpath.
> >>
> >> With the rise of cheap and powerful combustion engines, this practice 
> >> became disused and towpaths became service roads and cycleways.
> >>
> >> As stated, these often are excellent and heavily preferred by cyclists. 
> >> Normally, they are wide, asphalted, there are very few cars and 
> >> especially: there is the very nice scenery of the canal.
> >>
> >> Therefore, I would propose to introduce tagging in Belgium to tag towpaths.
> >>
> >>
> >> There are two ways to achieve this:
> >>
> >> - A towpath is typically a specific type of service road, so we can add 
> >> `service=towpath`
> >>
> >> - In the UK, the towpaths are tagged with `towpath=yes`
> >>
> >> Note that towpaths in Flanders are mostly signposted with an official 
> >> sign, even though that this is a bit of a legal remnant of a previous era. 
> >> However, it makes it very explicit and thus unambiguous to map.
> >>
> >> But now, for the serious questions:
> >>
> >> - what are your thoughts of mapping them somehow? IMHO it is an added 
> >> value and I'm quite in favour of them.
> >>
> >> - What is the best way of mapping them? I'm a bit on the edge of the 
> >> options above: `service=towpath` is IMHO semantically the most correct 
> >> form, as it indicates that it is a service road originally built for 
> >> towing. `towpath=yes` reeks more of the legal status (i.e. having a formal 
> >> road sign indicating 'jaagpad'). The latter has the advantage of already 
> >> being in use in the UK with over 3500 instances according to taginfo. 
> >> service=towpath is not in use at the moment.
> >>
> >>
> >> PS: fun etymological fact: the English verb 'to tow' is derived from the 
> >> Dutch word for rope: 'touw'
> >>
> >> --
> >> Met vriendelijke groeten,
> >> Pieter Vander Vennet
> >>
> >> ___
> >> Talk-be mailing list
> >> Talk-be@openstreetmap.org
> >>

Re: [OSM-talk-be] #equalstreetnames

2020-03-03 Thread Karel Adams

Marc,

In zoverre ga ik wel graag met u mee, en dat schreef ik eigenlijk ook al:

Het inzamelen van data doen we sowieso al, en bij het filteren en
catalogeren van informatie zijn we graag van dienst. De interpretatie
die daar dan aan gegeven wordt is politiek, maar dat gaat ons niet meer
aan, inderdaad.

Alleen vraag ik me af hoe enige automatisatie ooit gaat kunnen uitmaken
of "Guido Gezelleplein" of "Gezusters Lovelingplantsoen" of
"Dendermondse Steenweg" of "Zemst-Laar" naar mannen of naar vrouwen
verwijzen... Tenzij men een soort "dictionary" opzet die al even veel
werk vereist als het manueel uitzoeken van iedere straatnaam.

Vr.gr.,

Karel

On 2020-03-03 19:30, Marc Gemis wrote:

Hello Seppe

thanks a lot for sharing this information.
I do like the project (despite my comments on obtaining the data
before the start) because:

So thank you for setting up the project and let's hope it will hellp
OSM grow further in the future.

regards

On Tue, Mar 3, 2020 at 12:39 PM Santens Seppe wrote:

Hi all,

Of course, you can help spread the word, e.g. by sharing

https://www.facebook.com/OpenKnowledgeBE/photos/a.376589912722798/1030439804004469/?type=3

https://twitter.com/OpenKnowledgeBE/status/1234754767756386304

https://www.linkedin.com/posts/open-knowledge-belgium_opendata-activity-6640521647684100096-GvRU

Best regards,

Seppe

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

Re: [OSM-talk-be] #equalstreetnames

2020-03-03 Thread Marc Gemis

Hello Seppe

thanks a lot for sharing this information.
I do like the project (despite my comments on obtaining the data
before the start) because:

- it uses my 2 favourite crowd-sourced open data projects
- it really requires both projects to create the map
- Open Street Maps (sic) is not only used as background nor for navigation
- it brought together 60 people. I do hope they will somehow continue
to contribute to OSM and/or Wikidata
- It gave OSM and Wikidata some publicity

As for the criticism on participating in an event that tries to gather
data on gender inequality in street names.
I do not see any political statement in that. After all, OSM and
Wikidata are very natural sources for such events, as, you might have
guessed it, are open data. If one makes a political statement with
that,  mapping bicycle parking could be seen as supporting anti-car
policies as well.

I assume mappers are often activists or at least passionate for
certain features, be it slow roads, airfields, AEDs, historical
buildings, power infrastructure etc. We are often open data and open
source activists as well.
Recently, on the tagging mailing list, you see requests for tags to
map free drinking water, free refills, object sharing, food sharing,
etc. All those are somehow driven by activism. Is that wrong? Not in
my opinion, it enriches the OSM project. If we would only try to mimic
Google Maps by focussing on navigation and shops (for advertising), we
could as well stop now.

So thank you for setting up the project and let's hope it will hellp
OSM grow further in the future.

regards

m.

On Tue, Mar 3, 2020 at 12:39 PM Santens Seppe  wrote:
>
> Hi all,
>
>
>
> Today, #equalstreetnames was launched, something Open Knowledge / OSM Belgium 
> (among others) can be very proud of if you ask me. The project combines OSM 
> and Wikidata (+ extra data crowdsourced during a workshop) to make this map: 
> https://equalstreetnames.brussels/ (stunning isn’t it?). More info on why an 
> how can be found in this blogpost: 
> https://be.okfn.org/2020/03/03/equalstreetnames-brussels-launch-of-open-data-visualisation/
>
>
>
> The project already got some nice media coverage, e.g. 
> https://www.bruzz.be/samenleving/nauwelijks-brusselse-straten-naar-vrouwen-vernoemd-trage-inhaalbeweging-2020-03-03
>  and 
> https://www.rtbf.be/info/dossier/les-grenades/detail_combattre-le-sexisme-en-rebaptisant-les-rues-de-bruxelles?id=10446433
>
>
>
> Of course, you can help spread the word, e.g. by sharing
>
> https://www.facebook.com/OpenKnowledgeBE/photos/a.376589912722798/1030439804004469/?type=3
>
> https://twitter.com/OpenKnowledgeBE/status/1234754767756386304
>
> https://www.linkedin.com/posts/open-knowledge-belgium_opendata-activity-6640521647684100096-GvRU
>
>
>
>
>
> Best regards,
>
>
>
> Seppe
>
>
>
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be

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

Re: [OSM-talk-be] RFC: explicit tagging of 'Jaagpaden'

2020-03-03 Thread Steven Clays

To make it more complex, not every signposted towpath in Flanders is
legally a towpath. Check
http://www.start2boat.be/vaaropleiding/downloads/reglementen/Bijzondere%20reglementen.pdf

Op di 3 mrt. 2020 om 19:38 schreef Stijn Rombauts via Talk-be <
talk-be@openstreetmap.org>:

> Hi,
>
> 'Jaagpaden' are not always paved roads. Often compacted, gravel, earthen,
> grassy, ... roads/tracks and then highway=track seems a better choice.
> Sometimes the only thing that's left is just a path. Then the tag
> service=towpath is rather odd. I use description=jaagpad.
> And what about similar roads which usually have the same access
> restrictions but are called 'haven' or 'havengebied' instead of 'jaagpad'?
>
> Regards,
>
> StijnRR
>
>
> Op dinsdag 3 maart 2020 16:28:46 CET schreef Pieter Vander Vennet <
> pieterv...@posteo.net>:
>
>
> Hey Marc,
>
> Thanks for your response.
>
> IMHO all towpaths are indeed peculiar service roads, thus
> 'highway=service' + 'service=towpath'. The wiki even mentions explicitly
> that it should be a service road.
>
> The examples you sent are excellent examples where the legal signposting
> didn't catch up with the historic usage. These clearly used to be
> towpath but they didn't gain the legal recognition of a 'jaagpad'.
> Personally, I would tag those with 'service=towpath' (reflecting the
> historic usage) but not with 'towpath=yes', but this is very subject to
> change. We might even consider `towpath=no` (with a note clarifying this
> is legally _not_ a 'jaagpad') or `legal:towpath=no` or something similar.
>
> Another thought: if we are about using 'towpath=yes' to reflect the
> legal status, I'm doubting that there is no better tag scheme for this.
>
>
> Kind regards, Pieter
>
>
> On 03.03.20 16:12, Marc Gemis wrote:
> > I'm fine with explicitly mapping them.
> > Isn't service=towpath strange on a way that is not tagged as
> > highway=service? (but you know that I think they should have been
> > mapped as highway=service in the first place, but this is not the
> > case)
> >
> > So it's meant for all those that are explicitly signed as "Jaagpad"
> > and not for any others? So this
> > https://www.mapillary.com/map/im/3T0U_uBJxNXHfrgwdztQDQ is not a
> > Jaagpad? (a bit further
> >
> https://www.mapillary.com/app/?lat=51.05439739997222=4.4334043=17=photo=cmVJ5z_VXnZqwsdrEK0aHw
> > , but that still does not make it a Jaadpad?)
> >
> > m.
> >
> > On Tue, Mar 3, 2020 at 2:14 PM Pieter Vander Vennet
> >  wrote:
> >> Hello everyone,
> >>
> >> Even though the legal restrictions of 'Jaagpaden' (towpaths in proper
> English) is already described in detail on the wiki, it would still be
> useful to reflect the special status explicitly, in our case to give a
> comfort bonus in cycling route planning but also for historical purposes.
> >>
> >> For context, a 'jaagpad', 'trekpad' or towing path is a path that used
> to be used to (literally) tow boats through the canals, either with
> manpower or horsepower and a rope attached to the boat - hence there are
> never trees between a towpath.
> >>
> >> With the rise of cheap and powerful combustion engines, this practice
> became disused and towpaths became service roads and cycleways.
> >>
> >> As stated, these often are excellent and heavily preferred by cyclists.
> Normally, they are wide, asphalted, there are very few cars and especially:
> there is the very nice scenery of the canal.
> >>
> >> Therefore, I would propose to introduce tagging in Belgium to tag
> towpaths.
> >>
> >>
> >> There are two ways to achieve this:
> >>
> >> - A towpath is typically a specific type of service road, so we can add
> `service=towpath`
> >>
> >> - In the UK, the towpaths are tagged with `towpath=yes`
> >>
> >> Note that towpaths in Flanders are mostly signposted with an official
> sign, even though that this is a bit of a legal remnant of a previous era.
> However, it makes it very explicit and thus unambiguous to map.
> >>
> >> But now, for the serious questions:
> >>
> >> - what are your thoughts of mapping them somehow? IMHO it is an added
> value and I'm quite in favour of them.
> >>
> >> - What is the best way of mapping them? I'm a bit on the edge of the
> options above: `service=towpath` is IMHO semantically the most correct
> form, as it indicates that it is a service road originally built for
> towing. `towpath=yes` reeks more of the legal status (i.e. having a formal
> road sign indicating 'jaagpad'). The latter has the advantage of already
> being in use in the UK with over 3500 instances according to taginfo.
> service=towpath is not in use at the moment.
> >>
> >>
> >> PS: fun etymological fact: the English verb 'to tow' is derived from
> the Dutch word for rope: 'touw'
> >>
> >> --
> >> Met vriendelijke groeten,
> >> Pieter Vander Vennet
> >>
> >> ___
> >> Talk-be mailing list
> >> Talk-be@openstreetmap.org
> >> https://lists.openstreetmap.org/listinfo/talk-be
> >

Re: [OSM-talk-fr] Mise à jour BANO

2020-03-03 Thread Pierre-Yves Mevel via Talk-fr

Merci Vincent pour cette réponse.

Donc, ça finira bien par revenir. Je ne me sens pas les compétences pour
aller tripatouiller sur Github, mais si je peux être utile à quoi que ce
soit, n'hésite pas à me faire signe.

Bonne soirée

Le mar. 3 mars 2020 à 15:06, Vincent de Château-Thierry 
a écrit :

> Salut Pierre-Yves,
>
> > De: "Pierre-Yves Mevel via Talk-fr" 
> >
> > Désolé de remettre le sujet sur la table mais, après avoir parcouru
> > les différents échanges sur le sujet, il me semble qu'un point n'a
> > pas été abordé concernant la BANO. Depuis de nombreuses années, je
> > contribue à la création de points adresse sur OSM et je m'en sers
> > pour alimenter la base adresse de ma communauté d'agglo grâce aux
> > extractions quotidiennes que l'on peut trouver sur
> > http://bano.openstreetmap.fr/data/ . A priori, ces fichiers sont mis
> > à jour quotidiennement. Si je lis correctement le très complet
> > message que Vincent (dct) a écrit sur cette liste le 11 novembre
> > dernier, le passage en v2 ne devait pas changer cela.
>
> Oui dans mon message je disais que les exports ne changeaient pas.
> J'aurais du dire : "pas pour l'instant". L'objectif est bien que tout
> bascule sur une seule instance de BANO (celle qu'on appelle V2). Les
> exports depuis cette nouvelle instance sont un gros chantier, sur lequel je
> suis pile actuellement (cf le dernier commit en date [1]). Lorsque ce
> ticket sera terminé, alors on basculera l'alimentation de
> http://bano.openstreetmap.fr/data/ sur la V2, mise à jour
> quotidiennement.
>
> > Cependant, je constate que les fichiers concernant l'Ille-et-Vilaine
> > (et sans doute les autres départements) n'évoluent guère depuis le
> > début de l'année. Ainsi, si des changements faits le 18 décembre
> > sont bien intégrés dans le SHP (par exemple,
> > https://www.openstreetmap.org/node/7066812399 ), d'autres, faits le
> > 6 février, n'y apparaissent pas (cf.
> > https://www.openstreetmap.org/node/7191078724 ) et ils ne figurent
> > pas non plus en vert sur
> > http://tile.openstreetmap.fr/~cquest/leaflet/bano.html .
>
> J'avoue ne pas trop surveiller au jour le jour la V1, mais ton message
> laisse penser que la base OSM qui l'alimente a du retard (litote). Et comme
> c'est jusque là cette V1 qui alimente aussi le rendu carto BANO, on y
> constate le même retard. C'est sur la pile de trucs à faire de Christian
> que de brancher le rendu carto sur la V2.
>
> > Ai-je loupé un épisode concernant le lieu où trouver ces données ?
> > Dans ce cas, ne serait-il pas souhaitable de l'indiquer sur la page
> > dédiée de data.gouv.fr (
> >
> https://www.data.gouv.fr/fr/datasets/base-d-adresses-nationale-ouverte-bano/
> > ) ?
> > Ou bien y a-t-il un problème de moissonnage qui empêche l'extraction
> > quotidienne de se dérouler correctement ?
>
> Non tu n'as pas loupé de message, la comm' sur BANO est loin d'être au
> top  j'avoue /o\. En tout cas ce sujet des exports est le dernier "gros"
> sujet qui empêche la bascule de tout le système BANO sur une version
> unique, c'est bien ce qui me motive pour que ça ne s'éternise pas trop.
> Donc j'y travaille et je compte bien annoncer cette vrai v2 complète
> rapidement. Je n'ose pas dire "fin de ce mois" car c'est le meilleur moyen
> de ne pas tenir le délai. Donc non je l'ai pas dit :)
>
> vincent
>
> [1] :
> https://github.com/osm-fr/bano/commit/ba496b90a1ba37a919d9576694fd89a1c0cf0428
>
> ___
> 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-be] RFC: explicit tagging of 'Jaagpaden'

2020-03-03 Thread Stijn Rombauts via Talk-be

 Hi,
'Jaagpaden' are not always paved roads. Often compacted, gravel, earthen, 
grassy, ... roads/tracks and then highway=track seems a better choice. 
Sometimes the only thing that's left is just a path. Then the tag 
service=towpath is rather odd. I use description=jaagpad.And what about similar 
roads which usually have the same access restrictions but are called 'haven' or 
'havengebied' instead of 'jaagpad'?
Regards,
StijnRR


Op dinsdag 3 maart 2020 16:28:46 CET schreef Pieter Vander Vennet 
:  
 
 Hey Marc,

Thanks for your response.

IMHO all towpaths are indeed peculiar service roads, thus
'highway=service' + 'service=towpath'. The wiki even mentions explicitly
that it should be a service road.

The examples you sent are excellent examples where the legal signposting
didn't catch up with the historic usage. These clearly used to be
towpath but they didn't gain the legal recognition of a 'jaagpad'.
Personally, I would tag those with 'service=towpath' (reflecting the
historic usage) but not with 'towpath=yes', but this is very subject to
change. We might even consider `towpath=no` (with a note clarifying this
is legally _not_ a 'jaagpad') or `legal:towpath=no` or something similar.

Another thought: if we are about using 'towpath=yes' to reflect the
legal status, I'm doubting that there is no better tag scheme for this.


Kind regards, Pieter


On 03.03.20 16:12, Marc Gemis wrote:
> I'm fine with explicitly mapping them.
> Isn't service=towpath strange on a way that is not tagged as
> highway=service? (but you know that I think they should have been
> mapped as highway=service in the first place, but this is not the
> case)
>
> So it's meant for all those that are explicitly signed as "Jaagpad"
> and not for any others? So this
> https://www.mapillary.com/map/im/3T0U_uBJxNXHfrgwdztQDQ is not a
> Jaagpad? (a bit further
> https://www.mapillary.com/app/?lat=51.05439739997222=4.4334043=17=photo=cmVJ5z_VXnZqwsdrEK0aHw
> , but that still does not make it a Jaadpad?)
>
> m.
>
> On Tue, Mar 3, 2020 at 2:14 PM Pieter Vander Vennet
>  wrote:
>> Hello everyone,
>>
>> Even though the legal restrictions of 'Jaagpaden' (towpaths in proper 
>> English) is already described in detail on the wiki, it would still be 
>> useful to reflect the special status explicitly, in our case to give a 
>> comfort bonus in cycling route planning but also for historical purposes.
>>
>> For context, a 'jaagpad', 'trekpad' or towing path is a path that used to be 
>> used to (literally) tow boats through the canals, either with manpower or 
>> horsepower and a rope attached to the boat - hence there are never trees 
>> between a towpath.
>>
>> With the rise of cheap and powerful combustion engines, this practice became 
>> disused and towpaths became service roads and cycleways.
>>
>> As stated, these often are excellent and heavily preferred by cyclists. 
>> Normally, they are wide, asphalted, there are very few cars and especially: 
>> there is the very nice scenery of the canal.
>>
>> Therefore, I would propose to introduce tagging in Belgium to tag towpaths.
>>
>>
>> There are two ways to achieve this:
>>
>> - A towpath is typically a specific type of service road, so we can add 
>> `service=towpath`
>>
>> - In the UK, the towpaths are tagged with `towpath=yes`
>>
>> Note that towpaths in Flanders are mostly signposted with an official sign, 
>> even though that this is a bit of a legal remnant of a previous era. 
>> However, it makes it very explicit and thus unambiguous to map.
>>
>> But now, for the serious questions:
>>
>> - what are your thoughts of mapping them somehow? IMHO it is an added value 
>> and I'm quite in favour of them.
>>
>> - What is the best way of mapping them? I'm a bit on the edge of the options 
>> above: `service=towpath` is IMHO semantically the most correct form, as it 
>> indicates that it is a service road originally built for towing. 
>> `towpath=yes` reeks more of the legal status (i.e. having a formal road sign 
>> indicating 'jaagpad'). The latter has the advantage of already being in use 
>> in the UK with over 3500 instances according to taginfo. service=towpath is 
>> not in use at the moment.
>>
>>
>> PS: fun etymological fact: the English verb 'to tow' is derived from the 
>> Dutch word for rope: 'touw'
>>
>> --
>> Met vriendelijke groeten,
>> Pieter Vander Vennet
>>
>> ___
>> Talk-be mailing list
>> Talk-be@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-be
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be

-- 
Met vriendelijke groeten,
Pieter Vander Vennet
___
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be
  ___
Talk-be mailing list
Talk-be@openstreetmap.org

Re: [OSM-talk-fr] [SANTé MENTALE][CMP] [HDJ]

2020-03-03 Thread Yves P.


—
Yves Pratter




> Nœud : CMP de Chauvigny (7248478979 
> )


website=https://ch-laborit.fr/presentation-du-chl/sectorisation-soins-adultes/secteur-3-poitiers-montmorillon/
pas website=https://ch-laborit.fr/services-de-soins/adultes/hopitaux-de-jour/ ;)


alt_name="Centre médico-psychologique adultes de Chauvigny »
social_facility:for=mental_health;children
C’est pour adultes ou enfants et adolescents ? ;)

Pour le nom, c’est comme pour les postes ou les gares, non ?
Donc pas « CMP de Chauvigny » mais « CMP » (qui se trouve sur la commune de 
Chauvigny).

Après, nom, nom long, nom court, ça ne change pas grand chose si Nominatim 
retrouve l’établissement.
Avec la description, je doute ;)

Je préfère mettre l’abréviation parce que soignants et patients l’utilisent, 
que c’est court et plus lisible sur la carte.
Dans le cas du CMP de Chauvigny je mettrais :
name=CMP
alt_name=Centre médico-psychologique
Les puristes mettront :
name=Centre médico-psychologique
short_name=CMP
official_name=Antenne du Centre médico-psychologique enfants et adolescents de 
Chauvigny ???

Dans le cas du CSAPA de l’ADLCA de Lons-le-Saunier :
name=CSAPA Jura-Sud
short_name=CSAPA
alt_name=Centre de soins, d'accompagnement et de prévention en addictologie
Dans le cas du CSAPA de Passerelle 39 de Lons-le-Saunier :
name=Passerelle 39
short_name=CSAPA
alt_name=Centre de soins, d'accompagnement et de prévention en addictologie
operator=Passerelle 39
__
Yves

On aurait un tag explicit pour chaque établissement médico-social, ça éviterait 
de « bricoler » avec les clés *_name.
On peut aussi paramétrer nominatim pour rechercher des POI avec des noms et des 
synonymes en français.
cf. https://wiki.openstreetmap.org/wiki/Nominatim/Special_Phrases/FR



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

Re: [Talk-it] Via Chiusi a Roma

2020-03-03 Thread Martin Koppenhoefer

sent from a phone

> On 3. Mar 2020, at 17:47, Ivo Reano  wrote:
> 
> Se vuoi essere preciso devi avere delle buone aerofoto di sfondo, ben 
> posizionate o tarate con dati certi (come dei punti ottenuti con la funzione 
> del garmin che fa una campionatura del segnale per alcuni minuti, e che nelle 
> migliori condizioni permette di stimare una posizione al metro.

più che alla precisione della posizione geografica esatta punterei alla 
precisione topologica: mappare “la cosa” a cui è associato il civico (per 
esempio barrier=gate / entrance, oppure entrance=yes/main/no/..., eventuali 
level=1/... nel caso non si trovi al livello stradale), nel contesto (parte di 
un edificio, di un barrier=fence, etc.), orientandosi alle cose (case, incroci, 
alberi, ecc) che già ci sono. Meno che ci sono altri oggetti, meno importa la 
precisione al metro ;-), non ti far frenare dalla precisione assoluta. Dove non 
c’è niente va bene una stima, e altrimenti ti puoi orientare alla mappa 
esistente.

Ciao Martin 

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

Re: [Talk-it] Via Chiusi a Roma

2020-03-03 Thread Martin Koppenhoefer

sent from a phone

> On 3. Mar 2020, at 17:47, Ivo Reano  wrote:
> 
> Comunque sia. In Italia il civico corrisponde all'ingresso della 
> casa/condominio/attività o quello che è.

si, addr:housenumber descrive il numero civico di un indirizzo (proprietà di un 
oggetto), e anche “il civico“ come oggetto in se. 

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

Re: [Talk-it] Via Chiusi a Roma

2020-03-03 Thread Ivo Reano

>
> Allora la seconda parte, quale pagina di wiki devo consultare per inserire
> o modificare i punti GPS dei civici? Alcune volte non sono estremamente
> accurati..
>
> Per punti gpx cosa intendi?
Dei punti ricavati da un tuo survey?
O i nodi presenti su OSM che contengono i dati sull'indirizzo?

Comunque sia. In Italia il civico corrisponde all'ingresso della
casa/condominio/attività o quello che è.
Se vuoi essere preciso devi avere delle buone aerofoto di sfondo, ben
posizionate o tarate con dati certi (come dei punti ottenuti con la
funzione del garmin che fa una campionatura del segnale per alcuni minuti,
e che nelle migliori condizioni permette di stimare una posizione al metro.

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

Re: [Talk-it] Via Chiusi a Roma

2020-03-03 Thread Angelo Corsaro

:)

Allora la seconda parte, quale pagina di wiki devo consultare per inserire
o modificare i punti GPS dei civici? Alcune volte non sono estremamente
accurati..

Il Mar 3 Mar 2020, 17:15 Damjan Gerl  ha scritto:

> Si, ovviamente, intendevo dire "non esiste in OSM", no che non esista in
> realtà  :-)
>
> Damjan
>
>
> -- Original Header ---
>
> From  : "Andrea Musuruane" musur...@gmail.com
> To  : "openstreetmap list - italiano" talk-it@openstreetmap.org
> Cc  :
> Date  : Tue, 3 Mar 2020 16:07:58 +0100
> Subject : Re: [Talk-it] Via Chiusi a Roma
>
> > Credo intendesse dire che non è inserito nel database di OSM.
> >
> > Ciao,
> >
> > Andrea
> >
> >
> > On Tue, Mar 3, 2020 at 3:58 PM Angelo Corsaro 
> > wrote:
> >
> > >
> > > Il 52 esiste..
> > >
> > > Angelo
> > >
> > > Il 03/03/20 14:44, Damjan Gerl ha scritto:
> > > > La logica dovrebbe essere questa:
> > > > siccome il civico 52 non esiste cerca la via chiusi nel comune di
> roma e
> > > ne trova alcuni, visualizzati in ordine sparso.
> > > >
> > > > Per trovare come primo risultato quella giusta a Roma città devi
> > > scrivere "via chiusi, roma, roma"
> > > >
> > > > Damjan
> > > >
> > > >
> > > > -- Original Header ---
> > > >
> > > >  From  : "Cascafico Giovanni" cascaf...@gmail.com
> > > > To  : "openstreetmap list - italiano"
> talk-it@openstreetmap.org
> > > > Cc  :
> > > > Date  : Tue, 3 Mar 2020 14:26:44 +0100
> > > > Subject : Re: [Talk-it] Via Chiusi a Roma
> > > >
> > > >> Premetto che il civico 52 non esiste in nessuno dei match,
> > > >> strani risultati di Nominatim:
> > > >>
> > > >> - "via chiusi 52, roma" [1] restituisce la strada di campagna
> > > >> ma in "show more results" il secondo match è la via corretta
> > > >>
> > > >> - "via chiusi, roma" restituisce la via corretta
> > > >>
> > > >> - "52 via chiusi, roma" restituisce la via corretta
> > > >>
> > > >>
> > > >> [1]
> > > https://nominatim.openstreetmap.org/search.php?q=via+chiusi+52%2C+roma
> > > >>
> > > >> Il giorno mar 3 mar 2020 alle ore 10:23 Angelo Corsaro
> > > >>  ha scritto:
> > > >>> Buongiorno lista,
> > > >>> per mio cultura mi sto divertendo con punti GPS, distanza, etc e mi
> > > sono
> > > >>> imbattuto in una cosa particolare: Via Chiusi 52 a Roma. Se su OSM
> > > cerco
> > > >>> questo indirizzo completo, mi ritrovo a Nettuno, inserendo solo Via
> > > >>> Chiusi, Roma, trovo la strada in oggetto.
> > > >>> Ancora peggio se cerco prima via Chiusi 52 e poi via Chiusi, trovo
> > > >>> sempre la strada a Nettuno.
> > > >>> Non credo che sia un problema di Nominatim, ma vorrei capire (se
> > > dovessi
> > > >>> trovare altri casi come questo) se e come modificare i dati in OSM.
> > > >>>
> > > >>> Ciao,
> > > >>> Angelo
> > > >>>
> > > >>> PS con Google non esiste questo problema.
> > > >>>
> > > >>> ___
> > > >>> Talk-it mailing list
> > > >>> Talk-it@openstreetmap.org
> > > >>> https://lists.openstreetmap.org/listinfo/talk-it
> > > >> ___
> > > >> Talk-it mailing list
> > > >> Talk-it@openstreetmap.org
> > > >> https://lists.openstreetmap.org/listinfo/talk-it
> > > >>
> > > > ___
> > > > Talk-it mailing list
> > > > Talk-it@openstreetmap.org
> > > > https://lists.openstreetmap.org/listinfo/talk-it
> > >
> > >
> > > ___
> > > Talk-it mailing list
> > > Talk-it@openstreetmap.org
> > > https://lists.openstreetmap.org/listinfo/talk-it
> > >
> >
>
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [OSM-talk-fr] [PROPOSITION] [SANTé MENTALE][CMP] amenity=hospital et FINESS

2020-03-03 Thread Philippe Verdy

Le mar. 3 mars 2020 à 14:36,  a écrit :
>
> name=le nom relativement court, CMP de Chauvigny
>
> official_name= le nom super long que personne n'utilise.

Pas vraiment. "CMP" est utilisé par ceux qui y font référence souvent
car ils sont concernés en permanence ou pour de longues durées mais en
fait le sigle est appris uniquement parce que ce sont les agents
sociaux qui l'utilisent pour leur usage courant. Demandez à n'importe
qui d'autre, "CMP" ne signifie rien pour eux et il faudra leur
expliquer de quoi il s'agit, d'autant que le sigle est lui-même ambigu
et peut signifier des tas de choses même dans la même commune

(je suis certain qu'on peut trouver des noms d'établissements privés,
commerces, et même des services publics qui n'ont rien à voir avec le
domaine "médico-psychologique" qui doit être explicitement renseigné
dans un des tags affichés par les outils de recherche, ne serait-ce
que pour lever l'ambiguïté dans les recherches ou faciliter les
recherches de services apparentés; le tag utilisé doit être un de ceux
indexés et affichés par Nominatim, si ce n'est pas le cas, voir quel
tag serait mieux approprié mais par défaut on peut toujours utiliser
un tag générique "description=*" avec l'assurance qu'il sera bien
affiché si on sélectionne l'objet dans une liste ou en pointant sur la
carte n'affichant qu'un nom court ou abrégé et une vague icône). C'est
une remarque générale applicable à tout sigle court (5 lettres ou
moins), très peu signifiant et discriminant.

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

Re: [Talk-it] Via Chiusi a Roma

2020-03-03 Thread Martin Koppenhoefer

sent from a phone

> On 3. Mar 2020, at 10:23, Angelo Corsaro  wrote:
> 
> Via Chiusi 52 a Roma. Se su OSM cerco questo indirizzo completo, mi ritrovo a 
> Nettuno, inserendo solo Via Chiusi, Roma, trovo la strada in oggetto.
> Ancora peggio se cerco prima via Chiusi 52 e poi via Chiusi, trovo sempre la 
> strada a Nettuno.

forse parte del problema è che Nettuno si trova a Roma (Capitale).

Purtroppo nemmeno con la frase “via chiusi 52, roma, roma capitale” trova Roma, 
Roma prima di Nettuno, Roma.

Proverei di chiedere ai sviluppatori di Nominatim.

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

[OSM-talk] The benefits of cross-linking OSM and Wikidata

2020-03-03 Thread Andy Mabbett

Some of you will remember, around five years ago, a debate about
whether or not we should add Wikidata IDs to OSM.

We did, and so here's "EqualStreetNames.Brussels", an example of what
is now possible:

   https://equalstreetnames.brussels/en/index.html

It shows streets in Brussels named after men and women, visualized
with data from OpenStreetMap and Wikidata.

Does anyone have other good examples?

-- 
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk

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

Re: [Talk-it] Via Chiusi a Roma

2020-03-03 Thread Damjan Gerl

Si, ovviamente, intendevo dire "non esiste in OSM", no che non esista in realtà 
 :-)

Damjan


-- Original Header ---

From  : "Andrea Musuruane" musur...@gmail.com
To  : "openstreetmap list - italiano" talk-it@openstreetmap.org
Cc  : 
Date  : Tue, 3 Mar 2020 16:07:58 +0100
Subject : Re: [Talk-it] Via Chiusi a Roma

> Credo intendesse dire che non è inserito nel database di OSM.
> 
> Ciao,
> 
> Andrea
> 
> 
> On Tue, Mar 3, 2020 at 3:58 PM Angelo Corsaro 
> wrote:
> 
> >
> > Il 52 esiste..
> >
> > Angelo
> >
> > Il 03/03/20 14:44, Damjan Gerl ha scritto:
> > > La logica dovrebbe essere questa:
> > > siccome il civico 52 non esiste cerca la via chiusi nel comune di roma e
> > ne trova alcuni, visualizzati in ordine sparso.
> > >
> > > Per trovare come primo risultato quella giusta a Roma città devi
> > scrivere "via chiusi, roma, roma"
> > >
> > > Damjan
> > >
> > >
> > > -- Original Header ---
> > >
> > >  From  : "Cascafico Giovanni" cascaf...@gmail.com
> > > To  : "openstreetmap list - italiano" talk-it@openstreetmap.org
> > > Cc  :
> > > Date  : Tue, 3 Mar 2020 14:26:44 +0100
> > > Subject : Re: [Talk-it] Via Chiusi a Roma
> > >
> > >> Premetto che il civico 52 non esiste in nessuno dei match,
> > >> strani risultati di Nominatim:
> > >>
> > >> - "via chiusi 52, roma" [1] restituisce la strada di campagna
> > >> ma in "show more results" il secondo match è la via corretta
> > >>
> > >> - "via chiusi, roma" restituisce la via corretta
> > >>
> > >> - "52 via chiusi, roma" restituisce la via corretta
> > >>
> > >>
> > >> [1]
> > https://nominatim.openstreetmap.org/search.php?q=via+chiusi+52%2C+roma
> > >>
> > >> Il giorno mar 3 mar 2020 alle ore 10:23 Angelo Corsaro
> > >>  ha scritto:
> > >>> Buongiorno lista,
> > >>> per mio cultura mi sto divertendo con punti GPS, distanza, etc e mi
> > sono
> > >>> imbattuto in una cosa particolare: Via Chiusi 52 a Roma. Se su OSM
> > cerco
> > >>> questo indirizzo completo, mi ritrovo a Nettuno, inserendo solo Via
> > >>> Chiusi, Roma, trovo la strada in oggetto.
> > >>> Ancora peggio se cerco prima via Chiusi 52 e poi via Chiusi, trovo
> > >>> sempre la strada a Nettuno.
> > >>> Non credo che sia un problema di Nominatim, ma vorrei capire (se
> > dovessi
> > >>> trovare altri casi come questo) se e come modificare i dati in OSM.
> > >>>
> > >>> Ciao,
> > >>> Angelo
> > >>>
> > >>> PS con Google non esiste questo problema.
> > >>>
> > >>> ___
> > >>> Talk-it mailing list
> > >>> Talk-it@openstreetmap.org
> > >>> https://lists.openstreetmap.org/listinfo/talk-it
> > >> ___
> > >> Talk-it mailing list
> > >> Talk-it@openstreetmap.org
> > >> https://lists.openstreetmap.org/listinfo/talk-it
> > >>
> > > ___
> > > Talk-it mailing list
> > > Talk-it@openstreetmap.org
> > > https://lists.openstreetmap.org/listinfo/talk-it
> >
> >
> > ___
> > Talk-it mailing list
> > Talk-it@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-it
> >
> 

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

Re: [OSM-talk-be] RFC: explicit tagging of 'Jaagpaden'

2020-03-03 Thread Pieter Vander Vennet

Hey Marc,

Thanks for your response.

IMHO all towpaths are indeed peculiar service roads, thus
'highway=service' + 'service=towpath'. The wiki even mentions explicitly
that it should be a service road.

The examples you sent are excellent examples where the legal signposting
didn't catch up with the historic usage. These clearly used to be
towpath but they didn't gain the legal recognition of a 'jaagpad'.
Personally, I would tag those with 'service=towpath' (reflecting the
historic usage) but not with 'towpath=yes', but this is very subject to
change. We might even consider `towpath=no` (with a note clarifying this
is legally _not_ a 'jaagpad') or `legal:towpath=no` or something similar.

Another thought: if we are about using 'towpath=yes' to reflect the
legal status, I'm doubting that there is no better tag scheme for this.


Kind regards, Pieter


On 03.03.20 16:12, Marc Gemis wrote:
> I'm fine with explicitly mapping them.
> Isn't service=towpath strange on a way that is not tagged as
> highway=service? (but you know that I think they should have been
> mapped as highway=service in the first place, but this is not the
> case)
>
> So it's meant for all those that are explicitly signed as "Jaagpad"
> and not for any others? So this
> https://www.mapillary.com/map/im/3T0U_uBJxNXHfrgwdztQDQ is not a
> Jaagpad? (a bit further
> https://www.mapillary.com/app/?lat=51.05439739997222=4.4334043=17=photo=cmVJ5z_VXnZqwsdrEK0aHw
> , but that still does not make it a Jaadpad?)
>
> m.
>
> On Tue, Mar 3, 2020 at 2:14 PM Pieter Vander Vennet
>  wrote:
>> Hello everyone,
>>
>> Even though the legal restrictions of 'Jaagpaden' (towpaths in proper 
>> English) is already described in detail on the wiki, it would still be 
>> useful to reflect the special status explicitly, in our case to give a 
>> comfort bonus in cycling route planning but also for historical purposes.
>>
>> For context, a 'jaagpad', 'trekpad' or towing path is a path that used to be 
>> used to (literally) tow boats through the canals, either with manpower or 
>> horsepower and a rope attached to the boat - hence there are never trees 
>> between a towpath.
>>
>> With the rise of cheap and powerful combustion engines, this practice became 
>> disused and towpaths became service roads and cycleways.
>>
>> As stated, these often are excellent and heavily preferred by cyclists. 
>> Normally, they are wide, asphalted, there are very few cars and especially: 
>> there is the very nice scenery of the canal.
>>
>> Therefore, I would propose to introduce tagging in Belgium to tag towpaths.
>>
>>
>> There are two ways to achieve this:
>>
>> - A towpath is typically a specific type of service road, so we can add 
>> `service=towpath`
>>
>> - In the UK, the towpaths are tagged with `towpath=yes`
>>
>> Note that towpaths in Flanders are mostly signposted with an official sign, 
>> even though that this is a bit of a legal remnant of a previous era. 
>> However, it makes it very explicit and thus unambiguous to map.
>>
>> But now, for the serious questions:
>>
>> - what are your thoughts of mapping them somehow? IMHO it is an added value 
>> and I'm quite in favour of them.
>>
>> - What is the best way of mapping them? I'm a bit on the edge of the options 
>> above: `service=towpath` is IMHO semantically the most correct form, as it 
>> indicates that it is a service road originally built for towing. 
>> `towpath=yes` reeks more of the legal status (i.e. having a formal road sign 
>> indicating 'jaagpad'). The latter has the advantage of already being in use 
>> in the UK with over 3500 instances according to taginfo. service=towpath is 
>> not in use at the moment.
>>
>>
>> PS: fun etymological fact: the English verb 'to tow' is derived from the 
>> Dutch word for rope: 'touw'
>>
>> --
>> Met vriendelijke groeten,
>> Pieter Vander Vennet
>>
>> ___
>> Talk-be mailing list
>> Talk-be@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-be
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be

-- 
Met vriendelijke groeten,
Pieter Vander Vennet

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

Re: [OSM-talk-be] RFC: explicit tagging of 'Jaagpaden'

2020-03-03 Thread Marc Gemis

I'm fine with explicitly mapping them.
Isn't service=towpath strange on a way that is not tagged as
highway=service? (but you know that I think they should have been
mapped as highway=service in the first place, but this is not the
case)

So it's meant for all those that are explicitly signed as "Jaagpad"
and not for any others? So this
https://www.mapillary.com/map/im/3T0U_uBJxNXHfrgwdztQDQ is not a
Jaagpad? (a bit further
https://www.mapillary.com/app/?lat=51.05439739997222=4.4334043=17=photo=cmVJ5z_VXnZqwsdrEK0aHw
, but that still does not make it a Jaadpad?)

m.

On Tue, Mar 3, 2020 at 2:14 PM Pieter Vander Vennet
 wrote:
>
> Hello everyone,
>
> Even though the legal restrictions of 'Jaagpaden' (towpaths in proper 
> English) is already described in detail on the wiki, it would still be useful 
> to reflect the special status explicitly, in our case to give a comfort bonus 
> in cycling route planning but also for historical purposes.
>
> For context, a 'jaagpad', 'trekpad' or towing path is a path that used to be 
> used to (literally) tow boats through the canals, either with manpower or 
> horsepower and a rope attached to the boat - hence there are never trees 
> between a towpath.
>
> With the rise of cheap and powerful combustion engines, this practice became 
> disused and towpaths became service roads and cycleways.
>
> As stated, these often are excellent and heavily preferred by cyclists. 
> Normally, they are wide, asphalted, there are very few cars and especially: 
> there is the very nice scenery of the canal.
>
> Therefore, I would propose to introduce tagging in Belgium to tag towpaths.
>
>
> There are two ways to achieve this:
>
> - A towpath is typically a specific type of service road, so we can add 
> `service=towpath`
>
> - In the UK, the towpaths are tagged with `towpath=yes`
>
> Note that towpaths in Flanders are mostly signposted with an official sign, 
> even though that this is a bit of a legal remnant of a previous era. However, 
> it makes it very explicit and thus unambiguous to map.
>
> But now, for the serious questions:
>
> - what are your thoughts of mapping them somehow? IMHO it is an added value 
> and I'm quite in favour of them.
>
> - What is the best way of mapping them? I'm a bit on the edge of the options 
> above: `service=towpath` is IMHO semantically the most correct form, as it 
> indicates that it is a service road originally built for towing. 
> `towpath=yes` reeks more of the legal status (i.e. having a formal road sign 
> indicating 'jaagpad'). The latter has the advantage of already being in use 
> in the UK with over 3500 instances according to taginfo. service=towpath is 
> not in use at the moment.
>
>
> PS: fun etymological fact: the English verb 'to tow' is derived from the 
> Dutch word for rope: 'touw'
>
> --
> Met vriendelijke groeten,
> Pieter Vander Vennet
>
> ___
> Talk-be mailing list
> Talk-be@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-be

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

Re: [Talk-it] Via Chiusi a Roma

2020-03-03 Thread Andrea Musuruane

Credo intendesse dire che non è inserito nel database di OSM.

Ciao,

Andrea


On Tue, Mar 3, 2020 at 3:58 PM Angelo Corsaro 
wrote:

>
> Il 52 esiste..
>
> Angelo
>
> Il 03/03/20 14:44, Damjan Gerl ha scritto:
> > La logica dovrebbe essere questa:
> > siccome il civico 52 non esiste cerca la via chiusi nel comune di roma e
> ne trova alcuni, visualizzati in ordine sparso.
> >
> > Per trovare come primo risultato quella giusta a Roma città devi
> scrivere "via chiusi, roma, roma"
> >
> > Damjan
> >
> >
> > -- Original Header ---
> >
> >  From  : "Cascafico Giovanni" cascaf...@gmail.com
> > To  : "openstreetmap list - italiano" talk-it@openstreetmap.org
> > Cc  :
> > Date  : Tue, 3 Mar 2020 14:26:44 +0100
> > Subject : Re: [Talk-it] Via Chiusi a Roma
> >
> >> Premetto che il civico 52 non esiste in nessuno dei match,
> >> strani risultati di Nominatim:
> >>
> >> - "via chiusi 52, roma" [1] restituisce la strada di campagna
> >> ma in "show more results" il secondo match è la via corretta
> >>
> >> - "via chiusi, roma" restituisce la via corretta
> >>
> >> - "52 via chiusi, roma" restituisce la via corretta
> >>
> >>
> >> [1]
> https://nominatim.openstreetmap.org/search.php?q=via+chiusi+52%2C+roma
> >>
> >> Il giorno mar 3 mar 2020 alle ore 10:23 Angelo Corsaro
> >>  ha scritto:
> >>> Buongiorno lista,
> >>> per mio cultura mi sto divertendo con punti GPS, distanza, etc e mi
> sono
> >>> imbattuto in una cosa particolare: Via Chiusi 52 a Roma. Se su OSM
> cerco
> >>> questo indirizzo completo, mi ritrovo a Nettuno, inserendo solo Via
> >>> Chiusi, Roma, trovo la strada in oggetto.
> >>> Ancora peggio se cerco prima via Chiusi 52 e poi via Chiusi, trovo
> >>> sempre la strada a Nettuno.
> >>> Non credo che sia un problema di Nominatim, ma vorrei capire (se
> dovessi
> >>> trovare altri casi come questo) se e come modificare i dati in OSM.
> >>>
> >>> Ciao,
> >>> Angelo
> >>>
> >>> PS con Google non esiste questo problema.
> >>>
> >>> ___
> >>> Talk-it mailing list
> >>> Talk-it@openstreetmap.org
> >>> https://lists.openstreetmap.org/listinfo/talk-it
> >> ___
> >> Talk-it mailing list
> >> Talk-it@openstreetmap.org
> >> https://lists.openstreetmap.org/listinfo/talk-it
> >>
> > ___
> > Talk-it mailing list
> > Talk-it@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-it
>
>
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [Talk-it] Scout Morciano

2020-03-03 Thread Alessandro Oggioni

Grazie molto interessante ma al momento viene indicato come "temporarily 
disabled”.
Qualcuno ha altri esempi di script come questo?
Grazie

Alessandro

> On 3 Mar 2020, at 00:02, Andrea Albani  wrote:
> 
> E' stata creata con il plugin "WP GPX Maps" [1] per Wordpress che sfrutta due 
> note librerie javascript: Leaflet per la mappa e chart.js per il grafico con 
> l'altimetria.
> 
> Ciao
> 
> [1] https://wordpress.org/plugins/wp-gpx-maps/ 
> 
> Il giorno lun 2 mar 2020 alle ore 23:13 Lorenzo Pesci  > ha scritto:
> Buona sera a tutti, 
> Ho trovato interessante questa pagina che evidenzia percorsi escursionistici 
> e dislivelli usando Osm come base.
> Secondo voi come è stata creata ?
> Con Umap forse? Qgis?
> 
> https://www.scoutmorciano.it/?page_id=1602 
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org 
> https://lists.openstreetmap.org/listinfo/talk-it 
> 
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it

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

Re: [Talk-it] Via Chiusi a Roma

2020-03-03 Thread Angelo Corsaro



Il 52 esiste..

Angelo

Il 03/03/20 14:44, Damjan Gerl ha scritto:

La logica dovrebbe essere questa:
siccome il civico 52 non esiste cerca la via chiusi nel comune di roma e ne 
trova alcuni, visualizzati in ordine sparso.

Per trovare come primo risultato quella giusta a Roma città devi scrivere "via 
chiusi, roma, roma"

Damjan


-- Original Header ---

 From  : "Cascafico Giovanni" cascaf...@gmail.com
To  : "openstreetmap list - italiano" talk-it@openstreetmap.org
Cc  :
Date  : Tue, 3 Mar 2020 14:26:44 +0100
Subject : Re: [Talk-it] Via Chiusi a Roma


Premetto che il civico 52 non esiste in nessuno dei match,
strani risultati di Nominatim:

- "via chiusi 52, roma" [1] restituisce la strada di campagna
ma in "show more results" il secondo match è la via corretta

- "via chiusi, roma" restituisce la via corretta

- "52 via chiusi, roma" restituisce la via corretta


[1] https://nominatim.openstreetmap.org/search.php?q=via+chiusi+52%2C+roma

Il giorno mar 3 mar 2020 alle ore 10:23 Angelo Corsaro
 ha scritto:

Buongiorno lista,
per mio cultura mi sto divertendo con punti GPS, distanza, etc e mi sono
imbattuto in una cosa particolare: Via Chiusi 52 a Roma. Se su OSM cerco
questo indirizzo completo, mi ritrovo a Nettuno, inserendo solo Via
Chiusi, Roma, trovo la strada in oggetto.
Ancora peggio se cerco prima via Chiusi 52 e poi via Chiusi, trovo
sempre la strada a Nettuno.
Non credo che sia un problema di Nominatim, ma vorrei capire (se dovessi
trovare altri casi come questo) se e come modificare i dati in OSM.

Ciao,
Angelo

PS con Google non esiste questo problema.

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

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


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



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

Re: [Talk-it] Via Chiusi a Roma

2020-03-03 Thread Martin Koppenhoefer



sent from a phone

> On 3. Mar 2020, at 10:25, Andrea Musuruane  wrote:
> 
> Prova a scrivere il numero civico prima, in questo modo: "52 , Via Chiusi, 
> Roma"


non mi sembra un formato usato in Italia?

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

Re: [OSM-talk-be] #equalstreetnames

2020-03-03 Thread Karel Adams

Seppe, en collega-mappers,

Neem me mijn scepsis niet kwalijk, maar ik vraag me toch af we hier als
mappers wel aan de kar moeten trekken. Voorzover ik zie is het onze taak
om onze database te onderhouden, en aan te passen aan de permanente
stroom van wijzigende informatie; en om uit te kijken naar mechanismes
om de kwaliteit van ons aanbod te verbeteren, en om de kwantiteit uit te
breiden.

We kunnen en willen uiteraard graag ten dienste staan van eenieder die
onze database wil raadplegen! Bv. voor het opzetten van
Overpass-queries. Maar ik word een beetje schuw bij het entoesiasme voor
een dergelijke "politiek correcte" actie. Naar mijn (niet altijd even
bescheiden) mening is het de essentie van OSM om de feiten en de
werkelijkheid op te volgen, niet om ze aan te sturen.

Van op afstand bekeken, eventjes ruimer dan OSM: straten werden en
worden (soms) vernoemd naar beroemde personen, en het is een historisch
gegeven dat beroemde personen overwegend mannelijk zijn. Men kan dat
betreuren, maar het is niet anders. Er is terzake een inhaalbeweging aan
de gang, dat werd wel tijd, en mettertijd zal zich dat automatisch ook
weerspiegelen in de straatnamen. Als we al wel willen zo'n namen
invoeren, ik vind dat eigenlijk maar een 19de-eeuwse mode; misschien
kunnen we ze beter helemaal afvoeren. Maar als het dan toch aan de orde
is, dan wil ik graag aan de vroede moederen en vaderen van de stad
Mechelen voorstellen om een straat te vernoemen naar mevrouw Adèle Colson.

(English version, freely translated, for the sake of continuity - but
reactions in any Belgian language much preferred, for the sake of Belgium!)

Seppe, and all,

Excuse my scepticism, but I am unsure if this is a project where we, the
OSM mappers, should be on the forefront of action. Our vocation, as I
see it, is to keep our database up to date, adapting to the permanent
stream of change. And of course we should, and do, find novel ways to
improve the database, both in quantity and in quality.

We are of course gladly available to assist anybody in consulting our
database; through Overpass queries, for only one example. I am however
wary of our involvement in actions "politically correct" like this one
seems to be; I much prefer we limit ourselves to following facts, and
their endless changes; we should not seek to steer them.

My 0.02 € :)

Karel

On 2020-03-03 11:37, Santens Seppe wrote:

Hi all,

Today, #equalstreetnames was launched, something Open Knowledge / OSM
Belgium (among others) can be very proud of if you ask me. The project
combines OSM and Wikidata (+ extra data crowdsourced during a
workshop) to make this map: https://equalstreetnames.brussels/
(stunning isn’t it?). More info on why an how can be found in this
blogpost:
https://be.okfn.org/2020/03/03/equalstreetnames-brussels-launch-of-open-data-visualisation/

Of course, you can help spread the word, e.g. by sharing

https://www.facebook.com/OpenKnowledgeBE/photos/a.376589912722798/1030439804004469/?type=3

https://twitter.com/OpenKnowledgeBE/status/1234754767756386304

https://www.linkedin.com/posts/open-knowledge-belgium_opendata-activity-6640521647684100096-GvRU

Best regards,

Seppe

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

Re: [OSM-talk-fr] Inventaire existant des arbres d'une communauté d'agglomération

2020-03-03 Thread Leroy Olivier

Bonjour Romain,

Voila ce que j'avais fait pour les arbres de Lyon et Saint-Etienne :

https://wiki.openstreetmap.org/wiki/Les_arbres_de_la_ville_de_Saint-%C3%89tienne
https://wiki.openstreetmap.org/wiki/User:Defuneste/Les_alignements_d%27arbres_de_Lyon_M%C3%A9tropole

Dans ce que tu mentionnes :
 - Quercus petrae est les nom scientifique ou latin et correspond à la clef
species
- Chene pedoncule : correspond de ce que je comprends plus à species:fr

Ici ce sont bien des noms d'espèces donc autant garder la précision, un
taxon c'est un groupe dont la hiérarchie est pas toujours définit, comme
par exemple les pommiers (normalement cela serait un genre mais tu peux
avoir plusieurs genre de pommier, je ne sais pas où en sont les botanistes
et c'est eux l'autorité).

- classe d'age : ici pas d'avis meme si c'est interessant, attention
cependant tu peux avoir des dates de plantation qui ne sont pas l'age de
l'arbre (arbre planté avec plus ou moins d'années) même si cela jouera peu
à la fin. Je me demande souvent si les classes ne sont pas une meilleur
option.

- L'information ARBRE D'ALIGNEMENT: perso j'ai tout mis en arbre isolé, le
desaventage d'alignement est que tu peux pas changer l'espèce

- forme des feuilles :  j'ai essayé un tableau ici
https://wiki.openstreetmap.org/wiki/Tag:natural%3Dtree/List_of_Genus,_Leaf_cycle,_Leaf_type
avec le defaut que c'est pas toujours simple au niveau du genre

- l'état sanitaire c'est intéressant après je sais pas ci cela l'est dans
OSM, c'est interessant pour une collectivité meme si globalement les arbres
urbains ont la vie dure


Je ne suis pas allé au bout des imports car j'avais un peu peur de
conflation (et ne connaissait pas conflator) mais Jérôme de Grenoble est
venu il y trois semaines nous le montrer (merci beaucoup à lui!) et je
pense poursuivre.

Bon courage !

olivier



Le mar. 3 mars 2020 à 13:02, Romain  a écrit :

> Bonjour à toutes et à tous,
>
> Je travaille avec une communauté d'agglomération sur l'ouverture de leurs
> données. La collectivité souhaite encourager la contribution citoyenne à
> ces données, notamment via OpenStreetMap lorsque le sujet s'y prête.
>
> Sur le sujet de la biodiversité, et plus particulièrement des arbres, la
> collectivité dispose d'un registre résultant d'un inventaire sur une partie
> du territoire. Cet inventaire n'est pas exhaustif, mais dans la zone
> inventoriée les informations sont détaillées et de qualité. Il contient
> environ 3500 arbres.
>
> Nous avons pensé qu'il pourrait éventuellement être intéressant d'intégrer
> ces données dans OSM, dans l’idée de faciliter la participation et la
> réconciliation des données avec leur SIG.
>
> J'ai pu trouver des informations sur ce sujet sur les pages :
> - https://wiki.openstreetmap.org/wiki/City_tree_registers
> - https://wiki.openstreetmap.org/wiki/Nice,_France/Trees_Import
> - https://wiki.openstreetmap.org/wiki/Tag:natural%3Dtree
> - https://wiki.openstreetmap.org/wiki/Key:taxon
>
> Voici un exemple de modèle de tags que nous pourrions utiliser à partir
> d'un exemple issu de cet inventaire :
> - QUERCUS PETRAEA : taxon et/ou species. Peut-être qu'une règle
> permettrait de déduire le Genre, ici QUERCUS, pour le tag taxon:genus et/ou
> genus.
> - CHENE PEDONCULE : taxon:fr. Idem ci-dessus pour le Genre, ici CHENE,
> pour le tag genus:fr
> - Classe d'age JEU/ADU/MATU/ANC : éventuellement à convertir en start_date=
> - L'information ARBRE D'ALIGNEMENT pourrait peut-être servir à créer une
> ligne de type natural=tree_row
> - Il n'y a pas d'informations sur la forme des feuilles mais elle pourrait
> surement être déduite de l’espèce
> - Et d'autres informations comme vigueur, état sanitaire, pathologies,
> défaut principal, etc... dont nous ne sommes pas sûrs de la pertinence dans
> OSM.
>
> Pour information je n’ai jamais réalisé d’imports OSM mais j’ai pris
> connaissances des bonnes pratiques sur la page
> https://wiki.openstreetmap.org/wiki/FR:Import/Guidelines.
>
> Avant d'aller plus loin dans nos recherches pensez-vous que cette approche
> soit appropriée ?
>
> Merci et bonne journée,
>
> Romain
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>


-- 
Olivier Leroy
Docteur Géographie et Environnement
Post-doctorant EVS IMU GOURAMIC
06.18.37.18.08
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [OSM-talk-fr] Mise à jour BANO

2020-03-03 Thread Vincent de Château-Thierry

Salut Pierre-Yves,

> De: "Pierre-Yves Mevel via Talk-fr" 
> 
> Désolé de remettre le sujet sur la table mais, après avoir parcouru
> les différents échanges sur le sujet, il me semble qu'un point n'a
> pas été abordé concernant la BANO. Depuis de nombreuses années, je
> contribue à la création de points adresse sur OSM et je m'en sers
> pour alimenter la base adresse de ma communauté d'agglo grâce aux
> extractions quotidiennes que l'on peut trouver sur
> http://bano.openstreetmap.fr/data/ . A priori, ces fichiers sont mis
> à jour quotidiennement. Si je lis correctement le très complet
> message que Vincent (dct) a écrit sur cette liste le 11 novembre
> dernier, le passage en v2 ne devait pas changer cela.

Oui dans mon message je disais que les exports ne changeaient pas. J'aurais du 
dire : "pas pour l'instant". L'objectif est bien que tout bascule sur une seule 
instance de BANO (celle qu'on appelle V2). Les exports depuis cette nouvelle 
instance sont un gros chantier, sur lequel je suis pile actuellement (cf le 
dernier commit en date [1]). Lorsque ce ticket sera terminé, alors on basculera 
l'alimentation de http://bano.openstreetmap.fr/data/ sur la V2, mise à jour 
quotidiennement. 

> Cependant, je constate que les fichiers concernant l'Ille-et-Vilaine
> (et sans doute les autres départements) n'évoluent guère depuis le
> début de l'année. Ainsi, si des changements faits le 18 décembre
> sont bien intégrés dans le SHP (par exemple,
> https://www.openstreetmap.org/node/7066812399 ), d'autres, faits le
> 6 février, n'y apparaissent pas (cf.
> https://www.openstreetmap.org/node/7191078724 ) et ils ne figurent
> pas non plus en vert sur
> http://tile.openstreetmap.fr/~cquest/leaflet/bano.html .

J'avoue ne pas trop surveiller au jour le jour la V1, mais ton message laisse 
penser que la base OSM qui l'alimente a du retard (litote). Et comme c'est 
jusque là cette V1 qui alimente aussi le rendu carto BANO, on y constate le 
même retard. C'est sur la pile de trucs à faire de Christian que de brancher le 
rendu carto sur la V2.  

> Ai-je loupé un épisode concernant le lieu où trouver ces données ?
> Dans ce cas, ne serait-il pas souhaitable de l'indiquer sur la page
> dédiée de data.gouv.fr (
> https://www.data.gouv.fr/fr/datasets/base-d-adresses-nationale-ouverte-bano/
> ) ?
> Ou bien y a-t-il un problème de moissonnage qui empêche l'extraction
> quotidienne de se dérouler correctement ?

Non tu n'as pas loupé de message, la comm' sur BANO est loin d'être au top  
j'avoue /o\. En tout cas ce sujet des exports est le dernier "gros" sujet qui 
empêche la bascule de tout le système BANO sur une version unique, c'est bien 
ce qui me motive pour que ça ne s'éternise pas trop. Donc j'y travaille et je 
compte bien annoncer cette vrai v2 complète rapidement. Je n'ose pas dire "fin 
de ce mois" car c'est le meilleur moyen de ne pas tenir le délai. Donc non je 
l'ai pas dit :)

vincent

[1] 
:https://github.com/osm-fr/bano/commit/ba496b90a1ba37a919d9576694fd89a1c0cf0428

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

Re: [Talk-it] Via Chiusi a Roma

2020-03-03 Thread Damjan Gerl

La logica dovrebbe essere questa:
siccome il civico 52 non esiste cerca la via chiusi nel comune di roma e ne 
trova alcuni, visualizzati in ordine sparso.

Per trovare come primo risultato quella giusta a Roma città devi scrivere "via 
chiusi, roma, roma"

Damjan


-- Original Header ---

From  : "Cascafico Giovanni" cascaf...@gmail.com
To  : "openstreetmap list - italiano" talk-it@openstreetmap.org
Cc  : 
Date  : Tue, 3 Mar 2020 14:26:44 +0100
Subject : Re: [Talk-it] Via Chiusi a Roma

> Premetto che il civico 52 non esiste in nessuno dei match,
> strani risultati di Nominatim:
> 
> - "via chiusi 52, roma" [1] restituisce la strada di campagna
> ma in "show more results" il secondo match è la via corretta
> 
> - "via chiusi, roma" restituisce la via corretta
> 
> - "52 via chiusi, roma" restituisce la via corretta
> 
> 
> [1] https://nominatim.openstreetmap.org/search.php?q=via+chiusi+52%2C+roma
> 
> Il giorno mar 3 mar 2020 alle ore 10:23 Angelo Corsaro
>  ha scritto:
> >
> > Buongiorno lista,
> > per mio cultura mi sto divertendo con punti GPS, distanza, etc e mi sono
> > imbattuto in una cosa particolare: Via Chiusi 52 a Roma. Se su OSM cerco
> > questo indirizzo completo, mi ritrovo a Nettuno, inserendo solo Via
> > Chiusi, Roma, trovo la strada in oggetto.
> > Ancora peggio se cerco prima via Chiusi 52 e poi via Chiusi, trovo
> > sempre la strada a Nettuno.
> > Non credo che sia un problema di Nominatim, ma vorrei capire (se dovessi
> > trovare altri casi come questo) se e come modificare i dati in OSM.
> >
> > Ciao,
> > Angelo
> >
> > PS con Google non esiste questo problema.
> >
> > ___
> > Talk-it mailing list
> > Talk-it@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk-it
> 
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it
> 

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

[OSM-talk-fr] Mise à jour BANO

2020-03-03 Thread Pierre-Yves Mevel via Talk-fr

Bonjour,

Désolé de remettre le sujet sur la table mais, après avoir parcouru les
différents échanges sur le sujet, il me semble qu'un point n'a pas été
abordé concernant la BANO. Depuis de nombreuses années, je contribue à la
création de points adresse sur OSM et je m'en sers pour alimenter la base
adresse de ma communauté d'agglo grâce aux extractions quotidiennes que
l'on peut trouver sur http://bano.openstreetmap.fr/data/. A priori, ces
fichiers sont mis à jour quotidiennement. Si je lis correctement le très
complet message que Vincent (dct) a écrit sur cette liste le 11 novembre
dernier, le passage en v2 ne devait pas changer cela.

Cependant, je constate que les fichiers concernant l'Ille-et-Vilaine (et
sans doute les autres départements) n'évoluent guère depuis le début de
l'année. Ainsi, si des changements faits le 18 décembre sont bien intégrés
dans le SHP (par exemple, https://www.openstreetmap.org/node/7066812399),
d'autres, faits le 6 février, n'y apparaissent pas (cf.
https://www.openstreetmap.org/node/7191078724) et ils ne figurent pas non
plus en vert sur http://tile.openstreetmap.fr/~cquest/leaflet/bano.html.

Ai-je loupé un épisode concernant le lieu où trouver ces données ? Dans ce
cas, ne serait-il pas souhaitable de l'indiquer sur la page dédiée de
data.gouv.fr (
https://www.data.gouv.fr/fr/datasets/base-d-adresses-nationale-ouverte-bano/)
?
Ou bien y a-t-il un problème de moissonnage qui empêche l'extraction
quotidienne de se dérouler correctement ?

Dans l'attente de vous lire,

Bonne journée,

Pierre-Yves, aka Pymouss
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [OSM-talk-fr] [PROPOSITION] [SANTé MENTALE][CMP] amenity=hospital et FINESS

2020-03-03 Thread osm . sanspourriel


name=le nom relativement court, CMP de Chauvigny

official_name= le nom super long que personne n'utilise. Centre
médico-psychiatrique de Chauvigny ?

short_name=CMP Chauvigny

Le 03/03/2020 à 13:57, marc marc - marc_marc_...@hotmail.com a écrit :

Le 03.03.20 à 13:54, Jacques Lavignotte a écrit :

alt_name=Le nom long du CMP du centre Hospitalier Spécialisé
name=CMP de Chauvigny

name=Le nom long du CMP du centre Hospitalier Spécialisé
short_name=le nom court
:)
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr



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

Re: [Talk-it] Via Chiusi a Roma

2020-03-03 Thread Cascafico Giovanni

Premetto che il civico 52 non esiste in nessuno dei match,
strani risultati di Nominatim:

- "via chiusi 52, roma" [1] restituisce la strada di campagna
ma in "show more results" il secondo match è la via corretta

- "via chiusi, roma" restituisce la via corretta

- "52 via chiusi, roma" restituisce la via corretta


[1] https://nominatim.openstreetmap.org/search.php?q=via+chiusi+52%2C+roma

Il giorno mar 3 mar 2020 alle ore 10:23 Angelo Corsaro
 ha scritto:
>
> Buongiorno lista,
> per mio cultura mi sto divertendo con punti GPS, distanza, etc e mi sono
> imbattuto in una cosa particolare: Via Chiusi 52 a Roma. Se su OSM cerco
> questo indirizzo completo, mi ritrovo a Nettuno, inserendo solo Via
> Chiusi, Roma, trovo la strada in oggetto.
> Ancora peggio se cerco prima via Chiusi 52 e poi via Chiusi, trovo
> sempre la strada a Nettuno.
> Non credo che sia un problema di Nominatim, ma vorrei capire (se dovessi
> trovare altri casi come questo) se e come modificare i dati in OSM.
>
> Ciao,
> Angelo
>
> PS con Google non esiste questo problema.
>
> ___
> 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

[OSM-talk-be] RFC: explicit tagging of 'Jaagpaden'

2020-03-03 Thread Pieter Vander Vennet

Hello everyone,

Even though the legal restrictions of 'Jaagpaden' (towpaths in proper
English) is already described in detail on the wiki
, it would still be
useful to reflect the special status explicitly, in our case to give a
comfort bonus in cycling route planning but also for historical purposes.

For context, a 'jaagpad', 'trekpad' or towing path is a path that used
to be used to (literally) tow boats through the canals, either with
manpower or horsepower and a rope attached to the boat - hence there are
never trees between a towpath.

With the rise of cheap and powerful combustion engines, this practice
became disused and towpaths became service roads and cycleways.

As stated, these often are excellent and heavily preferred by cyclists.
Normally, they are wide, asphalted, there are very few cars and
especially: there is the very nice scenery of the canal.

Therefore, I would propose to introduce tagging in Belgium to tag towpaths.


There are two ways to achieve this:

- A towpath is typically a specific type of service road, so we can add
`service=towpath`

- In the UK, the towpaths are tagged with `towpath=yes`

Note that towpaths in Flanders are mostly signposted with an official
sign, even though that this is a bit of a legal remnant of a previous
era. However, it makes it very explicit and thus unambiguous to map.

But now, for the serious questions:

- what are your thoughts of mapping them somehow? IMHO it is an added
value and I'm quite in favour of them.

- What is the best way of mapping them? I'm a bit on the edge of the
options above: `service=towpath` is IMHO semantically the most correct
form, as it indicates that it is a service road originally built for
towing. `towpath=yes` reeks more of the legal status (i.e. having a
formal road sign indicating 'jaagpad'). The latter has the advantage of
already being in use in the UK with over 3500 instances according to
taginfo. service=towpath is not in use at the moment.


PS: fun etymological fact: the English verb 'to tow' is derived from the
Dutch word for rope: 'touw'

-- 
Met vriendelijke groeten,
Pieter Vander Vennet

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

Re: [OSM-talk-fr] Projet du mois de mars - #balanceTaBorne

2020-03-03 Thread Stéphane Péneau




Un contributeur à fait le boulot :
https://www.data.gouv.fr/fr/datasets/r/601cffc9-d63e-45da-a7d4-82461223c077

J'ai vu, mais c'est une vieille version (2018), et elle n'est pas 
récupérée par le script.


Stf

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

Re: [OSM-talk-fr] [PROPOSITION] [SANTé MENTALE][CMP] amenity=hospital et FINESS

2020-03-03 Thread marc marc

Le 03.03.20 à 13:54, Jacques Lavignotte a écrit :
> alt_name=Le nom long du CMP du centre Hospitalier Spécialisé
> name=CMP de Chauvigny

name=Le nom long du CMP du centre Hospitalier Spécialisé
short_name=le nom court
:)
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [OSM-talk-fr] [PROPOSITION] [SANTé MENTALE][CMP] amenity=hospital et FINESS

2020-03-03 Thread Jacques Lavignotte


Proposition :


alt_name=Le nom long du CMP du centre Hospitalier Spécialisé
amenity=social_facility
name=CMP de Chauvigny
operator=Centre Hospitalier Laborit
ref:FR:FINESS=86012
social_facility:for=mental_health;children
social_facility=ambulatory_care
type:FR:FINESS=156




Le 02/03/2020 à 01:03, Philippe Verdy a écrit :

Pas vraiment si on a aussi besoin de
"healthcare:speciality=psychiatry" (domaine de la santé) et de
"social_facility:*=*" (domaine social) : deux classifications
parallèles.
On poiurrait dire que tout ce qui est du domaine de la santé fait
partie du domaine social (comme notre sécurité sociale).
Dans ce cas social_facilty deviendrait *racine* de tous les services
médicaux, y compris cabinets de médecins (y compris médecine du
travail, médecine légale), pharmaciens, labos d'analyse, centres de
cure, plasticiens, orthésistes, boutiques de matériel médical, et tous
thérapeuthes (même ceux non conventionnés dans le domaine privé et
hors sécurité sociale et aides sociales publiques).
C'est un peu limite, et je pense que les deux classifications peuvent
coexister pour éviter de tout mélanger, on les mettra les deux
ensemble seulement où c'est approprié.
Concernant FINESS sur les établissements conventionnés, tout devrait
avoir des clés "social_facility" et probablement aussi "health_care";
certains auront aussi d'autres clés (tourisme, restauration, services
financiers, shop=*...)

Le dim. 1 mars 2020 à 23:24, Yves P.  a écrit :


  amenity=social_facility
  healthcare=centre
  healthcare:speciality=psychiatry




  [...]
  social_facility=ambulatory_care
  social_facility:for=mental_health
  type:FR:FINESS=156

Je pense qu'il y a tout ce qu'il faut.

Vos avis ?



Les clés healthcare font doublon avec les clés social_facility ?

__
Yves
___
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



--
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] Projet du mois de mars - #balanceTaBorne

2020-03-03 Thread Yves P.

>
> Pour le Doubs, le fichier est présent sur data.gouv, mais est mal encodé
> ce qui le rend inutilisable par le script qui consolide tous les fichiers
> des différentes collectivités.
>
> J'ai demandé à ce qu'il soit corrigé :
>
Merci 

Un contributeur à fait le boulot :
https://www.data.gouv.fr/fr/datasets/r/601cffc9-d63e-45da-a7d4-82461223c077

__
Yves

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

[OSM-talk-fr] Inventaire existant des arbres d'une communauté d'agglomération

2020-03-03 Thread Romain

Bonjour à toutes et à tous,

Je travaille avec une communauté d'agglomération sur l'ouverture de leurs 
données. La collectivité souhaite encourager la contribution citoyenne à ces 
données, notamment via OpenStreetMap lorsque le sujet s'y prête.

Sur le sujet de la biodiversité, et plus particulièrement des arbres, la 
collectivité dispose d'un registre résultant d'un inventaire sur une partie du 
territoire. Cet inventaire n'est pas exhaustif, mais dans la zone inventoriée 
les informations sont détaillées et de qualité. Il contient environ 3500 arbres.

Nous avons pensé qu'il pourrait éventuellement être intéressant d'intégrer ces 
données dans OSM, dans l’idée de faciliter la participation et la 
réconciliation des données avec leur SIG.

J'ai pu trouver des informations sur ce sujet sur les pages :
- https://wiki.openstreetmap.org/wiki/City_tree_registers 
- https://wiki.openstreetmap.org/wiki/Nice,_France/Trees_Import
- https://wiki.openstreetmap.org/wiki/Tag:natural%3Dtree
- https://wiki.openstreetmap.org/wiki/Key:taxon

Voici un exemple de modèle de tags que nous pourrions utiliser à partir d'un 
exemple issu de cet inventaire :
- QUERCUS PETRAEA : taxon et/ou species. Peut-être qu'une règle 
permettrait de déduire le Genre, ici QUERCUS, pour le tag taxon:genus et/ou 
genus.
- CHENE PEDONCULE : taxon:fr. Idem ci-dessus pour le Genre, ici CHENE, 
pour le tag genus:fr
- Classe d'age JEU/ADU/MATU/ANC : éventuellement à convertir en 
start_date=
- L'information ARBRE D'ALIGNEMENT pourrait peut-être servir à créer 
une ligne de type natural=tree_row
- Il n'y a pas d'informations sur la forme des feuilles mais elle 
pourrait surement être déduite de l’espèce
- Et d'autres informations comme vigueur, état sanitaire, pathologies, 
défaut principal, etc... dont nous ne sommes pas sûrs de la pertinence dans OSM.

Pour information je n’ai jamais réalisé d’imports OSM mais j’ai pris 
connaissances des bonnes pratiques sur la page 
https://wiki.openstreetmap.org/wiki/FR:Import/Guidelines 
.

Avant d'aller plus loin dans nos recherches pensez-vous que cette approche soit 
appropriée ?

Merci et bonne journée,

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

[OSM-talk-be] #equalstreetnames

2020-03-03 Thread Santens Seppe

Hi all,

Today, #equalstreetnames was launched, something Open Knowledge / OSM Belgium 
(among others) can be very proud of if you ask me. The project combines OSM and 
Wikidata (+ extra data crowdsourced during a workshop) to make this map: 
https://equalstreetnames.brussels/ (stunning isn't it?). More info on why an 
how can be found in this blogpost: 
https://be.okfn.org/2020/03/03/equalstreetnames-brussels-launch-of-open-data-visualisation/

The project already got some nice media coverage, e.g. 
https://www.bruzz.be/samenleving/nauwelijks-brusselse-straten-naar-vrouwen-vernoemd-trage-inhaalbeweging-2020-03-03
 and 
https://www.rtbf.be/info/dossier/les-grenades/detail_combattre-le-sexisme-en-rebaptisant-les-rues-de-bruxelles?id=10446433

Of course, you can help spread the word, e.g. by sharing
https://www.facebook.com/OpenKnowledgeBE/photos/a.376589912722798/1030439804004469/?type=3
https://twitter.com/OpenKnowledgeBE/status/1234754767756386304
https://www.linkedin.com/posts/open-knowledge-belgium_opendata-activity-6640521647684100096-GvRU


Best regards,

Seppe

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

[talk-ph] OSM Philippines celebrates Open Data Day 2020 with 3 events on March 7

2020-03-03 Thread maning sambale

Dear everyone,

Open Data Day will be celebrated all around the world on March 7.  Our
community has 3 events happening that day.
Choose an event you want to join!

1. OSM-PH Open Data Day 2020 at co.lab in Pasig City.  Morning
mapathon and afternoon talks -
https://www.facebook.com/events/2439505106154288/
2. Mapatime! sa SLU, Baguio City - https://ti.to/mapatime/slu-osmapaaralan
3. SlumBEAR Mapping Party an open data pajama mapathon by Mapbeks at
Farenheight Cafe and Fitness Center New Manila -
https://www.facebook.com/events/240026903659097/

Enjoy your open data day!  Happy mapping!
-- 
cheers,
maning
--
"Freedom is still the most radical idea of all" -N.Branden
https://github.com/maning
http://twitter.com/maningsambale
--

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

Re: [OSM-talk-fr] Projet du mois de mars - #balanceTaBorne

2020-03-03 Thread Stéphane Péneau


Le 01/03/2020 à 14:34, Yves P. a écrit :
Par exemple, il n’y a qu’une seule borne dans tout le Jura et rien 
dans le Doubs. Osmose 



Pour le Doubs, le fichier est présent sur data.gouv, mais est mal encodé 
ce qui le rend inutilisable par le script qui consolide tous les 
fichiers des différentes collectivités.


J'ai demandé à ce qu'il soit corrigé :

https://www.data.gouv.fr/fr/datasets/irve-syded-recensement-et-information-doubs/#discussion-5e5e2687634f416ca89964c5

Stf

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

[OSM-talk-fr] OrthoHR départements 32 (Gers) et 82 (Tarn-et-Garonne)...

2020-03-03 Thread Christian Quest

Voilà, comme indiqué hier, je viens d'ajouter les orthos HR du 32 et 82 
sur wms.openstreetmap.fr (couches orthohr_2019 et tous_fr)


--
Christian Quest - OpenStreetMap France


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

Re: [Talk-it] Via Chiusi a Roma

2020-03-03 Thread Andrea Musuruane

Prova a scrivere il numero civico prima, in questo modo: "52 , Via Chiusi,
Roma"

Ciao,

Andrea



On Tue, Mar 3, 2020 at 10:23 AM Angelo Corsaro 
wrote:

> Buongiorno lista,
> per mio cultura mi sto divertendo con punti GPS, distanza, etc e mi sono
> imbattuto in una cosa particolare: Via Chiusi 52 a Roma. Se su OSM cerco
> questo indirizzo completo, mi ritrovo a Nettuno, inserendo solo Via
> Chiusi, Roma, trovo la strada in oggetto.
> Ancora peggio se cerco prima via Chiusi 52 e poi via Chiusi, trovo
> sempre la strada a Nettuno.
> Non credo che sia un problema di Nominatim, ma vorrei capire (se dovessi
> trovare altri casi come questo) se e come modificare i dati in OSM.
>
> Ciao,
> Angelo
>
> PS con Google non esiste questo problema.
>
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

[Talk-it] Via Chiusi a Roma

2020-03-03 Thread Angelo Corsaro


Buongiorno lista,
per mio cultura mi sto divertendo con punti GPS, distanza, etc e mi sono 
imbattuto in una cosa particolare: Via Chiusi 52 a Roma. Se su OSM cerco 
questo indirizzo completo, mi ritrovo a Nettuno, inserendo solo Via 
Chiusi, Roma, trovo la strada in oggetto.
Ancora peggio se cerco prima via Chiusi 52 e poi via Chiusi, trovo 
sempre la strada a Nettuno.
Non credo che sia un problema di Nominatim, ma vorrei capire (se dovessi 
trovare altri casi come questo) se e come modificare i dati in OSM.


Ciao,
Angelo

PS con Google non esiste questo problema.

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

49 matches

Mail list logo