<html><body><div style="color:; background-color:; font-family:times new roman, new york, times, serif;font-size:12pt"><br><div><span>Les fichiers fixme me semblent très intéressants pour valider le contenu de la base OSM. Mon examen dans la région de Montréal m'a permis de constater rapidement divers endroits nécessitant des corrections.</span></div><div><br></div><div>Une petite note pour François et Nicolas. Lors de la comparaison du fichier Fixme de Canvec avec les données OSM, je ne peux pas facilement retrouver les attributs des ojbets que je veux modifier ou importer dans OSM. Par exemple, les ID dans le fichier 031H05.fixme sont différents des ID des 34 fichiers 031H05.*.osm et il est difficile de localiser et extraire cet objet. <br></div><div><br></div><div>Je vois deux solutions possibles pour facililter le travail de validation / correction. Soit les ID sont identiques, soit les attributs sont ajoutés directement dans le
fichier Fixme. Ce évidemment, en autant que ça ne crée pas des fichiers trop volumineux.</div><div><br></div><div><span>Merci beaucoup Daniel pour tout ce qui a été fait au cours des dernières années</span> et bon séjour à St-John.</div><span></span><div> </div><div><span style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;">Pierre <br></span></div><div> <br> <div>----- Mail original -----<br> > De : "Bégin, Daniel" <Daniel.Begin@RNCan-NRCan.gc.ca><br> > À : "talk-ca@openstreetmap.org" <talk-ca@openstreetmap.org><br> > Cc : <br> > Envoyé le : Mardi 31 juillet 2012 16h37<br> > Objet : Re: [Talk-ca] Fixme Files<br> > <br>> Bonjour Osmers<br>> <br>> First, a few personal news...<br>> I am currently transferring my files to François and Nicolas who will take over <br>> with the Openstreetmap community. François is already an Osm contributor and <br>>
Nicolas might soon be a contributor as well.<br>> <br>> This is not bad news for me as I will soon retire from NRCan and move to <br>> St-John's to start a PhD. As someone said ... "Go East Old Man!" - <br>> or something like this !-) <br>> <br>> Now, about fixme files...<br>> - As pointed out by Pnorman, some of the fixme files aren't zipped with <br>> related .osm : It will be fixed<br>> - The comparison isn't picking up on "highway=unclassified" : <br>> I'll see what can be done to make it run properly.<br>> <br>> Nicolas should work on it next week. Then, If the community agree, available <br>> fixme files will then be included with the corresponding Canvec.osm zip files.<br>> <br>> Finally, the entire Canvec content will eventually be processed the same way. I <br>> think it will be very helpful to the community and to NRCan!<br>> <br>> Cheers,<br>> Daniel <br>> <br>> <br>>
-----Original Message-----<br>> From: Adam Dunn [mailto:dunnadam@gmail.com] <br>> Sent: July 28, 2012 15:55<br>> To: Pierre Béland<br>> Cc: talk-ca@openstreetmap.org<br>> Subject: Re: [Talk-ca] Fixme Files<br>> <br>> Thanks for the mappaint style Pierre. That comes in very handy!<br>> <br>> (Following two paragraphs relate to 092G02.1.1.0, you will need to get correct <br>> Canvec files from main ftp, as the included files are incorrect, as pointed out <br>> by PNorman) Looks like the comparison isn't picking up on <br>> "highway=unclassified"?<br>> The notes tag doesn't specify unclassified as being covered, and this seems <br>> to be the case from the files. Take a look at this shopping mall<br>> area: <br>> [http://www.openstreetmap.org/?lat=49.192201&lon=-122.948192&zoom=18&layers=M].<br>> Both Canvec and OSM have the service roads marked as "unclassified", <br>> and are of equal
geometry (in fact, it is a GeoBase import that mbiker did), and <br>> yet they are marked as "committed" (missing in OSM).<br>> <br>> Across the highway to the south<br>> [http://www.openstreetmap.org/?lat=49.187566&lon=-122.945054&zoom=18&layers=M],<br>> there are several roads that are tagged "unclassified" in Canvec 10, <br>> but the tagging on OSM has been changed to "residential". The fixme <br>> file does not contain them (no changes necessary). It would appear that handling <br>> unclassified should be included or notification that it's a tagging issue, <br>> rather than a commit.<br>> <br>> (This is from 021I02.0.2.3)<br>> It also seems as though you are using newer Canvec data (11?) to generate the <br>> fixme file? Looking at random new residential area in Moncton <br>> [http://www.openstreetmap.org/?lat=46.071156&lon=-64.756724&zoom=18&layers=M],<br>> there are no roads in
OSM or the included Canvec files, but the Fixme file lists <br>> roads as being present. I guess this is a sneak preview of what will be coming <br>> in Canvec 11? The roads are partially constructed when looking at Bing imagery.<br>> <br>> So far this is some really really great information. Lets iron out the bugs and <br>> we'll have an awesome system to work with.<br>> <br>> Adam<br>> <br>> On Sat, Jul 28, 2012 at 12:00 PM, Pierre Béland <infosbelas-gps@yahoo.fr> <br>> wrote:<br>>> To facilitate the visualization of Canvec Fixme files and comparison <br>>> with OSM data in JOSM, I made a Custom Mappaint stylesheet and added <br>>> Imagery sources to the JOSM Imagery Sources.<br>>> <br>>> The file canvec-fixme.mapcss, enclosed in this message, highlights <br>>> objects with different colors based on the Fixme messages. This helps <br>>> distinguish the various warning
messages related to objects described <br>>> in the Canvec Fixme file.<br>>> <br>>> To use this Stylesheet, save it on your local disk and install it in <br>>> JOSM from the Mappaint Preferences menu. This will be added to the Map <br>>> Styles List.<br>>> <br>>> The objects are colored based on the Fixme message as described below :<br>>> <br>>> COLOR<br>>> <br>>> RED Commited - Canvec feature does not match any Osm feature.<br>>> Missing/Misclassified Osm feature?<br>>> GREEN Omited - Osm feature does not match any Canvec feature.<br>>> Missing/Misclassified Canvec feature?<br>>> BLUE Unmatched - OSM and Canvec geometries are significantly<br>>> different.Geometries need to be fixed?<br>>> YELLOW Attributed -
Osm and Canvec geometries matched but some common<br>>> attributes differ. Attributes need to be fixed?<br>>> <br>>> I also added Geobase / Canvec Imagery sources in the JOSM Wiki Map <br>>> page (https://josm.openstreetmap.de/wiki/Maps). To select these <br>>> Imagery sources in JOSM, select the WMS-TMS Preferences menu. Click <br>>> on the Refresh button at the right of the smallmap. Then, in the CA <br>>> section of the list of providers, you can activate Canvec, Geobase <br>>> Hydro or Geobase roads Imageries.<br>>> <br>>> I hope that both the stylesheet and the Imagery sources will simplify <br>>> the comparison of the Canvec Fixme files with the OSM database.<br>>> <br>>> <br>>> Pierre<br>>> <br>>> ________________________________<br>>> De : "Bégin, Daniel" <Daniel.Begin@RNCan-NRCan.gc.ca> À : <br>>>
"talk-ca@openstreetmap.org" <talk-ca@openstreetmap.org> <br>> Envoyé le : <br>>> Vendredi 27 juillet 2012 12h31 Objet : [Talk-ca] Fixme Files<br>>> <br>>> Bonjour,<br>>> <br>>> Here are some Fixme file samples for Calgary, Moncton, Montreal, <br>>> Ottawa, St-John's, Vancouver and Winnipeg <br>>> http://wiki.openstreetmap.org/wiki/CanVec:_Fixme_files<br>>> <br>>> <br>>> Please, have a look and comment on format/content to make it <br>>> appropriate for the community.<br>>> Good weekend!<br>>> <br>>> Daniel<br>>> <br>>> <br>>> <br>>> <br>>> _______________________________________________<br>>> Talk-ca mailing list<br>>> Talk-ca@openstreetmap.org<br>>> http://lists.openstreetmap.org/listinfo/talk-ca<br>>> <br>>> <br>>> <br>>>
_______________________________________________<br>>> Talk-ca mailing list<br>>> Talk-ca@openstreetmap.org<br>>> http://lists.openstreetmap.org/listinfo/talk-ca<br>>> <br>> <br>> _______________________________________________<br>> Talk-ca mailing list<br>> Talk-ca@openstreetmap.org<br>> http://lists.openstreetmap.org/listinfo/talk-ca<br>> <br>> _______________________________________________<br>> Talk-ca mailing list<br>> Talk-ca@openstreetmap.org<br>> http://lists.openstreetmap.org/listinfo/talk-ca<br>> </div> </div> </div></body></html>