Re: [Talk-ca] Exit with name on node *and* destination

C'est un Import Canvec. Je ne sais pas quelle est la règle pour ces chemins de service de façon générale sur les autoroutes. Les ajoute-t-on systématiquement. Si oui, il faudrait ajouter access=no, et sans doute emergency=yes. Je vois une telle route de service 1km plus au sud, au km 10.   

Re: [Talk-ca] Exit with name on node *and* destination

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

[Talk-ca] hebdoOSM Nº 432 2018-10-23-2018-10-29

Bonjour, Le résumé hebdomadaire n° 432 de l'actualité OpenStreetMap vient de paraître *en français*. Un condensé à retrouver sur : http://www.weeklyosm.eu/fr/archives/10878/ Bonne lecture ! hebdoOSM ? Qui : https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages Où :

Re: [Talk-ca] Exit with name on node *and* destination

Je disais précédemment> Je ne sais pour les autres provinces, mais au Québec les no. de sorties > correspondent aux bornes kilométriques de la route (ici 15 pour km 15). > Il est plus informatif d'afficher le no de sortie (ref=15) Ici c'est sortie 11pour km 11, et non 15 comme j'ai dit

Re: [Talk-ca] Stats Canada new building outlines Open Data do we wish to import it?

Sounds good to me.  At least we have raised the issue and discussed it. Cheerio John James wrote on 2018-11-05 3:17 PM: As "Frederick Ramm" would say having external IDs is pointless when you can do a spatial join to see what is there and what is not On Nov. 5, 2018 3:05 p.m., "John Whelan"

Re: [Talk-ca] Exit with name on node *and* destination

Right, I also thought that was the (only) appropriate use for the name tag on junction nodes. What may be misleading is that the names on Junction nodes are rendered on the map, which may encourage people to use the destination as the junction name.. Martijn > On Nov 5, 2018, at 12:59 PM,

Re: [Talk-ca] Exit with name on node *and* destination

Je ne sais pour les autres provinces, mais au Québec les no. de sorties correspondent aux bornes kilométriques de la route (ici 15 pour km 15). Il est plus informatif d'afficher le no de sortie (ref=15) sur cette node et d'éviter d'ajouter le nom de chemin(s) de destination. La destination

Re: [Talk-ca] Stats Canada new building outlines Open Data do we wish to import it?

As "Frederick Ramm" would say having external IDs is pointless when you can do a spatial join to see what is there and what is not On Nov. 5, 2018 3:05 p.m., "John Whelan" wrote: Something that has come up in the Netherlands is they did an import then try to update the buildings once a month.

Re: [Talk-ca] Stats Canada new building outlines Open Data do we wish to import it?

Something that has come up in the Netherlands is they did an import then try to update the buildings once a month.  By having some sort of id tag on the building their feeling is it makes it much easier to pick out new buildings. On the technical side would we have such an id on the building

Re: [Talk-ca] Exit with name on node *and* destination

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

Re: [Talk-ca] Talk-ca Digest, Vol 129, Issue 15

My personal view is if we have a process that follows the rules available then at least there is more chance they will be followed and edits will not be reversed. I might note the buildings in Regina have amazing similar outlines to the ones made available via the Stats Canada file but I

Re: [Talk-ca] Talk-ca Digest, Vol 129, Issue 15

On Nov 5, 2018, at 7:29 AM, keith hartley wrote: > I saw it was a great job. But you're correct, I have no documentation on how > they did it. Licence process, wiki ( I feel Steve already yelling at his > computer) If you mean me, I'm saddened to hear that others think I "yell." Rather, my

Re: [Talk-ca] Talk-ca Digest, Vol 129, Issue 15

I saw it was a great job. But you're correct, I have no documentation on how they did it. Licence process, wiki ( I feel Steve already yelling at his computer) On Nov 5, 2018 9:24 AM, "john whelan" wrote: >Someone already did Regina! and that is an issue and why we need to get this lot

Re: [Talk-ca] Talk-ca Digest, Vol 129, Issue 15

>Someone already did Regina! and that is an issue and why we need to get this lot formalised quickly before someone starts talking about imports being done without the correct license. Cheerio John On Mon, 5 Nov 2018 at 10:15, keith hartley wrote: > Someone already did Regina! > > On Mon, Nov

Re: [Talk-ca] Talk-ca Digest, Vol 129, Issue 15

Someone already did Regina! On Mon, Nov 5, 2018, 9:06 AM James Saskatchewan has Regina data. That's it. > > It's totally dependent on cities contributing to the open data effort > > On Mon., Nov. 5, 2018, 9:21 a.m. keith hartley wrote: > >> Hi all, >> I'd love to do more imports - I have a

Re: [Talk-ca] Talk-ca Digest, Vol 129, Issue 15

Saskatchewan has Regina data. That's it. It's totally dependent on cities contributing to the open data effort On Mon., Nov. 5, 2018, 9:21 a.m. keith hartley Hi all, > I'd love to do more imports - I have a group here that we get together to > do mapping as well as know some locals. Of course

Re: [Talk-ca] Talk-ca Digest, Vol 129, Issue 15

Hi all, I'd love to do more imports - I have a group here that we get together to do mapping as well as know some locals. Of course we'd add a wiki to the MB page to show the project ect. From what I can tell there's no stats can data for manitoba or sask though! Keith