Re: [Talk-ca] French street names in Ottawa

2016-09-26 Thread Jonathan Crowe
I just did a quick check. On OSM, Rue/Chemin/Boulevard/etc. are capitalized in 
Montréal, Québec, Paris, Marseille, Besançon, Lille — and Gatineau. Ottawa is 
the *only* place I’m aware of where capitalizing Rue etc. is even a question.

I mean, Quebec highway exit signs capitalize Rue, Boulevard, Chemin and so 
forth. Drive any autoroute.

Which is to say that to me the evidence of existing usage elsewhere in the 
francophone world is pretty overwhelming. (For the record, I have been 
capitalizing Rue etc. in my edits.)

This is the second time this month that anglophones (generally) have been 
discussing how to deal with names in other languages (see also the Nunavut 
place names thread). I think we need to be *very* careful about that: there’s 
an excellent chance that we don’t know what we’re talking about.

Also, I have a hard time believing that search is so case-sensitive that 
capitalizing/not capitalizing Rue etc. would break it. (It’s broken in other 
ways: searching “boulevard cite des jeunes” does not yield Gatineau’s Boulevard 
de la Cité-des-Jeunes. But that’s another issue.)


Jonathan Crowe
The Map Room
http://www.maproomblog.com



> On Sep 26, 2016, at 11:51 AM, john whelan <jwhelan0...@gmail.com> wrote:
> 
> I was under the impression that the City of Ottawa named the streets, they 
> use lower case for rue.   I assumed since they named the streets they were 
> the authority. 
> 
> The entries were confirmed with a Francophone School teacher before being 
> added.
> 
> Originally about 97% of the highways in Ottawa had the French name added 
> following the Ottawa by-law.  These were all done in lower case.  There were 
> one or two street names that had odd names that were not covered by the 
> by-law and these did not have the French added.  
> 
> Now we have a mixture as people have changed the entry to upper case in 
> roughly 20% of the cases which is unfortunate as it impacts searching the 
> French street name entry by name.  We also have had a number of highways 
> added as Ottawa has grown which may or may not have had the French name added.
> 
> Reality is most users use the English version of the street name and most 
> rendering is done in English.  This is similar to many francophones in Ottawa 
> prefer to use English versions of software as they feel they are less likely 
> to have undocumented features.
> 
> I only know of two renderers that use the French name and they are a custom 
> set of rules I made for Maperitive and also they can be shown in OSMand with 
> the right settings.
> 
> Cheerio John
> 
> 
> 
> On 26 September 2016 at 10:55, Loïc Haméon <hame...@gmail.com> wrote:
> Please note the correct French name for rue Sparks is "rue Sparks" and not 
> "Rue Sparks"
> The first word is not capitalised.
> This was carefully verified before the names were added.
> Thanks John
> 
> 
> Hi John,
> 
> It's true that in French the generic element of place names (rue, avenue, 
> chemin, etc.) are normally not capitalized as part of a text or address 
> (http://www.btb.termiumplus.gc.ca/redac-srch?lang=fra=rue=9=14=3=3.3.8#zz3).
> 
> However, in maps, where the street name is usually shown independent of 
> anything else and this generic name is the first element of the "sentence", 
> it is usual for it to be capitalized. This is how they are entered in OSM in 
> Quebec 
> (http://www.openstreetmap.org/way/165217842#map=17/46.82211/-71.28523=D)
>  and also in other French maps, whether in Quebec 
> (http://carte.ville.quebec.qc.ca/carteinteractive/) or France 
> (https://www.viamichelin.fr/web/Cartes-plans/Carte_plan-Nantes-44000-Loire_Atlantique-France?strLocid=31NDJqejUxMGNORGN1TWpFM09EUT1jTFRFdU5UVTNNVFE9).
> 
> As the "rue" part is not considered a proper name, it is subject to 
> typographical change depending on the context of its use. Regardless of how 
> it appears on Ottawa street signs, given there is an overwhelming norm for 
> capitalization in maps, I would recommend you do the same in Ottawa. 
> 
> Cheers!
> 
> Loïc


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


Re: [Talk-ca] Ref tags in Ontario -- also Manitoba and Quebec

2015-06-29 Thread Jonathan Crowe
It's worth mentioning that prefixes have been added in other provinces as
well:

- R (for Route) and A (for Autoroute) in Quebec (e.g. A 40, R 148)
- PTH (Provincial Trunk Highway), PR (Provincial Route, i.e. secondary
road) and Route in Manitoba (e.g. PTH 15, PR 241, Route 90)

Other than Route for metro routes in Winnipeg, the highway shields can be
determined algorithmically (in Manitoba, anything above 199 is a Provincial
Route; in Quebec, everything below 100 and above 399 is an Autoroute);
outside of Winnipeg, there is no chance of confusion as to which route
marker to use, as there might be in Ontario.


-- 
Jonathan Crowe
http://www.jonathancrowe.net
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] ON prefix on Ontario highways

2015-02-28 Thread Jonathan Crowe
Prefixes aren't always necessary for rendering labels.

RR and CR labels are good in an Ontario context (I'd been putting a few in
manually in the Ottawa area before this user got to work -- I assume it's
automated?), because road numbers and highway numbers regularly overlap and
since not every Regional Route or County Route is a secondary road (see RR
174 east of Ottawa, a motorway, to say nothing of urban boulevards and
expressways that probably warrant being tagged as primary or even trunk
routes, despite not being provincial or NTS highways). But it's safe to say
that everything else in Ontario can be rendered as a King's Highway, if the
number is less than 144 or in the 400s. (Secondary routes have higher
numbers in the 500s and 600s.)

In Quebec, any route number less than 100 or more than 400 is an autoroute;
everything else gets the standard route shield. In Manitoba, provincial
roads are numbered 200 and up; anything 199 or lower is a trunk highway.
Similar rules apply in Alberta, Saskatchewan, New Brunswick and Nova
Scotia: the number indicates the class of route and related marker.

It's really only in Ontario that you need to specify what kind of route
marker should be applied, rather than inferring it from the number -- oh
yes, and in Winnipeg, with its numbered metro route system that overlaps
with provincial numbers.

B.C. has no secondary routes, though some highways (1, 3, 5, 16, 113) get
specialized route markers.


On Sat, Feb 28, 2015 at 11:10 AM, Duncan Hill dun...@soncan.ca wrote:

 It might make sense to have that info included. Perhaps it could use a
 separate tag and then renderers can choose how to label it.

 On Sat, Feb 28, 2015 at 10:56 AM, Andrew MacKinnon andrew...@gmail.com
 wrote:

 Also this user has been adding A to Quebec autoroutes, R to Quebec
 provincial highways, CR to Ontario county roads, etc.

 On Sat, Feb 28, 2015 at 10:46 AM, Andrew MacKinnon andrew...@gmail.com
 wrote:
  I've noticed that User:Zachary77F has been adding the prefix ON to a
  lot of provincial highways in Ontario. I am not sure whether this
  makes sense (looks kind of weird on the default Mapnik renderer)
  though this convention seems to be used in the US for state highways.
  Should I keep provincial highways tagged this way or should they be
  changed back to the way they were?

 ___
 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




-- 
Jonathan Crowe
http://www.jonathancrowe.net
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] Road designations

2014-12-11 Thread Jonathan Crowe
Your example road looks like an edit in progress: someone changing the road
from tertiary to secondary and leaving it unfinished. (Lord knows I've done
that plenty of times: starting an edit, discovering it's *much* bigger or
more complicated than I thought it was when I started it, and having to
stop midway through and come back to it later -- sometimes much later.)
Changing road types can be a messy process, especially when you're dealing
with a CanVec import that breaks the road into individual segments at each
intersection.

In the first case, the connection should be a secondary_link, not a
tertiary or tertiary_link, I think.

In the second case, it would be appropriate to continue the edit, changing
the rest of the road from one to the other, whichever you think is the best
type for the road in question.

The map is never in a finished state.



On Thu, Dec 11, 2014 at 9:10 AM, Adam Martin s.adam.mar...@gmail.com
wrote:

 I have a question for the group regarding the designation of various roads
 within city regions. Specifically, with reference to primary, secondary,
 and tertiary roads. What exactly is the criteria being used to designate a
 road as one or the other? I know that the wiki provides guidance, but it
 does not appear that the guidance is always followed.

 For example, this is an area inside Montreal:

 As you can see, there are two secondary one-way roads here (orange) and a
 yellow tertiary road connecting them together in the lower right. I cannot
 fathom why that roadway would be tertiary - it's just a simple connection
 between the roads and should likely not be considered tertiary. Especially
 given the guidance on the wiki *The highway
 http://wiki.openstreetmap.org/wiki/Key:highway=tertiary tag is used for
 roads connecting smaller settlements, and within large settlements for
 roads connecting local centres. In terms of the transportation network,
 OpenStreetMap tertiary roads commonly also connect minor streets to more
 major roads.*

 Here is another example along the same roadway in Montreal:

 Here we see a similar connection as before, but this one is designated as
 a residential road. But we also get to see a very interesting thing occur -
 the two one-way secondary roads suddenly transform into two tertiary
 one-way roads. The problem here is that there does not seem to be a reason
 for that changeover in the road type; the road continues as two one-way
 roads through the Parc industriel d'Anjou area. The position of the change
 also appears to be random or arbitrary.

 I'm seeking a bit of clarification. I like to be cautious with changing
 road types in regions just in case there is a reason I am not aware of for
 them to be designated in this way.

 Thanks,

 Adam

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




-- 
Jonathan Crowe
http://www.jonathancrowe.net
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] Validating existing data in Ottawa area

2012-12-03 Thread Jonathan Crowe
Tom, I've been doing some manual work on Aylmer based on Bing imagery and
my own traces. I suspect that every urban road has been messed with by me
at some point over the past couple of years. Let me know where your
concerns are. I'm really reluctant to contemplate a CanVec import overtop
work based on imagery and GPS traces.

Aylmer is part of Gatineau.

-- 
Jonathan Crowe
http://www.jonathancrowe.net
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-ca


[Talk-ca] Fwd: Autoroute 50 Gatineau - Thurso

2012-12-03 Thread Jonathan Crowe
Forgot to cc the group.

-- Forwarded message --
From: Jonathan Crowe jonathan.cr...@gmail.com
Date: 2012/12/3
Subject: Re: [Talk-ca] Autoroute 50 Gatineau - Thurso
To: Pierre Béland infosbelas-...@yahoo.fr


C'était moi qui l'ai fait. C'est une route proposée (highway=proposed) et
non en construction (highway=construction). J'étais capable d'y placer :
dans les images de haute resolution, la location probable de la deuxième
voie était évident. Je n'ai aucune information sur la commencement de la
construction de cette deuxième voie.


2012/12/3 Pierre Béland infosbelas-...@yahoo.fr

 Suite à la complétion de l'autoroute 50 en Outaouis, je constate qu'il y a
 encore une zone près de Buckingham où l'autoroute est uniquement à deux
 voix. En parallèle, on voit une section de route en construction. Est-ce
 que ça correspond à la réalité? Ou au contraire, est-ce que l'autoroute est
 complétée avec dans chaque direction un segment de deux voies?


 Pierre

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




-- 
Jonathan Crowe
http://www.jonathancrowe.net




-- 
Jonathan Crowe
http://www.jonathancrowe.net
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] Validating existing data in Ottawa area

2012-12-03 Thread Jonathan Crowe
In my experience the addr:interpolation ways imported from CanVec do not
have reliable geometries, particularly in new subdivisions in Aylmer. (See,
for example, the new stuff near Wilfrid-Lavigne, at the far north end of
the neighbourhood.) It's not just a matter of being shifted over a few
metres.

I coded the very approximate Aylmer boundary myself (knowledge:
unreliable best guess) as a suburb of Gatineau, which itself is not shown
yet on the map. Looking forward to the boundary data for Quebec.



On Mon, Dec 3, 2012 at 10:26 AM, Tom Taylor tom.taylor.s...@gmail.comwrote:

 OK, the particular spot I was concerned about for misalignment was above
 Alexandria Bay. It's a little neighbourhood off Ch. Lattion, including R.
 de la Spartan, R. de la Lobo, and R. de la Cortland. CanVec shows R. de la
 Sparta running further north and another street or two coming off it. One
 of us really needs to run a GPS trace through there.

 Further west a number of the streets are lacking names.

 Surely you'll need CanVec, if only to get the administrative boundaries of
 Gatineau. Is the region broken down into sub-regions, so Aylmer continues
 to exist?

 I'll add that I know how to get CanVec as images in JOSM, but I don't know
 how to get the encoded data.


 On 03/12/2012 10:08 AM, Jonathan Crowe wrote:

 Tom, I've been doing some manual work on Aylmer based on Bing imagery and
 my own traces. I suspect that every urban road has been messed with by me
 at some point over the past couple of years. Let me know where your
 concerns are. I'm really reluctant to contemplate a CanVec import overtop
 work based on imagery and GPS traces.

 Aylmer is part of Gatineau.




-- 
Jonathan Crowe
http://www.jonathancrowe.net
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] Demande de vérification, question concernant name=

2012-10-31 Thread Jonathan Crowe
I've been doing a lot of work in western Quebec where there are a
number of majority-English communities, and have been doing my best to
come up with a reasonable approach to which language is used in the
name= tag.

I've generally been defaulting to name=frenchname name:en=englishname,
except in a few places with an overwhelming English majority. In those
cases, on the grounds that names should follow local usage, I've been
using name=englishname name:fr=frenchname, being careful to ensure
that the name:fr tag always exists.

For example, in Shawville (my current home town), 70 percent of the
local population is unilingual anglophone (which I agree is
unfortunate) and the road signs are bilingual; I've been using English
names there (name=Centre Street, name:fr=Rue Centre), because that's
what the locals would use. Whereas in surrounding Clarendon, whose
population is just as anglo, the road signs are in French, and I've
been using French names (name=Chemin de Calumet, name:en=Calumet Road)
for the most part.

I've also been tagging institutions with the appropriate language,
e.g., English institutions like schools always have English names, and
provincial facilities like government offices and hospitals are still
named in French even if they're in an English-majority community. I've
been tagging natural features (lakes and streams) and provincial
highways in French as well. Otherwise, it's on a case-by-case basis.

Generally, then, I've been tagging provincial-level features (however
vaguely defined) in French, and local-level features based on local
usage. When in doubt I choose French.


On Wed, Oct 31, 2012 at 4:28 PM, Bruno Remy bremy.qc...@gmail.com wrote:
 Despite the fact that both english and french are used langages in Canada,
 province of Quebec defines french as most official langage; So i think we
 could set name=frenchname, name:en=englishname, and name:fr=frenchname.
 It could be quite tricky (or a nightmare ;-) ) to choose default langage by
 a pondaration beetween french/english communities.

 In my opinion, OpenStreetMap has not the ability, role, mission to arbitrary
 settle street names. This is probably most in the hands of the local
 administration (City, toponomy commision, and so on) .
 In other words: don't you think we should be the most transparent as we can?
 :-)

 Concerning the multi-langage signs, the best way to go should probably be
 tag as it appears on the road or even tag as it appears on the city's
 website (if map is available, of course).

 Bruno Remy

 Le 2012-10-31 15:50, Harald Kliems kli...@gmail.com a écrit :

 I've run into similar issues. Street signs vary a lot, sometimes on the
 same street, a good (and maybe extreme) example is Bord-du-Lac/Lakeshore on
 the West Island. There are English-only signs: http://goo.gl/maps/Q4wQR ,
 bilingual ones (that leave out the Drive in English)
 http://goo.gl/maps/0goaN , French-only http://goo.gl/maps/3fcnX and maybe
 even more variations. I don't know what official_name=* is for this street,
 and I'm also not sure what to put into name/name:en/name:fr in this case.

  Harald.


 2012/10/31 Andrew MacKinnon andrew...@gmail.com

  Par exemple, un parc devrait-til être name=Jarry Park et
  name:fr=Parc
  Jarry ou simplement name=Parc Jarry? En utilisant OSMAnd~ sur
  Android
  j'ai pensé à ça car ce logiciel offre d'afficher les tags en anglais ou
  autres. Peut être avec un autre niveau d'impact, est-ce qu'on doit
  utiliser name=Park Avenue et name:fr=Avenue du Parc pour des rues
  aussi ou simplement name=Avenue du Parc? Avant d'en corriger
  systématiquement lorsque j'en vois je voulais demander l'avis ici.

 Car on est au Québec le nom officiel serait en français, donc je
 mettrais name=nom en français, name:fr=nom en français,
 name:en=English name. Le nom en anglais est probablement
 non-officiel et n'est pas signé (peut-être il est signé dans les
 communautés anglophone tels que Westmount et l'Ouest de l'Île mais le
 gouverment PQ veut probablement l'éliminer). Si le nom anglais est
 signé je mettrais name=nom en français/English name ou si c'est une
 rue avenue du Parc Avenue, autrement je mettrais le nom en français
 seulement dans name=*.

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




 --
 Please use encrypted communication whenever possible!
 Key-ID: 0x199DC50F

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


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




-- 
Jonathan Crowe
http://www.jonathancrowe.net

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


Re: [Talk-ca] Re : Images satellite Bing Montréal et Québec

2012-06-14 Thread Jonathan Crowe
Je pourrai ajouter qu'il y a aussi des nouvelles images dans
l'Outaouais : non seulement à Gatineau, mais aussi dans le MRC de
Pontiac (Shawville, Campbell's-Bay), où il n'y avait pas eu des images
à haute resolution avant celles-ci.

La correspondence entre ces images et la carte crée par mes traces GPS
est très proche. Ou, plus précisement, était très proche, parce que
j'ai déjà commencé à refaire la carte ici avec plus de détail.


2012/6/14 Pierre Béland infosbelas-...@yahoo.fr:
 Effectivement,

 comme je le disais dans le message précédent, en anglais, j'ai découvert
 hier de nouvelles images pour pratiquement toute la vallée du Richelieu,
 Bromont et Sherbrooke.


 Ce sont des images de très bonne qualité.  Quel plaisir de pouvoir tracer  à
 partir de ces images. J'ai ajouté plusieurs traces récemment dans la vallée
 du Haut-Richelieu que je peux maintenant mieux aligner à l'aide de
 l'Imagerie Google.

 Pierre

 
 De : Bruno Remy bremy.qc...@gmail.com
 À : talk-ca@openstreetmap.org
 Envoyé le : Jeudi 14 juin 2012 14h22
 Objet : Re: [Talk-ca] Images satellite Bing Montréal et Québec

 Openstreetmap a annoncé sur son tweeter il y a quelques jour, la publication
 de nouvelles cartes détaillées de BING dans certaines regions du canada
 je n'ai pas vu de différence à Québec mais peut-être que St-hilaire n'est
 plus la seule exception hors de ces deux grandes villes ;-)


 Le 7 juin 2012 09:23, Harald Kliems kli...@gmail.com a écrit :

 Just to add to this:
 in the Montreal area the alignment of the Bing imagery in my
 experience is very good. It is nonetheless a good idea to always also
 download the GPS tracks and make sure the images match those (and the
 Canvec import data).

 Harald (who has done a lot of aerial imagery-supported mapping in the
 Montreal area)

 2012/6/6 Pierre Béland infosbelas-...@yahoo.fr:
 Pour ceux intéressés à cartographier dans la région de Montréal et de
 Québec, notez que l'imagerie Bing est très détaillée à Montréal et Québec.
 À Montréal, cette couverture s'étend sur une partie de la rive-sud et de
 la
 rive nord. Ne pas oublier d'indiquer source=Bing si vous utilisez ces
 images.

 Pour obtenir les images de haute résolution, il faut zoomer en détail.
 Puis
 soudainement, les images de très basse résolution sont remplacées par les
 images de meilleure qualité. Curieusement, la région du mont St-Hilaire
 est
 aussi couverte.

 Es-ce que quelqu'un connait l'étendue de ces images de haute résolution et
 les plans de Microsoft à cet égard ?

 Pierre

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




 --
 Please use encrypted communication whenever possible!
 Key-ID: 0x199DC50F

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




 --
 Bruno Remy

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



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




-- 
Jonathan Crowe
http://www.jonathancrowe.net

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


Re: [Talk-ca] Some french translation advice

2012-01-22 Thread Jonathan Crowe
In practice, people are much more likely to use Highway 59 rather
than Provincial Trunk Highway 59. Even if the latter is the formally
correct name, it's extremely cumbersome and stilted; can you imagine
it in text-to-speech driving directions?

For French names of Manitoba highways, I'd consider using Route, as
is done in Quebec -- i.e., if name:en=Highway 59, then name:fr=Route
59. But what is the Franco-Manitoban practice? That's what should
determine it.

Other points: Provincial Trunk Highway would be wrong for 1, 16, 100
and 101; I'd use Trans-Canada Highway for 1 (except where it's a
street), Yellowhead Highway for 16, and Perimeter Highway for 100
and 101.

(I seem to have become a descriptivist rather than a prescriptivist.
We're making a map for people to use, not a GIS with precise
definitions.)

Note that provincial roads begin at 200. 110 is a trunk highway.

Also note that highways frequently have street names, especially when
passing through towns, but also sometimes in nominally rural areas. A
plugin might break all kinds of correct names.


On Sat, Jan 21, 2012 at 5:53 PM, Daniel Begin jfd...@hotmail.com wrote:
 Bonjour Tyler,

 I don't know the best practices about naming roads when a road is not really
 named like Tyler Gunn Trunk Highway. I prefer not adding any name tag when
 the name tag would actually be a combination of other tags and context as
 you suggest...

 Context: with few exceptions, all Canadian roads are provincial or municipal
 tag highway=trunk
 tag ref=99

 then, a name=Provincial Trunk Highway 99 tag seems a bit artificial for
 me.

 However, to answer your questions
 - Provincial Trunk Highway XY: As there is no real translation for trunk in
 this context, so I would suggest route provinciale XY
 - Provincial Road XYX: I would suggest route provinciale XYX

 Best regards
 Daniel

 -Original Message-
 From: Tyler Gunn [mailto:ty...@egunn.com]
 Sent: January-11-12 10:53
 To: Talk-CA OpenStreetMap
 Subject: [Talk-ca] Some french translation advice

 I'm working on a JOSM plugin to help rename/reclassify provincial
 roads and provincial trunk highways in Manitoba in the Canvec data.
 The goal is to enforce a common naming for PRs and PTHs in MB.

 Generally, highways with ref=0-99 are considered Provincial Trunk
 Highways, and as such I've got the following names:
 EN: Provincial Trunk Highway XY
 FR: route provinciale à grande circulation XY

 Generally, highways with ref99 are considered Provincial Roads, as
 as such I've got the following names:
 EN = Provincial Road XYX
 FR = route provinciale secondaire XYZ

 These are the french translations I could come up with, given my very
 limited understanding of the French language.

 Could someone proof these for me and let me know if I'm completely off base?

 Thanks,
 Tyler



-- 
Jonathan Crowe
http://www.jonathancrowe.net

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


Re: [Talk-ca] CanVec Imports

2011-12-15 Thread Jonathan Crowe
I've done this sort of thing when my edit changes something so
significantly that it no longer resembles what was imported -- for
example, rerouting a way to conform with Bing imagery or with my own
local knowledge. By the time I'm done with it, it's no longer Canvec;
in some cases I've actually deleted the Canvec and traced something
new over Bing imagery. I've been less good at updating the source tag
to reflect the source of the changes (e.g., knowledge, Bing, survey,
etc.).



On Thu, Dec 15, 2011 at 1:32 PM, john whelan jwhelan0...@gmail.com wrote:

 Why would someone remove a tag that says Canvec import?

 They had added a cycle lane but removed the Canvec Import tag at the same 
 time.

 Thanks John

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




--
Jonathan Crowe
http://www.jonathancrowe.net

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


Re: [Talk-ca] What should a Canadian style map look like?

2011-09-12 Thread Jonathan Crowe
I agree with most of these suggestions. OSM should render in a manner
familiar to Canadian map readers. Road colours should be limited to indicate
primary/trunk and secondary/county roads (in practice, that should probably
mean no distinction between highway=primary and highway=trunk -- like
Matthew, I don't think green works well, especially in a heavily forested
country). Road surface should be indicated. Add to that another: toll
highways, which are usually indicated on North American maps.

The question of long-distance northern roads is a question of information
density. At low zooms, the Canadian map can seem pretty empty if we follow
rules appropriate to higher density countries (Guten Tag, Deutschland). Is
there a way of changing the rendering threshold for, say, towns so that
empty parts of the map would have smaller centres rendered?

Generally speaking, I find too much of interest disappears when you zoom
out. Points of interest (historic, tourism) only really appear at the
highest zoom levels, and that's less useful in places where the point of
interest is outside the nearest town (e.g., the Royal Tyrrell Museum).

As for rendering things like railways and trails, that hinges on the
question of what the map is used for -- i.e., why people are using the map.
No one map can cover everything at once: a road map makes a lousy cycling
map, and so on. That's where layers come in. But it'll be hard to figure out
what information is important without some idea of why people are using the
map -- we're still in building mode at this point, I think, so the answer is
still to come.

-- 
Jonathan Crowe
http://www.jonathancrowe.net
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-ca


[Talk-ca] North of Regina SK

2011-08-26 Thread Jonathan Crowe
Not quite sure what happened here, but I'm reasonably sure than 99 percent
of this does not in fact exist:

http://osm.org/go/WmKBuFO


-- 
Jonathan Crowe
http://www.jonathancrowe.net
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-ca


Re: [Talk-ca] Ping John Whelan?

2011-06-07 Thread Jonathan Crowe
John is missing the point, perhaps deliberately. He hasn't listened to
a thing we've said. He's just justifying and rationalizing his
original decision.

There's no point in discussing this any further. He doesn't get it and
he never will. We're wasting time here. Treat his edits as vandalism
and proceed accordingly.

http://wiki.openstreetmap.org/wiki/Vandalism
http://wiki.openstreetmap.org/wiki/Change_rollback


-- 
Jonathan Crowe
The Map Room: A Weblog About Maps
http://www.maproomblog.com

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


Re: [Talk-ca] Ping John Whelan?

2011-06-06 Thread Jonathan Crowe
It's not up to John to determine, privately and unilaterally, what is
and isn't acceptable vis-à-vis CanVec and OSM. If he has a legitimate
concern, he should bring that concern to the attention of the OSM
community and have it thoroughly discussed -- and, you know, maybe
WARN US that he's going to be doing this -- rather than deciding to
take it upon himself to delete a substantial portion of the map of
Canada's capital city.

This is vandalism, pure and simple. As if the Ottawa OSM map wasn't
already in bad enough shape.

-- 
Jonathan Crowe
The Map Room: A Weblog About Maps
http://www.maproomblog.com

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


Re: [Talk-ca] Ping John Whelan?

2011-06-06 Thread Jonathan Crowe
Revert, revert, revert.

You can't decide, once the house is built, that you're taking back the
bricks you contributed to it.

Reimporting CanVec atop existing edits would cause all sorts of
trouble. The remaining, undeleted edits would be superimposed. I would
have thought John would know that by now, considering what happened
last February when he deleted my edits in Gatineau in favour of his
CanVec imports.

We've already have double or even triple layers of CanVec data in the
Ottawa area because of previous bad imports.

-- 
Jonathan Crowe
The Map Room: A Weblog About Maps
http://www.maproomblog.com

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


[Talk-ca] Ottawa River rendering: my bad

2011-04-28 Thread Jonathan Crowe
A while back I split the riverbank way for the Ottawa River through
Ottawa-Gatineau because my edits to said way exceeded the 2,000-node
limit. Looks like I didn't close one of the new ways, which meant that
tracts of the river west of the Champlain Bridge started disappearing.

I *think* I've fixed that now, and the river should render properly
when the tiles update. Sorry about that.


-- 
Jonathan Crowe
The Map Room: A Weblog About Maps
http://www.maproomblog.com

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


Re: [Talk-ca] Revert in Aylmer is complete

2011-02-23 Thread Jonathan Crowe
Richard, thank you. The reversion is coming up in Mapnik now -- I
didn't have to check in an editor after all -- and things look back to
normal as far as I can tell. If there are glitches, they can't be very
widespread.

I notice that the addr:interpolation ways are still there, which all
in all I think is a good thing. They can be a little off in some of
the newer developments (e.g., around Wilfrid-Lavigne north of
Allumettières); older streets match up better with the
addr:interpolation ways. And it's somewhat ghostly to see them where
there are no streets. These are things that can be tweaked manually --
but still less work than we would otherwise have faced. [1]

I'm reluctant to trace in street ways between the ghost
addr:interpolation ways without confirming on the ground the existence
of the street, in case the imported data includes streets on the
drawing boards that have not yet been built (which I spotted in at
least a couple of areas, unless the City of Gatineau has been busy
over the winter). I plan on surveying these streets in the spring,
unless someone else who lives closer beats me to it.

[1] http://osm.org/go/cIhDQbn1M-

Jonathan Crowe
The Map Room: A Weblog About Maps
http://www.maproomblog.com

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


[Talk-ca] Aylmer/Hull QC: CanVec import overwriting existing edits

2011-02-19 Thread Jonathan Crowe
This is rather discouraging and frustrating.

When the Bing imagery was made available, I spent a fair amount of
time cleaning up the maps in Aylmer, Quebec, a western suburb of
Gatineau. Just discovered that my edits have been overwritten by
another user importing CanVec data.

This import has introduced hundreds of errors:

- Proposed and under-construction streets are shown as completed.
- Streets are tagged as unclassified.
- Service roads have been removed altogether.
- Turning circles and traffic signals are missing.
- Certain streets do not line up with high-resolution Bing imagery,
and not in an off-by-a-few-metres way -- for example, the Bing image
has a subtle S-curve, the CanVec data has a rather crude straight line
bisecting the curve.

This means that Aylmer now needs dozens of person-hours to get it back
to where it was -- and at this point I'm discouraged enough to say the
hell with this project and find something better to do with my spare
time.

Much of Ottawa is in a similar state: manual edits superimposed with
CanVec imports that may or may not have been more accurate, and now
there are two or three duplicates on top of one another. It's a mess,
and it's in no way ready for MapQuest.

I thought CanVec imports were frowned upon when there was existing road data?

I'll tell you this: this is not the way to encourage people to
contribute, if all the work we do with imagery is subject to
obliteration by someone else's work with government vector data.

Yours in frustration,

Jonathan Crowe
The Map Room: A Weblog About Maps
http://www.maproomblog.com/

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