<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-CA link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bonjour,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Well, I understand that multipolygons are often not easy to work with. However, from what I understand of OSM data model, they should be used whenever appropriate.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>In that sense, I do not agree with Bruno that 'inner' roles are useless for lakes in the case of wooded areas. It might be OK for rendering (you see lakes inside wooded areas because priorities have been used to create the map) but, IMHO, it is not the case if you work only on wooded areas – or any feature type!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>About Canvec, the product often duplicates water bodies and inner polygons of wooded areas; which is not necessary where both were imported. In order to keep only the necessary geometries, I usually transfer all the tags from a waterbody to the duplicated geometry of an inner polygon and then, I delete the original - now duplicated - waterbody.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>a humble two cents...<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Daniel<o:p></o:p></span></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Bruno Remy [mailto:bremy.qc.ca@gmail.com] <br><b>Sent:</b> September-15-14 12:59<br><b>To:</b> Tom Taylor<br><b>Cc:</b> Sam Dyck; Talk-CA OpenStreetMap<br><b>Subject:</b> Re: [Talk-ca] Large polygons in JOSM<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Tom's strategy seems to be appropriate for woods areas:<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Canvec 'giant monster' multipolygons represents a set of several polygons quite closed but not adjascent , mostly separated by meadow/scrub or fire cut-lines or rivers, or roads ....<o:p></o:p></p></div><div><p class=MsoNormal>By the way: membership as 'inside' role of wood multipolygon is useless for a lake<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>So, you never need 'outside' or 'inside' role: just keep outlines of wood.<br><br>Mapping this way avoid the use of multipoygons, and encourage the use of simple polygons (prefered).<br><br>(imo)<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Simplier is better ;)<o:p></o:p></p></div><div><p class=MsoNormal>But .... indeed.. i agree with Sam: is time consuming ! :(<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Perhaps a motivation to encourage membership of new OSM contributors, as we celebrate the 10th of OpenStreetMap !! ;-)<o:p></o:p></p></div><div><p class=MsoNormal>The more we are.. the less we do ;)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Bruno<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>2014-09-15 11:46 GMT-04:00 Tom Taylor <<a href="mailto:tom.taylor.stds@gmail.com" target="_blank">tom.taylor.stds@gmail.com</a>>:<o:p></o:p></p><p class=MsoNormal>Might be dull, but I generally split multipolygons into reasonably-sized adjacent chunks rather than giant monsters. In my case, it's usually when I'm outlining a river.<br><br>Tom Taylor<br><br>On 14/09/2014 10:29 PM, Sam Dyck wrote:<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>HI<br><br>Currently I'm working on importing the Canvec tiles that make up Lac<br>Seul in NW Ontario into OSM. Importing the data as it is, split into<br>tiles and subtiles, is poor practice, and manually merging is time<br>consuming and dull. So I began using JOSM's Join Overlapping Areas<br>feature. This tool however requires that all ways be complete before<br>merging. Resulting is a 100 000 node area that far exceeds JOSMs import<br>limit and is time consuming to split up, and slows down JOSM. Is there<br>an faster way to split this?<br><br>Sam<br><br><br>_______________________________________________<br>Talk-ca mailing list<br><a href="mailto:Talk-ca@openstreetmap.org" target="_blank">Talk-ca@openstreetmap.org</a><br><a href="https://lists.openstreetmap.org/listinfo/talk-ca" target="_blank">https://lists.openstreetmap.org/listinfo/talk-ca</a><o:p></o:p></p><p class=MsoNormal><br>_______________________________________________<br>Talk-ca mailing list<br><a href="mailto:Talk-ca@openstreetmap.org" target="_blank">Talk-ca@openstreetmap.org</a><br><a href="https://lists.openstreetmap.org/listinfo/talk-ca" target="_blank">https://lists.openstreetmap.org/listinfo/talk-ca</a><o:p></o:p></p></div><p class=MsoNormal><br><br clear=all><br>-- <br>Bruno Remy <o:p></o:p></p></div></div></body></html>