Re: [talk-au] Discussion E: how to find faults in maps

2019-09-28 Per discussione David Wales
An example from the page Warin linked which may interest you is the
[Bicycle Tags map][1].
[1]: https://wiki.openstreetmap.org/wiki/Bicycle_tags_map)

For example, [here is Canberra][2] with all 'highway=cycleway' and
'bicycle=yes' tagged ways highlighted:
[2]:
http://mijndev.openstreetmap.nl/~ligfietser/fiets/index.html?map=cycleways=13=-35.32063=149.12057=B00TFT

Another link from the page Warin mentioned is [Osmose][3].
[3]: https://wiki.openstreetmap.org/wiki/Osmose

Here is [an example][4] with just cycleway errors flagged in Canberra:
[4]:
http://osmose.openstreetmap.fr/en/map/#zoom=13=-35.2845=149.122==1%2C2%2C3=cycleway=

If you have some knowledge of a tag that should be applied, you can use
JOSM filters to find which ways are missing the tag. For example, I use
filters to find roads which are missing speed limits.

Here are an [introduction][5] and [documentation][6] for JOSM filters.
[5]: https://blog.mapbox.com/using-filters-in-josm-99a7415f6235
[6]: https://josm.openstreetmap.de/wiki/Help/Dialog/Filter

An example filter is ('|' means inclusive 'OR'):

    highway=cycleway | bicycle=yes | bicycle=designated
   
By default, filters hide the selected tags. I have selected the 'invert'
option to hide everything except the selected tags.

See an [example of the above filter][7] here.
[7]: https://imgur.com/VNmUDWN

Regards,
David Wales

On 29/9/19 8:50 am, Warin wrote:
> On 29/09/19 07:30, Herbert.Remi via Talk-au wrote:
>>
>> I welcome your comments.
>>
>
> 1) This is not Australian specific.
> 2) The topic is an FAQ
> 3) Before you post .. do some research
>
> Read and use the tools from here 
> https://wiki.openstreetmap.org/wiki/Quality_assurance
>
> There are at least 264 fixmes in the ACT, that is more than 'dozens'
> you state.
>
>
>
> ___
> Talk-au mailing list
> Talk-au@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-au



signature.asc
Description: OpenPGP digital signature
___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


Re: [talk-au] Discussion E: how to find faults in maps

2019-09-28 Per discussione Warin

On 29/09/19 07:30, Herbert.Remi via Talk-au wrote:


I welcome your comments.



1) This is not Australian specific.
2) The topic is an FAQ
3) Before you post .. do some research

Read and use the tools from here 
https://wiki.openstreetmap.org/wiki/Quality_assurance


There are at least 264 fixmes in the ACT, that is more than 'dozens' you 
state.



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


Re: [Talk-ca] Importing buildings in Canada

2019-09-28 Per discussione Steve Singer

On Sat, 28 Sep 2019, Nate Wessel wrote:



I for one would be happy to support a local effort to import high quality 
buildings in Toronto and/or the GTA. I
think if we can actually meet up face to face our discussions may remain a bit 
more civil and productive. Hopefully
consensus will be a bit easier to achieve with smaller groups too!

I see that the OSM Toronto meetup doesn't have any upcoming events... Would 
others in the GTA be interested in
planning a meet up to talk about a local import plan? Is anyone on the list in 
charge of organizing these?


I am one of the organizers of the OSM Toronto meetup.

I've now posted the regular monthly mappy hour meetup for the Toronto OSM 
group. I had been meaning to do this anyway.


I'm also happy to post a special event dedicated to discussing an import in 
the GTA if people are interested.







Best,

Nate Wessel, PhD
Planner, Cartographer, Transport Nerd
NateWessel.com

On 2019-09-28 1:03 p.m., Jarek Piórkowski wrote:

Hi all,

To be a bit more positive:

If we want to get buildings on the map, but we can't get Canada-wide
data improved by Statcan to a standard acceptable to all mappers in
Canada, IMO the best bet will be to split this into much smaller
batches and support local mappers who would be interested in getting
the data in.

In my browsing of neis-one.org statistics for Canadian mappers and the
Notes active in Canada, I've seen active mappers and small communities
in at least Halifax, Calgary, Edmonton, Vancouver, and Victoria
metros, and I might have missed some more. Many of them I have never
seen on the mailing list (which is a whole another issue), but
contacting them directly (via osm.org messages?), asking if they are
aware of other local mappers, if they would be interested in having
building data, if it is of acceptable standard to them, and if they
would be willing to help validate-and-upload the data (with help of
the central tooling) might get some success.

I hope that will go better than the previous attempt which could be
read - uncharitably - as a bunch of mailing list insiders throwing
federal data over the fence with little consultation.

It'll be a lot of work communicating and organizing. But getting
buildings is a lot of work, and if data producers can't do better,
whoever wants the buildings will have to do the work. Maybe with more
local support even the imports list will be more bearable.

Thanks,
--Jarek

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



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


Re: [Talk-ca] Importing buildings in Canada

2019-09-28 Per discussione stevea
And several years later, here we are.  I'm glad to see such a "new arrival" at 
a place where good data can meet a good crowdsourced mapping database, and 
furthermore, I wish the project all good luck.

SteveA
California

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


[talk-au] Discussion E: how to find faults in maps

2019-09-28 Per discussione Herbert.Remi via Talk-au
# Discussion E: how to find faults in maps

## The Issue

The ACT has 3000km of roads, 2000km of footpaths, and 329 km of shared bike 
paths, 1000s of km of formed trails (2/3 the state is rideable), a few 100kms 
of mountain biking "single-track" and a few dozen active planners at best. How 
do you find errors in this network?

It is looking for a needle in the haystack. Here are some options I have tried, 
and I would be grateful for further suggestions. Going there or comparing with 
the satellite photos in OSM are two options that I will not mention further 
here as that is the way they are a map in the first place. Unfortunately, it is 
not enough. The ACT maps require quality and consistency improvements.

FIXME has not been all that helpful, with errors in the ACT in the dozens and 
not 100s or 1000s. FIXME is just the errors we know of not the ones we don’t.

QUESTION

What are the approaches you have used to find errors, particularly with tagging?

What follows are options that I have helped, that you might like to comment on.

## 1. Detection algorithms

Not surprising somebody has written code to do this – an OSM proofing tool. It 
is good for some things and completely misses others. It allows you to inspect 
OSM in different ways: geometry, tagging, places, highway, areas, coastline, 
routing, addresses, water, public transport stops and public transport routes. 
It fishes out all the FIXME tags too. The service is provided by Geofabrik. The 
website is in English as well. Take a look at it here.

http://tools.geofabrik.de/osmi/

## 2. A different perspective (alternate rendering)

The testing of a map helps. Try using the OSM data and see if it is fit for 
purpose. We are familiar with the Mapnik rendering (default). It is a 
general-purpose map. A map for riding bikes, hiking or mountain biking would 
look different. We can easily forget every Mapnik cherry picks OSM for 
information. Errors that don’t show on the Mapnik render may show on a bike 
map. Similar information may be shown differently or keys/tags displayed that 
are not visible on the Mapnik.

## Interesting render options

To make things challenging, there is more than one type of cyclist. I would 
like to distinguish between the type of riding mountain bikes do and that of 
other cyclists. Mountain bikes are built for unpaved and rough surfaces. Other 
bikes are only suitable for paved and relatively smooth surfaces. I will 
categorise these city bikes (just a label, please don't take offence). Mountain 
bikers and city bikers have different needs and their maps should reflect that.

The following websites have English language pages too. Look for the British 
flag if you end up in the wrong spot.

### CyclOSM for city bikes

CyclOSM is cyclist map and best suited for reviewing the OSM data for city 
bikes but show unpaved tracks and paths too. There are better maps for mountain 
biking though. This map can show inconsistent tagging of paths and relations. 
The tagging issues are raised in the post *Discussion D: mapping ACT for 
cyclists – complying with ACT law*.

https://www.cyclosm.org/#map=14/-35.2853/149.1188/cyclosm

This map is updated continually (live) from OSM and you can see editing changes 
just minutes after you save them. I have run this map and the ID editor in 
split-screen so that I could compare the two.

### openMTBmap for mountain bikes

If you ride a mountain bike you will like openMTBmap. This map is rendered for 
the off-road rider and shows the condition of tracks, permissions and other 
useful features (check website for details). Unfortunately, there is no live 
view of these maps, but you can download them for free and view them with 
BaseCamp from Garmin. If you like the map you can even save it on your Garman 
device and take it with you. Turn-by-turn navigation on a mountain bike, no 
problem! Maps are updated weekly. Openmtbmap is rendered for Garmin outdoor 
devices and looks a bit weird in HD.

https://openmtbmap.org/

I welcome your comments.

keywords: Australia, ACT, FOSS; website, rendering, mountain biking, city 
biking, Garmin, error detection, FIXME, speciality maps___
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au


Re: [OSM-talk-fr] switch2OSM

2019-09-28 Per discussione Vincent de Château-Thierry

Bonsoir,

Le 28/09/2019 à 22:48, osm.sanspourr...@spamgourmet.com a écrit :


Christian, tu dis que les entreprises sont assez réactives si on les 
titille sur Twitter, tu peux vérifier : https://twitter.com/Mappy


Twitter c'est bien quand on ne connaît pas ses interlocuteurs et qu'on 
veut leur mettre un coup de pression.
Mappy soutient le SOTM depuis plusieurs années en France, ce qui ne se 
fait pas par magie mais parce que ce sont des gens avec qui il est 
possible de discuter de manière constructive. C'est ce que je vais faire 
dans le cas présent, par mail, et on verra bien ce que ça donne. Je vous 
tiens au courant.


vincent

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


[OSM-talk-fr] switch2OSM

2019-09-28 Per discussione osm . sanspourriel

Joli poisson : sur la carte des Pages Jaunes (Mappy) j'ai eu la surprise
de voir :

© Mappy 
| 2018 TomTom, OpenStreetMap.

Bien ? Oui et non car seul Mappy est muni d'un lien.

Et le lien
https://blog.mappy.com/entreprise/conditions-dutilisations/copyright/

© Mappy 2018. Tous droits réservés, reproduction interdite.

Par vraiment ODbL mais s'ils parlent des tuiles pourquoi pas.

Et les différentes sources de données se voient attribuées les
copyrights qui vont bien.

Toutes ? Non visiblement on peut se moquer des données communautaires et
des collectivités :

2. AUTRES DONNÉES GÉOGRAPHIQUES
Natural Earth
GeoNames
OpenStreetMap
IleDeFranceMobilité
Toulouse
Lorient
Lille

Oui, aucun lien vers les copyrights et conditions d'utilisation respectifs.

Christian, tu dis que les entreprises sont assez réactives si on les
titille sur Twitter, tu peux vérifier : https://twitter.com/Mappy

Jean-Yvon

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


Re: [Talk-ca] Importing buildings in Canada

2019-09-28 Per discussione John Whelan
My suggestion would be to amend and clean up the original import plan to 
split out the country into regions and have a regional coordinator for 
each region based on local input.  I'd also add in the two other data 
sources as alternative data sources.


The reason for this approach is an amended import plan might be more 
acceptable to the import mailing list than new plans and in our smaller 
regions there may not be the resources to put together a full import 
plan for a thousand buildings.


Cheerio John

Nate Wessel wrote on 2019-09-28 1:37 PM:


I for one would be happy to support a local effort to import high 
quality buildings in Toronto and/or the GTA. I think if we can 
actually meet up face to face our discussions may remain a bit more 
civil and productive. Hopefully consensus will be a bit easier to 
achieve with smaller groups too!


I see that the OSM Toronto meetup 
 doesn't have any 
upcoming events... Would others in the GTA be interested in planning a 
meet up to talk about a local import plan? Is anyone on the list in 
charge of organizing these?


Best,

Nate Wessel, PhD
Planner, Cartographer, Transport Nerd
NateWessel.com 

On 2019-09-28 1:03 p.m., Jarek Piórkowski wrote:

Hi all,

To be a bit more positive:

If we want to get buildings on the map, but we can't get Canada-wide
data improved by Statcan to a standard acceptable to all mappers in
Canada, IMO the best bet will be to split this into much smaller
batches and support local mappers who would be interested in getting
the data in.

In my browsing of neis-one.org statistics for Canadian mappers and the
Notes active in Canada, I've seen active mappers and small communities
in at least Halifax, Calgary, Edmonton, Vancouver, and Victoria
metros, and I might have missed some more. Many of them I have never
seen on the mailing list (which is a whole another issue), but
contacting them directly (via osm.org messages?), asking if they are
aware of other local mappers, if they would be interested in having
building data, if it is of acceptable standard to them, and if they
would be willing to help validate-and-upload the data (with help of
the central tooling) might get some success.

I hope that will go better than the previous attempt which could be
read - uncharitably - as a bunch of mailing list insiders throwing
federal data over the fence with little consultation.

It'll be a lot of work communicating and organizing. But getting
buildings is a lot of work, and if data producers can't do better,
whoever wants the buildings will have to do the work. Maybe with more
local support even the imports list will be more bearable.

Thanks,
--Jarek

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



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


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


Re: [Talk-at] Pflanzfläche Bäume Mur Graz

2019-09-28 Per discussione Robert Grübler
Am Freitag, 30. August 2019 15:26 schrieb Lars Schimmer:

> Dort habe ich mal an der Stelle des Ausgleichsbereiches 
> https://osm.org/go/0Iz_pZwBc--?layers=N 
> das Wasser eingezeichnet, ...
> ...
> das Wasser hat Verbindung mit der Mur,
>  möchte aber die Murrelation ned kaputt machen

Das Wasser sollte nicht über dem Polygon landuse=forest liegen. M.E. müsste 
landuse ein Multipolygon sein. Siehe Beispiel "Wald mit See" in 
https://wiki.openstreetmap.org/wiki/DE:Multipolygon_Examples.
In  Bing sehe ich aber keine Bäume mehr...

Die Seen würde ich nicht zur Relation Mur hinzufügen, sondern eigenständig 
belassen und nur mit tunnel=culvert an die Mur anbinden.

LG Robert



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


Re: [Talk-ca] Importing buildings in Canada

2019-09-28 Per discussione John Whelan
And I totally agree.  Because the Stat Can data has come from many 
sources the data quality is variable to put it politely.  The Microsoft 
data has been shown in the US to also be of variable quality.  I'm not 
so sure about the NR Can LiDAR data hopefully it is at least consistent.


If we look at the history of the project then we can get an idea of how 
we came to be where we are.


First I wanted to import all the bus stops in Ottawa because only by 
importing could you ensure you had all the stops with their reference 
numbers but the City of Ottawa Open Data license did not align with 
OSM.  I was also talking to Treasury Board and explained to them that 
their Open Data license version 1 didn't align with OSM so we couldn't 
use their data.  Five years later TB released their Open Data license 
version 2 which they felt did align.


Stat Can has two types of project, pilot ones and ones that earn money. 
The original pilot was based on Ottawa and Gatineau and was for two 
years.  Their original plan was mapathons using iD.  I was impressed 
when a stat can employee managed to accurately map a building using iD 
during a presentation.  I hadn't thought it was possible after some of 
the efforts I'd seen in HOT mapping.   Fine except that it requires a 
lot of mappers and I think Fredrick has commented this sort of mapping 
with new mappers needs a lot of clean up effort sometimes more than 
required for an experienced mapper to map it right in the first place. 
Montreal has identified there just aren't enough experienced mappers 
available.


I worked at Stats Canada for a number of years.  The corporate culture 
is very different to OSM.  It makes its money by selling data.  Want to 
open a new coffee bar? Stats Canada will combine its data to sell you 
the ideal spot based on residents' income etc..  I had a meeting with 
Stats Canada, City of Ottawa planning department, an Open Data 
specialist from Carlton University, someone from Metrolink who had added 
data to openstreetmap to help people find the nearest bus stop and a 
couple of HOT board members.   We convinced Stats Canada to change the 
direction of the pilot to use Open Data rather than go the mapathon 
route partly for data quality reasons and partly because I didn't think 
we could find the mappers to map the buildings completely.  The Stat Can 
involvement meant the City of Ottawa was persuaded to change its Open 
Data license to the same as the TB one.  That took time and had to go to 
council for approval.  There was a lot of discussion with the local 
community and it was they who organised and did the import.   The local 
group worked nicely together and had a range of skill sets in the 
group.  I actually played more of a connecting role than anything else.


The import was challenged on the data license amongst other things but 
eventually the OSM legal working group was very kind and ruled the 
license was acceptable.  Stats is very interested in added detail to 
buildings.  I was very interested that we could now import the bus stops.


I think you picked up on the fact that the buildings mapped in a 
mapathon were less than ideal.  I was involved in one in Ottawa and just 
taught the new mappers to use JOSM and the building_tool.  That produced 
more buildings per mapper hour and they were fairly accurate.  I must 
confess not every attached garage was mapped in detail.


I seem to recall Mapbox being involved in the Maperthons in some way.

The Stats Can involvement meant we saw some interest from schools.  What 
I was interested in was added detail so mapped a couple of thousand 
buildings in Ontario using JONM and the building_tool so details could 
be added easily.  We got two addresses added.  Apparently in Ontario the 
provincial government has purchased ESRI for school children to learn 
about GIS.


At the end of the pilot the money had run out.  Stats covered some of 
the costs involved in the HOT summit that was held in Ottawa and during 
that summit phase two was launched but without any real funding.


What Stats could do though was release data from the municipalities 
under the government Open Data license and that is what they did.  As 
Jarek has pointed out following the import process is stressful so I 
volunteered to do the paperwork and submit the plan.  There was some 
discussion on talk ca and the idea surfaced to go with one plan rather 
than divide the country up.  So that's what I did.


Today we have three sources of data that could be imported, and I 
suspect the two that are not municipal data are more consistent.  We 
still have the original plan of mapathons with iD floating around.


My person view is the imported data quality is better than the mapathon 
approach but to go forward from here I think it needs to be re-planned 
and a new import plan(s) drawn up.


I don't think Stats have any real funding available at the moment.  They 
may find an odd hour in a quiet time but its coming up to 

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

2019-09-28 Per discussione Andrew Hain
We can check for properties where the brand:wikidata tag was left behind by 
checking the other tags, particularly name= and shop=.

--
Andrew

From: SK53 
Sent: 28 September 2019 17:32
To: Silent Spike 
Cc: Talk GB 
Subject: Re: [Talk-GB] Subject: Re: Thomas Cook shops

The specific problem with that suggestion is that you miss lots of Thomas Cook 
shops (particularly old Co-op Travel & Ilkeston Co-op travel): it hits about 3 
within 15 miles of Nottingham whereas there are nearer 11 (for obvious 
reasons), and one of those is apparently is 
not now a travel agent.

This latter aspect shows that editors other than iD may not surface 
Wikipedia/wikidata tags & that therefore such data needs to be cross-checked, 
and bulk edits may inadvertently change other things. In many ways I prefer 
that we acquire new local mappers (like OftenResident in Alfreton) who notice 
that an area is out-of-date & set about getting it up-to-date, rather than 
doing a partial update and missing other info (like the shop is now a 
hairdresser). Obviously others think we should keep everything as up-to-date as 
the information we have available. I don't think we have ever reached a 
consensus on this.

Jerry

On Sat, 28 Sep 2019 at 16:41, Silent Spike 
mailto:silentspike...@gmail.com>> wrote:
It's unclear to me if there's a consensus on the tagging here. Personally I 
like the `disused:` prefix.

I couldn't see if it was mentioned anywhere, but we can also query for all the 
locations explicitly marked as part of the Thomas Cook brand using the 
`brand:wikidata` tag: https://overpass-turbo.eu/s/MFP

All of the results here can really be automatically re-tagged as disused or 
vacant since we explicitly know they were locations belonging to Thomas Cook 
(the beauty of wikidata tagging). You might say some may already have been sold 
and re-signed, but that can always be tagged after - we at least know for 
certain that none of them are Thomas Cook travel agency shops anymore.
___
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] Importing buildings in Canada

2019-09-28 Per discussione Nate Wessel
I for one would be happy to support a local effort to import high 
quality buildings in Toronto and/or the GTA. I think if we can actually 
meet up face to face our discussions may remain a bit more civil and 
productive. Hopefully consensus will be a bit easier to achieve with 
smaller groups too!


I see that the OSM Toronto meetup 
 doesn't have any 
upcoming events... Would others in the GTA be interested in planning a 
meet up to talk about a local import plan? Is anyone on the list in 
charge of organizing these?


Best,

Nate Wessel, PhD
Planner, Cartographer, Transport Nerd
NateWessel.com 

On 2019-09-28 1:03 p.m., Jarek Piórkowski wrote:

Hi all,

To be a bit more positive:

If we want to get buildings on the map, but we can't get Canada-wide
data improved by Statcan to a standard acceptable to all mappers in
Canada, IMO the best bet will be to split this into much smaller
batches and support local mappers who would be interested in getting
the data in.

In my browsing of neis-one.org statistics for Canadian mappers and the
Notes active in Canada, I've seen active mappers and small communities
in at least Halifax, Calgary, Edmonton, Vancouver, and Victoria
metros, and I might have missed some more. Many of them I have never
seen on the mailing list (which is a whole another issue), but
contacting them directly (via osm.org messages?), asking if they are
aware of other local mappers, if they would be interested in having
building data, if it is of acceptable standard to them, and if they
would be willing to help validate-and-upload the data (with help of
the central tooling) might get some success.

I hope that will go better than the previous attempt which could be
read - uncharitably - as a bunch of mailing list insiders throwing
federal data over the fence with little consultation.

It'll be a lot of work communicating and organizing. But getting
buildings is a lot of work, and if data producers can't do better,
whoever wants the buildings will have to do the work. Maybe with more
local support even the imports list will be more bearable.

Thanks,
--Jarek

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


Re: [Talk-ca] Importing buildings in Canada

2019-09-28 Per discussione Jarek Piórkowski
Hi all,

To be a bit more positive:

If we want to get buildings on the map, but we can't get Canada-wide
data improved by Statcan to a standard acceptable to all mappers in
Canada, IMO the best bet will be to split this into much smaller
batches and support local mappers who would be interested in getting
the data in.

In my browsing of neis-one.org statistics for Canadian mappers and the
Notes active in Canada, I've seen active mappers and small communities
in at least Halifax, Calgary, Edmonton, Vancouver, and Victoria
metros, and I might have missed some more. Many of them I have never
seen on the mailing list (which is a whole another issue), but
contacting them directly (via osm.org messages?), asking if they are
aware of other local mappers, if they would be interested in having
building data, if it is of acceptable standard to them, and if they
would be willing to help validate-and-upload the data (with help of
the central tooling) might get some success.

I hope that will go better than the previous attempt which could be
read - uncharitably - as a bunch of mailing list insiders throwing
federal data over the fence with little consultation.

It'll be a lot of work communicating and organizing. But getting
buildings is a lot of work, and if data producers can't do better,
whoever wants the buildings will have to do the work. Maybe with more
local support even the imports list will be more bearable.

Thanks,
--Jarek

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


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

2019-09-28 Per discussione SK53
The specific problem with that suggestion is that you miss lots of Thomas
Cook shops (particularly old Co-op Travel & Ilkeston Co-op travel): it hits
about 3 within 15 miles of Nottingham whereas there are nearer 11 (for
obvious reasons), and one of those is apparently is not
 now a travel agent.

This latter aspect shows that editors other than iD may not surface
Wikipedia/wikidata tags & that therefore such data needs to be
cross-checked, and bulk edits may inadvertently change other things. In
many ways I prefer that we acquire new local mappers (like OftenResident in
Alfreton) who notice that an area is out-of-date & set about getting it
up-to-date, rather than doing a partial update and missing other info (like
the shop is now a hairdresser). Obviously others think we should keep
everything as up-to-date as the information we have available. I don't
think we have ever reached a consensus on this.

Jerry

On Sat, 28 Sep 2019 at 16:41, Silent Spike  wrote:

> It's unclear to me if there's a consensus on the tagging here. Personally
> I like the `disused:` prefix.
>
> I couldn't see if it was mentioned anywhere, but we can also query for all
> the locations explicitly marked as part of the Thomas Cook brand using the
> `brand:wikidata` tag: https://overpass-turbo.eu/s/MFP
>
> All of the results here can really be automatically re-tagged as disused
> or vacant since we explicitly know they were locations belonging to Thomas
> Cook (the beauty of wikidata tagging). You might say some may already have
> been sold and re-signed, but that can always be tagged after - we at least
> know for certain that none of them are Thomas Cook travel agency shops
> anymore.
> ___
> 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] Importing buildings in Canada

2019-09-28 Per discussione Pierre Béland via Talk-ca
Je comprends que c'est la saison des tomates. Mais essayons de les utiliser 
pour nos conserves et non comme argument pour convaincre les autres 
contributeurs !  ;)
Comme les autres l'ont exprimé, c'est à ceux qui proposent de faire des imports 
de bien documenter le processus, non l'inverse. Et les menaces d'agir de façon 
impériale et négliger les communautés locales, cela ne tient évidemment pas la 
route.
Pour discuter sur la qualité des données, il est nécessaire de pouvoir 
facilement examiner les données. Et je ne penses pas que les données soient 
comparables d'un endroit à l'autre. La qualité des images, la densité du bâti 
en milieu urbains sont autant de facteurs.
 Les fichiers accessibles aussi bien pour StatCan que Microsoft sont très gros. 
Simplement pour analyser les données de nos municipalités respectives, il faut 
traiter de gros fichiers et tenter d'extraire les données. Ce qui n'est pas 
nécessairement facile et va bien sûr limiter la participation.
Question de donner des exemples sur les limites d'observation des images par 
les technique de AI, j'ai publié des images avec les 2 tweets suivants montrant 
des bâtiments au centre de Toronto :
https://twitter.com/pierzen/status/1177976517902684160
https://twitter.com/pierzen/status/1177978125377884160
On voit bien qu'il ne suffit pas de valider si les angles sont droits. Ces 
exemples montrent bien comment le tracé peut varier significativement vs la 
réalité au sol. Et tout comme les humains, les techniques de AI ont de la 
difficulté à identifier les bâtiments individuels.

cordialement 
Pierre 
 

Le vendredi 27 septembre 2019 22 h 52 min 59 s UTC−4, Jarek Piórkowski 
 a écrit :  
 
 On Fri, 27 Sep 2019 at 11:45, john whelan  wrote:
> ...
> About that time an American mapper, Nate, who was living in Toronto ...

Sorry, one more thing.

Nate was an active editor in Toronto at the time of the initial import
conflict/objection and has remained so as regularly as we can ask of
any community member. In Toronto we call people living here and
contributing to the community "Torontonians".

As you will recall, I disagree with Nate about the suitability of
initial building import data. Notwithstanding, the description quoted
above reads unfairly dismissive to me. You can maybe make arguments
about Torontonians discussing what shouldn't be imported in rest of
Canada, or about whether we should expect mappers to be subscribed to
talk-ca, but let's leave places of birth out of this.

--Jarek

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


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

2019-09-28 Per discussione Silent Spike
It's unclear to me if there's a consensus on the tagging here. Personally I
like the `disused:` prefix.

I couldn't see if it was mentioned anywhere, but we can also query for all
the locations explicitly marked as part of the Thomas Cook brand using the
`brand:wikidata` tag: https://overpass-turbo.eu/s/MFP

All of the results here can really be automatically re-tagged as disused or
vacant since we explicitly know they were locations belonging to Thomas
Cook (the beauty of wikidata tagging). You might say some may already have
been sold and re-signed, but that can always be tagged after - we at least
know for certain that none of them are Thomas Cook travel agency shops
anymore.
___
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

2019-09-28 Per discussione Philip Barnes
OSMand also shows them.

Phil  (trigpoint)

On Tuesday, 24 September 2019, 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
>

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


Re: [Talk-it] Tag ref anche per Codice Fiscale

2019-09-28 Per discussione Francesco Ansanelli
Ciao Marco!

In realtà le aziende italiane hanno entrambi i codici anche se spesso
coincidono...


Il sab 28 set 2019, 09:54 mbranco2  ha scritto:

> Ciao Francesco,
> visto che lasciamo perdere i codici fiscali personali, e quindi parliamo
> solo del codice numerico di 11 cifre dei soggetti che non sono persone
> fisiche, c'è già il tag ref:vatin che avevi citato all'inizio...
>
> Il giorno sab 28 set 2019 alle ore 09:23 Francesco Ansanelli <
> franci...@gmail.com> ha scritto:
>
>> Ciao,
>>
>> se nessuno ha qualcosa in contrario, propongo di togliere i codici
>> fiscali alfanumerici che, come segnalato da Andrea, sono anche dati
>> personali e di indicare solo quelli numerici, visto che si tratta di un
>> dato specifico per le aziende italiane, associazioni/enti e bed and
>> breakfast, propongo:
>>
>> ref:cf:it
>>
>> Con la regola di inserire solo il valore numerico senza prefisso IT.
>>
>> Francesco
>>
>>
>> Il lun 23 set 2019, 19:14 Andrea Albani  ha scritto:
>>
>>> Per cosa vuoi usarlo esattamente ?
>>> Il codice fiscale è un dato personale e come tale va trattato secondo
>>> normativa.
>>>
>>> Ciao
>>>
>>>
>>> Il giorno lun 23 set 2019 alle ore 19:06 Francesco Ansanelli <
>>> franci...@gmail.com> ha scritto:
>>>
 Buonasera lista,

 cosa ne pensate di usare il tag ref, analogamente a come viene fatto
 per la Partita IVA (
 https://wiki.openstreetmap.org/wiki/IT:Key:ref:vatin), per il Codice
 Fiscale?
 Proporrei qualcosa come "ref:ssn", in modo che possa essere adottato
 anche in altri paesi...
 Sinceramente fin'ora ho inserito il dato in "operator" ad esempio
 "Mario Rossi - RSSMRA...", ma credo sia più appropriato creare un tag
 apposito e vorrei raccogliere qualche feedback.

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

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


Re: [Talk-it] Tag ref anche per Codice Fiscale

2019-09-28 Per discussione mbranco2
Ciao Francesco,
visto che lasciamo perdere i codici fiscali personali, e quindi parliamo
solo del codice numerico di 11 cifre dei soggetti che non sono persone
fisiche, c'è già il tag ref:vatin che avevi citato all'inizio...

Il giorno sab 28 set 2019 alle ore 09:23 Francesco Ansanelli <
franci...@gmail.com> ha scritto:

> Ciao,
>
> se nessuno ha qualcosa in contrario, propongo di togliere i codici fiscali
> alfanumerici che, come segnalato da Andrea, sono anche dati personali e di
> indicare solo quelli numerici, visto che si tratta di un dato specifico per
> le aziende italiane, associazioni/enti e bed and breakfast, propongo:
>
> ref:cf:it
>
> Con la regola di inserire solo il valore numerico senza prefisso IT.
>
> Francesco
>
>
> Il lun 23 set 2019, 19:14 Andrea Albani  ha scritto:
>
>> Per cosa vuoi usarlo esattamente ?
>> Il codice fiscale è un dato personale e come tale va trattato secondo
>> normativa.
>>
>> Ciao
>>
>>
>> Il giorno lun 23 set 2019 alle ore 19:06 Francesco Ansanelli <
>> franci...@gmail.com> ha scritto:
>>
>>> Buonasera lista,
>>>
>>> cosa ne pensate di usare il tag ref, analogamente a come viene fatto per
>>> la Partita IVA (https://wiki.openstreetmap.org/wiki/IT:Key:ref:vatin),
>>> per il Codice Fiscale?
>>> Proporrei qualcosa come "ref:ssn", in modo che possa essere adottato
>>> anche in altri paesi...
>>> Sinceramente fin'ora ho inserito il dato in "operator" ad esempio "Mario
>>> Rossi - RSSMRA...", ma credo sia più appropriato creare un tag apposito e
>>> vorrei raccogliere qualche feedback.
>>>
>>> Francesco
>>> ___
>>> Talk-it mailing list
>>> Talk-it@openstreetmap.org
>>> https://lists.openstreetmap.org/listinfo/talk-it
>>>
>> ___
>> Talk-it mailing list
>> Talk-it@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-it
>>
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it


Re: [Talk-it] Tag ref anche per Codice Fiscale

2019-09-28 Per discussione Francesco Ansanelli
Ciao,

se nessuno ha qualcosa in contrario, propongo di togliere i codici fiscali
alfanumerici che, come segnalato da Andrea, sono anche dati personali e di
indicare solo quelli numerici, visto che si tratta di un dato specifico per
le aziende italiane, associazioni/enti e bed and breakfast, propongo:

ref:cf:it

Con la regola di inserire solo il valore numerico senza prefisso IT.

Francesco


Il lun 23 set 2019, 19:14 Andrea Albani  ha scritto:

> Per cosa vuoi usarlo esattamente ?
> Il codice fiscale è un dato personale e come tale va trattato secondo
> normativa.
>
> Ciao
>
>
> Il giorno lun 23 set 2019 alle ore 19:06 Francesco Ansanelli <
> franci...@gmail.com> ha scritto:
>
>> Buonasera lista,
>>
>> cosa ne pensate di usare il tag ref, analogamente a come viene fatto per
>> la Partita IVA (https://wiki.openstreetmap.org/wiki/IT:Key:ref:vatin),
>> per il Codice Fiscale?
>> Proporrei qualcosa come "ref:ssn", in modo che possa essere adottato
>> anche in altri paesi...
>> Sinceramente fin'ora ho inserito il dato in "operator" ad esempio "Mario
>> Rossi - RSSMRA...", ma credo sia più appropriato creare un tag apposito e
>> vorrei raccogliere qualche feedback.
>>
>> Francesco
>> ___
>> Talk-it mailing list
>> Talk-it@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-it
>>
> ___
> Talk-it mailing list
> Talk-it@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-it
>
___
Talk-it mailing list
Talk-it@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-it