Hello,
First post here, sorry if I mess anything up!
A few months back I noticed that station names for Vancouver Skytrain
rapid transit system (all lines) are inconsistent: 32 of them have
"Station" in their name, but 23 don't, with little apparent pattern by
line or location.
Most of all I
Hi,
Thanks for the feedback! It helps a lot to have information from real
world users.
I looked into the data briefly. The data that _has been_ entered in
OpenStreetMap looks correct. However, much data is not available.
A brief explanation of what is happening:
Postal codes are potentially
On 17 February 2018 at 00:03, OSM Volunteer stevea
<stevea...@softworkers.com> wrote:
> On Feb 16, 2018, at 2:56 PM, Jarek Piórkowski <ja...@piorkowski.ca> wrote:
>> With "street" in a street name, it's clear to most everyone that Pine St is
>> an abbrev
t Thomas, but a computer might have a bit
> of trouble there. And don't get me started on the absurdity that St is a
> contraction, not an abbreviation.
>
> I'm not going to rush out and change any existing tagging but I think this
> is one instance where rational thought needs to over
he code forward
means the direction in which the way is drawn in OpenStreetMap, while
backward means the opposite direction. "
On 14 July 2018 at 21:04, john whelan wrote:
> Fine but how does one decide which is forward?
>
> Thanks John
>
> On Sat, 14 Jul 2018, 3:02 pm Jarek Piórko
you likely want
https://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right
combined with https://wiki.openstreetmap.org/wiki/Key:cycleway
something like cycleway:forward=shared_lane, cycleway:backward=lane
On 14 July 2018 at 20:44, john whelan wrote:
> Ottawa has been adding these
Hi all,
Damien's question appears to be about nodes like
https://www.openstreetmap.org/node/438843513, which has
name=Berri-UQAM, operator=Société de transport de Montréal.
short_name=STM seems inappropriate here, we could do
operator:short_name=STM or something but it seems a bit much.
The
I have seen this used in Germany for "junction names", e.g.
https://www.openstreetmap.org/node/30249931 is one of the exits making
up "Frankfurter Kreuz" which is the major interchange near Frankfurt
and has its own (quite extensive) Wikipedia page:
https://de.wikipedia.org/wiki/Frankfurter_Kreuz
Yep, so in this case removing the name and keeping the ref on the
junction node sounds appropriate.
While we're at it, the service road
https://www.openstreetmap.org/way/48154169 doesn't seem to show up on
any of the current imagery in iD. Does it still exist?
--Jarek
On Mon, 5 Nov 2018 at
t; most likely to be already mapped. To a large degree, it's up the individual
> importer to do some quality control, review against existing object,
> satellite, etc. If we have specific issues we can and should address them,
> but if the data is largely good then I see no need to abort or revert.
&g
On Thu, 17 Jan 2019 at 21:46, OSM Volunteer stevea
wrote:
> Thanks, Jarek. Considering I am a proponent of "perfection must not be the
> enemy of good" (regarding OSM data entry), I think data which are "darn good,
> though not perfect" DO deserve to enter into OSM. Sometimes "darn good"
>
On Thu, 17 Jan 2019 at 21:04, OSM Volunteer stevea
wrote:
>> The import was discussed on talk-ca and in my opinion there was a consensus
>> of opinion it should go ahead. The data comes from the municipalities of
>> which there are some 37,000 separate ones in Canada. The idea of a single
>>
On Tue, 26 Mar 2019 at 13:10, Begin Daniel wrote:
> There is actually no standard “code” available since I use FME
> (www.safe.com). It is a proprietary ETL application and all operations are
> done using “transformers” (https://www.safe.com/transformers/). I can provide
> you with the
On Tue, 26 Mar 2019 at 11:58, Begin Daniel wrote:
> a first version of the cleaning tool is now functional.
>
> At this point, the tool is built to remove extra vertices, orthogonalize
> building footprints (when possible) and identify overlapped geometries.
> Details about the application are
On Fri, 15 Mar 2019 at 13:02, Nate Wessel wrote:
> Don't forget about the various alternative naming tags like alt_name=*,
> short_name=*, loc_name=*, and also name:etymology=* to make things absolutely
> clear.
>
> Having either spelling in one of these alternatives as appropriate would
>
Hi all,
A couple of months back we established a consensus [1] that "St." in
Canadian English city names should not be expanded.
I have been thinking of having the same for street names, and would
like to ask people's opinions.
My main motivation is St. Clair Avenue in Toronto. Every city
Hi Martijn,
I am around tomorrow afternoon. Where roughly will you be? If you have
a Meeetup.com account you can also try sending a message in
https://www.meetup.com/OpenStreetMap-Toronto as some people there
might be interested as well!
(sending to the list so others now meetup group has been
s no consensus on what is acceptable.
> After a request from a local group then I think that particular area can
> proceed.
>
> Quebec I think is being organised by Tim.
>
> Thanks John
>
> On Thu, 14 Mar 2019 at 18:56, Jarek Piórkowski wrote:
>>
>&
Are people aware that there are buildings being imported by
https://www.openstreetmap.org/user/huronavemapper (most recent 12
hours ago) and https://www.openstreetmap.org/user/hamptonavemapper
(most recent 5 days ago)?
I notice the wiki still says the import is on hold.
Thanks,
--Jarek
of Geography, PhD candidate in Urban Planning
> NateWessel.com
>
> On 3/14/19 7:42 PM, Jarek Piórkowski wrote:
>
> The changeset comment messages link to the Stats Canada import plan on
> the OSM wiki.
>
> I missed it but there were also some edits in Alberta
Hi Pierre,
Thanks for sending these out.
Can you briefly confirm what the "building.geojson",
"building_extring.geojson", "building_extring_orthogonal.geojson"
files represent? I'm not really familiar with the terms, perhaps
because I don't have much of a GIS or geometry background. Is the
On Mon, 13 May 2019 at 12:13, Clifford Snow wrote:
> A MAPS.ME user added 66 attractions [1] in a changeset that included
> Vancouver, Montreal and Vermont. While I visit Vancouver I'm not familiar
> with any of them. I left a changeset comment that has been replied to in the
> last 16 hours.
I would expect this to be the same as the many "1st Street", "Twenty
Second Street", "16A Street", or "96 Avenue" we have in English
Canada: we go by what is signed and the software adapts. Hardcoding a
special case mapping "1e Avenue" within Québec to pronunciation
"Première Avenue" would be
-9701
>
> On Jul 8, 2019, at 09:25, Jarek Piórkowski wrote:
>
> I don't know if that is the case here, but I've also seen objects
> straight-up missing from the cycle map layer. I think its import of new and
> changed ways is sometimes buggy.
> https://www.openstreetmap.
Hi Joshua,
Welcome to OSM, and thank you for your contributions!
To answer your first question: the non-building data sets (parks,
address points, bus stops, etc) are not currently importable without
further effort: we would have to get that exact licence (with text
including "City of Airdrie")
iki/Import/ODbL_Compatibility
--Jarek
On Tue, 23 Apr 2019 at 11:56, Joshua Kenney wrote:
>
> If I can obtain explicit permission from the city, would I still need to
> wait for the LWG approval?
>
> --Joshua
>
> On 2019-04-22 16:03, Jarek Piórkowski wrote:
> > Hi Joshua,
nist
[5] recipients on August 27: Undearius, zzptichka, DannyMcD, egli,
OttawaHiking, MaximusSayan
On Wed, 3 Apr 2019 at 21:11, Jarek Piórkowski wrote:
>
> Hi all,
>
> I'm responding to the saints discussion I started last month. (Finally -
> sorry.)
>
> Question: does anyone identi
ther 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
>
>
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
On Fri, 27 Sep 2019 at 11:45, john whelan wrote:
> I do know that a number of departments and agencies would like to use
> buildings and although they can use the open data sources using OSM would be
> more convenient.
Then you can encourage these agencies to urge Statcan to improve the
On Fri, 27 Sep 2019 at 20:43, John Whelan wrote:
> The Stat Can data comes directly from the municipalities so each municipality
> will have a different quality of data. The Microsoft and NR Can data maybe
> more consistent.
Statcan could improve the data and make it more consistent. On this
Yeah, Canada Post currently considers postal codes their commercial
data. Crowd-sourcing all or a substantial amount of full codes seems
infeasible. Crowd-sourcing the forward sortation areas (the first A1A)
seems difficult since verifiability is going to be a problem
especially around the edges
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
Hi Joan, this is the Canadian mailing list, not the Catalan one :)
Thanks,
--Jarek
On Sun, 3 Nov 2019 at 19:59, Joan Quintana wrote:
>
> Aquesta importació ha de ser fàcil, només són 25 parkings amb carsharing.
> El dubte és l'etiqueta.
> A [1] es proposa dues etiquetes:
>
> amenity=parking
>
Thanks for the summary, weeklyteam!
The tagging proposal
https://wiki.openstreetmap.org/wiki/Proposed_features/park_drive might
be of interest to Canadian mappers. It is intended to cover carpool
lots. At least in Ontario, many MTO carpool lots are tagged with
park_ride= (park & ride) and
Thanks for the summaries, Weekly Team!
Of particular interest should be the upcoming release of a game that
takes in data from OSM, which might sometimes result in edits adding
fake data for sake of having data in the game, as we saw with Pokémon
Go:
"The Scandinavian gaming website IGN Nordic
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 20
On Sun, 6 Oct 2019 at 12:23, weeklyteam wrote:
> The weekly round-up of OSM news, issue # 480,
> is now available online in English, giving as always a summary of all things
> happening in the openstreetmap world:
> http://www.weeklyosm.eu/en/archives/12433/
>
> Enjoy!
>
> Did you know that you
Just to add an opinion: I think this tag is a great idea.
I don't care as much for promoting OpenStreetMap in this case - I'm
not sure we have a critical density of surveyors to make this a
valuable resource in Canada or individual cities. And I'm not sure
this would be a great project to
For anyone interested, it appears the link for this week's news should
be https://weeklyosm.eu/archives/13839
On Sun, 18 Oct 2020 at 06:13, weeklyteam wrote:
>
> The weekly round-up of OSM news, issue # 534,
> is now available online in English, giving as always a summary of a lot of
> things
On Thu, 16 Jul 2020 at 11:30, Andrew Deng via Talk-ca
wrote:
> Hello, I believe Yonge Street in Toronto and York Region (Regional Road 1)
> should be tagged as highway=primary rather than highway=secondary as it is
> tagged now.
> Here are some reasons I believe why:
> 1) Yonge Street is
The limitation is generally licensing.
Openstreetmap can accept an import of data that is freely licensed, but the
criteria for "freely" are fairly strict - most Canadian cities' "open data"
don't meet it. If you're familiar with Creative Commons, the license will
likely have to be as free or
42 matches
Mail list logo