Re: [talk-au] Consistent tagging of botanic gardens around Australia - leisure=park vs leisure=garden

[Andrew Harvey]

On Tue, 24 Sep 2019 at 10:58, Daniel Graus  wrote:

> Recently, the Sydney Royal Botanic Gardens were changed from
> leisure=garden to leisure=park. This change prompted some discussion (
> https://www.openstreetmap.org/changeset/73984430) but no firm conclusions
> really arose, with the gardens still being mapped as a park at this stage.
>
>
> As botanic gardens are a reasonably common feature of major Australian
> cities, I looked at other cases around Australia, and found that tagging on
> these areas is quite inconsistent, with some being tagged as gardens such
> as Melbourne’s Royal Botanic Gardens, the Adelaide Botanic Gardens and (up
> until recently) Sydney’s Royal Botanic Gardens. Whereas, the Brisbane City
> Botanic Gardens, the Royal Tasmanian Botanical Gardens, and several others
> are mapped as parks.
>
>
> As the previously linked discussion highlighted, these spaces are quite
> diverse in their use and could easily be interpreted as parks, but at the
> same time, their design, function and general day to day use is
> considerably more horticulture/botany focused when compared to (as some
> examples) Hyde park in Sydney or the larger area of Kings Park in Perth.
>
>
> Additionally (also as discussed in the link), the tag
> garden:type=botanical descends in "tagging hierarchy" (whatever that is
> worth) from leisure=garden. The notion that this tag should be removed from
> a functional botanical garden or that it should sit alongside leisure=park
> doesn’t seem like it’s correct.
>
>
> Should all botanical gardens be changed to match one another? Is
> leisure=park or leisure=garden more correct in some/the majority/all of
> these cases?
>

One issue is this same tag leisure=garden is being used for both individual
gardens and the whole garden grounds. For example the "Royal Botanic
Gardens" in Sydney has a number of smaller named gardens like the "Rose
Garden", "Herb Garden" etc. Someone building an app for these gardens might
want to know which are the higher level gardens which probably have a
website, contact number, etc. and the individual gardens inside. Currently
you'd just need to guess based on the geometry being inside another.

The advantage of tagging as leisure=park is that you no longer have an
issue with the tag being used for two diferent things.

On the other hand if I'm building a map I might want to render a flower
icon for "gardens" and maybe a tree for a park. If we tag "Royal Botanic
Gardens" as a park, I can't distinguish these gardens from a regular park.

There's always going to be a fair amount of overlap, some gardens will have
open spaces for leisure more like a park like
https://www.openstreetmap.org/relation/3744999
 and
some parks will have some small gardens as part of the park like
https://www.openstreetmap.org/way/19603604, where you draw the line is
always going to be uncertain.

I still think Royal Botanic Gardens is more a garden than a park, because
of the amount of work that goes on there towards maintaining the actual
gardens, this is it's primary function. The fact that you could use a
clearing to kick a ball around (more like a park) I think is a secondary
function.
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au

Re: [Talk-ee] verbatium buiding import discussion

[Jaak Laineste]

Hi,

When I did Tartu bulk delete-replace with the city gov data long time ago, then 
I contacted all the previous editors in the area and asked their permission. As 
number of existing data was small, then they were ok.

Here most buildings seem to have some manual or semi-manual edits after import, 
I would group the edits by the involved users (juhanjuku, kaupov seem to be 
popular), and ask their permission before basically deleting their efforts. 
Where you dont get permission better use soft approach there: just mark changes 
for manual checks by community. 


Jaak



> On 24 Sep 2019, at 07:50, SviMik  wrote:
> 
> I have analyzed the largest verbatium's import (changesets 591093, 579407, 
> 572107, 569277, 569055 (ways) + 561094, 559707, 558636, 558056, 557568, 
> 557358, 557193, 556899 (nodes only)), which was made in 2008. That covers 
> 86.7% of all his edits.
> The import was covering Tallinn, Saue and Maardu. Turned out verbatium wasn't 
> particulary active outside Harjumaa.
> There were total 67813 ways imported, 9032 of them are already deleted by 
> other editors, and 17878 were changed either in geometry or tags* department 
> (15529 has a geometry change, and 5077 has a tag change), which leaves 40903 
> buildings for deletion.
> * I did not count the following tags because they are part of my imports 
> anyway: addr:city, addr:country, addr:housenumber, addr:street, maaamet:ETAK, 
> maaamet:orig_tunnus, source, source:addr, addr2:*
> * If some change was reverted I do not count it as a change, because I only 
> compare the first and the last version
> 
> Here is the list of ways for deletion:
> http://svimik.com/verbatium_import1_ways_unchanged1.txt
> 
> Here is the full report for all the 67813 ways:
> http://svimik.com/verbatium_import1_ways1.csv
> 
> Full list of his changesets:
> http://svimik.com/verbatium_changesets.xls
> 
> Currently, the bbox of his changesets has 91324 buildings, which means... 
> We're gonna delete 44.79% of Saue-Tallinn-Maardu buildings. That gonna be 
> interesting. Should we split it by 10k for example? Or just start with Maardu 
> and see what happens?
> 
> 
> Воскресенье, 15 сентября 2019, 9:42 +03:00 от "Jaak Laineste" 
> :
>> Hoi,
>> 
>> Jah, need peaks kustutama. Enne võiks teha muudatuse analüüsi - kui palju ja
>> kus kustutataks, ega mõned linnad kohe väga tühjaks ei jää.
>> 
>> Jaak 
>> 
>> p.s. sama asi ka corine impordi osade tag-idega, näiteks põllud (field), need
>> on pigem müra kui info kaardil.
>> 
>> 
>> 
>>> On 14 Sep 2019, at 15:34, SviMik via Talk-ee 
>> wrote:
>>> 
>>> Hi everyone!
>>> 
>>> I'd like to discuss the import made by verbatium in 2008:
>>> https://www.openstreetmap.org/changeset/569055
>>> (...and other similar changesets)
>>> 
>>> There are two issues with that import:
>>> 1. Unknown data source with unknown license (probably it was a Garmin map
>> judging by the Type=0x13 tag)
>>> 2. Poor quality of the data. If you see a building distorted like this:
>> http://svimik.com/verbatiumimport1.png
>>> - you can be sure it's verbatium's. Maybe it was OK in 2008, but in 2019 we
>> have much better options.
>>> 
>>> What can be done:
>>> 1. Remove all buildings which geometry and tags were not edited since the
>> initial import. For the tags the following exceptions can be made because 
>> they
>> were automatic edits:
>>> - User xybot has fixed the tag typo (buildung=yes) in the initial import and
>> added its own tag (created_by=xybot)
>>> - User juhanjuku has removed the Type=0x13 and created_by=xybot tags
>>> - User SviMik_import has imported the address tags to these buildings from
>> the Maa-amet database (nothing that can't be imported again)
>>> 2. Proceed with the Maa-amet building import as usual
>>> 
>>> It will solve:
>>> 1. The license issue (if there is any)
>>> 2. The quality issue (if you agree there is an issue)
>>> 3. Will update the map in general, for example the demolished buildings will
>> be removed from OSM.
>>> 
>>> For buildings which geometry was changed by other contributors after the
>> initial import - we can assume both license and quality issues were solved
>> since they no longer contain the imported geometry. I know it's a grey field,
>> and I'm not sure it works like that, but at least these buildings do have 
>> some
>> excuse to stay.
>>> 
>>> For buildings which geometry was NOT changed, but some POI tags were added -
>> let them stay for now and discuss it later if needed. I suspect it will be a
>> rare case, but the exact number is unknown right now.
>>> 
>>> Questions:
>>> 1. Has anyone else digged into the issue, maybe asked verbatium himself?
>>> 2. Can anyone confirm that the import indeed has the license problem?
>>> 3. Is the proposed plan good? (in case if you agree that it needs to be
>> fixed)
>>> 
>>> -- 
>>> SviMik
>>> ___
>>> Talk-ee mailing list
>>> Talk-ee@openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/talk-ee
>> 
>> 

[OSM-talk-fr] effet SNT

[David Crochet]

Bonjour

OSM ressent-il déjà les premiers effets de la nouvelle discipline SNT ?

Cordialement

--
David Crochet


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

Re: [Talk-ee] verbatium buiding import discussion

[Jaak Laineste]

Would you consider using osmose-qa here? It would require one-time creating 
connector for maa-amet buildings shp, and this will be useful in any case, for 
whole country and for long time, permanently even. 

Then there are two ways to apply it for Tallinn: (a) remove all verbatium and 
then it shows all deleted buildings as missing or (b) softer - no delete, shows 
latest maaamet ones as just more uptodate and users can click through each. 
Maybe it has some more bulk updating also. I’d start with the soft one, helps 
to precheck the changes also, even if you end up bulk delete+upload. 

Creating and deploy proper connector which identifies both maaamet real updates 
and verbatium properly may require some learning and sweat. 

Jaak
(Sent from mobile)

> On 24 Sep 2019, at 23:46, SviMik  wrote:
> 
> http://svimik.com/verbatiumimportmap1.png
> Here's the screenshot. Not precise, but gives some idea.
> 40903 buildings is a bit too much for JOSM.
> 
> 
> Вторник, 24 сентября 2019, 22:08 +03:00 от "Jaak Laineste" :
>> 
>> These txt reports with IDs are not too visual, can you create any renderable
>> file for josm (.osm for example) or screenshot to show the community what it
>> really means? Are the building under question random or somehow in specific
>> areas etc.  I dont know if there is any "test osm server” for such 
>> experiments
>> nowadays somewhere, probably not. 
>> 
>> Jaak
>> 
>>> On 24 Sep 2019, at 07:50, SviMik  wrote:
>>> 
>>> I have analyzed the largest verbatium's import (changesets 591093, 579407,
>> 572107, 569277, 569055 (ways) + 561094, 559707, 558636, 558056, 557568,
>> 557358, 557193, 556899 (nodes only)), which was made in 2008. That covers
>> 86.7% of all his edits.
>>> The import was covering Tallinn, Saue and Maardu. Turned out verbatium
>> wasn't particulary active outside Harjumaa.
>>> There were total 67813 ways imported, 9032 of them are already deleted by
>> other editors, and 17878 were changed either in geometry or tags* department
>> (15529 has a geometry change, and 5077 has a tag change), which leaves 40903
>> buildings for deletion.
>>> * I did not count the following tags because they are part of my imports
>> anyway: addr:city, addr:country, addr:housenumber, addr:street, maaamet:ETAK,
>> maaamet:orig_tunnus, source, source:addr, addr2:*
>>> * If some change was reverted I do not count it as a change, because I only
>> compare the first and the last version
>>> 
>>> Here is the list of ways for deletion:
>>> http://svimik.com/verbatium_import1_ways_unchanged1.txt
>>> 
>>> Here is the full report for all the 67813 ways:
>>> http://svimik.com/verbatium_import1_ways1.csv
>>> 
>>> Full list of his changesets:
>>> http://svimik.com/verbatium_changesets.xls
>>> 
>>> Currently, the bbox of his changesets has 91324 buildings, which means...
>> We're gonna delete 44.79% of Saue-Tallinn-Maardu buildings. That gonna be
>> interesting. Should we split it by 10k for example? Or just start with Maardu
>> and see what happens?
>>> 
>>> 
>>> Воскресенье, 15 сентября 2019, 9:42 +03:00 от "Jaak Laineste"
>> :
 Hoi,
 
 Jah, need peaks kustutama. Enne võiks teha muudatuse analüüsi - kui palju
>> ja
 kus kustutataks, ega mõned linnad kohe väga tühjaks ei jää.
 
 Jaak 
 
 p.s. sama asi ka corine impordi osade tag-idega, näiteks põllud (field),
>> need
 on pigem müra kui info kaardil.
 
 
 
> On 14 Sep 2019, at 15:34, SviMik via Talk-ee 
 wrote:
> 
> Hi everyone!
> 
> I'd like to discuss the import made by verbatium in 2008:
> https://www.openstreetmap.org/changeset/569055
> (...and other similar changesets)
> 
> There are two issues with that import:
> 1. Unknown data source with unknown license (probably it was a Garmin map
 judging by the Type=0x13 tag)
> 2. Poor quality of the data. If you see a building distorted like this:
 http://svimik.com/verbatiumimport1.png
> - you can be sure it's verbatium's. Maybe it was OK in 2008, but in 2019
>> we
 have much better options.
> 
> What can be done:
> 1. Remove all buildings which geometry and tags were not edited since the
 initial import. For the tags the following exceptions can be made because
>> they
 were automatic edits:
> - User xybot has fixed the tag typo (buildung=yes) in the initial import
>> and
 added its own tag (created_by=xybot)
> - User juhanjuku has removed the Type=0x13 and created_by=xybot tags
> - User SviMik_import has imported the address tags to these buildings from
 the Maa-amet database (nothing that can't be imported again)
> 2. Proceed with the Maa-amet building import as usual
> 
> It will solve:
> 1. The license issue (if there is any)
> 2. The quality issue (if you agree there is an issue)
> 3. Will update the map in general, for example the demolished buildings
>> will
 be removed from OSM.
> 
> For buildings which geometry 

Re: [Talk-GB] Subject: Re: Thomas Cook shops

[Mateusz Konieczny]

Is it possible to buy any services there?

24 Sep 2019, 15:20 by tonyo...@gmail.com:

>
> I think this is all premature. The shops still have the branding,  they 
> could be taken over by a new company operating as Thomas  Cook. I Think 
> that nothing should be done until there is greater  clarity.
>
>
> Tony Shield
>
>
> TonyS999
>
> On 24/09/2019 14:10, Tadeusz Cantwell  wrote:
>
>> Thanks, I have used once shop=vacant before, nowthat you mention it. 
>> Will read up on the wiki to see thedifferent intended uses for them. 
>> The old_name is an interestingoption. 
>>
>> On Tue, 24 Sep 2019 at 14:00,  Jez Nicholson <>> 
>> jez.nichol...@gmail.com >> >  wrote:
>>
>>> I'm a fan of shop=vacant, old_name=Thomas Cookmyself 
>>>
>>> You could argue for not:name=Thomas Cook  maybe
>>>
>>> On Tue, 24 Sep 2019, 13:34  Tadeusz Cantwell, <>>> 
>>> t4d...@gmail.com   wrote:
>>>
 I changed the three shops in N.I to  
 disused;shop=travel-agent since I wasn't sure what the  
 best practice was in this case. Not all of them had  the 
 wiki links etc. Any advice on a better way?

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

Re: [Talk-ca] Saints in street names in Ontario

[Jarek Piórkowski]

Hi all,

I have now made the edit at
https://wiki.openstreetmap.org/w/index.php?title=Canadian_tagging_guidelines=revision=1907677=1898100
and I saw that Matthew has edited a few of the more prominent examples
already.

Thanks!

--Jarek

On Tue, 24 Sep 2019 at 17:09, Matthew Darwin  wrote:
>
> Hi,
>
> It sounds fine for me.
>
> On 2019-09-10 7:54 a.m., john whelan wrote:
>
> Looks good to me and if Matthew has cast his eye over it and not spotted 
> anything major then I think we can safely say Ottawa is happy with it.
>
> Cheerio John
>
> On Mon, Sep 9, 2019, 9:57 PM Pierre Béland via Talk-ca, 
>  wrote:
>>
>> Cela semble bien préciser, mais les collègues d'Ontario pourront mieux 
>> répondre.
>>
>> Pierre
>>
>> Envoyé à partir de Yahoo Courriel sur Android
>>
>> Le lun., sept. 9 2019 à 3:11 PM, Jarek Piórkowski
>>  a écrit :
>> Hi Pierre,
>>
>> (I responded via email at first, but realized one more thing, so
>> adding on and sending to talk-ca:)
>>
>> The proposed wiki addition does start with "In Ontario". However
>> thanks bringing this up, as I realized I forgot to account for parts
>> of Ontario where streets will be named in French - this change should
>> not apply to those.
>>
>> I am changing the suggested wording to:
>>
>> In parts of **Ontario** that primarily name streets in English,
>> street and road names containing initial "St." or "St" should only be
>> expanded to "Saint" when "Saint" is common usage for that street. To
>> be clear, this overrides the general rule
>> https://wiki.openstreetmap.org/wiki/Names#Abbreviation_.28don.27t_do_it.29
>> for "St." which does not stand for "street". As with other names in
>> OSM, factors you might want to consider when determining common usage
>> include spellings posted on street signs ("on the ground" rule),
>> spellings used in local media, GeoBase street name data, and spellings
>> used by official municipal sources including open data datasets. See
>> discussion on talk-ca [0].
>>
>> Would this wording be fine for Ottawa and other bilingual areas, or am
>> I missing a pitfall?
>>
>> Thanks,
>> --Jarek
>>
>> On Mon, 9 Sep 2019 at 08:51, Pierre Béland  wrote:
>> >
>> > Marek
>> >
>> > Ces instructions ne s'appliquent pas à toutes les provinces. Il faudrait 
>> > donc indiquer sur la page wiki à quelles provinces elles s'appliquent
>> >
>> > Pierre
>> >
>> > Envoyé à partir de Yahoo Courriel sur Android
>> >
>> > Le lun., sept. 9 2019 à 2:51 AM, Jarek Piórkowski
>> >  a écrit :
>> > Hello,
>> >
>> > I'm following up on the thread about saints and lack thereof in street
>> > names from a couple of months ago (see archives [1] [2]).
>> >
>> > I would like to suggest the following wording added to Canadian
>> > tagging guidelines at
>> > https://wiki.openstreetmap.org/wiki/Canadian_tagging_guidelines#Street_names
>> > :
>> >
>> >In Ontario, street and road names containing initial "St." or "St"
>> > should only be expanded to "Saint" when "Saint" is common usage for
>> > that street. To be clear, this overrides the general rule
>> > https://wiki.openstreetmap.org/wiki/Names#Abbreviation_.28don.27t_do_it.29
>> > for "St." which does not stand for "street". As with other names in
>> > OSM, factors you might want to consider when determining common usage
>> > include spellings posted on street signs ("on the ground" rule),
>> > spellings used in local media, GeoBase street name data, and spellings
>> > used by official municipal sources including open data datasets. See
>> > discussion on talk-ca [0].
>> >
>> > where [0] would be a link to this message/thread archive. (Comments on
>> > the wording and suggestions appreciated!)
>> >
>> > Is anyone opposed to this change?
>> >
>> > I have attempted to advertise/announce this proposed change. This was:
>> > - posted in this mailing list in March/April of this year (some quoted
>> > below, see list archives for more discussion)
>> > - I posted a note https://www.openstreetmap.org/note/1741334 in
>> > Toronto with a link to this thread (supportive responses from Kevo and
>> > DannyMcD)
>> > - on April 10, sent a message [2] with a link to the note to editors
>> > who were showing up as top editors on
>> > http://osmstats.neis-one.org/?item=countries=Canada
>> > (they aren't necessarily representative of the community, but it's
>> > really the closest we can reasonably do given our current tooling) [3]
>> > (no private message responses)
>> > - posted on OSM Canada Slack on 17 August
>> > https://osm-ca.slack.com/archives/CASP8UQNT/p1566053199044200
>> > (supportive responses from Matthew Darwin and Eric Geiler)
>> > - on August 27, sent a few more private messages to editors in top 50
>> > on the stats page who had done Ontario edits [4] (no private message
>> > responses)
>> >
>> > If you know of anyone else who might have a further opinion on this,
>> > please forward as possible.
>> >
>> > Thanks,
>> > --Jarek
>> >
>> >
>>
>> ___
>> Talk-ca mailing list

Re: [talk-au] Discussion A: Is this forum fit for purpose?

[Sebastian S.]

Hi,
I've said it before but this is not a forum. It is a mailing list. Therefore 
many of your points seem to have the wrong perspective.

On 25 September 2019 9:00:50 am AEST, "Herbert.Remi via Talk-au" 
 wrote:
># Discussion A: Is this forum fit for purpose?
>
> “PLEASE KEEP IT BRIEF. SPACE OF OF A PREMIUM. THANKS, JANE”
>
>## The Issue
>
>The forum needs to be robust. It needs to tolerate a lot of traffic. It
>needs to work on the busy days, not just the quiet. It needs a
>functionality that allows you to manage congestion. It needs to
>tolerate diverse interest and writing styles. It needs to have room for
>growth.
>
>**I believe OSM is too important for anything else!**
>
>If you love OSM, and I am sure you do, then we need a more modern
>platform then this. This mailing list is so 90s.
>
>The good news is there is plenty of options and I am sure that here
>there is the technical expertise and ability to put it on a better
>footing.
>
>## Features that would be of value:
>
>- You need to be able to tailor your view of the content without
>intervention of a group moderator or group consensus.
>
>- You need to filter the content for topics your interest in and topics
>you’re not
>
>- You need to filter the content with posts from people you like and
>block those that you don’t (whitelist and blacklist).
>
>- You need to be able to search by including and excluding keywords,
>preferably both in the same query
>
>- You need to be able to search by post tags, again both including and
>excluding
>
>- Preferable, it would be best to combine both tag and keyword searches
>(but many platforms have problems with this)
>
>- Every post should be tagged with country and state of jurisdiction.
>The country could be default and I only suggest it as at some time
>other this idea may spread.
>
>- Provide the option to tag (plain text) the posts with the topic under
>discussion e.g. highway, lifecycle, announcement, events, registration,
>mapping party, instructions, and message type (“The Facts”, “The
>Issue”, etc)
>
>- You should be able to move between chat groups and follow multiple
>chat groups. Slack does this well.
>
>- A post should be able to include “attachments” that are not visible
>until open: office files, photos, PDF, HTML links. This saves screen
>space.
>
>- Posts should have a header. It provides a (searchable) overview and
>the actual post could be blended in and out.
>
>- A smartphone app would be great. Why? Seek data shows most job
>applications are done on the app and take less than 15 minutes. It is
>remarkable how much you get done on the way to work on the bus.
>
>- The help provided by this forum should be made available as soon as
>it is posted: 365 days a year, 24 hours per day.
>
>- Ideally, it should support a "forms" function for registration to
>group events (or link to an external platform that supports such)
>
>- It would be great to have a calendar function for events.
>
>- We need more than a plain text. Rich text functionality is advisable.
>A HTML capable editor is an option (transparent). As I have previously
>mentioned, "markdown" is a popular modern option support by FOSS/GitHub
>
>Everybody is welcome in an OSM forum, no matter the interest. We need
>everybody we can find to help with this project. We should try to
>create an environment where is happy to do what they do best, and come
>and go as they please.
>
>I welcome your comments. 
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au

Re: [talk-au] Consistent tagging of botanic gardens around Australia - leisure=park vs leisure=garden

[Warin]

On 24/09/19 20:56, Andrew Davidson wrote:

On 24/9/19 10:56 am, Daniel Graus wrote:


Should all botanical gardens be changed to match one another? Is 
leisure=park or leisure=garden more correct in some/the majority/all 
of these cases?


OK, a quick global survey

Of the ~2,500 botanical gardens that are in Wikidata and have a match 
in OSM there are:


320 leisure=garden
204 leisure=park
 22 tourism=attraction
 20 tourism=zoo
 12 leisure=nature_reserve
 11 tourism=museum
  4 tourism=theme_park
  1 tourism=botanical_garden
  1 leisure=yes

and 47 with no apparent object tag.

Wikidata lists 37 botanical gardens in Australia that don't have a 
wikidata tag or aren't mapped. Will have to check these before we can 
get an Australian list.


There are some ~700 garden:type=botanical  in the OSM data base of some 
~57,000 garden:type=*.
Most, ~ 56,000 are garden:type=residential, with botanical being second 
most frequent.



I don't think the most frequent use in the data base should override a 
logical tagging system, rather the reverse. A logical tagging system is 
far easier to learn and retain in memory rather then an an illogical one.


-
Mapping missing botanic gardens would be worthwhile. They can be 
interesting places to visit, certainly worth a lunch stop.






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

Re: [talk-au] Discussion A: Is this forum fit for purpose?

[Ben Kelley]

You are missing one need: It needs to be something that people will use.

For that reason, there are many ways to handle this, with the talk-au list
being one of those.

Some people use some of the other (existing) options for discussing OSM. A
mailing list has its advantages and disadvantages, but there are other
options that implement some of the features you suggest in a better way.
The more modern platforms already exist.

- Ben.

On Wed, 25 Sep 2019 at 09:02, Herbert.Remi via Talk-au <
talk-au@openstreetmap.org> wrote:

> # Discussion A: Is this forum fit for purpose?
>
>  “PLEASE KEEP IT BRIEF. SPACE OF OF A PREMIUM. THANKS, JANE”
>
> ## The Issue
>
> The forum needs to be robust. It needs to tolerate a lot of traffic. It
> needs to work on the busy days, not just the quiet. It needs a
> functionality that allows you to manage congestion. It needs to tolerate
> diverse interest and writing styles. It needs to have room for growth.
>
>
> **I believe OSM is too important for anything else!**
>
>
> If you love OSM, and I am sure you do, then we need a more modern platform
> then this. This mailing list is so 90s.
>
> The good news is there is plenty of options and I am sure that here there
> is the technical expertise and ability to put it on a better footing.
>
>
>
> ## Features that would be of value:
>
>- You need to be able to tailor your view of the content without
>intervention of a group moderator or group consensus.
>- You need to filter the content for topics your interest in and
>topics you’re not
>- You need to filter the content with posts from people you like and
>block those that you don’t (whitelist and blacklist).
>- You need to be able to search by including and excluding keywords,
>preferably both in the same query
>- You need to be able to search by post tags, again both including and
>excluding
>- Preferable, it would be best to combine both tag and keyword
>searches (but many platforms have problems with this)
>- Every post should be tagged with country and state of jurisdiction.
>The country could be default and I only suggest it as at some time other
>this idea may spread.
>- Provide the option to tag (plain text) the posts with the topic
>under discussion e.g. highway, lifecycle, announcement, events,
>registration, mapping party, instructions, and message type (“The Facts”,
>“The Issue”, etc)
>- You should be able to move between chat groups and follow multiple
>chat groups. Slack does this well.
>- A post should be able to include “attachments” that are not visible
>until open: office files, photos, PDF, HTML links. This saves screen space.
>- Posts should have a header. It provides a (searchable) overview and
>the actual post could be blended in and out.
>- A smartphone app would be great. Why? Seek data shows most job
>applications are done on the app and take less than 15 minutes. It is
>remarkable how much you get done on the way to work on the bus.
>- The help provided by this forum should be made available as soon as
>it is posted: 365 days a year, 24 hours per day.
>- Ideally, it should support a "forms" function for registration to
>group events (or link to an external platform that supports such)
>- It would be great to have a calendar function for events.
>- We need more than a plain text. Rich text functionality is
>advisable. A HTML capable editor is an option (transparent). As I have
>previously mentioned, "markdown" is a popular modern option support by
>FOSS/GitHub
>
> Everybody is welcome in an OSM forum, no matter the interest. We need
> everybody we can find to help with this project. We should try to create an
> environment where is happy to do what they do best, and come and go as they
> please.
>
> I welcome your comments. 
>
>
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au

[talk-au] Discussion A: Is this forum fit for purpose?

[Herbert.Remi via Talk-au]

# Discussion A: Is this forum fit for purpose?

 “PLEASE KEEP IT BRIEF. SPACE OF OF A PREMIUM. THANKS, JANE”

## The Issue

The forum needs to be robust. It needs to tolerate a lot of traffic. It needs 
to work on the busy days, not just the quiet. It needs a functionality that 
allows you to manage congestion. It needs to tolerate diverse interest and 
writing styles. It needs to have room for growth.

**I believe OSM is too important for anything else!**

If you love OSM, and I am sure you do, then we need a more modern platform then 
this. This mailing list is so 90s.

The good news is there is plenty of options and I am sure that here there is 
the technical expertise and ability to put it on a better footing.

## Features that would be of value:

- You need to be able to tailor your view of the content without intervention 
of a group moderator or group consensus.

- You need to filter the content for topics your interest in and topics you’re 
not

- You need to filter the content with posts from people you like and block 
those that you don’t (whitelist and blacklist).

- You need to be able to search by including and excluding keywords, preferably 
both in the same query

- You need to be able to search by post tags, again both including and excluding

- Preferable, it would be best to combine both tag and keyword searches (but 
many platforms have problems with this)

- Every post should be tagged with country and state of jurisdiction. The 
country could be default and I only suggest it as at some time other this idea 
may spread.

- Provide the option to tag (plain text) the posts with the topic under 
discussion e.g. highway, lifecycle, announcement, events, registration, mapping 
party, instructions, and message type (“The Facts”, “The Issue”, etc)

- You should be able to move between chat groups and follow multiple chat 
groups. Slack does this well.

- A post should be able to include “attachments” that are not visible until 
open: office files, photos, PDF, HTML links. This saves screen space.

- Posts should have a header. It provides a (searchable) overview and the 
actual post could be blended in and out.

- A smartphone app would be great. Why? Seek data shows most job applications 
are done on the app and take less than 15 minutes. It is remarkable how much 
you get done on the way to work on the bus.

- The help provided by this forum should be made available as soon as it is 
posted: 365 days a year, 24 hours per day.

- Ideally, it should support a "forms" function for registration to group 
events (or link to an external platform that supports such)

- It would be great to have a calendar function for events.

- We need more than a plain text. Rich text functionality is advisable. A HTML 
capable editor is an option (transparent). As I have previously mentioned, 
"markdown" is a popular modern option support by FOSS/GitHub

Everybody is welcome in an OSM forum, no matter the interest. We need everybody 
we can find to help with this project. We should try to create an environment 
where is happy to do what they do best, and come and go as they please.

I welcome your comments. ___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au

Re: [Talk-ca] Présentation à SotM2019 sur l'analyse des bâtiments

[John Whelan]

Where are we up to with imported buildings in Canada?

I understood someone was looking at some routines to run on the data 
before import for Microsoft, Stats Canad and the Natural Resources 
Canada LiDAR data sources.


Has that been done for Canada as a whole or are we at the point where 
local mappers are deciding to import their local area?


I note there seems to be a fair number of buildings in many cities but 
apart from Ottawa I don't think any are complete.


Thanks John

Pierre Béland via Talk-ca wrote on 2019-09-24 6:47 PM:

Bonjour,

Je suis de retour du SOTM-2019 à Heidelberg où j'ai pu me rendre grâce 
à un Scholarship de la Fondation OSM.  Des présentations et rencontres 
fort intéressantes. Les videos des présentations sont déja disponibles 
à partir du lien https://media.ccc.de/b/conferences/sotm2019


Vous pouvez voir le video de ma présentation «OSM Quality Mapping : 
Metrics to monitor Buildings outbounds»
à l'adresse 
https://media.ccc.de/v/sotm2019-1046-osm-quality-mapping-metrics-to-monitor-buildings-outbounds
Les diapos sont disponibles sur le Blog OpendatalRDC. Je prévois aussi 
y publier au cours des prochaines semainesles analyses détaillées des 
projets analysés. 
https://github.com/opendatalabrdc/Blog/blob/master/SOTM_2019-OSM-Quality-Mapping--Metrics-to-monitor-Buildings-outbounds_Pierre_Beland.odp


Je vais aussi réviser le contenu du répertoire OQ_Analysis sur Github 
avec la nouvelle version des fonctions PostGIS contenant les nouvelles 
variables d'analyse que j'ai ajouté au projet.


Lors de la présentation, j'y ai fait une brève comparaison d'imports 
de données comparant Toronto et Dallas (import Microsoft). L'image 
Microsoft auquelle je fait référencepour l'Afrique dans ma 
présentations est accessible sur l'article de Blog Microsoft releases 
18M building footprints in Uganda and Tanzania to enable AI Assisted 
Mapping 
 


https://blogs.bing.com/BingBlogs/media/MapsBlog/2019/09/Extractions_MusomaTanzania.jpg

Sur cette image, Les données vectorielles de bâtiments observées sont 
en général rectangulaires. Par contre on observe certaines 
inexactitudes dans les géométries dérivées par les technique 
d'intelligence artificielle (angles inexacts ou plusieurs bâtiments 
regroupés).  J'en ai discuté avec les développeurs de Microsoft et 
nous avons convenu que ceci semble s'expliquer dans ce cas spécifique 
pour la Tanzanie par une moins grande qualité des images satellites.


J'ai brièvement examiné ces données pour le centre-ville de 
Saint-Jean-sur-Richelieuet constaté que les blocs de bâtiments y sont 
représentés dans les données Microsoft comme un seul bâtiment. Les 
techniques d'IA rencontrent donc le même problème que nous avons comme 
contributeurs avec difficulté de déterminer chaque bâtiment individuel 
à partir d'images non suffisamment précises.



Pierre


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

[Talk-ca] Présentation à SotM2019 sur l'analyse des bâtiments

[Pierre Béland via Talk-ca]

Bonjour,
Je suis de retour du SOTM-2019 à Heidelberg où j'ai pu me rendre grâce à un 
Scholarship de la Fondation OSM.  Des présentations et rencontres fort 
intéressantes. Les videos des présentations sont déja disponibles à partir du 
lien https://media.ccc.de/b/conferences/sotm2019
Vous pouvez voir le video de ma présentation «OSM Quality Mapping : Metrics to 
monitor Buildings outbounds» 
 à l'adresse 
https://media.ccc.de/v/sotm2019-1046-osm-quality-mapping-metrics-to-monitor-buildings-outbounds
Les diapos sont disponibles sur le Blog OpendatalRDC. Je prévois aussi y 
publier au cours des prochaines semaines les analyses détaillées des projets 
analysés. 
https://github.com/opendatalabrdc/Blog/blob/master/SOTM_2019-OSM-Quality-Mapping--Metrics-to-monitor-Buildings-outbounds_Pierre_Beland.odp
Je vais aussi réviser le contenu du répertoire OQ_Analysis sur Github avec la 
nouvelle version des fonctions PostGIS contenant les nouvelles variables 
d'analyse que j'ai ajouté au projet.
Lors de la présentation, j'y ai fait une brève comparaison d'imports de données 
comparant Toronto et Dallas (import Microsoft). L'image Microsoft auquelle je 
fait référence pour l'Afrique dans ma présentations est accessible sur 
l'article de Blog  Microsoft releases 18M building footprints in Uganda and 
Tanzania to enable AI Assisted Mapping 
https://blogs.bing.com/BingBlogs/media/MapsBlog/2019/09/Extractions_MusomaTanzania.jpg
Sur cette image, Les données vectorielles de bâtiments observées sont en 
général rectangulaires. Par contre on observe certaines inexactitudes dans les 
géométries dérivées par les technique d'intelligence artificielle (angles 
inexacts ou plusieurs bâtiments regroupés).  J'en ai discuté avec les 
développeurs de Microsoft et nous avons convenu que ceci semble s'expliquer 
dans ce cas spécifique pour la Tanzanie par une moins grande qualité des images 
satellites.

J'ai brièvement examiné ces données pour le centre-ville de 
Saint-Jean-sur-Richelieu et constaté que les blocs de bâtiments y sont 
représentés dans les données Microsoft comme un seul bâtiment.  Les techniques 
d'IA rencontrent donc le même problème que nous avons comme contributeurs avec 
difficulté de déterminer chaque bâtiment individuel à partir d'images non 
suffisamment précises.


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

Re: [OSM-talk-fr] CyclOSM, rendu cyclable libre

[François]

Le 24/09/2019 à 19:43, 
osm.sanspourr...@spamgourmet.com a écrit :
non, non c'était dev.{s}, donc s=a|b|c comme d'habitude et ça donne le 
lien que tu mets en exemple.


Bref, si Viking se comporte comme les autres services, tu laisses {s}, 
il remplacera normalement.


Ne marche pas avec {s}


Et si ça ne marche pas tu mets a ou b ou c.



Ça fonctionne maintenant. Merci à tous les deux.

Voici le fichier ~/.viking/maps.xml que j'ai créé (sous Linux) :


   
 CyclOSM
 name="hostname">https://dev.a.tile.openstreetmap.fr/cyclosm/

 /%d/%d/%d.png
 30
 cyclOSM
   
 


Pour ceux que ça intéresse, notamment si on veut rajouter plusieurs cartes :
- Les lignes  et  sont respectivement des lignes de 
début et fin de fichier.
- La valeur name="id" (30 ici) doit être une valeur unique. S'assurer 
que la valeur choisie n'est pas déjà utilisée dans le fichier

/usr/share/viking/maps.xml.

--
François



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

Re: [Talk-it] tagliare osm.pbf con bounding box

[Martin Koppenhoefer]

sent from a phone

> On 24. Sep 2019, at 20:24, Alessandro P. via Talk-it 
>  wrote:
> 
> se hai la fortuna di lavorare con una macchina Linux, io stravedo per Osmium


anch’io, su mac è anche facile da installare, ci sono pacchetti 

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

Re: [Talk-ca] Saints in street names in Ontario

[Matthew Darwin]

Hi,

It sounds fine for me.

On 2019-09-10 7:54 a.m., john whelan wrote:
Looks good to me and if Matthew has cast his eye over it and not 
spotted anything major then I think we can safely say Ottawa is 
happy with it.


Cheerio John

On Mon, Sep 9, 2019, 9:57 PM Pierre Béland via Talk-ca, 
mailto:talk-ca@openstreetmap.org>> wrote:


Cela semble bien préciser, mais les collègues d'Ontario pourront
mieux répondre.

Pierre

Envoyé à partir de Yahoo Courriel sur Android



Le lun., sept. 9 2019 à 3:11 PM, Jarek Piórkowski
mailto:ja...@piorkowski.ca>> a écrit :
Hi Pierre,

(I responded via email at first, but realized one more thing, so
adding on and sending to talk-ca:)

The proposed wiki addition does start with "In Ontario". However
thanks bringing this up, as I realized I forgot to account
for parts
of Ontario where streets will be named in French - this
change should
not apply to those.

I am changing the suggested wording to:

    In parts of **Ontario** that primarily name streets in
English,
street and road names containing initial "St." or "St"
should only be
expanded to "Saint" when "Saint" is common usage for that
street. To
be clear, this overrides the general rule

https://wiki.openstreetmap.org/wiki/Names#Abbreviation_.28don.27t_do_it.29
for "St." which does not stand for "street". As with other
names in
OSM, factors you might want to consider when determining
common usage
include spellings posted on street signs ("on the ground" rule),
spellings used in local media, GeoBase street name data, and
spellings
used by official municipal sources including open data
datasets. See
discussion on talk-ca [0].

Would this wording be fine for Ottawa and other bilingual
areas, or am
I missing a pitfall?

Thanks,
--Jarek

On Mon, 9 Sep 2019 at 08:51, Pierre Béland
mailto:pierz...@yahoo.fr>> wrote:
>
> Marek
>
> Ces instructions ne s'appliquent pas à toutes les
provinces. Il faudrait donc indiquer sur la page wiki à
quelles provinces elles s'appliquent
>
> Pierre
>
> Envoyé à partir de Yahoo Courriel sur Android
>
> Le lun., sept. 9 2019 à 2:51 AM, Jarek Piórkowski
> mailto:ja...@piorkowski.ca>> a écrit :
> Hello,
>
> I'm following up on the thread about saints and lack
thereof in street
> names from a couple of months ago (see archives [1] [2]).
>
> I would like to suggest the following wording added to
Canadian
> tagging guidelines at
>

https://wiki.openstreetmap.org/wiki/Canadian_tagging_guidelines#Street_names
> :
>
>    In Ontario, street and road names containing initial
"St." or "St"
> should only be expanded to "Saint" when "Saint" is common
usage for
> that street. To be clear, this overrides the general rule
>

https://wiki.openstreetmap.org/wiki/Names#Abbreviation_.28don.27t_do_it.29
> for "St." which does not stand for "street". As with other
names in
> OSM, factors you might want to consider when determining
common usage
> include spellings posted on street signs ("on the ground"
rule),
> spellings used in local media, GeoBase street name data,
and spellings
> used by official municipal sources including open data
datasets. See
> discussion on talk-ca [0].
>
> where [0] would be a link to this message/thread archive.
(Comments on
> the wording and suggestions appreciated!)
>
> Is anyone opposed to this change?
>
> I have attempted to advertise/announce this proposed
change. This was:
> - posted in this mailing list in March/April of this year
(some quoted
> below, see list archives for more discussion)
> - I posted a note
https://www.openstreetmap.org/note/1741334 in
> Toronto with a link to this thread (supportive responses
from Kevo and
> DannyMcD)
> - on April 10, sent a message [2] with a link to the note
to editors
> who were showing up as top editors on
> http://osmstats.neis-one.org/?item=countries=Canada
> (they aren't necessarily representative of the community,
but it's
> really the closest we can reasonably do given our current
tooling) [3]
> (no private message 

Re: [Talk-ee] verbatium buiding import discussion

[Mihkel Rämmel]

Hi,
osm test server exists complete with rendering.
https://wiki.openstreetmap.org/wiki/Sandbox_for_editing

Regards,
Mihkel

On Tue, Sep 24, 2019 at 10:08 PM Jaak Laineste  wrote:
>
>
> These txt reports with IDs are not too visual, can you create any renderable 
> file for josm (.osm for example) or screenshot to show the community what it 
> really means? Are the building under question random or somehow in specific 
> areas etc.  I dont know if there is any "test osm server” for such 
> experiments nowadays somewhere, probably not.
>
> Jaak
>
> > On 24 Sep 2019, at 07:50, SviMik  wrote:
> >
> > I have analyzed the largest verbatium's import (changesets 591093, 579407, 
> > 572107, 569277, 569055 (ways) + 561094, 559707, 558636, 558056, 557568, 
> > 557358, 557193, 556899 (nodes only)), which was made in 2008. That covers 
> > 86.7% of all his edits.
> > The import was covering Tallinn, Saue and Maardu. Turned out verbatium 
> > wasn't particulary active outside Harjumaa.
> > There were total 67813 ways imported, 9032 of them are already deleted by 
> > other editors, and 17878 were changed either in geometry or tags* 
> > department (15529 has a geometry change, and 5077 has a tag change), which 
> > leaves 40903 buildings for deletion.
> > * I did not count the following tags because they are part of my imports 
> > anyway: addr:city, addr:country, addr:housenumber, addr:street, 
> > maaamet:ETAK, maaamet:orig_tunnus, source, source:addr, addr2:*
> > * If some change was reverted I do not count it as a change, because I only 
> > compare the first and the last version
> >
> > Here is the list of ways for deletion:
> > http://svimik.com/verbatium_import1_ways_unchanged1.txt
> >
> > Here is the full report for all the 67813 ways:
> > http://svimik.com/verbatium_import1_ways1.csv
> >
> > Full list of his changesets:
> > http://svimik.com/verbatium_changesets.xls
> >
> > Currently, the bbox of his changesets has 91324 buildings, which means... 
> > We're gonna delete 44.79% of Saue-Tallinn-Maardu buildings. That gonna be 
> > interesting. Should we split it by 10k for example? Or just start with 
> > Maardu and see what happens?
> >
> >
> > Воскресенье, 15 сентября 2019, 9:42 +03:00 от "Jaak Laineste" 
> > :
> >> Hoi,
> >>
> >> Jah, need peaks kustutama. Enne võiks teha muudatuse analüüsi - kui palju 
> >> ja
> >> kus kustutataks, ega mõned linnad kohe väga tühjaks ei jää.
> >>
> >> Jaak
> >>
> >> p.s. sama asi ka corine impordi osade tag-idega, näiteks põllud (field), 
> >> need
> >> on pigem müra kui info kaardil.
> >>
> >>
> >>
> >>> On 14 Sep 2019, at 15:34, SviMik via Talk-ee 
> >> wrote:
> >>>
> >>> Hi everyone!
> >>>
> >>> I'd like to discuss the import made by verbatium in 2008:
> >>> https://www.openstreetmap.org/changeset/569055
> >>> (...and other similar changesets)
> >>>
> >>> There are two issues with that import:
> >>> 1. Unknown data source with unknown license (probably it was a Garmin map
> >> judging by the Type=0x13 tag)
> >>> 2. Poor quality of the data. If you see a building distorted like this:
> >> http://svimik.com/verbatiumimport1.png
> >>> - you can be sure it's verbatium's. Maybe it was OK in 2008, but in 2019 
> >>> we
> >> have much better options.
> >>>
> >>> What can be done:
> >>> 1. Remove all buildings which geometry and tags were not edited since the
> >> initial import. For the tags the following exceptions can be made because 
> >> they
> >> were automatic edits:
> >>> - User xybot has fixed the tag typo (buildung=yes) in the initial import 
> >>> and
> >> added its own tag (created_by=xybot)
> >>> - User juhanjuku has removed the Type=0x13 and created_by=xybot tags
> >>> - User SviMik_import has imported the address tags to these buildings from
> >> the Maa-amet database (nothing that can't be imported again)
> >>> 2. Proceed with the Maa-amet building import as usual
> >>>
> >>> It will solve:
> >>> 1. The license issue (if there is any)
> >>> 2. The quality issue (if you agree there is an issue)
> >>> 3. Will update the map in general, for example the demolished buildings 
> >>> will
> >> be removed from OSM.
> >>>
> >>> For buildings which geometry was changed by other contributors after the
> >> initial import - we can assume both license and quality issues were solved
> >> since they no longer contain the imported geometry. I know it's a grey 
> >> field,
> >> and I'm not sure it works like that, but at least these buildings do have 
> >> some
> >> excuse to stay.
> >>>
> >>> For buildings which geometry was NOT changed, but some POI tags were 
> >>> added -
> >> let them stay for now and discuss it later if needed. I suspect it will be 
> >> a
> >> rare case, but the exact number is unknown right now.
> >>>
> >>> Questions:
> >>> 1. Has anyone else digged into the issue, maybe asked verbatium himself?
> >>> 2. Can anyone confirm that the import indeed has the license problem?
> >>> 3. Is the proposed plan good? (in case if you agree that it needs to be
> >> 

[Talk-GB] Overpass question: Fixmes and surroundings

[Rob Nickerson]

Hi all,

I'm trying to craft a overpass query that returns fixmes and the
surrounding OSM data. I seem to have got it working in Overpass Turbo. I
want to use this in JOSM but it's not returning all the same Ways as seen
in Overpass Turbo.

http://overpass-turbo.eu/s/Myw

Anyone able to help me please?

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

Re: [Talk-ee] verbatium buiding import discussion

[SviMik via Talk-ee]

http://svimik.com/verbatiumimportmap1.png
Here's the screenshot. Not precise, but gives some idea.
40903 buildings is a bit too much for JOSM.


Вторник, 24 сентября 2019, 22:08 +03:00 от "Jaak Laineste" :
> 
> These txt reports with IDs are not too visual, can you create any renderable
> file for josm (.osm for example) or screenshot to show the community what it
> really means? Are the building under question random or somehow in specific
> areas etc.  I dont know if there is any "test osm server” for such experiments
> nowadays somewhere, probably not. 
> 
> Jaak
> 
> > On 24 Sep 2019, at 07:50, SviMik  wrote:
> > 
> > I have analyzed the largest verbatium's import (changesets 591093, 579407,
> 572107, 569277, 569055 (ways) + 561094, 559707, 558636, 558056, 557568,
> 557358, 557193, 556899 (nodes only)), which was made in 2008. That covers
> 86.7% of all his edits.
> > The import was covering Tallinn, Saue and Maardu. Turned out verbatium
> wasn't particulary active outside Harjumaa.
> > There were total 67813 ways imported, 9032 of them are already deleted by
> other editors, and 17878 were changed either in geometry or tags* department
> (15529 has a geometry change, and 5077 has a tag change), which leaves 40903
> buildings for deletion.
> > * I did not count the following tags because they are part of my imports
> anyway: addr:city, addr:country, addr:housenumber, addr:street, maaamet:ETAK,
> maaamet:orig_tunnus, source, source:addr, addr2:*
> > * If some change was reverted I do not count it as a change, because I only
> compare the first and the last version
> > 
> > Here is the list of ways for deletion:
> > http://svimik.com/verbatium_import1_ways_unchanged1.txt
> > 
> > Here is the full report for all the 67813 ways:
> > http://svimik.com/verbatium_import1_ways1.csv
> > 
> > Full list of his changesets:
> > http://svimik.com/verbatium_changesets.xls
> > 
> > Currently, the bbox of his changesets has 91324 buildings, which means...
> We're gonna delete 44.79% of Saue-Tallinn-Maardu buildings. That gonna be
> interesting. Should we split it by 10k for example? Or just start with Maardu
> and see what happens?
> > 
> > 
> > Воскресенье, 15 сентября 2019, 9:42 +03:00 от "Jaak Laineste"
> :
> >> Hoi,
> >> 
> >> Jah, need peaks kustutama. Enne võiks teha muudatuse analüüsi - kui palju
> ja
> >> kus kustutataks, ega mõned linnad kohe väga tühjaks ei jää.
> >> 
> >> Jaak 
> >> 
> >> p.s. sama asi ka corine impordi osade tag-idega, näiteks põllud (field),
> need
> >> on pigem müra kui info kaardil.
> >> 
> >> 
> >> 
> >>> On 14 Sep 2019, at 15:34, SviMik via Talk-ee 
> >> wrote:
> >>> 
> >>> Hi everyone!
> >>> 
> >>> I'd like to discuss the import made by verbatium in 2008:
> >>> https://www.openstreetmap.org/changeset/569055
> >>> (...and other similar changesets)
> >>> 
> >>> There are two issues with that import:
> >>> 1. Unknown data source with unknown license (probably it was a Garmin map
> >> judging by the Type=0x13 tag)
> >>> 2. Poor quality of the data. If you see a building distorted like this:
> >> http://svimik.com/verbatiumimport1.png
> >>> - you can be sure it's verbatium's. Maybe it was OK in 2008, but in 2019
> we
> >> have much better options.
> >>> 
> >>> What can be done:
> >>> 1. Remove all buildings which geometry and tags were not edited since the
> >> initial import. For the tags the following exceptions can be made because
> they
> >> were automatic edits:
> >>> - User xybot has fixed the tag typo (buildung=yes) in the initial import
> and
> >> added its own tag (created_by=xybot)
> >>> - User juhanjuku has removed the Type=0x13 and created_by=xybot tags
> >>> - User SviMik_import has imported the address tags to these buildings from
> >> the Maa-amet database (nothing that can't be imported again)
> >>> 2. Proceed with the Maa-amet building import as usual
> >>> 
> >>> It will solve:
> >>> 1. The license issue (if there is any)
> >>> 2. The quality issue (if you agree there is an issue)
> >>> 3. Will update the map in general, for example the demolished buildings
> will
> >> be removed from OSM.
> >>> 
> >>> For buildings which geometry was changed by other contributors after the
> >> initial import - we can assume both license and quality issues were solved
> >> since they no longer contain the imported geometry. I know it's a grey
> field,
> >> and I'm not sure it works like that, but at least these buildings do have
> some
> >> excuse to stay.
> >>> 
> >>> For buildings which geometry was NOT changed, but some POI tags were added
> -
> >> let them stay for now and discuss it later if needed. I suspect it will be
> a
> >> rare case, but the exact number is unknown right now.
> >>> 
> >>> Questions:
> >>> 1. Has anyone else digged into the issue, maybe asked verbatium himself?
> >>> 2. Can anyone confirm that the import indeed has the license problem?
> >>> 3. Is the proposed plan good? (in case if you agree that it needs to be
> >> fixed)
> >>> 
> >>> -- 
> >>> SviMik
> >>> 

[OSM-talk-fr] qui sont ces internautes qui cartographie la Corée du Nod sur OSM

[thevenon . julien]

Un article de Numérama

https://www.numerama.com/politique/550269-qui-sont-ces-internautes-qui-cartographient-la-coree-du-nord-sur-openstreetmap.html

Julien

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

Re: [Talk-GB] Subject: Re: Thomas Cook shops

[Philip Barnes]

I am inclined to go with disused:shop to indicate it is no longer a  travel 
agent, but leave the name as it is likely to remain a landmark for sometime.

Our local Toys'R'Us has only recently lost its branding.

Also being careful not to remove his statue from outside Leicester railway  
station, or any other objects named after Leicester's famous son. 

Phil (trigpoint)


On Tuesday, 24 September 2019, Frederik Ramm wrote:
> Hi,
> 
> On 24.09.19 16:42, Dave F via Talk-GB wrote:
> > Something has happened. The company went into liquidation (not
> > administration under which, I believe, they could still operate) & the
> > shops have closed.
> 
> If you walk past your local shop and they are closed, by all means
> delete them or replace with "disused:shop" or "shop=vacant" if you want.
> (Though, if my local chippie had just closed yesterday and there was a
> rumour of someone else taking over the business next week I might be
> tempted to tolerate the incorrectness for a little while.)
> 
> Just don't take the lawnmower over the database and assume that
> everything that is called Thomas Cook is now closed without even looking ;)
> 
> Bye
> Frederik
> 
> -- 
> Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09" E008°23'33"
> 
> ___
> Talk-GB mailing list
> Talk-GB@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-gb
>

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

Wochennotiz Nr. 478 10.09.2019–16.09.2019

[Wochennotizteam]

Hallo,

die Wochennotiz Nr. 478 mit vielen wichtigen Neuigkeiten aus der
OpenStreetMap-Welt ist da:

http://blog.openstreetmap.de/blog/2019/09/wochennotiz-nr-478/

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

Viel Spaß beim Lesen

Euer Wochennotizteam
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de

Re: [Talk-ee] verbatium buiding import discussion

[Jaak Laineste]

These txt reports with IDs are not too visual, can you create any renderable 
file for josm (.osm for example) or screenshot to show the community what it 
really means? Are the building under question random or somehow in specific 
areas etc.  I dont know if there is any "test osm server” for such experiments 
nowadays somewhere, probably not. 

Jaak

> On 24 Sep 2019, at 07:50, SviMik  wrote:
> 
> I have analyzed the largest verbatium's import (changesets 591093, 579407, 
> 572107, 569277, 569055 (ways) + 561094, 559707, 558636, 558056, 557568, 
> 557358, 557193, 556899 (nodes only)), which was made in 2008. That covers 
> 86.7% of all his edits.
> The import was covering Tallinn, Saue and Maardu. Turned out verbatium wasn't 
> particulary active outside Harjumaa.
> There were total 67813 ways imported, 9032 of them are already deleted by 
> other editors, and 17878 were changed either in geometry or tags* department 
> (15529 has a geometry change, and 5077 has a tag change), which leaves 40903 
> buildings for deletion.
> * I did not count the following tags because they are part of my imports 
> anyway: addr:city, addr:country, addr:housenumber, addr:street, maaamet:ETAK, 
> maaamet:orig_tunnus, source, source:addr, addr2:*
> * If some change was reverted I do not count it as a change, because I only 
> compare the first and the last version
> 
> Here is the list of ways for deletion:
> http://svimik.com/verbatium_import1_ways_unchanged1.txt
> 
> Here is the full report for all the 67813 ways:
> http://svimik.com/verbatium_import1_ways1.csv
> 
> Full list of his changesets:
> http://svimik.com/verbatium_changesets.xls
> 
> Currently, the bbox of his changesets has 91324 buildings, which means... 
> We're gonna delete 44.79% of Saue-Tallinn-Maardu buildings. That gonna be 
> interesting. Should we split it by 10k for example? Or just start with Maardu 
> and see what happens?
> 
> 
> Воскресенье, 15 сентября 2019, 9:42 +03:00 от "Jaak Laineste" 
> :
>> Hoi,
>> 
>> Jah, need peaks kustutama. Enne võiks teha muudatuse analüüsi - kui palju ja
>> kus kustutataks, ega mõned linnad kohe väga tühjaks ei jää.
>> 
>> Jaak 
>> 
>> p.s. sama asi ka corine impordi osade tag-idega, näiteks põllud (field), need
>> on pigem müra kui info kaardil.
>> 
>> 
>> 
>>> On 14 Sep 2019, at 15:34, SviMik via Talk-ee 
>> wrote:
>>> 
>>> Hi everyone!
>>> 
>>> I'd like to discuss the import made by verbatium in 2008:
>>> https://www.openstreetmap.org/changeset/569055
>>> (...and other similar changesets)
>>> 
>>> There are two issues with that import:
>>> 1. Unknown data source with unknown license (probably it was a Garmin map
>> judging by the Type=0x13 tag)
>>> 2. Poor quality of the data. If you see a building distorted like this:
>> http://svimik.com/verbatiumimport1.png
>>> - you can be sure it's verbatium's. Maybe it was OK in 2008, but in 2019 we
>> have much better options.
>>> 
>>> What can be done:
>>> 1. Remove all buildings which geometry and tags were not edited since the
>> initial import. For the tags the following exceptions can be made because 
>> they
>> were automatic edits:
>>> - User xybot has fixed the tag typo (buildung=yes) in the initial import and
>> added its own tag (created_by=xybot)
>>> - User juhanjuku has removed the Type=0x13 and created_by=xybot tags
>>> - User SviMik_import has imported the address tags to these buildings from
>> the Maa-amet database (nothing that can't be imported again)
>>> 2. Proceed with the Maa-amet building import as usual
>>> 
>>> It will solve:
>>> 1. The license issue (if there is any)
>>> 2. The quality issue (if you agree there is an issue)
>>> 3. Will update the map in general, for example the demolished buildings will
>> be removed from OSM.
>>> 
>>> For buildings which geometry was changed by other contributors after the
>> initial import - we can assume both license and quality issues were solved
>> since they no longer contain the imported geometry. I know it's a grey field,
>> and I'm not sure it works like that, but at least these buildings do have 
>> some
>> excuse to stay.
>>> 
>>> For buildings which geometry was NOT changed, but some POI tags were added -
>> let them stay for now and discuss it later if needed. I suspect it will be a
>> rare case, but the exact number is unknown right now.
>>> 
>>> Questions:
>>> 1. Has anyone else digged into the issue, maybe asked verbatium himself?
>>> 2. Can anyone confirm that the import indeed has the license problem?
>>> 3. Is the proposed plan good? (in case if you agree that it needs to be
>> fixed)
>>> 
>>> -- 
>>> SviMik
>>> ___
>>> Talk-ee mailing list
>>> Talk-ee@openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/talk-ee
>> 
>> 
> 
> 
> -- 
> Svjatoslav Mikhailov


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

[Talk-hr] Javni prijevoz u Zagrebu

[Ivan Habunek]

Bok!

Pokrenuo sam neki pet projekt  koji koristi osm podatke o javnom prijevozu pa 
malo gledam koje je stanje i nalazim dosta zbrke, pa bih volio mišljenje malo 
iskusnijih prije nego što krenem u veće zahvate.

Evo na primjeru autobusa 109, Črnomerec - Dugave.

Prvo sam potražio što kažu wiki stranice: 
https://wiki.openstreetmap.org/wiki/WikiProject_Croatia/Javni_prijevoz#Zagreb

Tu je navedena samo jedna relacija, ali to je samo jedan smjer:
https://www.openstreetmap.org/relation/145956

Pregledavanjem karte, našao sam i suprotan smjer koji nije u wikiju:
https://www.openstreetmap.org/relation/2104525

I također sam našao još jednu relaciju koja mapira rutu u oba smjera:
https://www.openstreetmap.org/relation/6061416

Da li je poželjno imati 2 relacije za rute javnog prijevoza? Vidio sam da sve 
tramvajske linije imaju odvojene relacije za svaki smjer.

Je li ok obrisati 6061416 i ostaviti samo starije relacije? Treba ih malo 
popraviti, fali dio rute oko rotora.

Uglavnom, bio bih voljan uložiti nešto truda oko podataka i wikija, ali ne 
želim nikome gaziti po prstima u procesu.

Pozdrav,
-- Ivan

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

Re: [Talk-it] tagliare osm.pbf con bounding box

[Alessandro P. via Talk-it]

Il 24/09/19 18:10, Roberto Brazzelli ha scritto:

Ciao,
qualche consiglio per tagliare i dati osm.pbf
con un'area data da coordinate geografiche?



Ciao,
se hai la fortuna di lavorare con una macchina Linux, io stravedo per Osmium

https://osmcode.org/osmium-tool/
https://osmcode.org/osmium-tool/manual.html

con una macchina ben attrezzata dall'intero planet ho estratto categorie 
di oggetti in una trentina di minuti.


Alessandro

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

Re: [OSM-talk-fr] CyclOSM, rendu cyclable libre

[Axel Listes]

Bonsoir,

Le 23/09/2019 à 10:41, Florimond Berthoux a écrit :
> Merci pour les remarques, mes réponses :
> Pour les chemins partagés piéton/vélo (voies vertes, pistes sur trottoir),
> tu as raison et c'est la prochaine chose que j'aimerai améliorer.
> Les rendre plus grosse et avec une couleur vélo friendly.

Dans le même genre, les chemins piétons qui ne sont équipés d'aucune
balise d'indication que les vélos peuvent y circuler sont trop mis en
évidence, ça prête à confusion.

Dans l'ensemble, le travail est remarquable :)

Axel.

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

Re: [OSM-talk-fr] CyclOSM, rendu cyclable libre

[osm . sanspourriel]

non, non c'était dev.{s}, donc s=a|b|c comme d'habitude et ça donne le
lien que tu mets en exemple.

Bref, si Viking se comporte comme les autres services, tu laisses {s},
il remplacera normalement.

Et si ça ne marche pas tu mets a ou b ou c.

Jean-Yvon

Le 24/09/2019 à 18:59, Yves P. - yves.prat...@gmail.com a écrit :




J'essaie de faire apparaître la carte dans Viking, mais que faut-il
mettre à la place de {s} ?

En général c’est *a*, *b* ou *c* mais ici, c’est *dev.a*, *dev.b* ou
*dev.c*

https://dev.a.tile.openstreetmap.fr/cyclosm/15/16917/11580.png

—
Yves


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

Re: [Talk-de] Telegram Gruppe Hamburg

[bergaufsee via Talk-de]

Hallo,

ich weiß daß Telegram hier sehr verbreitet ist. Da OSM eine freie
Alternative zu anderen Kartendiensten darstellt, bevorzuge ich auch bei
der Kommunikation freie Alternativen. Daher habe ich auch vor wenigen
Monaten für Berlin-Brandenburg einen Jabber/XMPP-MUC (Multi User Chat)
eingerichtet, erreichbar z.B. unter
https://conversations.im/j/osm...@rooms.dismail.de . Da es derzeit der
einzige deutschsprachige OSM-Raum ist, sind natürlich auch interessierte
Leute aus anderen Regionen herzlich eingeladen, einen Abstecher in die
XMPP Welt zu wagen, möglicherweise hat ja auch der ein oder andere noch
einen Jabber Account, das Protokoll gibt es ja schließlich schon 20
Jahre und es hat sich hier mittlerweile viel getan. Infos gibt es u.a.
auch unter https://www.freie-messenger.de/ , hier gibt es z.B. auch
unter https://www.freie-messenger.de/warum/warumnicht/ eine Übersicht
mit den Nachteilen diverser Alternativen.

Schöne Grüße

Bernd


Am 24.09.19 um 17:20 schrieb Martin Scholtes:
> Hallo zusammen,
>
> seit heute haben wir für Hamburg und Umgebung eine eigene Telegram Gruppe.
> Beitritts Link ist dieser hier: https://t.me/osm_de_hh
>
> Gruß
> Martin
>
>
>
> ___
> Talk-de mailing list
> Talk-de@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-de
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de

Re: [talk-cz] SotM deníček - den třetí

[Marián Kyral]

Dne 24. 09. 19 v 13:59 Petr Vozdecký napsal(a):


pokud mi skleroza slouzi tohle se tu uz kdysi probiralo, a
minimalne v
podminkach CR to nemuze fungovat. Jednoduse proto, ze temi body by z
logiky veci byly zastavky, a hledat muzes tak maximalne nejkratsi
nebo
"nejrychlejsi" trasu, ale to neni vzdy ta, po ktere MHD realne jezdi.
Pokud bys pridaval nejake "pomocne" body nekde na trase, tak by to
byl
prozmenu velmi brzo nehoraznej bordel. Pricemz cim podrobneji budes
mapovat (jizdni pruhy, konkretni mista zastaveni na nadrazich ...)
tim
horsi.


+1!

Jina vec jepochopitelne to, ze ty trasy nejsou zrovna aktualni, a
jejich
aktualizace je vopruz. To je podle me ale dano spis tim, ze
neexistuje
vhodny nastroj. Ten by se podle me mel chovat podobne jako navigace -
reknu odkud a kam, a on spocita nejakou trasu, kterou pak muzu
modifikovat a rovnou nabidne pridat/upravit zastavky po trase -
vcetne
prace s relacemi zastavek atd.


Království za takovou funkcionalitu! Vytváření relací liniových tras 
poloautomatickým výběrem. Zobrazím si podkladový render dle potřeby, 
zvolím si do vrstvy nad tím zobrazení vyfiltrovaných OSM dat (jen 
prvky s konkrétními parametry jako třeba linie: highway=track; body: 
tourism=information; pak manuálně "vyzobnu" koncové body (třeba 
koncové linie), funkcionalita to "vyroutuje" a já postupným přidávání 
zpřesňujících úseků docílím vydefinování celé trasy. Pak k tomu můžu 
přidat potřebné body...


To je krásná představa - muselo by to ale být schopno v případě 
potřeby rozdělit linii v OSM datech na více úseků...



Taky by se mi to líbilo. Teď už jen drobnost. Kdo to naprogramuje?

Tohle je na mě už docela komplikované :-(


Marián


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

Re: [OSM-talk-fr] CyclOSM, rendu cyclable libre

[Yves P.]

> 
> J'essaie de faire apparaître la carte dans Viking, mais que faut-il mettre à 
> la place de {s} ?
En général c’est a, b ou c mais ici, c’est dev.a, dev.b ou dev.c

https://dev.a.tile.openstreetmap.fr/cyclosm/15/16917/11580.png

—
Yves

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

Re: [Talk-it] tagliare osm.pbf con bounding box

[Stefano]

Ciao,
Osmosis è lo strumento più flessibile (fa anche altro)
https://wiki.openstreetmap.org/wiki/Osmosis

Stefano

On Tue, 24 Sep 2019, 18:11 Roberto Brazzelli, 
wrote:

> Ciao,
> qualche consiglio per tagliare i dati osm.pbf
> con un'area data da coordinate geografiche?
>
> grazie
> roberto
>
>
> ___
> 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] tagliare osm.pbf con bounding box

[Roberto Brazzelli]

Ciao,
qualche consiglio per tagliare i dati osm.pbf
con un'area data da coordinate geografiche?

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

Re: [Talk-it] Masso erratico

[liste DOT girarsi AT posteo DOT eu]

Il 24/09/19 12:08, demon_box ha scritto:
> ciao devo mappare un masso erratico che ha un nome proprio "Balòta dela al di
> Precc" quindi faccio
> 
> natural=stone
> name=Balòta dela al di Precc
> 
> c'è qualche altro tag che potrei aggiungere per indicare che non è un
> semplice masso ma è appunto un "masso erratico"?
> 
> grazie
> 

Su taginfo risultano due occorrenze con stone_type=glacial__erratic, che
io trasformerei per via dei namespace in stone:type_glacial_erratic.


https://taginfo.openstreetmap.org/tags/stone_type=glacial_erratic



Il masso erratico vedendo su wikipedia in italiano, diventa quanto
sopra, cliccando sulla rispettiva lingua inglese.


https://en.wikipedia.org/wiki/Glacial_erratic


In sostanza rocce/massi erratici sono stati trasportati da un ghiacciaio
tanto tempo fa.


-- 
_|_|_|_|_|_|_|_|_|_
|_|_|_|_|_|_|_|_|_|_|
Simone Girardelli

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

Re: [Talk-GB] Next quarters project will be fixmes and notes

[Silent Spike]

On Tue, Sep 24, 2019 at 3:38 PM Peter Neale  wrote:

> Thank you for trying to help me, but I am still confused (I'm getting used
> to that feeling!)
>
> Clearly I am missing something??
>

In your second screenshot, on the right hand toolbar, the icon ("Map Data")
underneath the "Background settings" one which you have selected. It will
open the Data panel (also shortcut F) which has "Data Layers" that can be
enabled - one of them is Notes.

I should clarify that until you hit "Edit" on the OSM website you're not
actually in the iD editor. The layers available before entering the editor
are part of the website itself, which is maintained by separately.
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [OSM-talk-fr] CyclOSM, rendu cyclable libre

[François]

Le 21/09/2019 à 07:52, Phyks a écrit :

Les tuiles générées
par OSM-FR sont disponibles sur
https://dev.{s}.tile.openstreetmap.fr/cyclosm/{z}/{x}/{y}.png.


Bonjour,
J'essaie de faire apparaître la carte dans Viking, mais que faut-il 
mettre à la place de {s} ?


--
François


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

Re: [Talk-GB] Subject: Re: Thomas Cook shops

[Dave F via Talk-GB]

My OP should indicate I'm aware of variants.
There's the head office, which I believe is still functioning as a part 
of Matterhorn, a bus stop & a statue


DaveF

On 24/09/2019 15:44, Frederik Ramm wrote:


Just don't take the lawnmower over the database and assume that
everything that is called Thomas Cook is now closed without even looking ;)





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

[Talk-de] Telegram Gruppe Hamburg

[Martin Scholtes]

Hallo zusammen,

seit heute haben wir für Hamburg und Umgebung eine eigene Telegram Gruppe.
Beitritts Link ist dieser hier: https://t.me/osm_de_hh

Gruß
Martin


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

Re: [Talk-ee] Maa-amet Tase 6 (maaüksuse nimi) – addr:place või addr:housename?

[Jaak Laineste]

There is a wiki page: https://wiki.openstreetmap.org/wiki/Et:Key:addr ., I 
think it is basically tase 5: housename, tase 6: housenumber if I get the 
question right.

Feel free to enhance the wiki page, not everyone reads talk-ee, but wiki is 
more official doc :)


Jaak


> On 24 Sep 2019, at 17:51, SviMik via Talk-ee  
> wrote:
> 
> Hi all,
> 
> I have a tagging puzzle here. Maa-amet classifies address parts in the 
> following way:
> 
> Tase 3 – asustusüksus ja linnaosa
> Tase 4 – väikekoht
> Tase 5 – liikluspind (tänav)
> Tase 6 – maaüksuse nimi
> Tase 7 – aadressi number
> 
> The problem is, that many buildings in Estonia do not have Tase 5 (street 
> name), but instead have Tase 6 (lot name) and may or may not have Tase 7 
> (housenumber) at the same time.
> 
> According to OSM wiki, addr:place is "part of an address which refers to the 
> name of some territorial zone".
> Looks perfect so far, "the name of some territorial zone" is literally 
> "maaüksuse nimi".
> But...
> 1. addr:place requires place=* node or area to be mapped too, which is not 
> really doable for every land lot.
> 2. I'm already using addr:place for Tase 4 (väikekoht, aiandusühistu, etc) 
> which fits better for this role.
> 
> We could use addr:housename for this instead.
> Indeed, Tase 6 is often used as a replacement for the street+number scheme, 
> and in most cases is literally the property name.
> But...
> 1. Sometimes Tase 6 comes with Tase 7 (housenumber). I'm not sure if 
> addr:housename can be used together with addr:housenumber, the addr:housename 
> sounds like it must be the final address part.
> 
> Examples with house number:
> 
> Harju maakond;Kuusalu vald;Leesi küla;Kasemäe;1
> Harju maakond;Kuusalu vald;Leesi küla;Kasemäe;2
> - here Kasemäe is tase6, not street (tase5), but it still uses house 
> numbering. This example looks like addr:place.
> 
> Lääne-Viru maakond;Kadrina vald;Arbavere küla;Palkoja baas
> Harju maakond;Kuusalu vald;Vihasoo küla;Pumbamaja
> Harju maakond;Anija vald;Härmakosu küla;Härmakosu tehnopark
> - here the last part is tase6 too. They don't have house numbers, and these 
> examles do look like addr:housename.
> 
> So, the questions is: where exactly do I put the Maa-amet "Tase 6" address 
> part in OSM tagging scheme?
> And is it OK to use addr:housename together with addr:housenumber?
> 
> --
> SviMik
> ___
> Talk-ee mailing list
> Talk-ee@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ee


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

[Talk-ee] Maa-amet Tase 6 (maaüksuse nimi) – addr:place või addr:housename?

[SviMik via Talk-ee]

Hi all,

I have a tagging puzzle here. Maa-amet classifies address parts in the 
following way:

Tase 3 – asustusüksus ja linnaosa
Tase 4 – väikekoht
Tase 5 – liikluspind (tänav)
Tase 6 – maaüksuse nimi
Tase 7 – aadressi number

The problem is, that many buildings in Estonia do not have Tase 5 (street 
name), but instead have Tase 6 (lot name) and may or may not have Tase 7 
(housenumber) at the same time.

According to OSM wiki, addr:place is "part of an address which refers to the 
name of some territorial zone".
Looks perfect so far, "the name of some territorial zone" is literally 
"maaüksuse nimi".
But...
1. addr:place requires place=* node or area to be mapped too, which is not 
really doable for every land lot.
2. I'm already using addr:place for Tase 4 (väikekoht, aiandusühistu, etc) 
which fits better for this role.

We could use addr:housename for this instead.
Indeed, Tase 6 is often used as a replacement for the street+number scheme, and 
in most cases is literally the property name.
But...
1. Sometimes Tase 6 comes with Tase 7 (housenumber). I'm not sure if 
addr:housename can be used together with addr:housenumber, the addr:housename 
sounds like it must be the final address part.

Examples with house number:

Harju maakond;Kuusalu vald;Leesi küla;Kasemäe;1
Harju maakond;Kuusalu vald;Leesi küla;Kasemäe;2
- here Kasemäe is tase6, not street (tase5), but it still uses house numbering. 
This example looks like addr:place.

Lääne-Viru maakond;Kadrina vald;Arbavere küla;Palkoja baas
Harju maakond;Kuusalu vald;Vihasoo küla;Pumbamaja
Harju maakond;Anija vald;Härmakosu küla;Härmakosu tehnopark
- here the last part is tase6 too. They don't have house numbers, and these 
examles do look like addr:housename.

So, the questions is: where exactly do I put the Maa-amet "Tase 6" address part 
in OSM tagging scheme?
And is it OK to use addr:housename together with addr:housenumber?

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

Re: [Talk-GB] Subject: Re: Thomas Cook shops

[Frederik Ramm]

Hi,

On 24.09.19 16:42, Dave F via Talk-GB wrote:
> Something has happened. The company went into liquidation (not
> administration under which, I believe, they could still operate) & the
> shops have closed.

If you walk past your local shop and they are closed, by all means
delete them or replace with "disused:shop" or "shop=vacant" if you want.
(Though, if my local chippie had just closed yesterday and there was a
rumour of someone else taking over the business next week I might be
tempted to tolerate the incorrectness for a little while.)

Just don't take the lawnmower over the database and assume that
everything that is called Thomas Cook is now closed without even looking ;)

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09" E008°23'33"

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

Re: [Talk-GB] Subject: Re: Thomas Cook shops

[Dave F via Talk-GB]

Something has happened. The company went into liquidation (not 
administration under which, I believe, they could still operate) & the 
shops have closed.


If your local chippy closed would you leave it mapped as still open for 
business?


On 24/09/2019 14:47, Chris Hill wrote:
Thomas Cook shops are not vacant. They may not be open to the public 
today, but they may well be reopened by a new owner in the future and 
that may even be under the Thomas Cook brand if the administrator 
sells some or all of them to another company. In the mean time they 
are still branded and still a landmark of sorts.


If a shop is emptied or reused by another firm then change that one 
otherwise I think we should wait for a while to see what happens.


cheers
Chris Hill (chillly)

On 24/09/2019 14:00, Jez Nicholson wrote:

I'm a fan of shop=vacant, old_name=Thomas Cook myself

You could argue for not:name=Thomas Cook maybe

On Tue, 24 Sep 2019, 13:34 Tadeusz Cantwell, > wrote:


    I changed the three shops in N.I to disused;shop=travel-agent
    since I wasn't sure what the best practice was in this case. Not
    all of them had the wiki links etc. Any advice on a better way?






___
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] mapbox, (Changeset Analyzer), whodidit

[john whelan]

I think the problem has been resolved.  There was a misunderstanding on
which tags should be used for which values.

Strangely enough bus stops and bus routes are quite specialised and it
isn't always apparent how they should be tagged especially with the newer
platform tags.

Cheerio John

On Tue, 24 Sep 2019, 5:01 am Mateusz Konieczny, 
wrote:

>
> 24 Sep 2019, 04:42 by talk@openstreetmap.org:
>
> and will not let anyone else add – edit to that category.
>
> Is (s)he making incorrect edits or rude
> changeset comments?
>
> Have you commented in their
> changeset with explanation that it is a problem?
>
> Can you link such changeset comments?
> ___
> 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-cz] Chyby RUIAN, jak na opravy a reklamace

[Vladimír Slávik]

Ahoj,
myslím že mi nezbývá nic :) Díky!

Pokud mohu nějak pomoct s tím stavem wiki, dej(te?) vědět, ale asi o tom 
nevím dost na to abych to přepisoval, spíš bych to celé vyházel a napsal 
znova to co je pro mě jako bfu zajímavé... což nevím jestli je přijatelné.


V.


Dne 21.9.2019 v 0:05 Jan Macura napsal(a):

Ahoj,

dík za odkazy. Označil jsem ty prehistorické stránky za zastaralé. Je 
otázka, asi hlavně na jejich původní autory, zda už nejsou zralé úplně 
ke smazání, aby nemátly případné nové čtenáře. Stránku RÚIAN jsem 
lehce aktualizoval.


Zbývají ještě nějaké otázky k zodpovězení? :-)

H.

On Fri, 20 Sep 2019 at 18:11, Vladimír Slávik 
mailto:slavik.vladi...@seznam.cz>> wrote:


Ahoj, díky, PointInfo je skutečně odpověď na skoro vše!

Pokud jde o wiki,

https://wiki.openstreetmap.org/wiki/Cs:R%C3%9AIAN#Nalezen.C3.A9_chyby_v_R.C3.9AIAN
je naprosto zavádějící - neříká nic o PointInfo, ale zato zmiňuje
stránku https://wiki.openstreetmap.org/wiki/Cs:RUIAN/chyby , což
je ta prehistorie. Mimo to je tam ještě i
https://wiki.openstreetmap.org/wiki/Cs:RUIAN/nove_budovy .

Díky!
V.


Dne 19.9.2019 v 16:50 Jan Macura napsal(a):

Ahoj,

myslím, že odpověď ad 2 je stáhnout si do JOSM doplněk PointInfo.
Návod na wiki je "lehce" zastaralý, ale obecně platný:

https://wiki.openstreetmap.org/wiki/Cs:R%C3%9AIAN#PointInfo_-_dopln.C4.9Bk_JOSM

Jinak můžeš pls dát odkaz na "nějaký seznam na wiki, který je tři
roky nehnutý"? Hnul bych s ním. Díky.

H.

On Thu, 19 Sep 2019 at 10:22, Vladimír Slávik
mailto:slavik.vladi...@seznam.cz>> wrote:

Ahoj,
brodím se jednou vesnicí (Dolní Újezd, Svitavy) kde zřejmě
proběhlo
nějaké to tracerováníčko od německých přátel a tak. Není to
až tak
hrozné, ale leccos nesouhlasí s realitou. Tak mám pár dotazů...

1) Jak vlastně určím co je skutečný stav? Mám v JOSM stažené
data, mám
zapnutou vrstvu z poloha.net . Vidím něco
co není budova, vedle zase pro
změnu chybí kus budovy, a třetí je křivá. Stav dat OSM
odpovídá té
vrstvě z poloha.net . Ale když si vezmu to
RUIAN ID co máme v OSM a jdu
hlásit chybu přes formulář, otevře se mi úplně jiný stavební
objekt.
Takže je to asi blbě celé na entou. Co s tím?

2) Nejsem schopný dohledat žádné vodítko komu a jak hlásit
chyby,
ačkoliv tady diskuse v minulosti proběhla. Oficiální
formuláře vidím.
Pak je ta věc na poloha.net , kde vůbec
netuším co to je a co to dělá
(návod?) a jak se přidat do toho zřejmě seznamu lidí co můžou
hlásit
chyby. No a ještě je nějaký seznam na wiki, který je tři roky
nehnutý.

Kacířská myšlenka - když mají v digitálu tak každý dvanáctý
dům, a z
toho skoro všechny blbě, tak se nebudu obtěžovat úřední
fikcí. To by
bylo totiž třeba nahlásit celou vesnici :D Kde je to
tragické, smažu
ruianové tagy, ať to jde do... pozadí... a upravím správně
podle KM a
satelitu. Názory? A bonus, jak zamezit náletu klikacích
kobylek když se
za chvíli objeví v nějakém feedu že se tam dá něco naklikat?

(Jo, miluju to celé k sežrání... ale to je asi dostatečně známo.)

VS


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


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



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


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



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

Re: [Talk-GB] Next quarters project will be fixmes and notes

[Silent Spike]

On Tue, Sep 24, 2019 at 2:40 PM Peter Neale via Talk-GB <
talk-gb@openstreetmap.org> wrote:

> Could this be changed to make all open Notes appear in the iD Edit
> window?  How could I request it?
>

There is an option to show notes under the data panel in the iD editor
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb

Re: [Talk-GB] Subject: Re: Thomas Cook shops

[Chris Hill]

Thomas Cook shops are not vacant. They may not be open to the public 
today, but they may well be reopened by a new owner in the future and 
that may even be under the Thomas Cook brand if the administrator sells 
some or all of them to another company. In the mean time they are still 
branded and still a landmark of sorts.


If a shop is emptied or reused by another firm then change that one 
otherwise I think we should wait for a while to see what happens.


cheers
Chris Hill (chillly)

On 24/09/2019 14:00, Jez Nicholson wrote:

I'm a fan of shop=vacant, old_name=Thomas Cook myself

You could argue for not:name=Thomas Cook maybe

On Tue, 24 Sep 2019, 13:34 Tadeusz Cantwell, > wrote:


I changed the three shops in N.I to disused;shop=travel-agent
since I wasn't sure what the best practice was in this case. Not
all of them had the wiki links etc. Any advice on a better way?


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

Re: [Talk-GB] Subject: Re: Thomas Cook shops

[Dave F via Talk-GB]

Re: shop=vacant. This is a popular alternative tag, but removes the 
previous usage from the latest version. I found knowing this helpful 
when a new shop replaces it - "There's a new café opening in what used 
to be the flower shop"

How is the name tag dealt with if disused: isn't used?

Tony.
If the shops are closed tagging them as such improves the quality of the 
database. If they are bought out lock, stock & barrel a mass swap over 
edit can be easily executed.


Cheers
Davef

On 24/09/2019 14:20, Tony OSM wrote:
I think this is all premature. The shops still have the branding, they 
could be taken over by a new company operating as Thomas Cook. I Think 
that nothing should be done until there is greater clarity.


Tony Shield

TonyS999

On 24/09/2019 14:10, Tadeusz Cantwell wrote:
Thanks, I have used once shop=vacant before, now that you mention it. 
Will read up on the wiki to see the different intended uses for them. 
The old_name is an interesting option.


On Tue, 24 Sep 2019 at 14:00, Jez Nicholson > wrote:


    I'm a fan of shop=vacant, old_name=Thomas Cook myself

    You could argue for not:name=Thomas Cook maybe

    On Tue, 24 Sep 2019, 13:34 Tadeusz Cantwell, mailto:t4d...@gmail.com>> wrote:

    I changed the three shops in N.I to disused;shop=travel-agent
    since I wasn't sure what the best practice was in this case.
    Not all of them had the wiki links etc. Any advice on a better
    way?

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




___
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] Next quarters project will be fixmes and notes

[Peter Neale via Talk-GB]

I too have encountered a number of Notes that have been addressed, but not 
formally "Resolved".  (e.g. the name of a business marked on a building that 
now has that name tagged)  I surmise that this is because (in the iD editor, at 
least) the Notes are not visible when in Edit mode, so the mapper adding the 
business name may be unaware that someone else has created a Note, suggesting a 
name.
Could this be changed to make all open Notes appear in the iD Edit window?  How 
could I request it?
Regards,Peter

 

On Tuesday, 24 September 2019, 13:56:09 BST, Tom Hukins  
wrote:  
 
 On Tue, Sep 24, 2019 at 01:24:49PM +0100, Michael Booth wrote:
> Think there should also be an effort to open notes for some fixmes which 
> require a survey, as many go unnoticed.

I'm not an extremely active mapper, but I often encounter fixmes that
have already been fixed and notes that have already been dealt with, but
the note or fixme remains open.

It's easy enough to close the note, or delete the fixme, but the risk of
the duplication you suggest is that mappers need to edit more stale
information as time passes.

If mappers follow the approach you suggest, it would be very helpful to
ensure the new notes refer to the existing fixmes, and the fixmes are
edited to refer to the new notes.

Tom

___
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] Subject: Re: Thomas Cook shops

[Tadeusz Cantwell]

Thanks, I have used once shop=vacant before, now that you mention it. Will
read up on the wiki to see the different intended uses for them. The
old_name is an interesting option.

On Tue, 24 Sep 2019 at 14:00, Jez Nicholson  wrote:

> I'm a fan of shop=vacant, old_name=Thomas Cook myself
>
> You could argue for not:name=Thomas Cook maybe
>
> On Tue, 24 Sep 2019, 13:34 Tadeusz Cantwell,  wrote:
>
>> I changed the three shops in N.I to disused;shop=travel-agent since I
>> wasn't sure what the best practice was in this case. Not all of them had
>> the wiki links etc. Any advice on a better way?
>>
>> Tad
>> ___
>> 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] Subject: Re: Thomas Cook shops

[Jez Nicholson]

I'm a fan of shop=vacant, old_name=Thomas Cook myself

You could argue for not:name=Thomas Cook maybe

On Tue, 24 Sep 2019, 13:34 Tadeusz Cantwell,  wrote:

> I changed the three shops in N.I to disused;shop=travel-agent since I
> wasn't sure what the best practice was in this case. Not all of them had
> the wiki links etc. Any advice on a better way?
>
> Tad
> ___
> 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] Next quarters project will be fixmes and notes

[Paul Berry]

There is also this public query, courtesy of *marczoutendijk*, that you can
use for Overpass Turbo: http://overpass-turbo.eu/s/ltA

Regards,
*Paul*

On Tue, 24 Sep 2019 at 13:39, Andy Townsend  wrote:

> On 24/09/2019 13:24, Michael Booth wrote:
> > Fixmes can only be viewed in iD or with a QA tool, while notes can be
> > viewed on osm.org and StreetComplete which is useful for actually
> > going out and surveying them.
>
> If you're a Garmin user you can use
> https://github.com/SomeoneElseOSM/Notes01 from the command line to get a
> list of fixmes in a certain area.  I'm sure there are other options as
> well.
>
> Best Regards,
>
> Andy
>
>
>
> ___
> 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] Next quarters project will be fixmes and notes

[Andy Townsend]

On 24/09/2019 13:24, Michael Booth wrote:
Fixmes can only be viewed in iD or with a QA tool, while notes can be 
viewed on osm.org and StreetComplete which is useful for actually 
going out and surveying them.


If you're a Garmin user you can use 
https://github.com/SomeoneElseOSM/Notes01 from the command line to get a 
list of fixmes in a certain area.  I'm sure there are other options as well.


Best Regards,

Andy



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

Re: [Talk-GB] Next quarters project will be fixmes and notes

[Michael Booth]

Great idea.

Think there should also be an effort to open notes for some fixmes which 
require a survey, as many go unnoticed. Fixmes can only be viewed in iD 
or with a QA tool, while notes can be viewed on osm.org and 
StreetComplete which is useful for actually going out and surveying them.


Maybe a list of fixmes that haven't been edited in a few years would be 
good to review?


Found out about the NotesReview tool from Chris' talk - if you set the 
"to" date to 1/1/2014 or similar you can find some old notes in your 
area that perhaps have already been fixed or don't have useful info in 
them so can be resolved.


On 22/09/2019 14:14, Rob Nickerson wrote:

Hi all,

As we near the end of the current quarterly project (solar power) the 
time has come to announce the project for Quarter 4 2019.


By popular demand when discussing OSM UK's 2019/20 priority areas, the 
quarterly project will be fixmes and notes.


I have already made a start on the wiki page. Please update as you see 
fit:

https://wiki.openstreetmap.org/wiki/UK_2019_Q4_Project:_Fixmes_and_Notes

With best regards,
*Rob*

___
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-cz] SotM deníček - den třetí

[Petr Vozdecký]

"pokud mi skleroza slouzi tohle se tu uz kdysi probiralo, a minimalne v 
podminkach CR to nemuze fungovat. Jednoduse proto, ze temi body by z
logiky veci byly zastavky, a hledat muzes tak maximalne nejkratsi nebo
"nejrychlejsi" trasu, ale to neni vzdy ta, po ktere MHD realne jezdi.
Pokud bys pridaval nejake "pomocne" body nekde na trase, tak by to byl
prozmenu velmi brzo nehoraznej bordel. Pricemz cim podrobneji budes
mapovat (jizdni pruhy, konkretni mista zastaveni na nadrazich ...) tim
horsi."



+1!

""
 
"Jina vec jepochopitelne to, ze ty trasy nejsou zrovna aktualni, a jejich 
aktualizace je vopruz. To je podle me ale dano spis tim, ze neexistuje
vhodny nastroj. Ten by se podle me mel chovat podobne jako navigace -
reknu odkud a kam, a on spocita nejakou trasu, kterou pak muzu
modifikovat a rovnou nabidne pridat/upravit zastavky po trase - vcetne
prace s relacemi zastavek atd."



Království za takovou funkcionalitu! Vytváření relací liniových tras
poloautomatickým výběrem. Zobrazím si podkladový render dle potřeby, zvolím
si do vrstvy nad tím zobrazení vyfiltrovaných OSM dat (jen prvky s
konkrétními parametry jako třeba linie: highway=track; body: tourism=
information; pak manuálně "vyzobnu" koncové body (třeba koncové linie),
funkcionalita to "vyroutuje" a já postupným přidávání zpřesňujících úseků
docílím vydefinování celé trasy. Pak k tomu můžu přidat potřebné body...




To je krásná představa - muselo by to ale být schopno v případě potřeby
rozdělit linii v OSM datech na více úseků...
___
talk-cz mailing list
talk-cz@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-cz
https://openstreetmap.cz/talkcz

Re: [OSM-talk-ie] It's official

[Jeffrey Roe]

Great to hear. Well done to everyone involved.
Jeffrey Roe,
www.tog.ie

On Mon, 23 Sep 2019 at 17:14, Tadeusz Cantwell  wrote:
>
> At the State of the map closing ceremony today OSM Ireland CLG officially
> became a recognised chapter of OSM foundation.
> https://twitter.com/osm_ie/status/1176138390447808513
> ___
> Talk-ie mailing list
> Talk-ie@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ie

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

Re: [talk-au] Consistent tagging of botanic gardens around Australia - leisure=park vs leisure=garden

[Andrew Davidson]

On 24/9/19 10:56 am, Daniel Graus wrote:


Should all botanical gardens be changed to match one another? Is 
leisure=park or leisure=garden more correct in some/the majority/all of 
these cases?


OK, a quick global survey

Of the ~2,500 botanical gardens that are in Wikidata and have a match in 
OSM there are:


320 leisure=garden
204 leisure=park
 22 tourism=attraction
 20 tourism=zoo
 12 leisure=nature_reserve
 11 tourism=museum
  4 tourism=theme_park
  1 tourism=botanical_garden
  1 leisure=yes

and 47 with no apparent object tag.

Wikidata lists 37 botanical gardens in Australia that don't have a 
wikidata tag or aren't mapped. Will have to check these before we can 
get an Australian list.



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

Re: [Talk-GB] Thomas Cook shops

[Paul Berry]

I don't know about that but Rob is very quick off the mark with his Ghosts
tool: https://osm.mathmos.net/ghosts/thomas-cook/

Regards,
*Paul*

On Mon, 23 Sep 2019 at 23:21, Dave F via Talk-GB 
wrote:

> Anybody know of specific high st shops for Thomas Cook which have
> remained open?
>  From national/local media it appears they may have all shut.
>
> Currently 265 entities named 'Thomas Cook' mostly shop=travel_agency but
> a few office/travel_agent mixed in.
>
> DaveF
>
>
>
>
> ___
> 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

[Talk-it] Masso erratico

[demon_box]

ciao devo mappare un masso erratico che ha un nome proprio "Balòta dela al di
Precc" quindi faccio

natural=stone
name=Balòta dela al di Precc

c'è qualche altro tag che potrei aggiungere per indicare che non è un
semplice masso ma è appunto un "masso erratico"?

grazie

--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] Cartographie de la pub...

[osm . sanspourriel]

Pourquoi pas les panneaux électoraux, mais à condition de les distinguer.

Je vois que même ceux qui ont permanent=no son affichés. Là encore
pourquoi mais à distinguer. Adrien dira qu'on peut faire un PR sur
GitHub ;-).

D'ailleurs certains ont aussi un nom qui correspond à l'appellation du
bureau de vote correspondant et qui permet de mieux les croiser avec les
informations sur le site de la ville. Par exemple name=Crèche du petit
Poucet. Mais je ne suis pas sûr que ce soit approprié. Une meilleure
suggestion ?

Ça, une requête spatiale va te les donner.

Celui-ci , si je
devais lui donner un nom (descriptif) ce serait "des Cinq Chemins" parce
qu'il est situé aux Cinq Chemins à Guidel, c'est un panneau électoral
pour les bureaux de vote de Guidel qui sont regroupés dans une même
salle et il y a plusieurs lots de panneaux électoraux répartis sur la
commune. On ne va pas les nommer tous "de Guidel".

Et comme je dis c'est une description de la localisation et non un nom à
proprement parler.

Jean-Yvon

Le 23/09/2019 à 23:40, Francois Gouget - fgou...@free.fr a écrit :

On Mon, 23 Sep 2019, PanierAvide wrote:


Bonjour,

Et pour avoir un rendu qui donne une vue d'ensemble, il y a OpenAdvertMap :
https://openadvertmap.pavie.info/#15/45.7547/4.8354

Est-ce normal que l'on y trouve les panneaux d'affichage électoraux ?
Par exemple :

https://openadvertmap.pavie.info/#17/48.79355/2.33282


Ils sont tagués avec advertising=board + message=political +
permanent=no. Faudrait-il les tagger autrement ?

D'ailleurs certains ont aussi un nom qui correspond à l'appellation du
bureau de vote correspondant et qui permet de mieux les croiser avec les
informations sur le site de la ville. Par exemple name=Crèche du petit
Poucet. Mais je ne suis pas sûr que ce soit approprié. Une meilleure
suggestion ?



___
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] mapbox, (Changeset Analyzer), whodidit

[Mateusz Konieczny]

24 Sep 2019, 04:42 by talk@openstreetmap.org:
> and will not let anyone else add – edit to that category.
>
Is (s)he making incorrect edits or rude
changeset comments?
Have you commented in their
changeset with explanation that it is a problem?

Can you link such changeset comments?___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk-fr] Greffon tag2link de JOSM et supports ANFR

[Yves P.]

Pour info,

Il existe une carte qui affiche les données ANFR, avec parfois des photos :
https://infraviewer.net/mapObject/2cf98757-71d8-48d1-9212-d424772f9a25

La légende permet de filtrer dynamiquement la carte par exploitants, 
propriétaires, « technologie » (AIS, RDR, LTE, UMTS…) , type d’antenne, type de 
support.

@François, Elle affiche aussi les NRA télécoms.

(Il n’y a pas d’info sur ses concepteurs, et l’interrogation du nom de domaine 
ne donne pas plus d’infos.)

—
Yves

PS: encore une carte à ajouter à OpenSwitchMaps___
Talk-fr mailing list
Talk-fr@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-fr

Re: [OSM-talk-fr] CyclOSM, rendu cyclable libre

[Florimond Berthoux]

Bonjour,

Le lun. 23 sept. 2019 à 21:49, Baptiste Jonglez 
a écrit :

> Bonjour,
>
> Super boulot, bravo !
>
> Je rejoins Christian sur le contraste : par exemple, les champs et routes
> mineures sont très visibles, alors que certaines voies comme les Eurovélos
> sont peu visibles aux faibles zooms (rose pâle avec un trait fin).
>
> Exemple pour les champs :
> https://www.cyclosm.org/#map=12/47.8360/-0.1693/cyclosm
>
> Exemple pour les routes mineures :
> https://www.cyclosm.org/#map=14/47.2414/-1.5807/cyclosm
> Ces routes assez contrastées donnent un effet "labyrinthe" qui rend moins
> lisible les grands axes vélos.
> À comparer avec le rendu standard :
> https://www.openstreetmap.org/#map=14/47.2414/-1.5807
>

Certains veulent voir les itinéraires vélo, d'autres non, et il y a CyclOSM
au milieu ¯\_(ツ)_/¯
Difficile de rendre les itinéraires en superposition sans ne voir que ça
sur la carte et tout en pouvant voir l'infrastructure en dessous.
On a passé du temps dessus pour équilibrer le rendu.

Si les routes mineurs (tertiary-unclassified-residiential-service) sont
affichées avec presque la même taille que les routes principales
c'est justement pour les mettre en valeurs car ce sont généralement les
plus cyclables par l'absence de trafic.
Cela a été fait particulièrement pour le cas d'utilisation en campagne.
Nous ne voulions pas mettre en valeur les grandes routes qui sont au
contraire à éviter.
Ton exemple montre au contraire qu'en zone résidentielle cela marche bien
aussi : il y a l'affichage des bandes cyclables, pistes et des itinéraires
qui mettent bien en valeur les rues de transit vélo.
Dans une ville sans infra cyclable cela permet aussi de mettre en valeur
des routes qui sont potentiellement cyclable sans que les routes primary et
secondary attirent plus l'œil :
https://www.cyclosm.org/#map=14/43.1803/5.7303/cyclosm


>
> Les highway=path + bicycle=designated sont beaucoup moins visibles que les
> highway=cycleway, alors que les deux sont parfois utilisés de façon
> presque interchangeable (en principe, le premier autorise les piétons par
> défaut alors que le second non).  Ça peut donner un rendu étrange :
>
> https://www.cyclosm.org/#map=18/45.18947/5.75133/cyclosm


Oui c'est à faire.

Par ailleurs, certains POI (campings, eau potable, certains magasins) ne
> sont rendus qu'à un zoom élevé, alors qu'ils sont aussi pertinents aux
> zooms inférieurs.  Exemple :
>
> https://www.cyclosm.org/#map=15/46.7570/-2.0100/cyclosm
> https://www.cyclosm.org/#map=16/46.7571/-2.0147/cyclosm
>
>
Effectivement, après c'est aussi la difficulté de régler l'affiche des POI
entre ville et campagne


> Ceci étant dit, il y a eu une vraie progression depuis le début, c'est
> chouette à voir :)
>
> Baptiste
>

Merci

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

[OSM-talk-be] Geopunt dag

[rodeo .be]

Hey all,

I'm attending the Geopunt day
 later today
(I'm there for professional reasons).

Anything I should mention? I'm thinking about the ongoing GRB imports,
addition of OSM in geopunt (maybe even the historical versions?), check
their willingness to support technically, ...

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

Re: [OSM-talk] mapbox, (Changeset Analyzer), whodidit

[Marc Gemis]

On Tue, Sep 24, 2019 at 4:47 AM 80hnhtv4agou--- via talk
 wrote:
>
>   What are these for anyway, other than stalking ?,

Quality assurance (QA). It helps more experienced mappers to see where
new people add things.
If they spot mistakes, they should engage in a friendly conversation
via private messages or changeset comments.
Being friendly is not always easy, so sometimes messages can be too rude.
And there are people that simply do not engage in conversations, which
is often understandable, as there are so many people that make a few
edits and disappear forever.
Other people are overly protective of "their" area, and change
everything to the way they want, which is not really desirable.

In general, those tools are used to follow edits in an area, not for
following individuals.

As Warin pointed out, try to start a conversation with the other
mapper, or the local community to find out why he is changing
everything you edit.
If all else fail, you can contact the DWG, they can e.g. block the
other mapper until he reads a certain message.

Good luck (and hope you are not too disappointed in OSM due to the
behaviour of 1 individual).

regards

m

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

Re: [talk-cz] SotM deníček - den třetí

[jzvc via talk-cz]

Dne 23.9.2019 v 23:08 xkomc...@centrum.cz napsal(a):

Naposledy ahoj,

dnes to bude stručnější, protože ráno jsem se ještě snažil nachystat 
na prezentaci co to šlo a pořád dokola ji pročítal, tak jsem toho moc 
nestihl. Nicméně, hodně zajímavé byly Lightening talks VII, kde mluvil 
SK53 o mapování poštovních schránek v UK (všichni, co mapují schránky 
v ČR by měli shlédnout - máme toho ještě hodně co dohánět :-D), pak 
člověk z Geofabriku představoval OSMInspector pro hledání chyb v 
routovacích relacích a na to navazoval poslední příspěvek, ve které 
padl návrh na zrušení routovacích relací (tj. veřejná doprava, 
cyklotrasy, pěší trasy, ...) jak je známe a jejich nahrazení systémem 
"routovacích relací", ve kterých by byly jen body, přes které se má 
jít a o výběr cesty by se staral hledač tras.


Cus,

pokud mi skleroza slouzi tohle se tu uz kdysi probiralo, a minimalne v 
podminkach CR to nemuze fungovat. Jednoduse proto, ze temi body by z 
logiky veci byly zastavky, a hledat muzes tak maximalne nejkratsi nebo 
"nejrychlejsi" trasu, ale to neni vzdy ta, po ktere MHD realne jezdi. 
Pokud bys pridaval nejake "pomocne" body nekde na trase, tak by to byl 
prozmenu velmi brzo nehoraznej bordel. Pricemz cim podrobneji budes 
mapovat (jizdni pruhy, konkretni mista zastaveni na nadrazich ...) tim 
horsi.


Jina vec jepochopitelne to, ze ty trasy nejsou zrovna aktualni, a jejich 
aktualizace je vopruz. To je podle me ale dano spis tim, ze neexistuje 
vhodny nastroj. Ten by se podle me mel chovat podobne jako navigace - 
reknu odkud a kam, a on spocita nejakou trasu, kterou pak muzu 
modifikovat a rovnou nabidne pridat/upravit zastavky po trase - vcetne 
prace s relacemi zastavek atd.





Johan Wiklund představoval otevřené řešení, které používají pro 
veřejnou dopravu v Norsku. Je to podobný systém (částečně stejný), co 
mají v Helsinkách (o tom loni mluvil Markku Huotari - ten tam byl i 
letos - moc fajn člověk, dá se s ním skvěle pokecat o všem možném). 
Tak jsem se zasnil o tom, že bychom něco podobného měli v ČR... 
Mimochodem, i spolková země Bádensko-Württembersko (kde leží 
Heidelberg), používá OSM kde to jenom jde a zároveň přispívá zpět. No 
nic, jdu snít dál...


A nakonec menší sebepropagace: moji přednášku najdete na 
https://www.youtube.com/watch?v=GELhDZLtSMI , slidy jsou na 
https://www.slideshare.net/MapTiler/osm-vector-tiles-in-custom-coordinate-systems-sotm-2019-175139514


Zbytek přednášek, co jste nestihli live, lze najít na adrese 
https://media.ccc.de/c/sotm2019


Mějte se a příští rok třeba někdo přidá své poznatky z Kapského Města ;-)

Jirka


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




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