Re: [OSM-talk] Reordering and rewriting Good Practice wiki page

[dcapillae]

These days I've been busier than usual updating the Spanish version of the
"Good practice" page. Now I know why.

Thank you all.

Regards,
Daniel



--
Sent from: http://gis.19327.n8.nabble.com/General-Discussion-f5171242.html

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

Re: [OSM-talk] OSM user diary etiquette

[dcapillae]

It would hurt a Philosophy student to read that.

Socrates didn't write anything. Plato would write it.

Excuse me for this off-topic.



--
Sent from: http://gis.19327.n8.nabble.com/General-Discussion-f5171242.html

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

Re: [Talk-in] Open Government Data- India Health Facilities Import

[Naveen Francis]

Thank you, Aruna

This is a very important dataset which has to be imported to OSM.
Every time when we discuss with govt on open geodata, we lacked a use-case
to show.
This import will help in that direction.

And as per osm-analytics tool
,
there are only 6549 hospitals mapped till now in India.
This import will help to add more hospitals.

Thanks
naveenpf


On Tue, 9 Jul 2019 at 17:02, Aruna Valli 
wrote:

> Hello OSM Community,
>
> I, Aruna, on behalf of RMSI would like to propose an import of Health
> facilities of India. The source data is provided by the Open Government
> Data (OGD) which is globally available to everyone - India Data Sources
> which is under a compatible license for Import.
> This import will improve the accessibility of the health care information
> in OSM- India. We have communicated about the dataset in multiple platforms
> - GitHub, OSM Forum, Telegram etc...
>
> The data sources (OGD) provides the health related information of India in
> three different directories and has good coverage of the facilities
> information all over the India https://wiki.openstreetmap.org/wiki/
> File:India_Health_Facility.jpg
> 
> .
> • Hospital Directory: Includes private hospitals, clinics, Government
> hospitals, nursing homes etc...
> • NIN health facilities: Includes health centers- PHCs, CHCs, sub centers,
> dispensaries, area hospitals, PPUs etc...
> • Blood banks : Includes blood bank units in hospitals, blood banks.
>
> To analyze the data quality we have selected our AOI as Hyderabad and
> other sub regions of Telangana based on our local knowledge by using the
> Maproulette challenges. In addition to local regions we have also created
> MR Challenges to the community for the other regions - Bihar & Bangalore to
> improve their own localities based on the local knowledge.
>
> While analyzing the data of NIN health facility directory for PHC’s,
> CHC’s, UPHC’s etc…we observed that it has a huge set of unique information
> of “sub centers” which is covering all over the India.
> As these dataset has good coverage even in the remote areas as well, it
> will be of greater help in the time of need. So we are planning to import
> these facilities with small batches in each submission, based on the city
> or block size.
>
> This proposal has been cross-posted in
> • GitHub -> https://github.com/osm-in/mapping/issues/2
> ,
> https://github.com/RMSI-OSM/India-Health-Facilities
> 
> • Forum> https://forum.openstreetmap.org/viewtopic.php?id=66300
> 
> )
> • Telegram & Twitter.
>
> Please visit our import guidelines wiki document for more details:
> https://wiki.openstreetmap.org/wiki/India_Health_Facilities_Import
> 
>
> In this regard we are eagerly looking forward to working with the OSM
> Indian community to make OSM- India coverage better with high quality
> mapping.
>
> Many Thanks
> Aruna Valli Parimi
> Assistant General Manager (GIS)
> RMSI Pvt. Ltd
> Ascendas IT Park- Vega Building, 11th Floor
> Madhapur, Hyderabad, Telangana 50008
> Email: o...@rmsi.com
> Phone: +91 40 44347100 Extn: 2006.
> ___
> Talk-in mailing list
> Talk-in@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-in
>
___
Talk-in 

Re: [Talk-es] Etiqueta para centros de exámenes psicotécnico para tráfico.

[dcapillae]

Hola, Manuel.

Por tu descripción, imagino que te refieres a un centro de reconocimiento de
conductores. No existe una etiqueta específica en OSM para mapear centros de
reconocimiento de conductores (que yo sepa), pero puedes emplear el
etiquetado de un centro de reconocimiento médico general.

Yo usaría «amenity=doctors» junto con «name=*». Si quieres puedes usar el
esquema de etiquetado «healthcare» para especificar aún más, por ejemplo,
«healthcare:for=drivers» o algún otro valor de «healthcare» que veas que se
ajusta bien.[1]

En cualquier caso, siempre puedes usar «description=*» para describir el
tipo de centro, aunque con «amenity=doctors» y el nombre, «Centro Médico
para Conductores Tal y Cual...», queda claro de qué tipo de centro se trata.

Atentamente,
Daniel



--
Sent from: http://gis.19327.n8.nabble.com/Spain-f5409873.html

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

Re: [OSM-talk] How can I create a oshdb?

[Andrew Davidson]

https://github.com/GIScience/oshdb/blob/master/oshdb-tool/etl/README.md

On Sat., 13 Jul. 2019, 09:30 Milo van der Linden,  wrote:

> Thanks! The download server has no oshdb files for Curacao, the Caribbean
> Island I am interested in. Is there a converter available?
>
> Thanks again!
>
> On Fri, Jul 12, 2019, 23:18 Mateusz Konieczny 
> wrote:
>
>>
>> https://github.com/GIScience/oshdb/blob/master/documentation/first-steps/README.md
>> has some docs.
>>
>>
>> 12 Jul 2019, 23:11 by m...@dogodigi.net:
>>
>> Can anyone point me in the direction of how to create the ohsome oshdb
>> from planet files?
>>
>> Thanks in advance!
>>
>> Milo
>>
>> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

[Talk-uy] Proyecto de Importación de Direcciones

[Jorge Aguirre]

Aprovecho este medio para hacer de su conocimiento que con el equipo de 
editores del grupo Kaart estamos por iniciar un proyecto para hacer una 
importación de las direcciones de Uruguay.


Se puede leer más al respecto aquí 

 o en la página de wiki de OpenStreetMap del Uruguay 
 bajo el inciso - "5. 
Proyectos".


Estamos abiertos a sus comentarios al respecto para poder realizar esta 
actualización de la mejor manera posible.


Atentamente,

Jorge




Jorge Aguirre  | Kaart  |  +502.4191.1999  |  jo...@kaartgroup.com


KAART CONFIDENTIAL
This message (including any attachments) is for the private use of the 
addressee only and may contain confidential or privileged information. If you 
have received this message by mistake please notify the sender by return e-mail 
and delete this message and any attachments from your system. Any unauthorized 
use or dissemination of this message, and any attachments in whole or in part 
is strictly prohibited.

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

Re: [OSM-talk-fr] grèves Loire - résumé et conclusion ?

[marc marc]

Bonjour,

globalement c'est un bon résumé, quelques détails :

Le 12.07.19 à 23:29, François Boucault a écrit :
>   o source:geometry=survey (si relevé GPS) OU
> source:geometry=BDOrtho IGN (par exemple)
>   o source:geometry:date=* (date du relevé GPS ou de la prise de
> photo satellite)

cela n'a pas de sens de rajouter des tags source sur l'objet en 2019 :)
le suivant modifie un noeud, aucun outil ne met ses tags à jour et ils 
sont donc périmé. donc pour savoir si un tag source est bien 
d'actualité, il faut allez voir l'historique de l'objet donc à ce moment 
là on a tout aussi bien avec les tags sources su le changeset

>   o check_date=* (si on a été sur le terrain pour vérifier le tracé)

c'est survey:date

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

Re: [Talk-GB] Trig Point references

[Philip Barnes]

--- Original message ---
> On Friday, 12 July 2019, Dave F via Talk-GB wrote:
> > On 12/07/2019 21:19, Philip Barnes wrote:
> > > Hi Brian
> > > Each pillar has a plate with an OS reassigned reference, which is easily  
> > > on the ground verifiable. I believe that we should be using that rather 
> > > than those randomly assigned by a 3rd party site of unknown origin.
> > 
> > Hmm... Good job no one did 'randomly assigned' on PROWs 
> > 
> PROW references are assigned by the local highway authority, not randomly 
> assigned.
> 
> Trig points have an easily verifiable reference assigned by OS at the time of 
> construction, it makes sense to use that.
> 
> Phil (trigpoint)
> 
> -- 
> Sent from my Sailfish devic

-- 
Sent from my Sailfish device
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [Talk-us] Mapping rail trails

[stevea]

Phil! and Kevin, I like everything said!

"Huge are tough to edit," yes.  "Tie them all together with a super-relation to 
show that they are together with certain tags," yes, or maybe.  I'm kicking it 
around, we are.

The C Trail does make for an interesting case.  We might agree that 
cycle_network=US:NPS is a good start.  But exactly which object in OSM to tag 
this?  Sometimes we make what seems like a duplicate of existing data, 
sometimes we shine a bright light forward by keeping things separate at the 
cost of a bit of apparent redundancy but really more like specificity.  
Sometimes we tie a bow AND a ribbon on things.  OK.

Richard (username) edited relation 1392951 a day or so ago and I'd say 
tightened up at the Maryland level.  If somebody tied this COC and others 
together into a "C" super-relation tagged with cycle_network=US:NPS (and "the 
correct" member elements as state-level routes) I could see balls continuing to 
bounce as they have been, especially as mild naming conventions "stitch a 
whole" together, Lonvia's routes panel is quite informative in this regard, 
though the alphabetic vs. numeric sorting of the USBRs went out the window long 
ago.  If not, OK.  If COC and others get a cycle_network=US:NPS tag, and we 
pause, no super-relation, OK, that makes sense, too.  I think we have to "keep 
being sensible."  Maybe have a check point amongst ourselves every once in a 
while.  Consensus can be slow.

With less wordiness, I know.  It's a big country, a big map, a big planet.  
Let's do our best, especially when talking with each other about how we agree 
things are built.  It's been chaotic, it has always a little chaotic, nothing 
wrong with a little order understood amongst us.

SteveA

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

[Talk-es] Etiqueta para centros de exámenes psicotécnico para tráfico.

[Manuel Arteaga]

Esta pregunta es quizá más propia de tagg...@openstreetmap.org, pero no sé cómo 
se dice lo que busco en inglés, ni si existen exámenes equivalentes fuera de 
España o la Unión Europea.

¿Cómo puedo marcar los centros donde se hacen exámenes psicotécnicos para 
tráfico? Es obligatorio acudir a uno de estos centros cada tanto tiempo para 
que verifiquen que uno tiene los reflejos y la coordinación necesarias para 
conducir.

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

Re: [OSM-talk-fr] grèves Loire - résumé et conclusion ?

[François Boucault]

Six mois plus tard, je fais un point sur les bancs de sable de la
Loire... 

J'ai relu le fil de discussion, les pages wiki OSM, les définitions
Wikipédia et Wikidata, etc. Évidemment il n'y a pas de solution idéale
pour ces zones "entre deux eaux", mais avec le recul voici ce qui me
semble pertinent : 

- Cartographier ou pas ? 

Ces zones font entièrement partie des paysages de Loire, car elles sont
largement découvertes tous les ans lorsque le niveau s'approche de
l'étiage [14] (atteint de juin à octobre environ). Leur dessin permet
donc de mieux rendre compte des formes et du fonctionnement du fleuve. 

- Comment cartographier ? 

* Vérifier sur différentes images satellites et/ou par sa propre
expérience que le banc de sable ne bouge pas, ou repérer les parties de
banc qui ne sont pas soumis à des changements fréquents
* Dans les parties navigables (en aval de la Maine) et/ou stabilisées
(entre des épis de Loire), il faut s'attendre à moins de mouvements des
bancs que dans les autres zones
* Pour des bancs stabilisés, on peut faire des relevés GPS précis (un
pied dans l'eau, l'autre sur le sable ;-), le mieux est de le faire
lorsque le niveau de la Loire est au seuil d'étiage (0m) à la station de
mesure la plus proche [15] (car ce seuil représente un niveau minimum
"normal"), merci @Ades.
* Pour des bancs qui bougent un peu, étant donné que la clef
natural=shoal (que je préconise ci-dessous) accepte aussi des bancs de
sable faiblement immergés, cela permet d'avoir une certaine souplesse
dans le dessin ou le niveau de l'eau de référence.

- Comment tagguer ? 

* Pour un banc de sable avec peu ou pas de végétation... Le terme
anglais "shoal" semble ne désigner que des bancs de sable maritimes sur
le wiki OSM, écrit en anglais, mais dans les autres langues de la page
wikidata, "shoal" est assimilé à un banc de sable générique (sandbank)
désignant également des bancs de sables fluviaux (sur la page wikipedia
française aussi, sur la page anglaise il est fait référence à des bancs
de sable d'embouchure). À propos d'un fleuve aussi large que la Loire,
je pense donc qu'on peut utiliser ce tag efficacement (exemple ici [16])
:

* natural=shoal
* surface=sand OU surface=gravel (rare dans ma région)

* Pour un banc de sable recouvert à la saison humide, mais bien
stabilisé et avec de la végétation (car placé plus haut, près des
berges), je propose (exemple ici [17]) :

* natural=grassland
* grassland=dune

* Pour les 2 types de polygones décrits ci-dessus, on rajoute encore
les tags suivants :

* seasonal=dry_season
* source:geometry=survey (si relevé GPS) OU source:geometry=BDOrtho
IGN (par exemple)
* source:geometry:date=* (date du relevé GPS ou de la prise de photo
satellite)
* check_date=* (si on a été sur le terrain pour vérifier le tracé)
* rôle "inner" dans la relation rivière "la Loire"
* rôle "outer" dans la relation rivière "Bancs de sable de la Loire"
(cf ci-dessous)

* Le multipolygone rivière "Bancs de sable de la Loire [18]" permet de
recenser tous les bancs de sable, et de réaffirmer leur appartenance au
lit principal de la Loire, avec la différence d'être des zones d'eaux
intermittentes. Les tags : 

* type=multipolygon
* natural=water
* water=river
* intermittent=yes (les hachures bleues sont ajoutées avec la présence
de ce tag)
* seasonal=dry_season
* name=Bancs de sable de la Loire

- Remarque : pas besoin du tag wikidata car tous les éléments
natural=shoal sont référencés globalement sur le wiki OSM (pas non plus
besoin de description car l'élément wikidata [19] en fournit une très
bien.) 

- Questions : 

* Où puis-je trouver la date de prise de vue d'une image satellite,
sur Id ou JOSM ?
* Faudrait-il modifier le wiki osm de natural=shoal en anglais [9]
afin qu'il fasse référence aux bancs de sable de rivière ? Comme c'est
le cas lorsqu'on traduit le terme dans wikidata et wikipedia ? Ce serait
dommage que la version anglaise restreigne l'utilité de ce tag alors
qu'il a une valeur plus générique dans les autres langues...

Voilà pour le topo ! N'hésitez pas si vous avez des remarques... 

Le 29/11/2018 à 09:38, Jérôme Seigneuret a écrit : 

> Pour faire plus simple tout les wetland=tidal_flat c'est uniquement en lien 
> avec les marais donc pas dans les terre chez nous sauf certains cours d'eau 
> on cela remonte comme sur la Gironde, Peut être la Dordogne, La Charante etc. 
> Les fleuves dans la montée des eau est impactée par les marées. La cote est 
> défini par un niveau de marée coef 120 par les anglais mais ne correspond pas 
> chez nous en terme de définition.  
> 
> Le niveau de définition du coastline est à 95 c'est un niveau qualifié de 
> "marée de vive eau" donc en marée haut sachant que les grande marée c'est à 
> partir de 100 à 120 sur notre échelle. 
> Le 0 terrestre 

Re: [OSM-talk] How can I create a oshdb?

[Milo van der Linden]

Thanks! The download server has no oshdb files for Curacao, the Caribbean
Island I am interested in. Is there a converter available?

Thanks again!

On Fri, Jul 12, 2019, 23:18 Mateusz Konieczny 
wrote:

>
> https://github.com/GIScience/oshdb/blob/master/documentation/first-steps/README.md
> has some docs.
>
>
> 12 Jul 2019, 23:11 by m...@dogodigi.net:
>
> Can anyone point me in the direction of how to create the ohsome oshdb
> from planet files?
>
> Thanks in advance!
>
> Milo
>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-GB] Trig Point references

[Dave F via Talk-GB]

On 12/07/2019 21:19, Philip Barnes wrote:

Hi Brian
Each pillar has a plate with an OS reassigned reference, which is easily  on 
the ground verifiable. I believe that we should be using that rather than those 
randomly assigned by a 3rd party site of unknown origin.


Hmm... Good job no one did 'randomly assigned' on PROWs 

DaveF

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

Re: [Talk-us] Next Mappy Hour July 10!

[Mateusz Konieczny]

I like this idea, I would be happy to talk about StreetComplete and Vespucci.

12 Jul 2019, 23:10 by m...@rtijn.org:

> Hi all, 
>
> Thanks for participating in the Virtual Mappy Hour this week! We had a record 
> number of 16 participants (from as far away as Poland and Japan) and lively 
> discussion on a variety of mappy topics. I enjoyed it very much and I hope 
> you did as well. 
>
> I will announce the next Mappy Hour soon. I suggest we make the next one 
> about field mapping and associated tools like StreetComplete, GoMap, 
> Vespucci, Fieldpapers etc! What do you think?
> -- 
>  Martijn van Exel
>  m...@rtijn.org
>
> On Tue, Jul 9, 2019, at 12:34, Martijn van Exel wrote:
>
>> Hi all, 
>> Final call for people who want to present a mappy topic at tomorrow's 
>> mappy hour!
>> Doesn't have to be anything too formal / prepared.. Just take 5 minutes 
>> to present what you work on / how you map / how OSM has changed your 
>> life / what you think the difference is between amenity=pub and 
>> amenity=bar / ... 
>> In any case, see you tomorrow!
>> -- 
>>  Martijn van Exel
>>  m...@rtijn.org
>>
>> On Tue, Jul 2, 2019, at 08:58, Martijn van Exel wrote:
>> > Hi all!
>> > 
>> > Here’s a reminder, Mappy Hour next Wednesday! Sending out the reminder 
>> > a little early because of the upcoming holiday weekend. Details and 
>> > sign up link in the thread below. So far we have 9 folks signed up. 
>> > Signing up is optional but you get to express your topic preferences. 
>> > So far we have a wide range:
>> > 
>> > * Tagging for data consumers
>> > * Vodka
>> > * Mapping bike routes and trails; and OSMAnd Specific considerations
>> > * A future program to qualify new mappers
>> > * Tips on how to quickly determine potentially missing/old information 
>> > of existing ways (buildings, roads, forests, etc.) 
>> > 
>> > I hope to see you there! July 10 6pm PT / 9pm ET
>> > 
>> > Martijn
>> > 
>> > -- 
>> >   Martijn van Exel
>> >   m...@rtijn.org
>> > 
>> > On Wed, Jun 26, 2019, at 16:05, Martijn van Exel wrote:
>> > > Here's a sign up link. It helps me a lot if you fill this out if you 
>> > > plan to attend. Thanks!
>> > > https://forms.gle/WktPPimyB69jGnH29
>> > > -- 
>> > >   Martijn van Exel
>> > >   m...@rtijn.org
>> > > 
>> > > On Wed, Jun 26, 2019, at 11:16, Martijn van Exel wrote:
>> > > > Hi all,
>> > > > The next OSM US Virtual Mappy Hour will be on July 10 at 6pm PT / 9pm 
>> > > > ET!
>> > > > As always the Mappy Hour is a great place to catch up with your fellow 
>> > > > mappers, and learn something new. 
>> > > > I am always looking for volunteers to do a 5 minute presentation on 
>> > > > something they are working on. This can be a personal mapping project, 
>> > > > a local mapping group update, something interesting going on at your 
>> > > > company.. As long as it's OSM related!
>> > > > See the OSM wiki for more details on how to join --> 
>> > > > https://wiki.openstreetmap.org/wiki/Foundation/Local_Chapters/United_States/Virtual_Mappy_Hours
>> > > > See you then!
>> > > > -- 
>> > > >   Martijn van Exel
>> > > >   m...@rtijn.org
>> > > > 
>> > > > ___
>> > > > 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
>> > >
>> > 
>> > ___
>> > 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
>>
>
> ___
> 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

Re: [OSM-talk] How can I create a oshdb?

[Mateusz Konieczny]

https://github.com/GIScience/oshdb/blob/master/documentation/first-steps/README.md
 

has some docs.


12 Jul 2019, 23:11 by m...@dogodigi.net:

> Can anyone point me in the direction of how to create the ohsome oshdb from 
> planet files?
>
> Thanks in advance!
>
> Milo
>___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

[OSM-talk] How can I create a oshdb?

[Milo van der Linden]

Can anyone point me in the direction of how to create the ohsome oshdb from
planet files?

Thanks in advance!

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

Re: [Talk-us] Next Mappy Hour July 10!

[Martijn van Exel]

Hi all, 

Thanks for participating in the Virtual Mappy Hour this week! We had a record 
number of 16 participants (from as far away as Poland and Japan) and lively 
discussion on a variety of mappy topics. I enjoyed it very much and I hope you 
did as well. 

I will announce the next Mappy Hour soon. I suggest we make the next one about 
field mapping and associated tools like StreetComplete, GoMap, Vespucci, 
Fieldpapers etc! What do you think?
-- 
  Martijn van Exel
  m...@rtijn.org

On Tue, Jul 9, 2019, at 12:34, Martijn van Exel wrote:
> Hi all, 
> Final call for people who want to present a mappy topic at tomorrow's 
> mappy hour!
> Doesn't have to be anything too formal / prepared.. Just take 5 minutes 
> to present what you work on / how you map / how OSM has changed your 
> life / what you think the difference is between amenity=pub and 
> amenity=bar / ... 
> In any case, see you tomorrow!
> -- 
>   Martijn van Exel
>   m...@rtijn.org
> 
> On Tue, Jul 2, 2019, at 08:58, Martijn van Exel wrote:
> > Hi all!
> > 
> > Here’s a reminder, Mappy Hour next Wednesday! Sending out the reminder 
> > a little early because of the upcoming holiday weekend. Details and 
> > sign up link in the thread below. So far we have 9 folks signed up. 
> > Signing up is optional but you get to express your topic preferences. 
> > So far we have a wide range:
> > 
> > * Tagging for data consumers
> > * Vodka
> > * Mapping bike routes and trails; and OSMAnd Specific considerations
> > * A future program to qualify new mappers
> > * Tips on how to quickly determine potentially missing/old information 
> > of existing ways (buildings, roads, forests, etc.) 
> > 
> > I hope to see you there! July 10 6pm PT / 9pm ET
> > 
> > Martijn
> > 
> > -- 
> >   Martijn van Exel
> >   m...@rtijn.org
> > 
> > On Wed, Jun 26, 2019, at 16:05, Martijn van Exel wrote:
> > > Here's a sign up link. It helps me a lot if you fill this out if you 
> > > plan to attend. Thanks!
> > > https://forms.gle/WktPPimyB69jGnH29
> > > -- 
> > >   Martijn van Exel
> > >   m...@rtijn.org
> > > 
> > > On Wed, Jun 26, 2019, at 11:16, Martijn van Exel wrote:
> > > > Hi all,
> > > > The next OSM US Virtual Mappy Hour will be on July 10 at 6pm PT / 9pm 
> > > > ET!
> > > > As always the Mappy Hour is a great place to catch up with your fellow 
> > > > mappers, and learn something new. 
> > > > I am always looking for volunteers to do a 5 minute presentation on 
> > > > something they are working on. This can be a personal mapping project, 
> > > > a local mapping group update, something interesting going on at your 
> > > > company.. As long as it's OSM related!
> > > > See the OSM wiki for more details on how to join --> 
> > > > https://wiki.openstreetmap.org/wiki/Foundation/Local_Chapters/United_States/Virtual_Mappy_Hours
> > > > See you then!
> > > > -- 
> > > >   Martijn van Exel
> > > >   m...@rtijn.org
> > > > 
> > > > ___
> > > > 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
> > >
> > 
> > ___
> > 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
>

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

Re: [Talk-GB] Trig Point references

[Gareth L]

Adjacent to this query, there’s a Facebook group where people post photos of 
postboxes https://m.facebook.com/postboxcollection/
It would be very useful to be able to fill in the blanks, like royal_cypher and 
potentially collection times. Many postboxes have just the reference number on 
Osm. Who owns the data here? Each submitter, the group admin, Facebook?

Apologies for derail, but there is quite a parallel.

Gareth

On 12 Jul 2019, at 21:59, Simon Ritchie 
mailto:simonritchie...@gmail.com>> wrote:

> I've noticed that some trigpoints are tagged with  a reference prefixed TPUK. 
> This is a reference to the numbers assigned by the website 
> http://trigpointing.uk/ which has the following text as a footer: "The 
> TrigpointingUK database is owned and maintained by Ian Harris (Teasel)"
That doesn't sound very open to me - does anyone know what permission we have 
to use this data?

Hmm.  Good point.  Most of the data in Ian's database is contributed by the 
trigpointers - reports of visits to the trigs.  Most of the data about the 
actual trigs on the site (position etc) comes from the OS.  See this page 
https://www.ordnancesurvey.co.uk/gps/legacy-control-information/triangulation-stations,
 which says "This data, which is no longer maintained, is available for use 
under Open Government Licence Terms."

That page provides a downloadable CSV  giving the names used by the OS. 
position, type, status etc.  However, the names starting TP seem to be created 
by Ian, so I think he owns them, just as Royal Mail owns the postcode data.

One solution would be to quote the OS names instead.  Another would be to use 
the contact page on Ian's site and ask him for permission to use his names.  
I'm guessing that he would be happy.

Regards

Simon


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

Re: [Talk-GB] Trig Point references

[Philip Barnes]

On Friday, 12 July 2019, Philip Barnes wrote:
> On Friday, 12 July 2019, Brian Prangle wrote:
> > I've noticed that some trigpoints are tagged with  a reference prefixed
> > TPUK. This is a reference to the numbers assigned by the website
> > http://trigpointing.uk/ which has the following text as a footer: "The
> > TrigpointingUK database is owned and maintained by Ian Harris (Teasel)"
> > That doesn't sound very open to me - does anyone know what permission we
> > have to use this data? The OSM wiki says we *can* use it but who has the
> > text of  the explicit permission (or licence) and shouldn't we have  a
> > system of being able to reference(hyperlink) permissions such as these from
> > the wiki (just to be safe)?
> > 
> > Apologies if there is a talk-gb thread buried in the archives relating to
> > this
> > 
> Hi Brian
> Each pillar has a plate with an OS reassigned reference, which is easily  on 
> the ground verifiable. I believe that we should be using that rather than 
> those randomly assigned by a 3rd party site of unknown origin. 
> 
> For example Titterstone Clee is 2943, which I can't remember if I added it.
>
That should have said OS assigned.
 
Phil (trigpoint)

-- 
Sent from my Sailfish device
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [Talk-GB] Trig Point references

[Philip Barnes]

On Friday, 12 July 2019, Brian Prangle wrote:
> I've noticed that some trigpoints are tagged with  a reference prefixed
> TPUK. This is a reference to the numbers assigned by the website
> http://trigpointing.uk/ which has the following text as a footer: "The
> TrigpointingUK database is owned and maintained by Ian Harris (Teasel)"
> That doesn't sound very open to me - does anyone know what permission we
> have to use this data? The OSM wiki says we *can* use it but who has the
> text of  the explicit permission (or licence) and shouldn't we have  a
> system of being able to reference(hyperlink) permissions such as these from
> the wiki (just to be safe)?
> 
> Apologies if there is a talk-gb thread buried in the archives relating to
> this
> 
Hi Brian
Each pillar has a plate with an OS reassigned reference, which is easily  on 
the ground verifiable. I believe that we should be using that rather than those 
randomly assigned by a 3rd party site of unknown origin. 

For example Titterstone Clee is 2943, which I can't remember if I added it.

Phil (trigpoint)

-- 
Sent from my Sailfish device
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [Talk-GB] UK coastline data

[Devonshire]

On Fri, Jul 12, 2019, at 8:05 PM, Borbus wrote:.
> Does that matter, though? The way many things in OSM are tagged is quite
> arbitrary. What if "coastline" just means "mean high water level"? A tag
> for MHWL seems much more useful than "you would probably consider this
> the coast rather than a river bank".
> 
> > I don't really care either way but what would be the benefit of changing
> > it to coastline (and slavishly copying the OS is not a benefit) ?
> 
> The benefit is we don't have to arbitrarily draw the line somewhere. The
> tidal limit is well-defined so it's easy to be consistent.

Just because the coastline follows MLW as it goes around the coast doesn't mean 
it needs to follow every tidal waterway inland. That doesn't follow at all.

To achieve what you want you would need to add yet another way inside of the 
riverbank and intertidal areas which seems like a fair bit of effort to do for 
every river for no real benefit to map users whatsoever. Then you need to get 
it all to render right where you have tidal mud banks, etc. in the centre of 
the river.

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

[Talk-GB] Trig Point references

[Brian Prangle]

I've noticed that some trigpoints are tagged with  a reference prefixed
TPUK. This is a reference to the numbers assigned by the website
http://trigpointing.uk/ which has the following text as a footer: "The
TrigpointingUK database is owned and maintained by Ian Harris (Teasel)"
That doesn't sound very open to me - does anyone know what permission we
have to use this data? The OSM wiki says we *can* use it but who has the
text of  the explicit permission (or licence) and shouldn't we have  a
system of being able to reference(hyperlink) permissions such as these from
the wiki (just to be safe)?

Apologies if there is a talk-gb thread buried in the archives relating to
this

Regards

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

Re: [Talk-GB] UK coastline data

[Borbus]

On Fri, Jul 12, 2019 at 12:40 PM  wrote:
> The old coastline (August 2018) is blue and the current coastal line
> is red.

The blue shows what I was talking about earlier where some of the
coastline was at MLWL and some was all the way up at the sea wall
(exceptionally high tide).

> The affected areas are wetlands, whose "coastline" is very complex. In
> my opinion, the problem is that this "coastline" is not static,
> because it is a natural runoff that will never be stable. It will look
> quite different after several months.

I am familiar with this area. Those areas are salt marshes and much more
stable than you might think. The main change that has happened over the
past ten years in this area is the high water marks have receded. This
is reflected in the most recent OS data that I've used. Those inlets are
deep tidal channels and definitely should be on the map. A smoothed
coastline would be a huge loss in this area.

The bits that would change a lot more are the low water levels because
this land is comprised of soft mud and sand. Unfortunately none of the
aerial imagery we have available cover these vast tidal flats. Most cut
off at the "coastline" (high water level).

Borbus.

On Fri, Jul 12, 2019 at 12:40 PM  wrote:

> Hi,
>
> I don't think you should accept this data.
> see:
> https://wambachers-osm.website/images/osm/snaps_2019/strange_coastline.png_2019/strange_coastline.png
>
> The old coastline (August 2018) is blue and the current coastal line is
> red.
>
> The affected areas are wetlands, whose "coastline" is very complex. In my
> opinion, the problem is that this "coastline" is not static, because it is
> a natural runoff that will never be stable. It will look quite different
> after several months.
>
> A manually smoothed coastline (better than the one from 2018) would be
> appropriate.
>
> ym2c from germany.
>
> walter
> Translated with www.DeepL.com/Translator
>
> --
> My projects:
>
> Admin Boundaries of the World 
> Missing Boundaries
> 
> Emergency Map 
> Postal Code Map (Germany only) 
> Fools (QA for zipcodes in Germany) 
> Postcode Boundaries of Germany
> 
> ___
> Talk-GB mailing list
> Talk-GB@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-gb
>
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [Talk-GB] UK coastline data

[Borbus]

On Fri, Jul 12, 2019 at 9:17 AM Mark Goodge  wrote:
> It's also one of the most useful from a leisure perspective, as a lot of
> popular beaches fall primarily or wholly in the intertidal zone. Take,
> for example, Hunstanton in Norfolk - at high tide the sea comes all the
> way up to the sea wall, and there is no beach as such on the town centre
> seafront. But, at low tide, there's a large expanse of sand. And, in
> between, there are differing amounts of sand visible!

Hunstantson was one of the beaches I updated in my edits. The
data is now correct, but the carto layer doesn't actually show
the coastline (the MHW level) unfortunately.

Interesting that you mention the sand and mud further south. At
some point between Hunstanton and Snettisham the intertidal zone
changes from "beach" to "tidal flat". I've actually continued
the "beach" all the way down to Snettisham with the "tidal flats"
starting beyond the nature reserve. This is quite an important
distinction, because if you go to those areas expecting a beach
but get a tidal flat you'll be in for a (probably unpleasant)
surprise.

Any idea where to draw the line here?

There's a similar situation on the other side between Skegness
and Gibraltar Point.

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

Re: [Talk-GB] UK coastline data

[Borbus]

On Fri, Jul 12, 2019 at 7:46 AM Devonshire  wrote:
> I think the main reason I did that back in the day is that mapping
> coastline all the way up to Totnes seems extremely
> non-intuitive. Someone standing on Totnes quay (10 miles inland) is not
> standing on the coast in any meaningful way.

Does that matter, though? The way many things in OSM are tagged is quite
arbitrary. What if "coastline" just means "mean high water level"? A tag
for MHWL seems much more useful than "you would probably consider this
the coast rather than a river bank".

> I don't really care either way but what would be the benefit of changing
> it to coastline (and slavishly copying the OS is not a benefit) ?

The benefit is we don't have to arbitrarily draw the line somewhere. The
tidal limit is well-defined so it's easy to be consistent.

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

Re: [OSM-talk-fr] Sotm Heidelberg : on y va ensemble ?

[PanierAvide]

Bonjour,
À vérifier mais c'est sans doute si tu veux venir accompagné d'une personne qui 
ne participe pas au reste de la conférence.
Cordialement,
Adrien.Le 12 juil. 2019 7:41 PM, Vincent Privat  a 
écrit :
>
> Hello,
> les tickets "early bird" à tarif réduit sont disponibles jusqu'au 21 juillet.
> Je suis en train de regarder les différentes options:
>
> Conference Tickets (Early Bird fee)
>
> Community - Early Bird
> € 75.00
> Regular (Business) - Early Bird
> € 180.00
> Supporter (Business) - Early Bird
> € 700.00
> Add-on: Social Event (for Guest)
> € 50.00
> Add-on: Heidelberg Guided Tour
> € 15.00
>
> Je ne comprends pas la précision "for Guest" du "social event"? En quoi ça 
> consiste exactement ?
>
> Vincent
>
> Le ven. 28 juin 2019 à 08:49, PanierAvide  a écrit :
>>
>> Bonjour,
>>
>> Petite relance : n'oubliez pas de remplir le tableau dont le lien est 
>> ci-dessous si vous vous rendez au State of the Map d'Heidelberg pour que 
>> l'on trouve le meilleur coup de pouce que l'asso peut offrir ;-)
>>
>> Cordialement,
>>
>> Adrien P.
>>
>> Le 17/06/2019 à 14:51, PanierAvide a écrit :
>> > Bonjour à tous,
>> >
>> > Le State of the Map mondial se déroule cette année à Heidelberg, ville 
>> > allemande assez proche de nos frontières. L'association OSM France 
>> > souhaite ainsi faciliter la venue de contributeurs français à 
>> > l'évènement. Plusieurs idées ont été émises pour y parvenir :
>> >
>> > - Partager le transport depuis Paris pour converger vers Heidelberg
>> > - Partager un hébergement sur place pour réduire les frais
>> > - Prendre en charge les frais de transport/hébergement de contributeurs
>> >
>> > Afin que nous puissions trouver les solutions répondant au mieux aux 
>> > attentes, j'ai ouvert un tableur partagé où vous pouvez indiquer si 
>> > vous prévoyez de vous rendre à l'évènement, et quels aspects vous 
>> > intéresseraient pour faciliter votre venue :
>> >
>> > https://lite.framacalc.org/orga_fr_sotm_heidelberg
>> >
>> > Je vous laisse y ajouter vos infos le plus rapidement possible (avant 
>> > la fin du mois) pour que nous puissions ensuite vous proposer une 
>> > offre mutualisée ou prise en charge dans la mesure du possible :-)
>> >
>> > Cordialement.
>> >
>>
>> ___
>> 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] Sotm Heidelberg : on y va ensemble ?

[Vincent Privat]

Hello,
les tickets "early bird" à tarif réduit sont disponibles jusqu'au 21
juillet.
Je suis en train de regarder les différentes options:

Conference Tickets (Early Bird fee)
Community - Early Bird € 75.00
Regular (Business) - Early Bird € 180.00
Supporter (Business) - Early Bird € 700.00
Add-on: Social Event (for Guest) € 50.00
Add-on: Heidelberg Guided Tour € 15.00

Je ne comprends pas la précision "for Guest" du "social event"? En quoi ça
consiste exactement ?

Vincent

Le ven. 28 juin 2019 à 08:49, PanierAvide  a écrit :

> Bonjour,
>
> Petite relance : n'oubliez pas de remplir le tableau dont le lien est
> ci-dessous si vous vous rendez au State of the Map d'Heidelberg pour que
> l'on trouve le meilleur coup de pouce que l'asso peut offrir ;-)
>
> Cordialement,
>
> Adrien P.
>
> Le 17/06/2019 à 14:51, PanierAvide a écrit :
> > Bonjour à tous,
> >
> > Le State of the Map mondial se déroule cette année à Heidelberg, ville
> > allemande assez proche de nos frontières. L'association OSM France
> > souhaite ainsi faciliter la venue de contributeurs français à
> > l'évènement. Plusieurs idées ont été émises pour y parvenir :
> >
> > - Partager le transport depuis Paris pour converger vers Heidelberg
> > - Partager un hébergement sur place pour réduire les frais
> > - Prendre en charge les frais de transport/hébergement de contributeurs
> >
> > Afin que nous puissions trouver les solutions répondant au mieux aux
> > attentes, j'ai ouvert un tableur partagé où vous pouvez indiquer si
> > vous prévoyez de vous rendre à l'évènement, et quels aspects vous
> > intéresseraient pour faciliter votre venue :
> >
> > https://lite.framacalc.org/orga_fr_sotm_heidelberg
> >
> > Je vous laisse y ajouter vos infos le plus rapidement possible (avant
> > la fin du mois) pour que nous puissions ensuite vous proposer une
> > offre mutualisée ou prise en charge dans la mesure du possible :-)
> >
> > Cordialement.
> >
>
> ___
> 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-legal-talk] Copy information from official business website (WAS: Proposal for a revision of JA:Available Data)

[Martin Koppenhoefer]

sent from a phone

> On 12. Jul 2019, at 11:37, Mateusz Konieczny  wrote:
> 
> For example I may draw a red circle
> and publish it under CC BY-NC.
> 
> But drawing of a red circle is not copyrightable,
> as it is to simple to qualify for protection
> and lacks originality.


it may depend on the story you tell about your red circle. 

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

Re: [OSM-talk-fr] Josm - traduction wiki - changelog

[Vincent Privat]

Hello,
- ça serait plutôt "inverser" l'ordre des filtres plutôt que "annuler"
- "télécharger les URIs geo: depuis la ligne de commande"
pour le "decimal places of length" je ne suis pas sûr que l'anglais soit
correct. J'ai rajouté un chiffre après la virgule pour les longueurs
affichées à la demande de Stéphane:
https://josm.openstreetmap.de/ticket/17823
Sinon le reste OK, merci !

Le ven. 12 juil. 2019 à 19:27, lenny.libre  a écrit :

> Bonjour.
>
> La page https://josm.openstreetmap.de/wiki/Fr%3AChangelog a été mise à
> jour avec la version anglaise.
>
> Je n'ai pas su traduire clairement certains points, le texte original
> anglais a été mis en gras (des versions 14760 à la version stable 15238)
>
> Merci de m'indiquer si vous avez une traduction correcte ou si certains
> termes techniques peuvent rester en anglais.
>
> Cordialement
>
> Leni
>
>
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr
>
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [Talk-at] minderwertige Importe

[gppes_osm]

Hallo,

Du musst mit dem juengsten Edit (also dem Edit, der v3 erzeugt hat) anfangen 
und dann zu immer aelteren Versionen (also dann den Edit der v2 gemacht hat, 
zuletzt den erzeugenden Edit), sonst wird's schwierig!

Lg, Gppes

> Gesendet: Freitag, 12. Juli 2019 um 17:47 Uhr
> Von: "andreas wecer" 
> An: "OpenStreetMap AT" 
> Betreff: Re: [Talk-at] minderwertige Importe
>
> Kann mir mal jemand beim (partiellen) Revert dieses Changesets behilflich
> sein?
> https://www.openstreetmap.org/changeset/71043071
> 
> Hier hat er existierende Adressen gelöscht, die kein addr:street oder
> addr:place hatten, u.a. auch 200 vollständig angegebene Adressen, die nur
> addr:hamlet statt addr:place hatten, wie diese hier:
> https://www.openstreetmap.org/relation/2666001/history
> 
> Neben diesen hat er allerdings auch noch seine eigenen Duplikate gelöscht,
> wobei er die aus irgendeinem Grund in diesem Changeset nicht direkt
> gelöscht hat, sondern nur die Tags entfernt hat und die leeren Nodes
> anschließend in einem anderen Changeset gelöscht hat
> https://www.openstreetmap.org/node/6533111972/history
> https://www.openstreetmap.org/changeset/71043190
> 
> Wenn ich jetzt #71043071 mit dem JOSM Reverter rückgängig machen möchte,
> bekomme ich damit haufenweise Konflikte, weil es davon schon wieder die v3
> gibt, wo sie im separaten Changeset gelöscht wurden. Ich könnte jetzt
> annehmen, dass die Konflikte immer diese Fälle betreffen und daher einfach
> alle Konflikte auf die Server-Version auflösen, aber so ganz wohl ist mir
> dabei auch nicht.
> 
> LG
>   Andreas
> ___
> Talk-at mailing list
> Talk-at@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-at
>

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

[OSM-talk-fr] Josm - traduction wiki - changelog

[lenny.libre]

Bonjour.

La page https://josm.openstreetmap.de/wiki/Fr%3AChangelog a été mise à 
jour avec la version anglaise.


Je n'ai pas su traduire clairement certains points, le texte original 
anglais a été mis en gras (des versions 14760 à la version stable 15238)


Merci de m'indiquer si vous avez une traduction correcte ou si certains 
termes techniques peuvent rester en anglais.


Cordialement

Leni


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

Re: [Talk-at] minderwertige Importe

[Johann Haag]

> Am 12.07.2019 um 17:47 schrieb andreas wecer :
> 
> Kann mir mal jemand beim (partiellen) Revert dieses Changesets behilflich 
> sein?
> https://www.openstreetmap.org/changeset/71043071 
> 
> 
> Hier hat er existierende Adressen gelöscht, die kein addr:street oder 
> addr:place hatten, u.a. auch 200 vollständig angegebene Adressen, die nur 
> addr:hamlet statt addr:place hatten, wie diese hier: 
> https://www.openstreetmap.org/relation/2666001/history 
> 
> 
> Neben diesen hat er allerdings auch noch seine eigenen Duplikate gelöscht, 
> wobei er die aus irgendeinem Grund in diesem Changeset nicht direkt gelöscht 
> hat, sondern nur die Tags entfernt hat und die leeren Nodes anschließend in 
> einem anderen Changeset gelöscht hat
> https://www.openstreetmap.org/node/6533111972/history 
> 
> https://www.openstreetmap.org/changeset/71043190 
> 
> 
> Wenn ich jetzt #71043071 mit dem JOSM Reverter rückgängig machen möchte, 
> bekomme ich damit haufenweise Konflikte, weil es davon schon wieder die v3 
> gibt, wo sie im separaten Changeset gelöscht wurden. Ich könnte jetzt 
> annehmen, dass die Konflikte immer diese Fälle betreffen und daher einfach 
> alle Konflikte auf die Server-Version auflösen, aber so ganz wohl ist mir 
> dabei auch nicht.

Hallo Andreas,
Bitte lass das besser Profis machen, 
Notfalls könnte auch ich dir helfen. Bin aber derzeit in Urlaub

Bevor du unkontrolliert zu revertieren beginnst, beschreibe bitte hier genau 
was du vorhast.
Lg Johann

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

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

Re: [Talk-at] minderwertige Importe

[andreas wecer]

Kann mir mal jemand beim (partiellen) Revert dieses Changesets behilflich
sein?
https://www.openstreetmap.org/changeset/71043071

Hier hat er existierende Adressen gelöscht, die kein addr:street oder
addr:place hatten, u.a. auch 200 vollständig angegebene Adressen, die nur
addr:hamlet statt addr:place hatten, wie diese hier:
https://www.openstreetmap.org/relation/2666001/history

Neben diesen hat er allerdings auch noch seine eigenen Duplikate gelöscht,
wobei er die aus irgendeinem Grund in diesem Changeset nicht direkt
gelöscht hat, sondern nur die Tags entfernt hat und die leeren Nodes
anschließend in einem anderen Changeset gelöscht hat
https://www.openstreetmap.org/node/6533111972/history
https://www.openstreetmap.org/changeset/71043190

Wenn ich jetzt #71043071 mit dem JOSM Reverter rückgängig machen möchte,
bekomme ich damit haufenweise Konflikte, weil es davon schon wieder die v3
gibt, wo sie im separaten Changeset gelöscht wurden. Ich könnte jetzt
annehmen, dass die Konflikte immer diese Fälle betreffen und daher einfach
alle Konflikte auf die Server-Version auflösen, aber so ganz wohl ist mir
dabei auch nicht.

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

Re: [Talk-us] Mapping rail trails

[Kevin Kenny]

On Fri, Jul 12, 2019 at 9:36 AM Phil! Gold  wrote:
> The "state at a time" pattern, as I have always understood it, exists to
> keep vastly distant objects from being linked with each other.  It makes
> it much less likely for someone, say, updating I-95 in Florida to get an
> editing conflict with someone else who made a change in Massachusetts.
> State borders provide convenient locations for the division of overly-lond
> relations.

It's mostly, as I understand it,  "huge routes cause editing
conflicts, make validation difficult, and otherwise make trouble for
the tools," combined with, "if you're going to break up a route, break
it in places that make some sort of sense."

When I created the (still incomplete, sorry!) relation for the Long
Path hiking trail, I found that the tools were struggling with the
number of way segments. (I switched to Meerkartor briefly at one point
because JOSM would crash on me!) I made the totally arbitrary decision
that the best points to break it up were the county lines.  I then
made the even more arbitrary decision that I'd lump in the George
Washington Bridge and 179th Street in with Bergen County, because it
just didn't feel right to create a New York County trail section for
that short a distance over city streets.

If it turns out that the sections will indeed have distinct attributes
(this includes Richard Fairhurst's observation that different states
treat their bicycle routes with different levels of respect), it'll be
easy to break them apart.

Merging route relations is harder, because when two relations merge
into one, one of them is deleted, damaging the ability of some of the
history tools to track changes. I'm therefore inclined to say, "if
it's already split in the database, leave it split; create a group if
necessary". The tools deal with routes-inside-routes pretty well.
https://hiking.waymarkedtrails.org/#route?id=919642 manages to
assemble the sections into a coherent whole.

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

Re: [Talk-GB] UK coastline data

[David Groom]

-- Original Message --
From: "Devonshire" 
To: talk-gb@openstreetmap.org
Sent: 12/07/2019 07:44:55
Subject: Re: [Talk-GB] UK coastline data



On Thu, Jul 11, 2019, at 10:41 PM, Borbus wrote:


The Dart cuts the coastline off right at the mouth, which doesn't seem 
right...


I think the main reason I did that back in the day is that mapping 
coastline all the way up to Totnes seems extremely non-intuitive. 
Someone standing on Totnes quay (10 miles inland) is not standing on 
the coast in any meaningful way.
I agree, I long ago made the same point regarding the River Thames as it 
passes through London.

David




I don't really care either way but what would be the benefit of 
changing it to coastline (and slavishly copying the OS is not a 
benefit) ?


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

Re: [Talk-us] Mapping rail trails

[Phil! Gold]

* stevea  [2019-07-11 17:38 -0700]:
> I know it seems "like it just makes sense" to combine Maryland and DC
> relations, but there are rather deliberate reasons to keep these
> separate.  One is state-level, the other is federal-level (is one), but
> the "state at a time for route relations" is a fairly well-established
> method of tossing things into buckets.  We do it with bike routes,
> motorways and more.

However:

The C Trail is contained within the C National Historic Park, which is
owned by the National Park Service, so it's all really at the same
(federal) level.

The "state at a time" pattern, as I have always understood it, exists to
keep vastly distant objects from being linked with each other.  It makes
it much less likely for someone, say, updating I-95 in Florida to get an
editing conflict with someone else who made a change in Massachusetts.
State borders provide convenient locations for the division of overly-lond
relations.

It's also a rule of thumb; I've seen plenty of cases where short distances
in multiple states are aggregated into a single relation.  (e.g. there's
only one relation for US 340, although it spans MD, VA (in two sections),
and WV.)

Since there's only a short section of the C Canal Trail in DC, I don't
really see the harm in putting all of its ways into a single relation.

-- 
...computer contrarian of the first order... / http://aperiodic.net/phil/
PGP: 026A27F2  print: D200 5BDB FC4B B24A 9248  9F7A 4322 2D22 026A 27F2
--- --
Anyone who has never hacked sendmail.cf has no soul.  Anyone who has
hacked it twice has no brain.
   -- Peter da Silva
 --- --

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

Re: [OSM-talk-fr] Uniformiser le wiki "Bicycle" (était Re: Sidewalk:bicycle dans le wiki bicycle)

[Phyks]

Bonjour à tous,

Je viens de refaire une passe sur la page FR:Bicycle et ma proposition
actuelle (avec les diffs visibles dans l'historique de la page) est sur

https://wiki.openstreetmap.org/wiki/User:Phyks/FR:Bicycle

J'ai tenté d'harmoniser les descriptions entre elles et avec la version
anglaise.

(Au moins) deux points restent à traiter, à mon avis:

1. Je ne comprends toujours pas très bien ce que décrit
https://wiki.openstreetmap.org/wiki/User:Phyks/FR:Bicycle#Am.C3.A9nagements_cyclables_sur_trottoirs,
surtout que la photographie ne semble pas correspondre aux schémas. Que
devrait-on faire de cette partie ?

2. Suite à la discussion qui avait eu lieu sur talk-fr, on avait convenu
de tagger les parkings "deux roues" (ouverts aux vélos mais aussi aux
scooters) comme
https://wiki.openstreetmap.org/wiki/Montrouge#Stationnements_deux_roues
(ce qu'on a adopté à Montrouge). Que pensez-vous de reporter cette
documentation dans la page FR:Bicycle ?

Bonne journée,
-- 
Phyks
Le 01/07/2019 à 15:12, Phyks a écrit :
>> sauver la page initiale dans son espace utilisateur du wiki,
>> faire la modifi sur cette page, l'historique permet alors à la fois de
>> comparer et de regarder le résultat comme à l'habitude.
> 
> Bien vu, je viens donc de faire
> https://wiki.openstreetmap.org/wiki/User:Phyks/FR:Bicycle.
> 
> Discutons sur le résultat de cette page et oublions le gist du coup :)
> -- 
> Phyks
> 
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr

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

Re: [Talk-GB] UK coastline data

[wambacher]

sorry, wrong link:
https://wambachers-osm.website/images/osm/snaps_2019/strange_coastline.png

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

Re: [Talk-GB] UK coastline data

[wambacher]

Hi,

I don't think you should accept this data.

see:
https://wambachers-osm.website/images/osm/snaps_2019/strange_coastline.png_2019/strange_coastline.png

The old coastline (August 2018) is blue and the current coastal line is red.

The affected areas are wetlands, whose "coastline" is very complex. In
my opinion, the problem is that this "coastline" is not static, because
it is a natural runoff that will never be stable. It will look quite
different after several months.

A manually smoothed coastline (better than the one from 2018) would be
appropriate.

ym2c from germany.

walter

Translated with www.DeepL.com/Translator

-- 
My projects:

Admin Boundaries of the World 
Missing Boundaries

Emergency Map 
Postal Code Map (Germany only) 
Fools (QA for zipcodes in Germany) 
Postcode Boundaries of Germany 
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

[Talk-es] M-30/Calle 30

[A A]

Hola a todos. Revisando la M-30 en Madrid me han surgido algunas dudas:

1. ¿Cuál debería ser el nombre? La referencia creo que tengo claro que debería 
de ser M-30 (en todos los carteles aparece así) pero tengo dudas a cerca del 
nombre, por un lado creo que debería de ser Calle 30, ya que desde que es 
titularidad del ayuntamiento se llama así (excepto los tramos con nombre 
propio, claro, como avenida de la Ilustración Paseo del Marqués de Monistrol o 
Avenida de la Paz) pero tengo dudas, de hecho empezé a cambiar el nombre en un 
tramo para poner Calle 30 pero no he querido seguir hasta estar seguro.

2. Por otro lado, existen 2 relaciones que se refieren a esta vía, una 
denominada Calle 30 y otra que se llama autovía de circunvalación M30 ¿está 
bien mantener estas dos relaciones? creo que son relaciones duplicadas y se 
debería de eliminar una.

3. En el tramo este existe una calzada lateral para canalizar mejor las 
entradas y salidas ¿este tramo debería formar parte de las relaciones que he 
nombrado antes? ¿Cuál debería de ser el nombre de esta calzada lateral, 
"Calzada lateral M30" o "Calzada lateral Calle 30"?
___
Talk-es mailing list
Talk-es@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-es

Re: [OSM-legal-talk] Copy information from official business website (WAS: Proposal for a revision of JA:Available Data)

[Mateusz Konieczny]

9 Jul 2019, 09:03 by muramototom...@gmail.com:
> Assume that TESCO has published the shop data under the CC BY license. Then 
> can I use that data for OSM?
> I think that data is not available because CC BY license is incompatible with 
> ODbL as OSMF has stated.
> https://blog.openstreetmap.org/2017/03/17/use-of-cc-by-data/ 
> 
>
CC-BY is not making data available.

But data not covered by copyright is not 
becoming copyrightable by releasing
or under a license.

The same applies to copyright-like restrictions applied to databases 

For example I may draw a red circle
and publish it under CC BY-NC.

But drawing of a red circle is not copyrightable,
as it is to simple to qualify for protection
and lacks originality.

So anyone may take this image and use it for any purposes,
 including commercial purposes forbidden by CC BY-NC.

> However, current data published by TESCO under the "misleading" terms is 
> considered as available.
>
Assuming that this part of data is not 
eligible for 
copyright and copyright-like restrictions then
it can not be restricted by using copyright and copyright-like rules.
> After this discussion I would like to make an OSM wiki page as an agreement 
> by the OSM global community. 
> wiki/Available_Data is fine for it?
>
It would be a great idea to document summary of this.

Note that there is already "Copyright" page.

Adding it there or linking new page would be likely a good idea.
In case of doing this (what would be great), please link it 
here - some people may be able to name further
improvements.___
legal-talk mailing list
legal-talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/legal-talk

Re: [OSM-legal-talk] Copy information from official business website (WAS: Proposal for a revision of JA:Available Data)

[Mateusz Konieczny]

11 Jul 2019, 22:48 by dieterdre...@gmail.com:

> It’s more likely they would pay you for this than sue you.
>
Note that it is perspective that we should
use during using external data.

Using data on incompatible license is still utterly
unacceptable, even in cases where suing is not going to happen.___
legal-talk mailing list
legal-talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/legal-talk

[Talk-hr] OpenCage interview about OSM Croatia

[hbogner]

Ima li netko volje/želje sudjelovati?
Pismeni intervju sa nekoliko pitanja.
U stilu kao ovi:
https://blog.opencagedata.com/tagged/countryprofile


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

Re: [Talk-GB] UK coastline data

[Mark Goodge]

On 11/07/2019 20:38, Borbus wrote:

The mess often happens because mappers don't necessarily know what a 
"coastline" is (I didn't before I researched it). For land-based maps 
the coastline that is shown is generally shown is mean high water level. 
The other "coastline" that is also shown on land-based maps is the mean 
lower water level. The bit between these lines is the intertidal zone. 
This is admittedly a bit less interesting, but it's certainly useful 
when there are causeways and other features in the intertidal zone.


It's also one of the most useful from a leisure perspective, as a lot of 
popular beaches fall primarily or wholly in the intertidal zone. Take, 
for example, Hunstanton in Norfolk - at high tide the sea comes all the 
way up to the sea wall, and there is no beach as such on the town centre 
seafront. But, at low tide, there's a large expanse of sand. And, in 
between, there are differing amounts of sand visible!


FWIW, I think that both OSM and OS currently show this correctly, with 
the intertidal beach being mapped as sand (as are the sand and mud banks 
further south near Heacham and Snettisham). Google, on the other hand, 
seems to be ignoring the intertidal area completely and mapping the 
coastline according to what is visible on their own aerial imagery (for 
a good example of that, zoom into Hunstanton Sea Life Centre on Google 
maps and then switch between map and satellite view).


Mark

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

Re: [Talk-it] Nome linea elettrica che cambia

[demon_box]

ciao, vi informo che alla fine (per ora) ho optato per la formula:

power=tower
ref=xx (valore numerico)
old_operator=(ASM, ENEL, AEM)

--enrico




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

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

Re: [OSM-talk-fr] grèves Loire - résumé et conclusion ?

[ades]

Pas le temps de tout relire. 
Pour info voir trace GPX (lien ci-dessous) établie à l’étiage 2013, à comparer 
avec l’Ortho 2016. Par défaut on a la position des grèves. ;-)
Chenal_GPS_Kit.gpx 

Je pense que la semaine prochaine je referai le même parcours, wait and see.
Juste une remarque, n’y aurait-il pas intérêt également à tagger les rives ou 
berges en linéaire ou en surfacique (cf question récente à Venise ) ? 
‘empierrement, ‘quai', ‘ripisylve’ ? avec complément par exemple 
‘empierremen:ruin’ 'ripisylve:wood’; «' ripisylve:grass' » etc. élément à 
placer au-dessus du riverbank (ligne) et/ou à l’intérieur (surface).
Pour ce que je connais, la limite du riverbank pourrait être celle des 
parcelles cadastrales, ce qui correspond en général au niveau de la rivière 
avant débordement. Dans les cas non cadastrés (levée de la Loire, Port…) à 
faire en interprétant l’Ortho, quand on connaît le site.

ça ne résout pas tout pour les grèves, les propositions faites me semblent 
plutôt bien, je relis semaine prochaine.

> Le 11 juil. 2019 à 16:32, François Boucault  a écrit :
> 
> OK, donc en fait pas besoin de ces tags, puisque le wiki osm pointe déjà vers 
> l'élément wikidata, et que celui-ci est lui-même relié à la page Wikipédia... 
> ça simplifie !
> Ps : lorsqu'on donne le tag wikidata dans l'éditeur id, il ajoute 
> automatiquement le tag wikipédia
> Merci pour l'aide :)
> 
> Le 11 juillet 2019 14:57:53 GMT+02:00, marc marc  
> a écrit :
> Bonjour,
> 
> Le 11.07.19 à 14:30, François Boucault a écrit :
> Pour un banc de sable avec peu ou pas de végétation : natural=shoal, 
> seasonal=dry_season, 
> wikidata=Q28337, wikipedia=fr:Banc de sable 
> 
> wikidata/wikipedia sert à renseigner l'élément ou LA page
> qui parle de cet objet.
> mettre le même wikidata/wikipedia sur tous les bancs de sable ne va pas.
> soit tu met le wikidata sur la page wiki du tag (le plus courant)
> soit tu veux vraiment un wikidata sur l'objet, le wikidata ne concernant 
> que la description, cela reviendrait à inventer description:wikidata
> 
> Cordialement,
> Marc
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr 
> 
> ___
> Talk-fr mailing list
> Talk-fr@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-fr


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

Re: [Talk-GB] UK coastline data

[Gregory Marler]

I have been seeing a lot of flooded tiles over the last week. Of course
doing a Cntrl+F5 on my browser refreshes the old tiles, so it's not
terrible.
Hopefully the current work now is avoiding that happening, as the country
"flooded" can look bad to new viewers. It was also annoying when I was out
of signal and OsmAnd seemed to have some tiles flooded.

For river coastlines, I believe The Thames is tidal as up as Teddington
lock. That would be even more excessive/impractical than Totnes, and have
all of central London be "by the sea".

For oddities with tidal marks, I don't know if the "Loe Bar" provides
anything interesting. It's a sand bar, on one side is the coast and on the
other is "The Loe" freshwater lake.

Thanks for your detailed help.
Gregory.

On Fri, 12 Jul 2019 at 07:46, Devonshire  wrote:

>
> On Thu, Jul 11, 2019, at 10:41 PM, Borbus wrote:
>
>
> The Dart cuts the coastline off right at the mouth, which doesn't seem
> right...
>
>
> I think the main reason I did that back in the day is that mapping
> coastline all the way up to Totnes seems extremely non-intuitive. Someone
> standing on Totnes quay (10 miles inland) is not standing on the coast in
> any meaningful way.
>
> I don't really care either way but what would be the benefit of changing
> it to coastline (and slavishly copying the OS is not a benefit) ?
>
> Kevin
> ___
> Talk-GB mailing list
> Talk-GB@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-gb
>


-- 
Gregory Marler
No More Grapes
07939 689 691
i...@nomoregrapes.com
http://www.nomoregrapes.com
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [Talk-us] Mapping rail trails

[Richard Fairhurst]

Minh Nguyen wrote:
> As with the network tag on bus routes, what's important for both 
> network and cycle_network is that the route is intended to form 
> part of a coherent *network* (almost like a brand, but not quite).

It's also useful for those of us writing routers, as it means we can avoid
applying a route relation uplift in those states that send bike routes along
entirely unsuitable state roads. (New York is a particular offender but
there are others.)

On my relationising travels, I spotted a couple of places where people had
mapped a city cycle network as a single route relation, often with "System"
in the title: Flagstaff Urban Trail System was one such. This is clearly
wrong. As a quick fix I changed the relation tagging from type=route to
type=network - which, interestingly, Waymarked Trails still renders:
https://cycling.waymarkedtrails.org/#route?id=2815833 - and created
relations for some of the longer routes. But really it needs all the routes
to be broken out into individual relations and given a common cycle_network
tag.

cheers
Richard



--
Sent from: http://gis.19327.n8.nabble.com/USA-f5284732.html

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

[OSM-talk-fr] Atelier transport.data.gouv.fr, Bordeaux, le 27 septembre

[Vincent Bergeot]

Bonjour,

le 27 septembre sur Bordeaux, si vous avez envie de venir dans le coin 
signalez le, nous devons pouvoir trouver


"Suite à la première rencontre publique autour de l'ouverture des 
données des parcs de stationnement, le Point d'Accès National, en 
partenariat avec la Métropole de Bordeaux, organise une deuxième 
rencontre autour de la définition du format unique de référencement des 
données des parcs de stationnement. L'événement est ouvert à toute 
personne qui travaille sur ou avec ces données, ou qui pourrait y être 
amenée."


https://www.eventbrite.fr/e/billets-rencontre-publique-transportdatagouv-referencement-des-donnees-parcs-de-stationnement-en-open-data-64786609493

à plus

--
Vincent Bergeot



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

Re: [Talk-at] minderwertige Importe

[various]

Würde ich eben so sehen. Sobald es nicht mehr v1 ist, sollte es kontrolliert 
worden sein. Ich habe dazu gerade etwas interessantes gefunden und werde einen 
neuen Gesprächsfaden aufmachen...

Man könne sogar zurück gehen bis 
https://www.openstreetmap.org/changeset/69861349 -> ich habe mir gerade noch 
ein paar ältere Changesets auch noch durchgeschaut. Die Anfrage könnte man also 
anpassen an:
node["at_bev:addr_date"="2019-04-01"](user:"addresshistory*org")(newer:"2019-05-03T00:00:00Z");out;


> andreas wecer  hat am 12. Juli 2019 um 07:41 
> geschrieben:
> 
> 
> 
> Am Do., 11. Juli 2019 um 22:21 Uhr schrieb Michael Reichert < 
> osm...@michreichert.de mailto:osm...@michreichert.de >:
> 
> > > Das Kriterium ist auf den ersten Blick machbar. Ich habe mir die
> > Änderungssätze bislang noch nicht angeschaut, daher die etwas dumme
> > Rückfrage meinerseits: Was tun, wenn ein v1-Node Mitglied eines
> > hochgeladenen Ways ist, der geändert worden ist (also jetzt v > 1), 
> > oder
> > später für einen Way verwendet worden ist?
> > 
> > > 
> Wenn die Daten inzwischen von jemand anderem bearbeitet wurden, kann das 
> meiner Meinung nach in den meisten Fällen als "kontrolliert" oder 
> "korrigiert" gewertet werden. Im allerschlimmsten Fall hat es sich zumindest 
> einmal jemand angesehen, solange nicht jemand anderes mit einem 
> großflächigen, mechanischen Edit darüber gefahren ist, aber davon ist nichts 
> bekannt.
> 
> 
> > > > * Changesets mit dem Beginn "Fehlende oder neue Adressen*"
> > 
> > Ab wann (Zeitpunkt) ist dieses Kriterium anzuwenden?
> > 
> > > 
> Das dürfte das erste Changeset außerhalb seiner Kernregion sein, ab wo er 
> nur noch großflächig importiert hat:
> https://www.openstreetmap.org/changeset/70645289
> 
> also im Grunde geht es um diese Nodes:
> 
> node["at_bev:addr_date"="2019-04-01"](user:"addresshistory*org")(newer:"2019-05-27T00:00:00Z");out;
> 
> Die Changesets, wo er existierende Daten bearbeitet und großflächig 
> Adressen gelöscht hat, sind großteils schon wieder rückgängig gemacht.
> 
> LG
>   Andreas
> 
> 
> ___
> Talk-at mailing list
> Talk-at@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-at
> 


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

Re: [Talk-GB] UK coastline data

[Devonshire]

On Thu, Jul 11, 2019, at 10:41 PM, Borbus wrote:
> 
> The Dart cuts the coastline off right at the mouth, which doesn't seem 
> right...
> 

I think the main reason I did that back in the day is that mapping coastline 
all the way up to Totnes seems extremely non-intuitive. Someone standing on 
Totnes quay (10 miles inland) is not standing on the coast in any meaningful 
way.

I don't really care either way but what would be the benefit of changing it to 
coastline (and slavishly copying the OS is not a benefit) ?

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