Re: [talk-au] Uncredited use of OSM map

[Phil Wyatt]

Looks like the old links are dead but all have been corrected

 

https://www.justice.tas.gov.au/strategic-infrastructure-projects/new-northern-prison#New-site-location

https://www.justice.tas.gov.au/__data/assets/image/0003/544584/DJustice-prison-map.png

https://www.justice.tas.gov.au/__data/assets/pdf_file/0004/571540/Flat-Map-Deloraine-to-Westbury.pdf

 

From: Ewen Hill  
Sent: Friday, 19 June 2020 6:55 PM
To: Phil Wyatt 
Cc: Charles Gregory ; talk-au 
Subject: Re: [talk-au] Uncredited use of OSM map

 

Top work Charles and Phil. Keeping 'em honest.

 

 

On Fri, 19 Jun 2020, 5:47 PM Phil Wyatt mailto:p...@wyatt-family.com> > wrote:

I have sent an appropriate message to the agency and the appropriate Government 
Minister and requested an update to the website and map with the correct 
attribution.

 

Cheers - Phil

 

From: Charles Gregory mailto:c...@chuq.net> > 
Sent: Friday, 19 June 2020 5:13 PM
To: talk-au mailto:talk-au@openstreetmap.org> >
Subject: [talk-au] Uncredited use of OSM map

 

Hi all,

 

The map rendering used by the Tasmanian Government in a recent announcement 
about a new prison site in Northern Tasmania looked familiar..

https://www.justice.tas.gov.au/__data/assets/pdf_file/0004/571540/Northern-Regional-Prison-map.pdf

 

Compared to OSM, there are some features missing, some other features are 
rendered differently.  It could well be a different site/source with similar 
rendering:

https://www.openstreetmap.org/#map=13/-41.5123/146.7475  

 

(Screenshots of both: https://imgur.com/a/7EE2GXV)

 

Just sharing for interest's sake - not sure if it is worth following up on, or 
making a big deal about?

 

Regards,

Charles

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

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

Re: [talk-au] Uncredited use of OSM map

[Phil Wyatt]

Hi Folks,

 

The web map and PDF have now been updated with the correct attribution.

 

Cheers - Phil

 

From: Ewen Hill  
Sent: Friday, 19 June 2020 6:55 PM
To: Phil Wyatt 
Cc: Charles Gregory ; talk-au 
Subject: Re: [talk-au] Uncredited use of OSM map

 

Top work Charles and Phil. Keeping 'em honest.

 

 

On Fri, 19 Jun 2020, 5:47 PM Phil Wyatt mailto:p...@wyatt-family.com> > wrote:

I have sent an appropriate message to the agency and the appropriate Government 
Minister and requested an update to the website and map with the correct 
attribution.

 

Cheers - Phil

 

From: Charles Gregory mailto:c...@chuq.net> > 
Sent: Friday, 19 June 2020 5:13 PM
To: talk-au mailto:talk-au@openstreetmap.org> >
Subject: [talk-au] Uncredited use of OSM map

 

Hi all,

 

The map rendering used by the Tasmanian Government in a recent announcement 
about a new prison site in Northern Tasmania looked familiar..

https://www.justice.tas.gov.au/__data/assets/pdf_file/0004/571540/Northern-Regional-Prison-map.pdf

 

Compared to OSM, there are some features missing, some other features are 
rendered differently.  It could well be a different site/source with similar 
rendering:

https://www.openstreetmap.org/#map=13/-41.5123/146.7475  

 

(Screenshots of both: https://imgur.com/a/7EE2GXV)

 

Just sharing for interest's sake - not sure if it is worth following up on, or 
making a big deal about?

 

Regards,

Charles

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

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

Re: [OSM-talk] Paid mapping

[John Whelan]

I've seen a lot of poor mapping get replicated in this way by newcomers 
copying the tags.


Cheerio John

Mike Thompson wrote on 2020-06-22 8:25 PM:



On Mon, Jun 22, 2020 at 4:12 PM Mateusz Konieczny via talk 
mailto:talk@openstreetmap.org>> wrote:


Jun 23, 2020, 00:07 by miketh...@gmail.com
:

"except for the preceding, we follow OSM community norms."

This should be enough to ban of all their mapping accounts until
changing their plan
(I assume that they either backtracked that or stopped editing)

They said that they were going to do some additional training for 
their staff.  They did give some indication they would make some 
changes, but I didn't follow up. Part of the problem is that another, 
non local, mapper got really enthusiastic a couple of years ago about 
changing all unpaved roads to highway=track.  Amazon Logistics people 
see this, and if they are adding a road, they perhaps compare it to 
the existing content nearby, and try to mimic that tagging.


Mike


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


--
Sent from Postbox 
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Paid mapping

[Mike Thompson]

On Mon, Jun 22, 2020 at 4:12 PM Mateusz Konieczny via talk <
talk@openstreetmap.org> wrote:

> Jun 23, 2020, 00:07 by miketh...@gmail.com:
>
> "except for the preceding, we follow OSM community norms."
>
> This should be enough to ban of all their mapping accounts until changing
> their plan
> (I assume that they either backtracked that or stopped editing)
>
They said that they were going to do some additional training for their
staff.  They did give some indication they would make some changes, but I
didn't follow up. Part of the problem is that another, non local, mapper
got really enthusiastic a couple of years ago about changing all unpaved
roads to highway=track.  Amazon Logistics people see this, and if they are
adding a road, they perhaps compare it to the existing content nearby, and
try to mimic that tagging.

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

[Talk-us] Whole-US Garmin Map update - 2020-06-20

[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-06-20

Map to visualize what each file contains:


http://daveh.dev.openstreetmap.org/garmin/Lambertus/2020-06-20/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-06-20

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

Re: [Talk-br] Nova proposta de classificação viária - Votação encerrada

[Fernando Trebien]

Nós tivemos 10 votos (sem contar as abstenções) dos quais 7 concordam,
o que dá 70% de aprovação. Contando com o voto do Vítor, que foi fora
do período de votação, são 8 de 11 aprovações, ou 72,7%. No mesmo
artigo diz que até 2015 era aceita a maioria simples com mais de 15
votos, o que não é o caso.

Esse valor de 74% é um tipo de maioria qualificada. No direito
brasileiro, o limiar adotado é de 60%. [1] O nível de 74% é
relativamente incomum no mundo, um dos comuns mais exigentes é o de
2/3 (67%). [2]

Esse processo de votação do OSM é bastante exigente em boa parte
porque se aplica ao mundo todo. No caso, estamos discutindo uma
mudança aplicável apenas ao Brasil, então pode ser difícil obter um
nível de participação tão alto.

No artigo sobre o processo de votação também diz: "todas as sugestões
devem ser levadas em consideração antes de uma proposta ser aprovada
ou rejeitada, a fim de resolver quaisquer deficiências na proposta
original (se houver)." Eu acho que isso que pode estar faltando nesse
caso.

No mesmo artigo, há uma seção para o período "pós-voto" (post-vote). O
template Proposal Page, [3] usado na maioria dos artigos anglófonos de
propostas, suporta o valor "Post-Vote" para o campo status. Se vocês
procurarem no wiki por "Post-Vote," vão encontrar vários artigos de
propostas com uma seção "Post-Vote" onde são discutidos os próximos
passos, onde se discute como tratar dos apontamentos feitos por quem
votou. Me parece que estamos exatamente nesta fase.

[1] https://pt.wikipedia.org/wiki/Maioria_qualificada
[2] https://en.wikipedia.org/wiki/Supermajority#Common_supermajorities
[3] https://wiki.openstreetmap.org/wiki/Template:Proposal_Page

On Fri, Jun 19, 2020 at 5:47 PM Guilherme Braga Alves
 wrote:
>
> Gostaria de compreender quais regras definem a proposta como aprovada. De 
> acordo com a Wiki,
>
> "se a proposta obteve apoio suficiente, seu status pode ser alterado para 
> aprovada. Uma regra geral para 'apoio suficiente' é 8 votos unânimes de 
> aprovação ou pelo menos 10 votos com mais de 74% de aprovação" (tradução 
> livre).
>
> Considerando que a proposta obteve 7 votos 'sim' e 3 votos 'não', o patamar 
> de 74% não foi atingido.
> ___
> Talk-br mailing list
> Talk-br@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-br



-- 
Fernando Trebien

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

Re: [OSM-talk-fr] Alternatives à Mapillary

[Jacques Lavignotte]

Le 22/06/2020 à 23:49, Frédéric Rodrigo a écrit :


Voilà, maintenant, il y a une carte pour visualiser les données

https://mapillary-takeout-web.openstreetmap.fr/map/#5.3/46.318/3.867


Super ! Merci,

J.

up 3.5k photos

--
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] Paid mapping

[John Whelan]

> In case of noticing low quality paid mapping - please, at least leave 
a changeset comment.


I think this is a sensible approach that I'll use in future rather than 
leave an email.


On the comments about the classification we are talking specifically 
about Africa where it is much more difficult to judge the importance of 
a highway from imagery.


/Pierre Béland /came up with a classification scheme in partnership with 
many players. /


/https://wiki.openstreetmap.org/wiki/Highway_Tag_Africa

It has stood the test of time and is normally accepted as the tagging 
standard for highways in Africa.


Many Thanks

Cheerio John

Mateusz Konieczny via talk wrote on 2020-06-22 5:16 PM:


In case of noticing low quality paid mapping - please, at least leave 
a changeset comment.



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


--
Sent from Postbox 
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Paid mapping

[Mateusz Konieczny via talk]

Jun 23, 2020, 00:07 by miketh...@gmail.com:

> "except for the preceding, we follow OSM community norms." 
>
This should be enough to ban of all their mapping accounts until changing their 
plan
 (I assume that they either backtracked that or stopped editing)
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Paid mapping

[Mike Thompson]

I know we are talking about Apple mappers here, but I wanted to point out
the Amazon Logistics mappers have been very responsive to changeset
comments. However:
1) One of their leaders explained their criteria for a track.  There were
about four, and that was followed with "except for the preceding, we follow
OSM community norms."  I responded that they should always follow community
norms.
2) Changeset comments, as is true for a lot of mappers, are not super
helpful, e.g. "Added a track road" (not new information, I could tell that
from the data), and then they cite a generic collection of sources (which
one did you use?). Sometimes the sources don't make sense, such as "Street
Side" when there is no Street Side content in the given area.

Mike

On Mon, Jun 22, 2020 at 3:56 PM Andreas Vilén 
wrote:

> Maybe the mappers think unclassified equals what we call highway=road, as
> in no classification yet determined?
>
> It’s a fairly common misconception among new mappers.
>
> /Andreas
>
> Skickat från min iPhone
>
> > 22 juni 2020 kl. 23:50 skrev Martin Koppenhoefer  >:
> >
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Paid mapping

[Mateusz Konieczny via talk]

Jun 22, 2020, 23:48 by dieterdre...@gmail.com:

>
>
> sent from a phone
>
>
>> On 22. Jun 2020, at 23:18, Mateusz Konieczny via talk 
>>  wrote:
>>
>>> These had been changed from highway unclassified surface unpaved to 
>>> highway=track by a mapper with Apple connections.
>>>
>> Can you link them? I would revert them as tagging for renderer if original 
>> mapping
>> was correct.
>>
>
>
> sure, but how would you know the way is an unpaved unclassified road and not 
> a track? You would need local knowledge. Well, what you could probably guess 
> correctly, is that every settlement will be reachable through at least one 
> road and not just tracks. If a road is the only connection between 2 
> settlements, it is probably a road.
>
I would review aerial and changesets changing that and changeset comments and 
quality
of work of paid mapper and whatever original mapping was done by someone more 
trustworthy.

For example if "unclassified=>track" would be described as
"changing unpaved roads to highway=track" and original would be "marking sole 
road to XYZ"
then revert would be obviously justified.

(real case would be likely murkier)

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

Re: [OSM-talk] Paid mapping

[Andreas Vilén]

Maybe the mappers think unclassified equals what we call highway=road, as in no 
classification yet determined?

It’s a fairly common misconception among new mappers.

/Andreas

Skickat från min iPhone

> 22 juni 2020 kl. 23:50 skrev Martin Koppenhoefer :
> 

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

Re: [OSM-talk] Paid mapping

[Martin Koppenhoefer]

sent from a phone

> On 22. Jun 2020, at 23:18, Mateusz Konieczny via talk 
>  wrote:
> 
> These had been changed from highway unclassified surface unpaved to 
> highway=track by a mapper with Apple connections.
> Can you link them? I would revert them as tagging for renderer if original 
> mapping
> was correct.


sure, but how would you know the way is an unpaved unclassified road and not a 
track? You would need local knowledge. Well, what you could probably guess 
correctly, is that every settlement will be reachable through at least one road 
and not just tracks. If a road is the only connection between 2 settlements, it 
is probably a road.

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

Re: [OSM-talk-fr] Alternatives à Mapillary

[Frédéric Rodrigo]

Le 22/06/2020 à 17:20, Frédéric Rodrigo a écrit :

Le 22/06/2020 à 10:53, Marc M. a écrit :

Bonjour,

Le 22.06.20 à 10:29, Stéphane Péneau a écrit :

Recensons les alternatives complètes ou partielles à Mapillary, les
briques réutilisables, etc...

https://github.com/gitouche-sur-osm/mapillary_takeout
https://github.com/frodrigo/mapillary_takeout_web
en cours d'install sur l'infra osm.fr


C'est en ligne. Vous pouvez le tester.

Limitations actuelles, ça télécharge sur le serveur, mais vous ne 
pouvez re-télécharger dupuis serveur que les photo que une à une. À 
ajouter, un export de streaming en zip de toutes les photo.


Pas floutage, c'est les photo brutes.

La place sur le serveur est limité pour l'instant. Ne l'utilisez pas 
si vous avez beaucoup de photo Mapillary.


Les photo d'un seul utilisateurs à la fois sont téléchargées, il y a 
une liste d'attente.


Il faut donner son mot de passe Mapillay, en clair.

Les contrib sur le github sont les bienvenues.


https://mapillary-takeout-web.openstreetmap.fr/


Frédéric.



Voilà, maintenant, il y a une carte pour visualiser les données

https://mapillary-takeout-web.openstreetmap.fr/map/#5.3/46.318/3.867



Sur la question du floutage une partie des images récupérées sont déjà 
floutées.




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

Re: [OSM-talk] Paid mapping

[Mateusz Konieczny via talk]

Jun 22, 2020, 22:54 by jwhelan0...@gmail.com:

> The ones that stood out were highways that connected settlements to other 
> settlements on the map.  These had been changed from highway unclassified 
> surface unpaved to highway=track by a mapper with Apple connections.
>
Can you link them? I would revert them as tagging for renderer if original 
mapping
was correct.

>
> They seemed to have retagged a fair number and I don't honestly recall 
> exactly where they where.  I seem to recall sending an email to the mapper 
> concerned pointing towards the Africian highway Wiki and assumed that was the 
> end of the tale.
>
Remember to comment on changeset! Especially in case of paid mappers, as it 
allows
to easily demonstrate they ignore requests from community and allows to better 
judge
whatever sending message is useful or whatever it is repeated offender 
qualifying for a block.

See https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines


> A conventional OSM mapper normally maps to add detail or correct glaring 
> errors in the map.  A paid mapper might not have the same point of view.
>
> I know I'm cynical and I'm not even sure there is much that can be done about 
> it.
>
Noticing that paid mappers at least care about both "paid" and "mapping" part
is obvious.

I would guess that getting paid is typically a primary concern, with OSM data 
quality
being a secondary concern (if present at all).

In case of noticing low quality paid mapping - please, at least leave a 
changeset comment.
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-it] iD traduce i marchi?

[Martin Koppenhoefer]

sent from a phone

> On 22. Jun 2020, at 20:08, Damjan Gerl  wrote:
> 
> Io cancellerei tutti i brand:* e lascerei solo quello originale italiano. 
> Oltretutto c'è un errore di battitura (Sandrio). Ma vedo che anche il name è 
> stato tradotto, anche qui io cancellerei.


sì, lascerei il brand:wikidata e wp, ma tutte le traduzioni non hanno nessun 
senso. Cosa mi preoccupa che l’utente ha 33000 edits ;-)

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

Re: [OSM-talk-fr] Alternatives à Mapillary

[Tyndare]

Le 22/06/2020 à 10:29, Stéphane Péneau a écrit :

Dans tous ces cas, il manque au moins le floutage, le nerf de la guerre


Ce qu'il faut c'est une bonne base d'exemples pour entraîner un algo 
d’apprentissage.
Aurais-t-on le droit de récupérer à là fois la version d'origine et la 
version floutée de nos images envoyé sur Mapillary pour pouvoir s'en 
servir pour entraîner un algo ?



Perso je trouve que flouter le visage n'est pas suffisant pour le 
respect de la vie privée, Facebook se vente d'être capable de 
reconnaître les gens à leur démarche, même de dos.


J'ai testé le modèle préentrainé suivant pour flouter les personnes en 
entier des images que j'envoie sur Mapillary et je trouve que ça marche 
assez bien même si ce n'est pas parfait:


https://averdones.github.io/real-time-semantic-image-segmentation-with-deeplab-in-tensorflow/


https://www.mapillary.com/map/im/kuSWiUlfKHrqJ_7lHgn4Ug





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

Re: [OSM-talk] Paid mapping

[john whelan]

The ones that stood out were highways that connected settlements to other
settlements on the map.  These had been changed from highway unclassified
surface unpaved to highway=track by a mapper with Apple connections.

They seemed to have retagged a fair number and I don't honestly recall
exactly where they where.  I seem to recall sending an email to the mapper
concerned pointing towards the Africian highway Wiki and assumed that was
the end of the tale.

Today I was looking at a very remote hamlet and was surprised to see it was
connected by a highway=tertiary that terminated in the hamlet.  I'm not
saying it was incorrectly labelled but being curious I had a look at the
history.  If it has been mapped by someone who only mapped twice on a HOT
project that's one thing but this highway had been tagged unclassified then
retagged to tertiary by a mapper who maps for Apple according to his OSM
page and had some 6,000 edits to their name.  It actually says on the
highway from Bing not local knowledge.

When I see two different Apple mappers whom I assume are paid mappers
essentially retagging things rather than mapping new things it raises the
question in my mind are they doing this to improve the map in some way or
are they measured by how many highways have their tag on them?

If it is the latter then a different metric for paid mappers might get more
useful results in the map.

A conventional OSM mapper normally maps to add detail or correct glaring
errors in the map.  A paid mapper might not have the same point of view.

I know I'm cynical and I'm not even sure there is much that can be done
about it.

Cheerio John

On Mon, Jun 22, 2020, 16:12 Joseph Eisenberg 
wrote:

> Please clarify: are the Apple mappers 1) changing the ways to
> highway=track, or 2) changing ways that are currently highway=track to
> something else?
>
> I would support #2 in any case where the way connects settlements, since
> we have always defined highway=track as a way that is used for agriculture,
> forestry etc., not for travel between settlements.
>
> – Joseph Eisenberg
>
> On Mon, Jun 22, 2020 at 11:17 AM John Whelan 
> wrote:
>
>> I've noticed a number of highways being changed in Africa from
>> unclassified to track and from unclassified to tertiary.The ones I've
>> noticed are Apple mappers usually with the comment of from Bing and often
>> the highways connect settlements so should be a minimum of unclassified or
>> path but not track.
>>
>> African highway wiki  says it is difficult to classify highways without
>> local knowledge above unclassified.  Track is fairly easy it doesn't
>> connect settlements according to the wiki.
>>
>> Do I get the impression we are talking targets here?  The paid mappers
>> have to do so many edits to meet their targets and changing the
>> classification using Bing is easier than adding to the map?
>>
>> Do we care?  Is it is just something to be aware of.
>>
>> Thoughts?
>>
>> Thanks
>>
>> Cheerio John
>> --
>> Sent from Postbox 
>> ___
>> talk mailing list
>> talk@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk
>>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Paid mapping

[Joseph Eisenberg]

Please clarify: are the Apple mappers 1) changing the ways to
highway=track, or 2) changing ways that are currently highway=track to
something else?

I would support #2 in any case where the way connects settlements, since we
have always defined highway=track as a way that is used for agriculture,
forestry etc., not for travel between settlements.

– Joseph Eisenberg

On Mon, Jun 22, 2020 at 11:17 AM John Whelan  wrote:

> I've noticed a number of highways being changed in Africa from
> unclassified to track and from unclassified to tertiary.The ones I've
> noticed are Apple mappers usually with the comment of from Bing and often
> the highways connect settlements so should be a minimum of unclassified or
> path but not track.
>
> African highway wiki  says it is difficult to classify highways without
> local knowledge above unclassified.  Track is fairly easy it doesn't
> connect settlements according to the wiki.
>
> Do I get the impression we are talking targets here?  The paid mappers
> have to do so many edits to meet their targets and changing the
> classification using Bing is easier than adding to the map?
>
> Do we care?  Is it is just something to be aware of.
>
> Thoughts?
>
> Thanks
>
> Cheerio John
> --
> Sent from Postbox 
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-it] Compresenza addr street e place

[Luigi Scuotto]

Ho visto sono su poste italiane ma forse si possono trovare almeno
quelle.della.Lombardia in open data credo sono delibere

Gigiorno

Il Lun 22 Giu 2020, 20:59 Cascafico Giovanni  ha
scritto:

> Al link che hai mandato c'è parecchio materiale utile... penso alle
> "Modifiche della toponomastica pervenute dagli Enti locali a partire dal
> mese di novembre 2017", prodotte con risorse pubbliche, da loro trasmesse
> per poi essere blindate dalla licenza proprietaria di Poste Italiane
> (azienda privata).
> :-(
>
> Il giorno lun 22 giu 2020 alle ore 17:23 Luigi Scuotto <
> luigiscuott...@gmail.com> ha scritto:
>
>> Buona sera forse può essere di aiuto una comunicazione di poste italiane
>> CAP
>> I nuovi CAP 
>> Dal *25 maggio 2020 *è operativo il nuovo aggiornamento del Codice di
>> Avviamento Postale (primo aggiornamento 2020 - vedi sezione "Informazioni e
>> aggiornamenti").
>> I vecchi CAP resteranno comunque in vigore *nei successivi sei mesi*.
>> Gli aggiornamenti dei Codici di Avviamento Postale sono finalizzati al
>> miglioramento dello smistamento e del recapito della corrispondenza.
>>
>> Alcune variazioni dei CAP sono state necessarie a seguito dei recenti
>> cambiamenti degli assetti amministrativi, che hanno generato la fusione di
>> nuovi Comuni, entrati in vigore successivamente alla data del 1 gennaio
>> 2019. L’elenco delle nuove assegnazioni è consultabile nella sezione
>> "Informazioni e aggiornamenti" riportata in basso.
>>
>> *Nota bene*: la fusione di due o più comuni potrebbe *generare casi di
>> omonimia nelle strade*, cioè strade con lo stesso nome presenti in due o
>> più comuni accorpati; in questi casi per individuare in modo univoco il
>> destinatario è opportuno indicare, *nel blocco indirizzo a fianco della
>> via*, anche il nome del Comune originario. Per esempio, Via Roma è
>> presente sia a Camairago che a Cavacurta, comuni fusi nell'unico comune di
>> Castelgerundo; di seguito come scrivere l'indirizzo:
>>
>> SIG. MARIO ROSSI
>> VIA ROMA CAMAIRAGO 8
>> 26844 CASTELGERUNDO
>>
>> SIG.GIUSEPPE BIANCHI
>> VIA ROMA CAVACURTA 8
>> 26844 CASTELGERUNDO
>> Gigi
>>
>> Il giorno gio 18 giu 2020 alle ore 14:08 Marcello  ha
>> scritto:
>>
>>> Il 18/06/20 12:51, Andrea Musuruane ha scritto:
>>>
>>> Ciao,
>>>
>>> On Thu, Jun 18, 2020 at 12:39 PM Damjan Gerl  wrote:
>>>
 Forse si, forse no... Le cose che mi hanno portato a non usarlo sono:
 - la regola che in addr:city si mette il comune (quindi Trieste)
 - se metto addr:city=Opicina per lo stesso cap (34151) mi trovo anche
 altri addr:city=Trieste per Barcola (place=suburb), perché lo stesso cap è
 usato anche in Trieste città.

 Quindi capito che addr:place è da togliere, cosa usiamo?
 o solo addr:city=Opicina / Opčine
 o addr:city=Trieste  + addr:town=Opicina / Opčine

 Io sarei per quest'ultimo..

>>>
>>> Cerco di fare un po' di chiarezza.
>>>
>>> In Italia gli indirizzi si assegnano a livello comunale. Quindi è errato
>>> mettere un addr:city diverso dal nome del comune in cui si trova
>>> l'indirizzo.
>>>
>>> Se, come riportato dalla pagina wiki, le chiavi addr:* corrispondono
>>> all'indirizzo postale, non mi sembra automatico che in addr:city vada il
>>> nome del comune. Secondo le regole di composizione degli indirizzi di Poste
>>> Italiane, postato qui qualche giorno fa da Andrea Falco, a pag.8 punto 11
>>> si legge che è necessario indicare il nome del comune se la frazione non è
>>> inclusa nel Codice di Avviamento Postale, ma alcune frazioni sono incluse.
>>> Per Opicina è giusto mettere Trieste perché facendo una ricerca del CAP nel
>>> sito delle Poste non trova nulla, ma non sempre è così.
>>>
>>> A volte capita ancora, anche se l'attuale normativa lo esclude
>>> esplicitamente, di avere odonimi uguali in differenti parti del comune (ad
>>> esempio in due frazioni). In questo caso si usa addr:hamlet. Tralasciamo il
>>> fatto che hamlet è un valore del tag place, così come city è un valore del
>>> tag place, con una sua specificità. E' solo una nomenclatura.
>>>
>>> Se proprio vuoi inserire lo stesso l'informazione su luogo in cui si
>>> trovano anche se questa è inutile per la sua localizzazione, puoi usare
>>> addr:hamlet.
>>>
>>> Se si usano altri tag non documentati come addr:town (anche se usati: in
>>> OSM può esistere qualsiasi tag, purtroppo), proprio perché non documentati,
>>> hanno un significato ambiguo e non ci saranno data user che li useranno.
>>>
>>> Ciao,
>>>
>>> Andrea
>>>
>>> --
>>> Ciao
>>> Marcello
>>>
>>>
>>> ___
>>> 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
> 

Re: [OSM-talk-fr] Alternatives à Mapillary

[Yves P.]

>
> Yves, je suppose que ce que tu as trouvé marche mal par faute
> d'entrainement.
>
Peu de visages dans mes photos, beaucoup de mobilier urbain 

Sur une photo avec 5 personnes,  il n'en trouve qu'une.

L'algorithme a peut-être aussi des soucis :
https://summerofcode.withgoogle.com/projects/#5233240182358016

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

Re: [Talk-it] Compresenza addr street e place

[Cascafico Giovanni]

Al link che hai mandato c'è parecchio materiale utile... penso alle
"Modifiche della toponomastica pervenute dagli Enti locali a partire dal
mese di novembre 2017", prodotte con risorse pubbliche, da loro trasmesse
per poi essere blindate dalla licenza proprietaria di Poste Italiane
(azienda privata).
:-(

Il giorno lun 22 giu 2020 alle ore 17:23 Luigi Scuotto <
luigiscuott...@gmail.com> ha scritto:

> Buona sera forse può essere di aiuto una comunicazione di poste italiane
> CAP
> I nuovi CAP 
> Dal *25 maggio 2020 *è operativo il nuovo aggiornamento del Codice di
> Avviamento Postale (primo aggiornamento 2020 - vedi sezione "Informazioni e
> aggiornamenti").
> I vecchi CAP resteranno comunque in vigore *nei successivi sei mesi*.
> Gli aggiornamenti dei Codici di Avviamento Postale sono finalizzati al
> miglioramento dello smistamento e del recapito della corrispondenza.
>
> Alcune variazioni dei CAP sono state necessarie a seguito dei recenti
> cambiamenti degli assetti amministrativi, che hanno generato la fusione di
> nuovi Comuni, entrati in vigore successivamente alla data del 1 gennaio
> 2019. L’elenco delle nuove assegnazioni è consultabile nella sezione
> "Informazioni e aggiornamenti" riportata in basso.
>
> *Nota bene*: la fusione di due o più comuni potrebbe *generare casi di
> omonimia nelle strade*, cioè strade con lo stesso nome presenti in due o
> più comuni accorpati; in questi casi per individuare in modo univoco il
> destinatario è opportuno indicare, *nel blocco indirizzo a fianco della
> via*, anche il nome del Comune originario. Per esempio, Via Roma è
> presente sia a Camairago che a Cavacurta, comuni fusi nell'unico comune di
> Castelgerundo; di seguito come scrivere l'indirizzo:
>
> SIG. MARIO ROSSI
> VIA ROMA CAMAIRAGO 8
> 26844 CASTELGERUNDO
>
> SIG.GIUSEPPE BIANCHI
> VIA ROMA CAVACURTA 8
> 26844 CASTELGERUNDO
> Gigi
>
> Il giorno gio 18 giu 2020 alle ore 14:08 Marcello  ha
> scritto:
>
>> Il 18/06/20 12:51, Andrea Musuruane ha scritto:
>>
>> Ciao,
>>
>> On Thu, Jun 18, 2020 at 12:39 PM Damjan Gerl  wrote:
>>
>>> Forse si, forse no... Le cose che mi hanno portato a non usarlo sono:
>>> - la regola che in addr:city si mette il comune (quindi Trieste)
>>> - se metto addr:city=Opicina per lo stesso cap (34151) mi trovo anche
>>> altri addr:city=Trieste per Barcola (place=suburb), perché lo stesso cap è
>>> usato anche in Trieste città.
>>>
>>> Quindi capito che addr:place è da togliere, cosa usiamo?
>>> o solo addr:city=Opicina / Opčine
>>> o addr:city=Trieste  + addr:town=Opicina / Opčine
>>>
>>> Io sarei per quest'ultimo..
>>>
>>
>> Cerco di fare un po' di chiarezza.
>>
>> In Italia gli indirizzi si assegnano a livello comunale. Quindi è errato
>> mettere un addr:city diverso dal nome del comune in cui si trova
>> l'indirizzo.
>>
>> Se, come riportato dalla pagina wiki, le chiavi addr:* corrispondono
>> all'indirizzo postale, non mi sembra automatico che in addr:city vada il
>> nome del comune. Secondo le regole di composizione degli indirizzi di Poste
>> Italiane, postato qui qualche giorno fa da Andrea Falco, a pag.8 punto 11
>> si legge che è necessario indicare il nome del comune se la frazione non è
>> inclusa nel Codice di Avviamento Postale, ma alcune frazioni sono incluse.
>> Per Opicina è giusto mettere Trieste perché facendo una ricerca del CAP nel
>> sito delle Poste non trova nulla, ma non sempre è così.
>>
>> A volte capita ancora, anche se l'attuale normativa lo esclude
>> esplicitamente, di avere odonimi uguali in differenti parti del comune (ad
>> esempio in due frazioni). In questo caso si usa addr:hamlet. Tralasciamo il
>> fatto che hamlet è un valore del tag place, così come city è un valore del
>> tag place, con una sua specificità. E' solo una nomenclatura.
>>
>> Se proprio vuoi inserire lo stesso l'informazione su luogo in cui si
>> trovano anche se questa è inutile per la sua localizzazione, puoi usare
>> addr:hamlet.
>>
>> Se si usano altri tag non documentati come addr:town (anche se usati: in
>> OSM può esistere qualsiasi tag, purtroppo), proprio perché non documentati,
>> hanno un significato ambiguo e non ci saranno data user che li useranno.
>>
>> Ciao,
>>
>> Andrea
>>
>> --
>> Ciao
>> Marcello
>>
>>
>> ___
>> 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] Alternatives à Mapillary

[Marc M.]

Le 22.06.20 à 19:03, Christian Quest a écrit :
> je peux m'en charger en lançant le script sur un serveur perso

installe le front de fred pour supprimer la contrainte humaine ?

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

Re: [OSM-talk-fr] Ajout d'un identifiant unique des cinémas en France

[Jérôme Amagat]

plus que 367 (dont 99 itinérants) !
Normalement je n'ai pas fait d'erreurs cette fois ci et dans la pièce
jointe il y a les 367 (dont 99 itinérants) cinémas dont la ref CNC n'est
pas encore dans osm géolocalisé dans leur commune.
et ici :
https://docs.google.com/spreadsheets/d/1t84RGxfaPcZoOv6JresR6OxnGQEs68UDQDndbWI4wkU/edit?usp=sharing
un extrait de la base SIRENE geocodé par cquest (
http://data.cquest.org/geo_sirene/v2019/last/) qui ont comme
'activitePrincipaleEtablissement' '59.14Z'
( il n'y a qu'environ 1/3 qui ont un nom ou quelque chose qui y ressemble)
ref:FR:CNC,name,screen,capacity,_CODE COMMUNE,_COMMUNE,_GENRE,_ART ET ESSAI,cinema:3D,latitude,longitude
12,GEORGE V,11,1666,75108,Paris 8e Arrondissement,FIXE,,yes,48.873645,2.3116
4713,BORIS VIAN GRANDE HALLE,1,287,75119,Paris 19e Arrondissement,FIXE,,no,48.887253,2.387709
8425,QUARTIER LATIN I,2,164,75105,Paris 5e Arrondissement,FIXE,,no,48.845277,2.35058
9616,MK2 A,4,520,75113,Paris 13e Arrondissement,FIXE,,yes,48.8302,2.365001
10184,REX,3,511,80001,Abbeville,FIXE,,yes,50.109435,1.829831
13161,ESPACE CULTUREL AREA (EX-ESPACE CULTUREL),1,268,62014,Aire-sur-la-Lys,FIXE,,yes,50.645609,2.402642
13683,ESPACE CULTUREL MUNICIPAL,1,319,2A004,Ajaccio,FIXE,,no,41.928987,8.712092
13684,AUDITORIUM PASCAL PAOLI,1,432,2A004,Ajaccio,FIXE,,no,41.928987,8.712092
13685,ESPACE DIAMANT,1,295,2A004,Ajaccio,FIXE,,no,41.928987,8.712092
13692,PALAIS DES CONGRES,1,432,2A004,Ajaccio,FIXE,,no,41.928987,8.712092
14693,LE POLE CULTUREL,1,410,94002,Alfortville,FIXE,,no,48.796239,2.421504
15374,BEL' DONNE,2,241,38006,Allevard,FIXE,,yes,45.394443,6.084186
15682,SALLE POLYVALENTE,1,600,72003,Allonnes,ITINERANT,,no,47.962441,0.145667
17961,CINEMA DE LA VIOUZE,1,347,63004,Les Ancizes-Comps,FIXE,,no,45.92885,2.80976
18701,NORMANDIE,1,250,28007,Anet,FIXE,,no,48.853125,1.437646
20311,SALLE DE CINEMA,1,103,71009,Anost,FIXE,,no,47.078514,4.107077
23323,LE FIGUIER BLANC,3,826,95018,Argenteuil,FIXE,,yes,48.948578,2.248098
23392,L EAU VIVE,1,159,05006,L' Argentière-la-Bessée,FIXE,,no,44.788599,6.555362
25722,CIRCUIT 1,1,100,45008,Artenay,ITINERANT,,no,48.075392,1.876596
26180,SALLE POLYVALENTE,1,,12011,Arvieu,ITINERANT,,no,44.185087,2.674777
28113,PAUL GRIMAULT,1,169,78029,Aubergenville,FIXE,,yes,48.957567,1.851294
29144,CINE THEATRE LOUIS ARAGON,1,514,62048,Auchel,FIXE,,yes,50.509614,2.465888
29741,SALLE POLYVALENTE,1,150,63016,Augerolles,ITINERANT,,no,45.73394,3.63153
31331,LES ECRINS,1,97,38020,Auris,FIXE,,no,45.043029,6.088154
33912,LE FAMILIA,1,193,62065,Avion,FIXE,,no,50.407403,2.830058
35953,THEATRE VICTOR HUGO,1,418,92007,Bagneux,FIXE,,no,48.797934,2.310181
36282,SALLE MUNICIPALE CLAUDE PLAN,1,200,34022,Baillargues,ITINERANT,,yes,43.656757,4.008437
38592,SALLE COMMUNALE,1,90,47021,Barbaste,ITINERANT,,no,44.16377,0.24213
39174,THEATRE MONTDORY,1,345,76057,Barentin,FIXE,,yes,49.544418,0.950553
42681,L ATALANTE,1,180,64102,Bayonne,FIXE,,no,43.486661,-1.462185
44239,COUR DE L'ECOLE,1,0,07028,Beaulieu,ITINERANT,,no,44.368303,4.245604
45471,THEATRE SAINT MARTIN,1,211,62100,Beaurainville,ITINERANT,,no,50.417093,1.902671
51261,CINE 89,1,196,13014,Berre-l'Étang,FIXE,,yes,43.505714,5.161253
52532,FOYER RURAL,1,0,63038,Besse-et-Saint-Anastaise,ITINERANT,,yes,45.514507,2.902716
54292,LA BARBACANE,1,292,78062,Beynes,FIXE,,no,48.852507,1.876106
54692,THEATRE PAUL ELUARD,2,598,95063,Bezons,FIXE,,no,48.927287,2.214879
55532,CENTRE CULTUREL,1,298,33051,Biganos,FIXE,,yes,44.653812,-0.950799
56558,CENTRE CULTUREL CLAUDE VIGEE,1,214,67046,Bischwiller,FIXE,,yes,48.763985,7.863265
57303,MAISON DES FETES,1,600,54076,Blainville-sur-l'Eau,ITINERANT,,no,48.557443,6.407226
57821,COLONNES,2,339,33056,Blanquefort,FIXE,,yes,44.921266,-0.615808
57851,SELECT,1,114,16046,Côteaux du Blanzacais,FIXE,,no,45.460879,0.019402
58121,SALLE DE CINEMA,1,150,43165,Rosières,ITINERANT,,yes,45.131602,4.005209
59033,AUDITORIUM BOURSE TRAVAIL,1,,93008,Bobigny,ITINERANT,,no,48.906702,2.443342
59351,LOUIS JOUVET,1,142,02095,Bohain-en-Vermandois,FIXE,,no,49.98791,3.461742
59604,JEAN RENOIR,1,300,92009,Bois-Colombes,FIXE,,yes,48.915287,2.268837
62121,GERARD PHILIPE,1,245,94011,Bonneuil-sur-Marne,FIXE,,no,48.772161,2.489652
67304,RIO BORVO,1,152,71047,Bourbon-Lancy,FIXE,,no,46.61924,3.753851
67312,CASINO,1,124,03036,Bourbon-l'Archambault,FIXE,,no,46.58337,3.048207
67324,CASINO DE BOURBONNE,1,150,52060,Bourbonne-les-Bains,FIXE,,no,47.937958,5.757476
67333,LE ROXY,1,192,63047,La Bourboule,FIXE,,no,45.585742,2.747331
67903,SALLE POLYVALENTE,1,0,38052,Le Bourg-d'Oisans,ITINERANT,,no,45.054822,6.040113
68114,LE CINEMA,1,83,93013,Le Bourget,FIXE,,no,48.937602,2.428852
68212,AUDITORIUM DU CONSERVATOIRE,1,177,92014,Bourg-la-Reine,FIXE,,no,48.780114,2.316361
68561,FAMILIA,1,224,37031,Bourgueil,FIXE,,no,47.303777,0.174675
68562,ABBAYE DE BOURGUEIL,1,380,37031,Bourgueil,FIXE,,no,47.303777,0.174675
69231,LE FOYER,1,356,59098,Bousbecque,FIXE,,no,50.761597,3.079806
73098,OCEANOPOLIS,1,267,29019,Brest,FIXE,,yes,48.406102,-4.498893
74471,LE 

Re: [OSM-talk-fr] Alternatives à Mapillary

[osm . sanspourriel]

Bonjour,

> C'est en ligne. Vous pouvez le tester.

Pour ça il faudrait avoir été producteur et non seulement consommateur ;-).

> Pas floutage, c'est les photo brutes.

Très bien, on récupère l'original.

Maintenant la demande au Père Noël :

S'il y a moyen en fonction de ces adresses de trouver les adresses des
photos floutées, même sous-échantillonnées ça permettrait par différence
de trouver les zones de floutage, ce qui nous permettrait si les
conditions le permettent d'entraîner une IA de reconnaissance de visages
et de plaques.

Yves, je suppose que ce que tu as trouvé marche mal par faute
d'entrainement.

Jean-Yvon




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

[OSM-talk] Paid mapping

[John Whelan]

I've noticed a number of highways being changed in Africa from 
unclassified to track and from unclassified to tertiary.    The ones 
I've noticed are Apple mappers usually with the comment of from Bing and 
often the highways connect settlements so should be a minimum of 
unclassified or path but not track.


African highway wiki  says it is difficult to classify highways without 
local knowledge above unclassified.  Track is fairly easy it doesn't 
connect settlements according to the wiki.


Do I get the impression we are talking targets here?  The paid mappers 
have to do so many edits to meet their targets and changing the 
classification using Bing is easier than adding to the map?


Do we care?  Is it is just something to be aware of.

Thoughts?

Thanks

Cheerio John
--
Sent from Postbox 
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-it] iD traduce i marchi?

[Damjan Gerl]

Martin Koppenhoefer je 22.6.2020 ob 17:37 napisal:
Ho appena e per caso trovato una banca popolare di Sondrio alla quale 
un utente ha aggiunto "brand:en=Popular Bank of Sandrio". Non escludo 
che alcuni marchi sono tradotti in altre lingue (o meglio il 
proprietario di un marchio usa un altro marchio in un altro paese), ma 
quella banca è una banca popolare di Sondrio, non ha un marchio 
inglese (che tra altro anche la wikipedia inglese usa il brand italiano).
Potrei semplicemente correggere, ma siccome sospetto che questo è un 
errore sistematico (suggerimento di iD), vorrei chiedere a voi se 
questi suggerimenti di iD vengono ancora proposti. (L'edit è stato 
fatto 4 mesi fa).


Si tratta di questo nodo:
https://www.openstreetmap.org/node/7090473329

Inoltre mi sembra strano anche il tag "brand:it", sopratutto su 
territorio Italiano.


Ciao
Martin


Io cancellerei tutti i brand:* e lascerei solo quello originale 
italiano. Oltretutto c'è un errore di battitura (Sandrio). Ma vedo che 
anche il name è stato tradotto, anche qui io cancellerei.


Damjan

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

Re: [Talk-it] Compresenza addr street e place

[Marcello]

Il 22/06/20 17:22, Luigi Scuotto ha scritto:

Buona sera forse può essere di aiuto una comunicazione di poste italiane


CAP


I nuovi CAP


Dal *25 maggio 2020 *è operativo il nuovo aggiornamento del Codice di 
Avviamento Postale (primo aggiornamento 2020 - vedi sezione 
"Informazioni e aggiornamenti").

I vecchi CAP resteranno comunque in vigore *nei successivi sei mesi*.
Gli aggiornamenti dei Codici di Avviamento Postale sono finalizzati al 
miglioramento dello smistamento e del recapito della corrispondenza.


Alcune variazioni dei CAP sono state necessarie a seguito dei recenti 
cambiamenti degli assetti amministrativi, che hanno generato la 
fusione di nuovi Comuni, entrati in vigore successivamente alla data 
del 1 gennaio 2019. L’elenco delle nuove assegnazioni è consultabile 
nella sezione "Informazioni e aggiornamenti" riportata in basso.


*Nota bene*: la fusione di due o più comuni potrebbe *generare casi di 
omonimia nelle strade*, cioè strade con lo stesso nome presenti in due 
o più comuni accorpati; in questi casi per individuare in modo univoco 
il destinatario è opportuno indicare, *nel blocco indirizzo a fianco 
della via*, anche il nome del Comune originario. Per esempio, Via Roma 
è presente sia a Camairago che a Cavacurta, comuni fusi nell'unico 
comune di Castelgerundo; di seguito come scrivere l'indirizzo:


SIG. MARIO ROSSI
VIA ROMA CAMAIRAGO 8
26844 CASTELGERUNDO

SIG.GIUSEPPE BIANCHI
VIA ROMA CAVACURTA 8
26844 CASTELGERUNDO
Gigi


Mi sembra di capire che le 2 vie continueranno a chiamarsi "Via Roma", 
ma ai fini dello smistamento postale è bene indicare anche la località 
(Camairago o Cavacurta), che non è più Comune. Se così fosse in 
addr:street non possiamo mettere quanto suggerito da Poste Italiane, ad 
esempio "Via Roma Cavacurta", perché non è il nome della via, quindi si 
ritorna a scegliere se utilizzare addr:place insieme a addr:street, 
contravvenendo alla raccomandazione della pagina wiki, oppure al posto 
di addr:place usare addr:hamlet o addr:suburb, a seconda dei casi.


Per operare questa scelta secondo me sarebbe utile conoscere come 
vengono trattati questi tag dai software che poi li utilizzano, nella 
ricerca degli indirizzi, nel routing, ecc. C'è qualcuno che ha 
informazioni al riguardo?

Grazie

--
Ciao
Marcello

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

Re: [OSM-talk-fr] Alternatives à Mapillary

[Christian Quest]

Le 22/06/2020 à 17:20, Frédéric Rodrigo a écrit :


C'est en ligne. Vous pouvez le tester.

Limitations actuelles, ça télécharge sur le serveur, mais vous ne 
pouvez re-télécharger dupuis serveur que les photo que une à une. À 
ajouter, un export de streaming en zip de toutes les photo.


Pas floutage, c'est les photo brutes.

La place sur le serveur est limité pour l'instant. Ne l'utilisez pas 
si vous avez beaucoup de photo Mapillary.


Les photo d'un seul utilisateurs à la fois sont téléchargées, il y a 
une liste d'attente.


Il faut donner son mot de passe Mapillay, en clair.

Les contrib sur le github sont les bienvenues.




Et si vous voulez récupérer un gros paquet de photos, sans qu'elles 
soient publiques (là elle le sont facilement), je peux m'en charger en 
lançant le script sur un serveur perso (hébergé at home). Juste besoin 
des mêmes infos.



--
Christian Quest - OpenStreetMap France


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

Re: [Talk-it] facebook compra mapillary

[Martin Koppenhoefer]

Am Mo., 22. Juni 2020 um 17:20 Uhr schrieb mbranco2 :

> mah, parlando di privacy, anche prima si sapeva che un utente mapillary il
> tal giorno alla tal ora si trovava nel tal posto (proprio come OSM sa che
> il tal giorno alla tal ora stavo mappando una certa zona).
>


certo, e anche Mapillary vedeva chi guardava cosa, con quale tipo di
device, con quale risoluzione di schermo, quale sistema operativo, a che
ora, ecc. ecc.. L'unica differenza era che Mapillary non era Facebook...

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

Re: [Talk-us] National Forest boundaries

[stevea]

>> A relation for all would be ok too, as long as the private inholdings are
>> not removed from the NF (which I think has been done in some cases).
> 
Bradley White  writes
> I've argued for this in the past on this mailing list, but have since
> come around to disagreeing with this position over tagging semantics.
> Most NF boundaries are now tagged with 'boundary=protected_area', in
> which case the boundary should represent physical land that the NF
> actually owns and manages, and not the congressionally-declared
> boundary. In my area, half of the city of Reno and nearly all of
> Truckee fall within an congress-declared/administrative NF boundary -
> these areas are certainly not protected.

"Private inholdings are NOT removed from the NF?"  (Emphasis mine).  That 
doesn't make sense to me.  OSM WANTS to (logically) remove private inholdings 
from NFs.  We do so with relations where inholdings are members with the 
"inner" role.

While it certainly may exist, I'm not aware of a disparity between the 
"congressionally declared boundary" and any other boundary of a NF, including 
"physical land that the NF actually owns and manages."  How would anyone know 
where this latter boundary is?  (Opinion?)  Around Reno is Humboldt-Toiyabe NF, 
largest NF in the lower 48, nearly 10,000 square miles, that is LARGE.  
Wikimedia has a nice interactive map of this (superimposed on OSM data) at 
https://en.wikipedia.org/wiki/Humboldt–Toiyabe_National_Forest .  Yes, it looks 
like "half of Reno" is within this boundary.  I agree with you it is odd / 
unusual that this mix of urbanization is technically within NF boundaries.  
Yet, it is.  I believe OSM wants to map this NF "as is," not "where it appears 
the area is 'not protected'" (again, by your opinion?)

National Forests are federally-managed land, often with many inholdings in 
highly complex landuse blends.  OSM has the "machinery" to represent them:  
data structures called multipolygons with membership roles of outer and inner, 
plus tags.  If thousands of residential parcels in Reno "should" logically be 
excluded from H-T, yes, that's ambitious (and rather odd / unusual / even 
wacky), but it seems to me it is correct to represent it that way in OSM.  Can 
somebody (literally or figuratively) call up Bill Dunkelberger (Forest 
Supervisor) and ask him the questions "why are thousands of Reno's residential 
parcels inside the boundaries of our forest?  Can you explain how a map might 
properly represent this?"  There might be some history about the city of Reno, 
how Congress declares federal protection with a fee simple boundary, likely a 
great deal of hand-waving and probably an "admission" that constructing a 
ridiculously-complex multipolygon could properly represent it, but only with 
mind-boggling intricacies of detail.  Are we up for the task?!

> IMO, a tagging scheme that better represents the meaning of these two
> boundaries would be:
> 1. 'boundary=protected_area' around fee simple NF land ownership,
> since this describes the actual protected areas of land
> 2. 'boundary=administrative' (with a not-yet-existing 'admin_level')
> around declared NF boundaries, since this is an administrative
> boundary for the NF and doesn't necessarily show what land is actually
> managed by the NF.

I am virtually certain we do not want to put boundary=administrative on NFs 
(and without admin_level, this doesn't make sense; the two tags are 
codependent).  This EXCLUDES them from whatever admin_level you MIGHT give 
them, making them a "hole" in that entity at that level.  Many years ago, I 
(mistakenly) thought that national parks should haven an admin_level=2 set on 
them (and state parks 4 and county parks 6) but that logically punches a hole 
in the country, state or county, so "don't do that."

> We should even consider not including congressionally-declared
> boundaries, since they aren't even theoretically verifiable on the
> ground, and really don't necessarily indicate any kind of protection
> of the land within the boundary. Fee simple ownership is at least
> usually ground-verifiable with small yellow "NF boundary" placards.

This needs more discussion, with a better declaration of terms.  If Congress 
declares an area as protected, OSM should map it as protected.  That doesn't 
seem weird to me, although "half of Reno in a NF" does.  Most importantly how 
would we / who declares where is this "other" boundary? (not the Congressional 
one, the one which says "the USFS actually owns and manages this")  Very 
confusing as stated; I think we can state this more clearly.

SteveA



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

Re: [Talk-it] iD traduce i marchi?

[Francesco Ansanelli]

Ciao Martin,

sospetto che iD abbia integrato un progetto di suggerimento dei nomi:

https://github.com/osmlab/name-suggestion-index/blob/7fb9b3979febab2e27bfb725eb83b4edd0d0f755/brands/amenity/bank.json#L1149

ho creato una issue per l'analogo: "Sella Bank":

https://github.com/osmlab/name-suggestion-index/issues/3967

Forse si può continuare lì la discussione.
Francesco

Il lun 22 giu 2020, 17:37 Martin Koppenhoefer  ha
scritto:

> Ho appena e per caso trovato una banca popolare di Sondrio alla quale un
> utente ha aggiunto "brand:en=Popular Bank of Sandrio". Non escludo che
> alcuni marchi sono tradotti in altre lingue (o meglio il proprietario di un
> marchio usa un altro marchio in un altro paese), ma quella banca è una
> banca popolare di Sondrio, non ha un marchio inglese (che tra altro anche
> la wikipedia inglese usa il brand italiano).
> Potrei semplicemente correggere, ma siccome sospetto che questo è un
> errore sistematico (suggerimento di iD), vorrei chiedere a voi se questi
> suggerimenti di iD vengono ancora proposti. (L'edit è stato fatto 4 mesi
> fa).
>
> Si tratta di questo nodo:
> https://www.openstreetmap.org/node/7090473329
>
> Inoltre mi sembra strano anche il tag "brand:it", sopratutto su territorio
> Italiano.
>
> Ciao
> Martin
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

[Talk-it] iD traduce i marchi?

[Martin Koppenhoefer]

Ho appena e per caso trovato una banca popolare di Sondrio alla quale un
utente ha aggiunto "brand:en=Popular Bank of Sandrio". Non escludo che
alcuni marchi sono tradotti in altre lingue (o meglio il proprietario di un
marchio usa un altro marchio in un altro paese), ma quella banca è una
banca popolare di Sondrio, non ha un marchio inglese (che tra altro anche
la wikipedia inglese usa il brand italiano).
Potrei semplicemente correggere, ma siccome sospetto che questo è un errore
sistematico (suggerimento di iD), vorrei chiedere a voi se questi
suggerimenti di iD vengono ancora proposti. (L'edit è stato fatto 4 mesi
fa).

Si tratta di questo nodo:
https://www.openstreetmap.org/node/7090473329

Inoltre mi sembra strano anche il tag "brand:it", sopratutto su territorio
Italiano.

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

Re: [Talk-it] Compresenza addr street e place

[Luigi Scuotto]

Buona sera forse può essere di aiuto una comunicazione di poste italiane
CAP
I nuovi CAP 
Dal *25 maggio 2020 *è operativo il nuovo aggiornamento del Codice di
Avviamento Postale (primo aggiornamento 2020 - vedi sezione "Informazioni e
aggiornamenti").
I vecchi CAP resteranno comunque in vigore *nei successivi sei mesi*.
Gli aggiornamenti dei Codici di Avviamento Postale sono finalizzati al
miglioramento dello smistamento e del recapito della corrispondenza.

Alcune variazioni dei CAP sono state necessarie a seguito dei recenti
cambiamenti degli assetti amministrativi, che hanno generato la fusione di
nuovi Comuni, entrati in vigore successivamente alla data del 1 gennaio
2019. L’elenco delle nuove assegnazioni è consultabile nella sezione
"Informazioni e aggiornamenti" riportata in basso.

*Nota bene*: la fusione di due o più comuni potrebbe *generare casi di
omonimia nelle strade*, cioè strade con lo stesso nome presenti in due o
più comuni accorpati; in questi casi per individuare in modo univoco il
destinatario è opportuno indicare, *nel blocco indirizzo a fianco della via*,
anche il nome del Comune originario. Per esempio, Via Roma è presente sia a
Camairago che a Cavacurta, comuni fusi nell'unico comune di Castelgerundo;
di seguito come scrivere l'indirizzo:

SIG. MARIO ROSSI
VIA ROMA CAMAIRAGO 8
26844 CASTELGERUNDO

SIG.GIUSEPPE BIANCHI
VIA ROMA CAVACURTA 8
26844 CASTELGERUNDO
Gigi

Il giorno gio 18 giu 2020 alle ore 14:08 Marcello  ha
scritto:

> Il 18/06/20 12:51, Andrea Musuruane ha scritto:
>
> Ciao,
>
> On Thu, Jun 18, 2020 at 12:39 PM Damjan Gerl  wrote:
>
>> Forse si, forse no... Le cose che mi hanno portato a non usarlo sono:
>> - la regola che in addr:city si mette il comune (quindi Trieste)
>> - se metto addr:city=Opicina per lo stesso cap (34151) mi trovo anche
>> altri addr:city=Trieste per Barcola (place=suburb), perché lo stesso cap è
>> usato anche in Trieste città.
>>
>> Quindi capito che addr:place è da togliere, cosa usiamo?
>> o solo addr:city=Opicina / Opčine
>> o addr:city=Trieste  + addr:town=Opicina / Opčine
>>
>> Io sarei per quest'ultimo..
>>
>
> Cerco di fare un po' di chiarezza.
>
> In Italia gli indirizzi si assegnano a livello comunale. Quindi è errato
> mettere un addr:city diverso dal nome del comune in cui si trova
> l'indirizzo.
>
> Se, come riportato dalla pagina wiki, le chiavi addr:* corrispondono
> all'indirizzo postale, non mi sembra automatico che in addr:city vada il
> nome del comune. Secondo le regole di composizione degli indirizzi di Poste
> Italiane, postato qui qualche giorno fa da Andrea Falco, a pag.8 punto 11
> si legge che è necessario indicare il nome del comune se la frazione non è
> inclusa nel Codice di Avviamento Postale, ma alcune frazioni sono incluse.
> Per Opicina è giusto mettere Trieste perché facendo una ricerca del CAP nel
> sito delle Poste non trova nulla, ma non sempre è così.
>
> A volte capita ancora, anche se l'attuale normativa lo esclude
> esplicitamente, di avere odonimi uguali in differenti parti del comune (ad
> esempio in due frazioni). In questo caso si usa addr:hamlet. Tralasciamo il
> fatto che hamlet è un valore del tag place, così come city è un valore del
> tag place, con una sua specificità. E' solo una nomenclatura.
>
> Se proprio vuoi inserire lo stesso l'informazione su luogo in cui si
> trovano anche se questa è inutile per la sua localizzazione, puoi usare
> addr:hamlet.
>
> Se si usano altri tag non documentati come addr:town (anche se usati: in
> OSM può esistere qualsiasi tag, purtroppo), proprio perché non documentati,
> hanno un significato ambiguo e non ci saranno data user che li useranno.
>
> Ciao,
>
> Andrea
>
> --
> Ciao
> Marcello
>
>
> ___
> 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-br] Importação de transformadores: Uso da "tag name"

[portalaventura]

Nem tudo no banco de dados é renderizado ou passível de ser encontrado 
por meio do campo de busca no site openstreetmap.org. É sua aplicação 
que deve se adequar à como os dados são tagueados, não o contrário.


Você pode gerar mapas personalizados utilizando, por exemplo, uMap. A 
forma adequada é utilizando a tag power=pole e seus complementos e 
colocando código na tag ref.


https://umap.openstreetmap.fr/en/

https://wiki.openstreetmap.org/wiki/Tag:power%3Dpole

https://wiki.openstreetmap.org/wiki/Key:transformer

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

Em 22/06/2020 10:43, Mapas Osm escreveu:

Olá,
Quanto ao uso das tags "ref" e "pole" os códigos dos transformadores 
só podem ser visualizados nos modos de edição do OpenStreetMap. Só 
consegui consultá-los usando as tags"transformer_tower" e substituindo 
"ref" por "name".
Existe alguma forma de mapeamento mais correta que essa em que é 
possível consultar os códigos de transformadores diretamente no campo 
de consulta do OpenStreetMap?


Em quinta-feira, 18 de junho de 2020 às 12:57 
> escreveu:


Enviar submissões para uma lista de discussão Talk-br para
talk-br@openstreetmap.org 

Para se registrar ou descobrir via WWW, visite o endereço
https: //lists.openstreetmap.or g / listinfo / talk-br

ou, via e-mail, envie uma mensagem com a palavra 'ajuda' no
assunto ou no
corpo da mensagem para
talk-br-request @ openstreetmap. org


rápido Você podera ENTRAR em Contato com uma pessoa that Gerencia
uma Lista cabelo
endereco
talk-br-ow...@openstreetmap.or g


QUANDO responder, por favor edite SUA Linha Assunto ASSIM ELA Será
Mais Específica que "Re: Conteúdo da conversa-br digerir. .. "


Tópicos de Hoje:

   1. Re: Digest Talk-br, volume 141, assunto 5 (Helio Cesar Tomio)


--  --
--

Mensagem: 1
Data: Qui, 18 Jun 2020 12:57:03 -0300
De: Helio Cesar Tomio < hcto...@gmail.com >
Para : OpenStreetMap no Brasil < talk-br@openstreetmap.org
>
Assunto: Re: [Discussão-br] Digest conversa-br, o volume de 141,
ASSUNTO 5
Message-ID:
        < CAE1uxb1UtokKTyVGUXKQYbyV8CRW
9nsebq8z_gj7mljoy2g...@mail.gm ail.com
>

Content-Type : texto / planície; charset = "utf-8"

Uma carta de solicitação para uma empresa não precisa ser
exatamente como o
modelo que o ambiente.
Basta autorizar ou usar dados de forma livre para realizar um
importação no Openstreetmap, compatível com uma licença do OSM.

Vc precisa ter o cuidado para não fazer edições que não segue as
regras
das tags já aprovadas.
Por exemplo, eu acho muito estranho colocar o nome nas postagens.
Não sei dizer
se isso está correto. Seria como colocar o nome em lixeiras,
hidrantes,
orelhões, ...
E uma tag de construção não parece adequada para postagens, qdo vc
tem por exemplo
power = pole.

Recentemente foram aprovadas novas tags para linhas de energia,
talvez na
linha do seu trabalho:
https://wiki.openstreetmap.org / wiki / Features_propostas /
Linhas_ de gerenciamento


Nas tuas futuras importações, necessário verificar a localização
dos postes
não está correto no OSM. Erro de referência não utilizado
(sad69 / sirgass2000 / wgs84) que foi comprometido.
Foi constatado que muitos posts acabaram ficando dentro de lotes ou
alterações, devido a algumas divergências de informações.

Se parece que chatice tudo isso, mas uma comunidade se preocupa
com os
dados do OSM não se transforma em uma confusão ou em informações
erradas ou
inúteis.

Cordialmente,
Tomio

Em 17 de junho de 2020 14:26, Mapas Osm < mapas...@gmail.com
> Escrito :

> Um respeito pela licença de dados, a mesma confirmação
confirmada por meio de carta
> (modelo em anexo).
> Os dados são do tipo ponto no formato shapefile coletado com
receptor
> GNSS com códigos de identificação de cada transformador e chave
em alguns
> municípios dos estados de São Paulo e Mato Grosso do Sul.
> A metodologia de importação seria útil para Josm importar os
dados em
> blocos e realizando todas as correções de conflitos que vieram a
aparecer.
> Para consultar os códigos ou os pontos que precisam ser mapeados
com
> "tag = building_transformer-towe r" e "ref" substituída por "name".
>>
Em terça-feira 

Re: [OSM-talk-fr] Alternatives à Mapillary

[Frédéric Rodrigo]

Le 22/06/2020 à 10:53, Marc M. a écrit :

Bonjour,

Le 22.06.20 à 10:29, Stéphane Péneau a écrit :

Recensons les alternatives complètes ou partielles à Mapillary, les
briques réutilisables, etc...

https://github.com/gitouche-sur-osm/mapillary_takeout
https://github.com/frodrigo/mapillary_takeout_web
en cours d'install sur l'infra osm.fr


C'est en ligne. Vous pouvez le tester.

Limitations actuelles, ça télécharge sur le serveur, mais vous ne pouvez 
re-télécharger dupuis serveur que les photo que une à une. À ajouter, un 
export de streaming en zip de toutes les photo.


Pas floutage, c'est les photo brutes.

La place sur le serveur est limité pour l'instant. Ne l'utilisez pas si 
vous avez beaucoup de photo Mapillary.


Les photo d'un seul utilisateurs à la fois sont téléchargées, il y a une 
liste d'attente.


Il faut donner son mot de passe Mapillay, en clair.

Les contrib sur le github sont les bienvenues.


https://mapillary-takeout-web.openstreetmap.fr/


Frédéric.



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

Re: [Talk-it] facebook compra mapillary

[mbranco2]

mah, parlando di privacy, anche prima si sapeva che un utente mapillary il
tal giorno alla tal ora si trovava nel tal posto (proprio come OSM sa che
il tal giorno alla tal ora stavo mappando una certa zona).
Non penso che possano in qualche modo associare gli account Mapillary (che
poi quasi tutti usiamo quello OSM) con quelli di FB; e anche se fosse, non
mi preoccupa visto che io l'account FB non ce l'ho... :-)

Il giorno lun 22 giu 2020 alle ore 16:57 Martin Koppenhoefer <
dieterdre...@gmail.com> ha scritto:

>
>
> sent from a phone
>
> > On 22. Jun 2020, at 15:44, mbranco2  wrote:
> >
> > Guarda Martin che non è così: il sito di mapillary continua a funzionare
> come sempre, e nel loro blog [1] dichiarano che tutto funzionerà come prima:
>
>
> solo che tutti i dati delle connessioni al loro sito ora finiscono sui
> server di facebook...
>
> Ciao Martin
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

Re: [Talk-cat] carreteres i pistes, unclassified vs grade1

[Jaume Figueras i Jové]

Hola,

estic quasi al 100% d'acord, esxepte quan dius que una pista asfaltada 
és highway=track tracktype=grade1. Jo hi afegiria surface=asphalt, o 
concrete, etc.


També afegiria en la teva explicació, l'ús, excepte contades ocasions la 
funció de la pista no és connectar nuclis, pot connectar masies, 
aïllats, té usos agricoles o forestals, però normalment no connecta nuclis.


Salut!

PS: Gràcies!! Que he aprofitat per canviar alguna pista al voltant del 
sanatori de Terrassa ara que s'hi movien tots els que no podien anar al 
bar. Que estaven malament.


On 21/6/20 22:30, Jan Esquerra wrote:

Bon dia a tothom i a totdon,

fa uns dies va sortir el tema al grup de Telegram, però no hi ha hagut 
més moviment i crec que el mitjà per debatre-ho és aquí, a la llista, 
per no barrejar temes i perdre el fil.

Desconec quanta gent hi ha aquí i allà, segur que falta algú.

Exposo el meu punt de vista:

A OSM hi ha una gran varietat i riquesa de tipus de vies de circulació 
per vehicles (que altres mapes no tenen), així hi ha 5 categories 
pistes, 5 categories de carretera, a més a més de les motorway i altres 
(residential, living_street, service, ...).


Crec que tots tenim clar que en les carreteres i pistes hi ha una 
gradació de millor a pitjor, de com quant bona és una via de circulació, 
és a dir, una /tertiary/ és millor que una /unclassified/, i una 
/unclassified /és millor que un /track grade1/, i un /track grade1/ és 
millor que un /track grade2/, i etc.


Si així és, es pot afirmar que no és el mateix una 
carretereta (unclassified) que una pista asfaltada (track grade1), i per 
tant, algunes diferències tindran, no? Per, mi és clar que són diferents 
i així ho hem de poder diferenciar en el mapa.


Per això em sembla equivocat i desencertat dir que qualsevol via de 
circulació asfaltada ja és una carretera.


Ah... El quit de la qüestió és: què vol dir millor o pitjor? I 
quines són aquestes diferències i com les podem identificar objectivament?


Doncs no seré jo qui us ho resolgui, però deixeu-me que us exposi les 
meves reflexions.


Des d'un punt de vista de la seva construcció, en general, i pel que jo 
conec:


- en la construcció d'una pista s'adapten a lo que permet el terreny 
intentant no gastar-s'hi gaires duros, o sigui que el que podem trobar 
és amplada la justa, corbes molt tancades i pendent el que sigui, ...


- en canvi, en les carreteres s'hi gasten més calers buscant un traçat 
més fluid i més segur, amb corbes més obertes, pendents més suaus, i si 
cal es fan ponts, trinxeres, túnels. Posats a gastar, l'asfalten, la 
pinten i la rematen amb cuneta, alguna senyal i guarda-rails. Quasi 
segur que qui està disposat a gastar-se més calers en la construcció 
d'una carretera és una administració o una gran empresa.



Des del punt de vista d'usuari de la vía:

- en una pista, encara que sàpiga que està asfaltada, circularé amb 
molta atenció ja que em puc trobar sorpreses: vehicles de cara en trams 
estrets, corbes sobtades i molt tancades, sense visibilitat, pendents 
exagerats, a part de les condicions de conservació (ferm en mal estat, 
pedres, rocs, branques, ...). És més, segons amb quin vehicle vagi 
(camions, remolc, autocaravanes, etc), sense conèixer-la millor no 
ficar-s'hi i buscar rutes alternatives o te la jugues a tenir problemes.
O vist d'una altra manera, anat amb un cotxe normal de nit i plovent, 
per una pista asfaltada he d'anar molt alerta perque em puc trobar 
qualsevol cosa.


- en una carretera puc circular més tranquil, o si més no, amb més 
garanties.



Evidentment, entre aquests dos exemples teòrics hi ha mil exemples de 
vies que estaran entremig. Per no parlar del traçat d'algunes 
carreteretes de fa 70 anys, i que malgrat la seva classificació 
administrativa deixen molt que desitjar (això és tema per un altre fil, 
jajaja).


Proposo el següent:

1- una pista que un bon dia decideixen asfaltar-la, sense fer-hi gaires 
més arranjaments és un highway = track + tracktype = grade1.
Podrem circular més ràpid i més còmodes que quan estava sense 
pavimentar, però excepte la superfície, la resta segueix igual.


2- una pista, que a més a més d'asfaltar-la, li fan altres obres de 
millora, com ara, eixamplar-la, arreglar corbes tancades, sanejar 
talussos, amb cuneta, pintura vial, senyals verticals, guarda-rails, 
etc. doncs podem dir que l'han millorat a carretera.


3- una carretera també serà aquella que ja des del seu inici, es fa un 
estudi i un projecte, i s'executa amb un traçat i unes característiques 
constructives que la fan millor que una simple pista afaltada.


4- en aquells casos que ni es clarament una pista que han asfaltat sense 
més, ni és una carretera que sabem/veiem que s'han gastat els quartos, 
si tenim dubtes fem-nos les següents preguntes:

   - té corbes molt tancades sense senyalitzar?
   - té algun tipus de pintura, senyalització o protecció que millori la 
seguretat?

   - m'hi ficaria amb un vehicle de gran volum 

Re: [Talk-it] facebook compra mapillary

[Martin Koppenhoefer]

sent from a phone

> On 22. Jun 2020, at 15:44, mbranco2  wrote:
> 
> Guarda Martin che non è così: il sito di mapillary continua a funzionare come 
> sempre, e nel loro blog [1] dichiarano che tutto funzionerà come prima:


solo che tutti i dati delle connessioni al loro sito ora finiscono sui server 
di facebook...

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

Re: [OSM-ja] 郡名の英語表記について

[OKADA Tsuneo]

岡田です。

郡名の英訳統一に3名の方に賛意をいただきありがとうございます。
他のページではCountyとなっているので、Japan taggingのページもDistrictからCountyに
変えようと思います。
wikiと登録されているデータは私の方で変えておきます。
(もちろん先にどなたかが変えていただいてもかまいません)



2020年6月20日(土) 9:30 tomoya muramoto :

> DistrictよりCountyのほうがよいという意見に賛成です。
>
> ただ、Japan taggingのガイドラインでは、
>
> ・Metropolis・Prefecture（北海道は除く）・Subprefecture・District・Ward（東京23区は除く）・-chomeを付ける。
> ・City・Ward（東京23区のみ）・Town・Villageは付けない。
> となっており、不統一感を覚えました。
>
> 郡・都道府県と市町村でname:enのガイドラインが異なる理由をご存知の方がいましたら教えていただけませんでしょうか。
>
> muramoto
> ___
> Talk-ja mailing list
> Talk-ja@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ja
>


-- 
岡田常雄(OKADA Tsuneo)
tsuneo.ok...@gmail.com
___
Talk-ja mailing list
Talk-ja@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ja

Re: [Talk-it] facebook compra mapillary

[mbranco2]

Guarda Martin che non è così: il sito di mapillary continua a funzionare
come sempre, e nel loro blog [1] dichiarano che tutto funzionerà come prima:
*Our OpenStreetMap commitment*

*Our commitment to OpenStreetMap stays. The plan is for the rights given to
OpenStreetMap editors to remain unchanged and for our work with
OpenStreetMap communities and companies to continue on the same path as
always. Mapillary will continue to spearhead a collaborative model where
all map communities, companies, cities, and others work together to keep
the maps of our world accurate, detailed, and up to date.*


[1] https://blog.mapillary.com/news/2020/06/18/Mapillary-joins-Facebook.html

Il giorno dom 21 giu 2020 alle ore 19:45 Martin Koppenhoefer <
dieterdre...@gmail.com> ha scritto:

>
>
> sent from a phone
>
> > On 21. Jun 2020, at 19:39, Martin Koppenhoefer 
> wrote:
> >
> > tra un po' FB vorrà rendere disponibili le immagini solo all'interno
> della sua piattaforma
>
>
> forse ho scritto troppo presto, ovviamente FB già da ora rende disponibile
> le foto solo all’interno della sua piattaforma, perché Mapillary è
> diventato parte della piattaforma di facebook. Così come Whatsapp, Oculus
> VR e altri.
>
> Ciao Martin
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it

[Talk-br] Importação de transformadores: Uso da "tag name"

[Mapas Osm]

Olá,
Quanto ao uso das tags "ref" e "pole" os códigos dos transformadores só
podem ser visualizados nos modos de edição do OpenStreetMap. Só consegui
consultá-los usando as tags"transformer_tower" e substituindo "ref" por
"name".
Existe alguma forma de mapeamento mais correta que essa em que é possível
consultar os códigos de transformadores diretamente no campo de consulta do
OpenStreetMap?

Em quinta-feira, 18 de junho de 2020 às 12:57 <
talk-br-requ...@openstreetmap.org> escreveu:

> Enviar submissões para uma lista de discussão Talk-br para
> talk-br@openstreetmap.org
>
> Para se registrar ou descobrir via WWW, visite o endereço
> https: //lists.openstreetmap.or g / listinfo / talk-br
> 
> ou, via e-mail, envie uma mensagem com a palavra 'ajuda' no assunto ou no
> corpo da mensagem para
> talk-br-request @ openstreetmap. org
> 
>
> rápido Você podera ENTRAR em Contato com uma pessoa that Gerencia uma
> Lista cabelo
> endereco
> talk-br-ow...@openstreetmap.or g 
>
> QUANDO responder, por favor edite SUA Linha Assunto ASSIM ELA Será
> Mais Específica que "Re: Conteúdo da conversa-br digerir. .. "
>
>
> Tópicos de Hoje:
>
>1. Re: Digest Talk-br, volume 141, assunto 5 (Helio Cesar Tomio)
>
>
> --  -- --
>
> Mensagem: 1
> Data: Qui, 18 Jun 2020 12:57:03 -0300
> De: Helio Cesar Tomio < hcto...@gmail.com >
> Para : OpenStreetMap no Brasil < talk-br@openstreetmap.org >
> Assunto: Re: [Discussão-br] Digest conversa-br, o volume de 141, ASSUNTO 5
> Message-ID:
> < CAE1uxb1UtokKTyVGUXKQYbyV8CRW 9nsebq8z_gj7mljoy2g...@mail.gm
> ail.com
>  >
> Content-Type : texto / planície; charset = "utf-8"
>
> Uma carta de solicitação para uma empresa não precisa ser exatamente como
> o
> modelo que o ambiente.
> Basta autorizar ou usar dados de forma livre para realizar um
> importação no Openstreetmap, compatível com uma licença do OSM.
>
> Vc precisa ter o cuidado para não fazer edições que não segue as regras
> das tags já aprovadas.
> Por exemplo, eu acho muito estranho colocar o nome nas postagens. Não sei
> dizer
> se isso está correto. Seria como colocar o nome em lixeiras, hidrantes,
> orelhões, ...
> E uma tag de construção não parece adequada para postagens, qdo vc tem por
> exemplo
> power = pole.
>
> Recentemente foram aprovadas novas tags para linhas de energia, talvez na
> linha do seu trabalho:
> https://wiki.openstreetmap.org / wiki / Features_propostas / Linhas_ de
> gerenciamento
> 
>
> Nas tuas futuras importações, necessário verificar a localização dos postes
> não está correto no OSM. Erro de referência não utilizado
> (sad69 / sirgass2000 / wgs84) que foi comprometido.
> Foi constatado que muitos posts acabaram ficando dentro de lotes ou
> alterações, devido a algumas divergências de informações.
>
> Se parece que chatice tudo isso, mas uma comunidade se preocupa com os
> dados do OSM não se transforma em uma confusão ou em informações erradas
> ou
> inúteis.
>
> Cordialmente,
> Tomio
>
> Em 17 de junho de 2020 14:26, Mapas Osm < mapas...@gmail.com > Escrito
>  :
>
> > Um respeito pela licença de dados, a mesma confirmação confirmada por
> meio de carta
> > (modelo em anexo).
> > Os dados são do tipo ponto no formato shapefile coletado com receptor
> > GNSS com códigos de identificação de cada transformador e chave em
> alguns
> > municípios dos estados de São Paulo e Mato Grosso do Sul.
> > A metodologia de importação seria útil para Josm importar os dados em
> > blocos e realizando todas as correções de conflitos que vieram a
> aparecer.
> > Para consultar os códigos ou os pontos que precisam ser mapeados com
> > "tag = building_transformer-towe r" e "ref" substituída por "name".
> >>
> Em terça-feira  , 16 de junho de 2020 às 08:44 Mapas
> Osm < mapas...@gmail.com > escreveu:
> >
> >> Segue o anexo
> >>
> mapas...@gmail.com > escreveu:
> >>
> >>> Obrigado pelos esclarecimentos,
> >>> Em relação à licença, usando o modelo de carta em anexo, já é possível
> >>> garantido?
> >>>
> >>> Em terça-feira  , 16 de junho de
> 2020 às 08:01 < talk-br-request @ openstreetmap
> .org
>  >
> >>> escreveu:
> >>>
>  Enviar submissões para uma lista de discussão Talk- br para
>   talk-br@openstreetmap.org
> 
>  Para se registrar ou descobrir via WWW, visite o endereço
>   https: //lists.openstreetmap.
> 
>
>  corpo da mensagem para
>   talk-br-request @ openstreetmap.org
> 
> 
>  Você pode entrar em contato com uma pessoa que gerencia uma lista
> pelo
>  endereço
> >>> >  talk-br-owner@openstreetmap.o rg
> 
> 
>  Quando responder, por favor edite sua linha Assunto como ela será
>  mais específica que "Re: Conteúdo do Talk-br digest ... "
> 
> 
>  

Re: [Talk-GB] TfL Cycle Infrastructure Database - matching against OSM

[Mateusz Konieczny via Talk-GB]

Jun 21, 2020, 03:54 by talk-gb@openstreetmap.org:

>
>
>
> Jun 21, 2020, 01:28 by list-osm-talk...@cyclestreets.net:
>
>> We think in particular that a significant part of the cycle parking data 
>> (generally the residential areas, where there is little parking presently) 
>> and the speed bumps data are ripe for automated conversion. These form tens 
>> of thousands of locations which we feel are very low risk, useful data, and 
>> eminently suitable for import.
>>
>> Speed bumps:
>> https://bikedata.cyclestreets.net/tflcid2osm:type=bumps_road/#14.98/51.47101/-0.02755
>>
>> Cycle parking:
>> https://bikedata.cyclestreets.net/tflcid2osm:type=parking_new/#14.98/51.46059/-0.05586
>>
> please, please, please do not add useless fixme tags
>
> fixme=Check bike parking type
>
> is not needed - just lack of bicycle_parking tag is enough to note that,
> and will be spotted by tools such as StreetComplete
>
> (spotted on id RWG102691)
>
I opened https://github.com/cyclestreets/tflcid-conversion/issues/36

>
>
> And instead of
> bicycle_parking=locked
> note=Own lock
>
> use
> access=private
>
> (id RWG102738)
>
and https://github.com/cyclestreets/tflcid-conversion/issues/37

> I remember big import preparations that had issue tracker about tag 
> conversion 
> - is it this project?
>
hopefully it is the correct location
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

[talk-au] Anyone famililar with

[Bo Percival]

Hi all,

Just a quick query, if anyone has experience with or knows of the work of
https://geoscape.com.au, could you reach out? I would be interested in
having a chat with them.

Kindness,

bo

-- 
*Bo Percival*
Director of Technology & Innovation
bo.perci...@hotosm.org
@bopercival

*Humanitarian OpenStreetMap Team*
*Using OpenStreetMap for Humanitarian Response & Economic Development*
web  | twitter  | facebook
 | donate 
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au

Re: [Talk-us] National Forest boundaries

[Mike Thompson]

On Sun, Jun 21, 2020 at 10:54 PM Bradley White 
wrote:
>
> > A relation for all would be ok too, as long as the private inholdings
are
> > not removed from the NF (which I think has been done in some cases).
>
>
> IMO, a tagging scheme that better represents the meaning of these two
> boundaries would be:
> 1. 'boundary=protected_area' around fee simple NF land ownership,
> since this describes the actual protected areas of land
> 2. 'boundary=administrative' (with a not-yet-existing 'admin_level')
> around declared NF boundaries, since this is an administrative
> boundary for the NF and doesn't necessarily show what land is actually
> managed by the NF.
The above is a good and workable solution in my opinion.
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [OSM-talk-fr] cadastre.openstreetmap.fr ???

[Vincent de Château-Thierry]

Bonjour Hélène,

> De: "Hélène PETIT" 
> 
> http://cadastre.openstreetmap.fr/
> 
> me donne une 403 forbidden.
> C'est normal ?

Pas forcément, mais tu peux accéder à une partie des ressources via 
https://bano.openstreetmap.fr/

vincent

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

Re: [OSM-talk-fr] Nouveau dépliant OpenStreetMap chez Linux-Alpes

[PanierAvide]

L'URL doit être celle-là : 
https://wiki.openstreetmap.org/wiki/France/Support_Communication


Cordialement,

Adrien P.

Le 22/06/2020 à 13:46, Cyrille37 OSM a écrit :

Bonjour

Peut être ajouter le lien sur la page "FR:Mémo pour cartopartie" du 
wiki 
https://wiki.openstreetmap.org/wiki/FR:M%C3%A9mo_pour_cartopartie#M.C3.A9diatisation


Peut être créer un nouveau sous chapitre à "Médiatisation", dans leque 
il y a un point "affiche" qui pourrait être développé ainsi.


Et sur d'autres pages que je n'ai pas en tête ; celle de l'asso où il 
y des dépliants mais dont je ne trouve pas l'url là tout de suite.


Bonne root
Cyrille37.

Le 22/06/2020 à 06:50, Jean-Christophe Becquet a écrit :

Bonjour,

L'association Linux-Alpes qui porte le groupe OSM Digne a travaillé sur
un nouveau dépliant de présentation d'OpenStreetMap.
http://www.linux-alpes.org/depliant-openstreetmap/

Ce document petit format a été distribué en amont de la cartopartie des
commerces et services du centre ville organisée à Digne jeudi 18 juin.
http://www.linux-alpes.org/cartopartie-reussie-a-digne-les-bains/

Nous nous sommes efforcés de veiller au vocabulaire employé afin de
garder le contenu le plus accessible possible pour un public novice.
Dans un souci d'exemplarité, nous avons apporté une grande attention aux
mentions de crédits et de licences.

Afin de permettre sa réutilisation dans d'autres contextes, nous l'avons
réalisé intégralement avec des logiciels libres dont Inkscape pour la
mise en page. Nous partageons les sources sous licence libre Creative
commons BY-SA.

Nous encourageons donc les groupes locaux mais aussi les structures de
médiation numérique, les collectivités ou les entreprises qui souhaitent
contribuer à la promotion d'OpenStreetMap à reprendre et à adapter cette
ressource à leur contexte local et à la décliner selon leur thématique.

Pour notre part, nous envisageons par exemple d'illustrer la prochaine
version avec un rendu OpenTopoMap.
https://opentopomap.org/#map=14/44.09279/6.23603

Bien entendu, nous recevrons avec plaisir vos réactions et propositions
d'amélioration.


L'association Linux Alpes publie un #flyer @OSM_FR @openstreetmap sous
licence libre, recto-verso personnalisable pour vos événements locaux.
https://twitter.com/Linux_Alpes/status/1274362587006861312

Bonne journée

JCB


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


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

Re: [OSM-talk-fr] Nouveau dépliant OpenStreetMap chez Linux-Alpes

[Cyrille37 OSM]

Bonjour

Peut être ajouter le lien sur la page "FR:Mémo pour cartopartie" du wiki 
https://wiki.openstreetmap.org/wiki/FR:M%C3%A9mo_pour_cartopartie#M.C3.A9diatisation


Peut être créer un nouveau sous chapitre à "Médiatisation", dans leque 
il y a un point "affiche" qui pourrait être développé ainsi.


Et sur d'autres pages que je n'ai pas en tête ; celle de l'asso où il y 
des dépliants mais dont je ne trouve pas l'url là tout de suite.


Bonne root
Cyrille37.

Le 22/06/2020 à 06:50, Jean-Christophe Becquet a écrit :

Bonjour,

L'association Linux-Alpes qui porte le groupe OSM Digne a travaillé sur
un nouveau dépliant de présentation d'OpenStreetMap.
http://www.linux-alpes.org/depliant-openstreetmap/

Ce document petit format a été distribué en amont de la cartopartie des
commerces et services du centre ville organisée à Digne jeudi 18 juin.
http://www.linux-alpes.org/cartopartie-reussie-a-digne-les-bains/

Nous nous sommes efforcés de veiller au vocabulaire employé afin de
garder le contenu le plus accessible possible pour un public novice.
Dans un souci d'exemplarité, nous avons apporté une grande attention aux
mentions de crédits et de licences.

Afin de permettre sa réutilisation dans d'autres contextes, nous l'avons
réalisé intégralement avec des logiciels libres dont Inkscape pour la
mise en page. Nous partageons les sources sous licence libre Creative
commons BY-SA.

Nous encourageons donc les groupes locaux mais aussi les structures de
médiation numérique, les collectivités ou les entreprises qui souhaitent
contribuer à la promotion d'OpenStreetMap à reprendre et à adapter cette
ressource à leur contexte local et à la décliner selon leur thématique.

Pour notre part, nous envisageons par exemple d'illustrer la prochaine
version avec un rendu OpenTopoMap.
https://opentopomap.org/#map=14/44.09279/6.23603

Bien entendu, nous recevrons avec plaisir vos réactions et propositions
d'amélioration.


L'association Linux Alpes publie un #flyer @OSM_FR @openstreetmap sous
licence libre, recto-verso personnalisable pour vos événements locaux.
https://twitter.com/Linux_Alpes/status/1274362587006861312

Bonne journée

JCB


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

Re: [Talk-GB] SotM shirts to the UK

[Dan S]

Hi Gregory

Aha, thanks for checking it out! I would be one happy customer.

(FWIW, I used Teemill for one design* - expensive print-on-demand £19
but with good ethical credentials.)

Cheers
Dan

* https://digitalcommoner.teemill.com/




Op ma 22 jun. 2020 om 11:16 schreef Gregory Marler :

>
> Hello everyone,
>
> This year State of the Map (SotM) conference is virtual, so you don't need to 
> travel to attend! Instead of getting a shirt at the registration desk, 
> volunteers are being asked to setup regional online shops[1].
>
> I did contact the SotM 2013 Birmingham supplier[2]. However to do them well 
> we'd need a minimum of 25, and it would cost about £8 + £6 postage per shirt. 
> Deadline to place orders would be the end of this weekend if you want them in 
> time to watch the conference. We concluded the postage cost and the rush 
> makes this not the best deal for OSMers.
>
> I'll see if someone sets up a section in one of the big custom-print sites 
> for Europe (that covers the UK), or I might look at helping with that myself.
>
> Watch this space!
>
>
> Gregory (LivingWithDragons)
>
> [1] T-shirt shop organisation 
> https://wiki.openstreetmap.org/wiki/State_of_the_Map_2020/Tshirt_shop_organization
> [2] https://www.movingforwardsports.co.uk/
> ___
> Talk-GB mailing list
> Talk-GB@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-gb

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

Re: [OSM-talk-fr] Nouveau dépliant OpenStreetMap chez Linux-Alpes

[GarenKreiz]

Ok merci pour le lien. Une collection impressionnante pour de nombreux
domaines!





On Mon, 22 Jun 2020 at 12:56, Jean-Christophe Becquet 
wrote:

> Le 22/06/2020 à 09:58, GarenKreiz a écrit :
> > Petite question : certaines icônes utilisées pour illustrer les points
> > d'intérêts sur le dépliant ressemblent très fortement à celles de
> > l'application Android Locus Map (forme globale, couleurs, graphismes) .
> > Si c'est bien le cas, sont-elles sous une licence qui permet leur
> > réutilisation dans d'autres cadres que ce dépliant?
>
> Les icônes proviennent de l'excellente Map Icons Collection partagée
> sous licence libre Creative Commons 3.0 BY-SA par Nicolas Mollet :
>
> https://mapicons.mapsmarker.com
>
> Librement
>
> JCB
> --
> George Bernard Shaw : si tu as une idée, que j'ai une idée et que l'on
> échange nos idées, nous aurons chacun deux idées
>
> http://www.apitux.org/index.php?2007/07/09/106-george-bernard-shaw-si-tu-as-une-idee-que-j-ai-une-idee-et-que-l-on-echange-nos-idees-nous-aurons-chacun-deux-idees
>
> ==APITUX : le choix du logiciel libre==
>
> APITUX - Jean-Christophe Becquet
> 2 chemin du Tivoli - 04000 Digne-les-Bains
> 06 25 86 07 92 - j...@apitux.com - http://www.apitux.com
> SIRET : 452 887 441 00031 - APE : 6202A
>
> ===
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [OSM-talk-fr] Nouveau dépliant OpenStreetMap chez Linux-Alpes

[Jean-Christophe Becquet]

Le 22/06/2020 à 09:58, GarenKreiz a écrit :
> Petite question : certaines icônes utilisées pour illustrer les points
> d'intérêts sur le dépliant ressemblent très fortement à celles de
> l'application Android Locus Map (forme globale, couleurs, graphismes) .
> Si c'est bien le cas, sont-elles sous une licence qui permet leur
> réutilisation dans d'autres cadres que ce dépliant?

Les icônes proviennent de l'excellente Map Icons Collection partagée
sous licence libre Creative Commons 3.0 BY-SA par Nicolas Mollet :

https://mapicons.mapsmarker.com

Librement

JCB
-- 
George Bernard Shaw : si tu as une idée, que j'ai une idée et que l'on
échange nos idées, nous aurons chacun deux idées
http://www.apitux.org/index.php?2007/07/09/106-george-bernard-shaw-si-tu-as-une-idee-que-j-ai-une-idee-et-que-l-on-echange-nos-idees-nous-aurons-chacun-deux-idees

==APITUX : le choix du logiciel libre==

APITUX - Jean-Christophe Becquet
2 chemin du Tivoli - 04000 Digne-les-Bains
06 25 86 07 92 - j...@apitux.com - http://www.apitux.com
SIRET : 452 887 441 00031 - APE : 6202A

===

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

Re: [Talk-us] Labeling county roads (Idaho)

[Mark Brown]

Thanks for all the feedback, especially from Kevin.

I will create road route relations as suggested, as I come across them. 



---


On Sun, 21 Jun 2020 18:35:28 -0700, Mark Wagner  wrote:

> On Sun, 21 Jun 2020 21:45:19 +0900
> tj-osmw...@lowsnr.net wrote:
> 
> > Newby here.
> > 
> > Started mapping an area of the Idaho panhandle around the Kootenai
> > river. I notice that currently minor roads have a "County Road nn"
> > name but TIGER2019 data also has names such as "Acacia Avenue". I
> > think most map users would want to use the "Acacia Avenue" name as it
> > what would be listed in postal addresses and they'd want to search it
> > in applications such as OSMand. Question is how to handle this. Also,
> > what to set the "ref" to for county roads.
> > 
> > There's not much information on the roads tagging page:
> > 
> > https://wiki.openstreetmap.org/wiki/United_States_roads_tagging#Individual_states_2
> > 
> > Proposal: use alt_name for "County Road nn" and name for "Acacia
> > Avenue" where a name is given. (I've seen name_1 used but this is not
> > really a "standard" OSM tag, AFAIK.)
> > 
> > For ref: set the ref to the county road number until someone can come
> > up with a better proposal...
> > 
> > Any Idahoans have any information?
> 
> Not an Idahoan, but I've driven in the area from time to time.  The
> roads I'm familiar with don't have a "County Road" designation on the
> sign, just the road name.
> 
> -- 
> Mark
> 
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us



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

[OSM-talk-fr] Assemblée Générale OSM-fr du 13 juin, résultat des votes

[Vincent Bergeot]

Bonjour,

cette année pour l'Assemblée Générale de l'association OpenStreetMap 
France 
(https://wiki.openstreetmap.org/wiki/France/OSM-FR/AGO_2020-06-13), les 
votes ont eu lieu dans la semaine qui a suivi la tenue de l'AG en 
visioconférence.


En résumé, concernant le vote :

139 votants, 77 exprimés

Bilan Moral :         76 oui     1 Vote blanc

Bilan Financier :     74 oui         3 Vote blanc

Sont élu-e-s au Conseil d'Administration :

Tony Emery, Donat Robaux, François Lacombe, Vincent Bergeot, 
Louis-Julien de la Bouëre, Christian Quest, René Chalon, Delphine 
Montagne, Fabienne Morel, Cécile Guégan, Jocelyn Jaubert, Frédéric 
Rodrigo, and Vincent de Château-Thierry


Tous les résultats ici : https://www.opavote.com/results/6010892359565312/1

La pression fut insoutenable cette année, une semaine à attendre !

Et si vous voulez en savoir plus sur le déroulé : vous avez des éléments 
sur le wiki cité plus haut, des notes ont été prises et beaucoup de 
discussions !


Bonne journée

--
Vincent Bergeot


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

[Talk-GB] SotM shirts to the UK

[Gregory Marler]

Hello everyone,

This year State of the Map (SotM) conference is virtual, so you don't need
to travel to attend! Instead of getting a shirt at the registration desk,
volunteers are being asked to setup regional online shops[1].

I did contact the SotM 2013 Birmingham supplier[2]. However to do them well
we'd need a minimum of 25, and it would cost about £8 + £6 postage per
shirt. Deadline to place orders would be the end of this weekend if you
want them in time to watch the conference. We concluded the postage cost
and the rush makes this not the best deal for OSMers.

I'll see if someone sets up a section in one of the big custom-print sites
for Europe (that covers the UK), or I might look at helping with that
myself.

Watch this space!


Gregory (LivingWithDragons)

[1] T-shirt shop organisation
https://wiki.openstreetmap.org/wiki/State_of_the_Map_2020/Tshirt_shop_organization

[2] https://www.movingforwardsports.co.uk/
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [OSM-talk-fr] Alternatives à Mapillary

[Stéphane Péneau]

Le 22/06/2020 à 10:53, Marc M. a écrit :

cela ne dépend-t-il pas du but et de l'accessibilité ?
par analogie geofabrik a restreint les données personnelles
aux contributeurs osm mais ils sont accessible aux contributeurs.
du coup un openstreetview accessible qu'aux contributeurs osm
est peut-être un groupe privé dispensé de ce genre de soucis.



Il faudrait vérifier, mais à partir du moment où n'importe qui peut 
devenir contributeur, je doute qu'on puisse considérer ça comme "privé".


Geofabrik a fait ces modifications pour le RGPD, mais pour les photos, 
il faut ajouter les restrictions du droit à l'image.


Pour ceux qui veulent creuser :

https://www.youtube.com/watch?v=-PP_aexji_s
https://blog.droit-et-photographie.com/

Stf



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

[OSM-talk-fr] Présentation European Water Project en visio cet apres-midi

[Yves P.]

Bonjour,

Stuart va présenter son projet, et indirectement OSM 

Le projet devrait intéresser bon nombre d'entre nous, et sa portée est
internationale.

__
Yves

-- Forwarded message -
De : European Water Project 
Date: mer. 17 juin 2020 à 10:53
Subject: Presentation at the World Summit of Information Society (WSIS 2020)
To: 
Cc: Stéphanie Rapoport 


Dear all,

We will present* European Water Project* and the NGO’s goal in its combat
against single-use plastic at the *WSIS* (World Summit of Information
Society) next *Monday, June 22nd, at 1 PM* Paris time. It is organised by
the ITU (International Telecommunication Union).

Everything will happen online because of Covid, so you actually have a
unique opportunity to attend the presentation without having to travel to
Geneva!

For those of you who can / want to come and listen to the presentation, you
can click on the link, you just need to register in advance.

 https://itu.zoom.us/webinar/register/WN_loayI_bXQ7iUSTZBEJ_2QQ



We wanted to share this exciting news with you as it will be an opportunity
to fully present European Water Project to you.


Thank you for your support.


Kind regards,


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

Re: [Talk-it] Import civici Milano - regole di traduzione

[Francesco Ansanelli]

Ciao,

Il lun 22 giu 2020, 09:25 Cascafico Giovanni  ha
scritto:

> Il 31/10/18, Andrea Musuruane ha scritto:
>
> > Il campo addr:housenumber conterrà il valore di NUMEROCOMP, con le
> > eventuali lettere convertite in minuscolo.
> >
> > NUMEROCOMP, seguendo quanto descritot nel file Istruzioni tecniche per
> > l'utilizzo dei dati_CIVICI.pdf è: NUMERO+LETTERA+BARRA
> >
> > Lo slash non viene usato se non per separare gli esponenti numerici.
>
>
> semi-OT:
>
> in Friuli mi sono trovato il caso (sul campo) di civici
> 9 bis/1
> 9 bis/2
> ...
>

Perché non li lasci così (omettendo gli spazi)? Es. 9bis/1


> di fatto sono unità immobiiari indipendenti, ciscuna con il suo
> ingresso, per cui non mi sentirei di definirli "interni". In ogni
> caso, visto che eliminare la barra non è deleterio per
> l'interpretazione del numero, li ho mappati come
> 9bis1
> 9bis2
> ...
>
> ___
> 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] cadastre.openstreetmap.fr ???

[Hélène PETIT]

Bonjour à tout le monde !

http://cadastre.openstreetmap.fr/

me donne une 403 forbidden.
C'est normal ?

A plus,
Hélène

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

Re: [OSM-talk-fr] Alternatives à Mapillary

[Yves P.]

Le logiciel Digikam dispose d'un module de détection de visages.
Je trouve qu'il y a beaucoup d'erreurs.

https://www.digikam.org/

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

Re: [OSM-talk-fr] Alternatives à Mapillary

[Marc M.]

Bonjour,

Le 22.06.20 à 10:29, Stéphane Péneau a écrit :
> Recensons les alternatives complètes ou partielles à Mapillary, les
> briques réutilisables, etc...

https://github.com/gitouche-sur-osm/mapillary_takeout
https://github.com/frodrigo/mapillary_takeout_web
en cours d'install sur l'infra osm.fr

> il manque au moins le floutage, le nerf de la guerre.

cela ne dépend-t-il pas du but et de l'accessibilité ?
par analogie geofabrik a restreint les données personnelles
aux contributeurs osm mais ils sont accessible aux contributeurs.
du coup un openstreetview accessible qu'aux contributeurs osm
est peut-être un groupe privé dispensé de ce genre de soucis.

Cordialement,
Marc

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

Re: [OSM-talk-fr] Alternatives à Mapillary

[Cédric Frayssinet]

Openstreetcam floutte, un exemple : 
https://openstreetcam.org/details/553003/123/track-info


Le 22/06/2020 à 10:29, Stéphane Péneau a écrit :

Salut,


Recensons les alternatives complètes ou partielles à Mapillary, les 
briques réutilisables, etc...


Pour ceux qui sont motivés, on peut tenter de détailler les briques 
disponibles dans chaque cas.


https://opentrailview.org

https://github.com/openstreetcam/

https://github.com/mapillary/

https://openpathview.fr/

Dans tous ces cas, il manque au moins le floutage, le nerf de la guerre.


Vous en voyez d'autres ?


Stéphane


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


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

[OSM-talk-fr] Alternatives à Mapillary

[Stéphane Péneau]

Salut,


Recensons les alternatives complètes ou partielles à Mapillary, les 
briques réutilisables, etc...


Pour ceux qui sont motivés, on peut tenter de détailler les briques 
disponibles dans chaque cas.


https://opentrailview.org

https://github.com/openstreetcam/

https://github.com/mapillary/

https://openpathview.fr/

Dans tous ces cas, il manque au moins le floutage, le nerf de la guerre.


Vous en voyez d'autres ?


Stéphane


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

Re: [OSM-talk-fr] Nouveau dépliant OpenStreetMap chez Linux-Alpes

[GarenKreiz]

Beau travail!

Petite question : certaines icônes utilisées pour illustrer les points
d'intérêts sur le dépliant ressemblent très fortement à celles de
l'application Android Locus Map (forme globale, couleurs, graphismes) . Si
c'est bien le cas, sont-elles sous une licence qui permet leur
réutilisation dans d'autres cadres que ce dépliant?

Cordialement

Garenkreiz



On Mon, 22 Jun 2020 at 06:50, Jean-Christophe Becquet 
wrote:

> Bonjour,
>
> L'association Linux-Alpes qui porte le groupe OSM Digne a travaillé sur
> un nouveau dépliant de présentation d'OpenStreetMap.
> http://www.linux-alpes.org/depliant-openstreetmap/
>
> Ce document petit format a été distribué en amont de la cartopartie des
> commerces et services du centre ville organisée à Digne jeudi 18 juin.
> http://www.linux-alpes.org/cartopartie-reussie-a-digne-les-bains/
>
> Nous nous sommes efforcés de veiller au vocabulaire employé afin de
> garder le contenu le plus accessible possible pour un public novice.
> Dans un souci d'exemplarité, nous avons apporté une grande attention aux
> mentions de crédits et de licences.
>
> Afin de permettre sa réutilisation dans d'autres contextes, nous l'avons
> réalisé intégralement avec des logiciels libres dont Inkscape pour la
> mise en page. Nous partageons les sources sous licence libre Creative
> commons BY-SA.
>
> Nous encourageons donc les groupes locaux mais aussi les structures de
> médiation numérique, les collectivités ou les entreprises qui souhaitent
> contribuer à la promotion d'OpenStreetMap à reprendre et à adapter cette
> ressource à leur contexte local et à la décliner selon leur thématique.
>
> Pour notre part, nous envisageons par exemple d'illustrer la prochaine
> version avec un rendu OpenTopoMap.
> https://opentopomap.org/#map=14/44.09279/6.23603
>
> Bien entendu, nous recevrons avec plaisir vos réactions et propositions
> d'amélioration.
>
>
> L'association Linux Alpes publie un #flyer @OSM_FR @openstreetmap sous
> licence libre, recto-verso personnalisable pour vos événements locaux.
> https://twitter.com/Linux_Alpes/status/1274362587006861312
>
> Bonne journée
>
> JCB
> --
> Utopie du logiciel libre
> http://www.apitux.org/index.php?2008/05/29/247-utopie-du-logiciel-libre
>
> ==APITUX : le choix du logiciel libre==
>
> APITUX - Jean-Christophe Becquet
> 2 chemin du Tivoli - 04000 Digne-les-Bains
> 06 25 86 07 92 - j...@apitux.com - http://www.apitux.com
> SIRET : 452 887 441 00031 - APE : 6202A
>
> ===
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [OSM-talk-fr] Statistiques post-cartopartie

[Jean-Christophe Becquet]

Le 22/06/2020 à 03:20, Adrien André via Talk-fr a écrit :
> je suis à la recherche de ce qu'il est possible d'obtenir comme
> statistiques post-cartopartie (combien d'objets créés, total de longueur
> de voies, etc).
> 
> Il me semble avoir vu passer plusieurs fois le sujet, mais je ne me
> souviens plus dans quel canal et je ne trouve pas vraiment de doc
> là-dessus.
> 
> Par exemple avec OSMCha, on arrive à compter le nombre de changesets en
> filtrant sur des hashtags, mais pour l'instant je n'ai pas trouvé plus
> élaboré.
> 
> Auriez-vous plus d'infos ?

Bonjour Adrien,

Voici une requête Overpass qui recherche les objets modifiés sur une
zone entre 2 dates :
http://overpass-turbo.eu/s/Vk8

Bonne journée

JCB
-- 
Debian GNU-Linux
http://www.apitux.org/index.php?2006/07/10/15-debian-gnu-linux

==APITUX : le choix du logiciel libre==

APITUX - Jean-Christophe Becquet
2 chemin du Tivoli - 04000 Digne-les-Bains
06 25 86 07 92 - j...@apitux.com - http://www.apitux.com
SIRET : 452 887 441 00031 - APE : 6202A

===

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

Re: [Talk-it] Import civici Milano - regole di traduzione

[Cascafico Giovanni]

Il 31/10/18, Andrea Musuruane ha scritto:

> Il campo addr:housenumber conterrà il valore di NUMEROCOMP, con le
> eventuali lettere convertite in minuscolo.
>
> NUMEROCOMP, seguendo quanto descritot nel file Istruzioni tecniche per
> l'utilizzo dei dati_CIVICI.pdf è: NUMERO+LETTERA+BARRA
>
> Lo slash non viene usato se non per separare gli esponenti numerici.


semi-OT:

in Friuli mi sono trovato il caso (sul campo) di civici
9 bis/1
9 bis/2
...

di fatto sono unità immobiiari indipendenti, ciscuna con il suo
ingresso, per cui non mi sentirei di definirli "interni". In ogni
caso, visto che eliminare la barra non è deleterio per
l'interpretazione del numero, li ho mappati come
9bis1
9bis2
...

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

Re: [OSM-talk-fr] Facebook achète Mapillary !

[Leroy Olivier]

Potentiellement en lien avec le rachat voici une vidéo du "Facebook Reality
Labs" : https://www.youtube.com/watch?v=JTa8zn0RNVM

Comme souvent il est difficile de savoir la part de com' de la volonté de
fournir un produit/service de ce type.

Olivier




Le dim. 21 juin 2020 à 22:13,  a écrit :

> Je ne connaissais pas mais tout ça marche aussi depuis un Droid sans
> compte BigBrother.
>
> Et mon téléphone n'est pas un des modèles en question :-( Pas loin
> pourtant !
>
> Et non je n'ai jamais créé de compte Google (ni utilisé les applis
> propriétaire Google).
>
> Enfin si l'autre jour à cause d'une vidéoconférence mais je n'ai pas
> donné mon numéro de téléphone mais celui de quelqu'un d'autre^^.
>
> /e/ utilise l'ersatz de Google Plaie Sévices ?
>
> Merci pour ce retour d'expérience.
>
> Jean-Yvon
>
> Le 21/06/2020 à 16:49, Georges Dutreix via Talk-fr -
> talk-fr@openstreetmap.org a écrit :
> >
> >
> > Le 21/06/2020 à 15:50, Philippe Verdy a écrit :
> >> Tu as un compte Google sur ton Android dès le moement où tu acceptes
> >> les conditions initiales de l'OS et que tu inscrit ton numéro de
> >> téléphone ou email (même hors Google)
> >
> > Bonjour,
> >
> > Il existe des alternatives hors google, comme lineageos ou /e/, même
> > si elles ne sont pas encore très répandues.
> >
> > J'ai un téléphone "android" fonctionnant sous /e/
> > (https://e.foundation/?lang=fr), et je crois que d'autres personnes
> > ici ont également installé cet OS.
> > Je peux affirmer ne jamais avoir saisi de compte google sur ce téléphone.
> > Je précise aussi que j'ai pû installer toutes les applis dont j'avais
> > besoin (banque, applis synology, sncf, etc.), et en plus elles
> > marchent :-)
> >
> > Bien cordialement,
> > Georges
> >
> >
> >
> > ___
> > 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
>


-- 
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