Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

Mon problème est dés le téléchargement. Cela m'indique que google ne peut effectuer l'analyse d'antivirus et m'offre de télécharger quand même. De là, message d'erreur.Voici le message avec Chrome Ce site ne peut pas fournir de connexion sécurisée doc-08-3g-docs.googleusercontent.com a envoyé

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

tar.xz c'est un fichier compressé contenant un fichier geojson(il se ouvre bien avec 7zip sur windows, ou n'importe quel program d'archive sur mac ou Linux), qui est servie via la Task Manager. Ce n'est pas la version originale de Stats Can, tu as raison, c'sst la version minifié sans les extras

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

James, Je pense que nous travaillons sur deux aspects différents. Tu te concentre sur la production / correction des fichiers d'import. A ma connaissance, tu n'a pas décrit le contenu dufichier ontario-simplified.tar.xz.  Je suppose que ce sont les données d'import originales où tu apportes

Re: [Talk-ca] OpenStreetMap, education and the buildings

Effectivement James, Comme ailleurs en Europe, les communautés OSM sont beaucoup plus organisées. La communauté OSM-France a mis en place des serveurs qui permettent l'accès à la carte OSM. On y retrouve aussi Osmose, uMap et l'hébergement du style humanitaire.  Au SOTM-Fr à chaque année, 

Re: [Talk-ca] OpenStreetMap, education and the buildings

Agreed but its part of a trend and perhaps needs a bit of planning. Cheerio John James wrote on 2019-01-19 8:46 PM: That's french: France. Not french: Québec On Sat., Jan. 19, 2019, 8:44 p.m. John Whelan wrote: From weeklyosm: Education

Re: [Talk-ca] OpenStreetMap, education and the buildings

That's french: France. Not french: Québec On Sat., Jan. 19, 2019, 8:44 p.m. John Whelan From weeklyosm: > Education > >- The new curriculum > > >(pdf) for French high

[Talk-ca] OpenStreetMap, education and the buildings

From weeklyosm: Education * The new curriculum (pdf) for French high schools states that all students should be introduced to geospatial data usage. One of the

[Talk-ca] weeklyOSM #443 2019-01-08-2019-01-14

The weekly round-up of OSM news, issue # 443, 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/11350/ Enjoy! weeklyOSM? who: https://wiki.openstreetmap.org/wiki/WeeklyOSM#Available_Languages

Re: [Talk-ca] Canada building import - Simplification discussion

Original(1.4GB file size): 9.263 Average points per feature Points:20346517 Features:2196329 Simplified (20cm) (1.2GB file size): 8.425 Average points per feature Points:18504036 Features:2196329 Simplified (40cm) (1.1GB file size): 8.07 Points:17741477 Features:2196329 For better statistics on

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

So my interpretation is we save about 9% by simplifying? However does it mean we probably do need to verify the before and after manually? Would someone care to comment on if we would need to manually look at the before and after and if 9% savings would be significant? My personal feeling would

[Talk-ca] Canada building import - Simplification discussion

I'm changing the subject line to try and retain some clarity for the mailing list. James, thanks for the stats! I'm surprised this didn't remove more points. Steve, I mentioned earlier that 20cm is where I happened to draw the line for the data we imported in Hamilton County, Ohio and I'm not

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

Resending because these emails are getting over 40KB in size and talk list is spazzing out: Original: 9.263 Average points per feature Points:20346517 Features:2196329 Simplified (20cm): 8.425 Average points per feature Points:18504036 Features:2196329

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

It appears the original discussion on talk-ca was missed by many. There appears to be an issue of local buy-in but I think for the moment we should first concentrate on the problems we expect to see. The building outlines we imported in Ottawa predated the Bing imagery I suspect. So first off

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

It seems that talk-ca works this way - long periods of silence, then a burst of emails because something went wrong! I just realized that this massive import of buildings started a few weeks ago and I'm surprised. I was trying to stay informed about the project because I was worried about how

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

Yeah, even going to 8 GB (-Xmx8192m on my java launch command line) I hang about halfway through opening "Loading json file." I'll try 16 GB (whew!) and QGIS next. Steve > On Jan 19, 2019, at 2:17 PM, James wrote: > > use qgis or launch josm with java in 64bit mode(d64) with memory options

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

use qgis or launch josm with java in 64bit mode(d64) with memory options (Xms, Xmx), or it will crap out at 3.5GB On Sat., Jan. 19, 2019, 5:13 p.m. OSM Volunteer stevea < stevea...@softworkers.com wrote: > On Jan 19, 2019, at 2:01 PM, James wrote: > > Is there no one that will analyse the data

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

Hi James, I for one will be happy to talk about the technical issues of simplification... though I think at the moment it seems to be taking a backseat here to bigger issues like building consensus around the validity of this import. Since this is a more technical issue, can I suggest that

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

On Jan 19, 2019, at 2:01 PM, James wrote: > Is there no one that will analyse the data I've posted here? > https://drive.google.com/file/d/1OK83yrPwMW4nefyu-6JsIInu0meK2rW6/view?usp=sharing > or are we just email thread warriors? Well, slow down there, cowboy, it is gigabytes of data and I've

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

Is there no one that will analyse the data I've posted here? https://drive.google.com/file/d/1OK83yrPwMW4nefyu-6JsIInu0meK2rW6/view?usp=sharing or are we just email thread warriors? On Sat., Jan. 19, 2019, 4:29 p.m. Pierre Béland via Talk-ca < talk-ca@openstreetmap.org wrote: > Voici une

Re: [Talk-ca] 2020 building import

On Jan 19, 2019, at 1:22 PM, john whelan wrote: > As a point of information the 2020 web page I think was started by Julia and > very heavily edited by Stevea. Sure I did, because it seriously lacked in the technical direction anybody would need to "map going forward" in the project/initiative

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

Voici une compilation statistique à partir des changesets de OSM pour la grande région de Toronto (bbox=-80.8951,42.9142,-78.1046,44.3297).  Depuis  Pour respecter la politique de confidentialité de OSM, les contributeurs ne sont identifiés que selon leur uid. Depuis décembre, on compte 6

[Talk-ca] 2020 building import

As a point of information the 2020 web page I think was started by Julia and very heavily edited by Stevea. I think we are now agreed that the 2020 project with its idea of mapping buildings in iD is not optimal. However Julia's style did make its mark with many students and educators and caught

Re: [Talk-ca] (no subject)

On Jan 19, 2019, at 10:48 AM, john whelan wrote: > There was an earlier discussion on talk-ca about how to handle this project. There were MANY. Speaking for myself only, I urged a very cautious, go-slow approach, to edit the data into "improvement / harmony-with-OSM" as much as possible

[Talk-ca] (no subject)

There was an earlier discussion on talk-ca about how to handle this project. It is similar to CANVEC in the original data sources are municipal data CANVEC uses a few other sources as well and it is released under exactly the same license but by a different federal government department. There

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

I was surprised this morning when I saw that a chunk of buildings had been imported in Victoria, BC. The changeset linked to the wiki plan and I then checked my email and saw this email chain. The "local" (in this case the Canadian community) has not been sufficiently consulted. Looking back

Re: [Talk-ca] Ongoing Canadian building import needs to be stopped, possibly reverted

Hi, Tangentially, I often remap areas with poor mapping and use the replace geometry tool. I estimate it adds about 5% time to the over all remapping effort, which is totally acceptable for the benefits of careful redoing and saving of object history and I encourage folks to use that way where

Re: [Talk-ca] 2020 building import wiki comment by Nate Wessel

I'm saying when the matter was first raised on the import mailing list as a heads up I made reference to the existing Ottawa pilot and gave a link basically saying we would be following the same pattern.  There was considerable discussion around the Ottawa import plan both on the import plan