Re: [Talk-ca] Canvec Import

[Viajero Perdido]

From: James 

not sure why Canvec always gets shat uppon, their water features are great
and pretty accurate


Bovine excrement.  Do I need to make an exhaustive list of the 
water-feature nonsense I keep finding?  Lakes dry up, and rivers change 
course (especially around Calgary in 2013).  Somebody imported a whole 
swath of ponds and lakes in NE Alberta, where a glance at imagery shows 
few if any still exist; it's all farmland now.


CanVec gets shat upon because the data quality is shite.  You can put 
water features in the BAD column along with landcover, POIs (schools are 
not prisons), trails (approximate is not good enough), and so on.


I am part of the CanVec immune system, because I want to see us create a 
*quality* map.


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

Re: [Talk-ca] Hydro Network (inland water) question

[Viajero Perdido]

On 2018-09-27 05:42 PM, talk-ca-requ...@openstreetmap.org wrote:

What happened during the import of inland water data?


Maybe people realized the poor quality of the data, and found positive 
ways to contribute instead?



Throw in flack from Germany

...and Canada!


Waterways change in thirty years; ask anyone in Calgary doing recreation 
nearby; the 2013 flood changed many things.  Satellite imagery covers 
the new reality.  CanVec/GeoBase do not.  And landcover can change 
dramatically in such time.


As to great vast areas of white on the map, I'd rather see those remain 
blank, rather than filled with garbage data.  When I'm standing on the 
ground trying to cross a river, sometimes I swear at CanVec.  And yes, I 
have put in many many hours adding natural-feature detail from 
satellite, the hard way, trying to stay ahead of the CanVec imports, 
which I consider disastrous.  I figure, if there's already data in 
place, hopefully nobody will wipe it out with an import (again).


So please, nobody pretend there's consensus here that CanVec/GeoBase 
imports are a good thing.


That's my two bits, now sorry, I have to leave the internet for a few 
days.  I'm going out to play in the woods, where hand-edited OSM will 
help me immensely.


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

Re: [Talk-ca] Trans-Canada Highway research

[Viajero Perdido]

On 18-03-26 05:33 AM, talk-ca-requ...@openstreetmap.org wrote:

Message: 3
Date: Mon, 26 Mar 2018 11:33:14 +
From: James 
To: "Olivia Robu - (p)" 
Cc: Talk-CA OpenStreetMap 
Subject: Re: [Talk-ca] Trans-Canada Highway research
Message-ID:

Content-Type: text/plain; charset="utf-8"

highway 417 should be tagged as highway 417 and not principally transcanada
way as this is how it's known locally. It can be tagged in transcanada
relation, but it's mainly known as the 417


I disagree.  "Highway 417" is a low-value name, because the "ref" tag 
should already contain the number, causing numbered shields to be 
shown.  "Highway 417" is just a verbosification of the number. 
"Trans-Canada Highway", however, is a real name; it belongs in the name 
field.


This way, most maps would show both name and number.

To me, the (completely separate) issue is whether ordinary numbered 
highways should have a name tag at all, "Highway nnn", or simply nothing 
because "ref" takes care of it.  I've been able to find no guidance on 
this, and I've looked.  I've been leaving "Highway nnn" in place when I 
see it, which is most of the time.  But that's another discussion for 
another day.


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

Re: [Talk-ca] Expanding vs abbreviating

[Viajero Perdido]

I continue to assert that our (OSM's) name=* wiki states these 
abbreviations should be fully expanded and that official_name=* might 
hold the abbreviation.


Hi Everyone.

I'll pop in here because I'd hate to see this considered "discussed and 
approved". (And replying a day late because I'm still getting the hang 
of mailing list technology.  Hope it doesn't catch on.)


From the wiki, "If the name is incorrect when spelled in full, however, 
do not falsely expand it."

https://wiki.openstreetmap.org/wiki/Names#Abbreviation_.28don.27t_do_it.29

On a related note, I live in Edmonton, where every street has a quadrant 
suffix, usually "NW".  The city made those abbreviations, not OSM 
mappers.  It's right there on my property tax bill; I'm paying tax for a 
property that ends in "NW".  I've got the whole city touched up to say 
NW etc. (after an old import) - and it bugs me to see mappers swoop in 
to expand things again.  Luckily the Edmonton wiki has explicit examples 
that agree with me.


My two bits.

Tom, aka VP


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