<html 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 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing
{mso-style-priority:1;
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-GB link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNoSpacing>Probably the most complete river systems that is possible to create from the OSM source data.</p><p class=MsoNoSpacing>The subject has been discussed several times from my side but mostly inside the river area object class. At that time, I was just indicating cross water-area object class problems. Now, here is one option that resolves these problems as well. The complete river systems is generated from the latest OSM dump and can be downloaded from here:</p><p class=MsoNoSpacing><a href="https://drive.google.com/file/d/0B6qGm3k2qWHqNERVWmtVQUxYTUE/view?usp=sharing">https://drive.google.com/file/d/0B6qGm3k2qWHqNERVWmtVQUxYTUE/view?usp=sharing</a> </p><p class=MsoNoSpacing>You can use it as you like but please respect the OSM licencing rules. Note that in this presentation there are no missing objects caused by area overlaps and different contents (holes in one are not in the other one consequently not visible in any vector mapping system), no brakes caused by tagging river sections as lakes and so on.</p><p class=MsoNoSpacing>The following notes indicate the major processing skeleton and might be of certain interest for vector map-makers and those interested in heavy topology and polygon algebra issues. </p><p class=MsoNoSpacing>The extracted and used object classes are rivers (waterway=riverbank and natural=water + water=river), riverlines (waterway=river), lakes (natural=water and natural=water + water=lake) and the planet_land (the natural=coastline based land/water area objects).</p><p class=MsoNoSpacing>All these object classes are passing a robust data-preparation-tool-chain ending with simple objects. During this procedure more than 100K consecutive replicated nodes are removed, more than 10K corridor and exact replicated polylines are removed and so on. In addition, for area object classes, two polygon classes are extracted: P0 not being inside any other polygons and P1 all the other polygons. E.g. rivers_P0 are all the outer disjunctive polygons from the rivers simple area class while the rivers_P1 contains all corresponding holes, holes-in- holes, holes-in-holes-in-… After this, I have added to the rivers simple area class the following correction areas:</p><p class=MsoNoSpacing>-planet_land_P1 (1119) being inside at least in one of the rivers_P0 (120 cases),</p><p class=MsoNoSpacing>-planet_land_P0 being inside in one of the rivers_P0 (490 cases),</p><p class=MsoNoSpacing>-circular/closed riverlines, longish areas statistically similar to riverbanks (4645 cases),</p><p class=MsoNoSpacing>-longish lakes crossed alongside by a riverline (28692 cases) and </p><p class=MsoNoSpacing>-longish lakes neighbouring similar riverbanks (5560 cases).</p><p class=MsoNoSpacing>The recognition algorithms and especially the heuristic criteria used are complex and based on many, many experiments and on large samples.</p><p class=MsoNoSpacing>Now, the extended river area set is input to the create-area-coverage algorithm, which is doing defragmentation and creates a perfect coverage. Instead of river-fragments there are now river systems like the Mississippi, Amazonas, Danube, Volga… river systems presented as huge and complex areas/relations yet any in a simple area structure. These objects are, if necessary, input to a data generalisation (scale levels), tiling and so on. Unfortunately, there are several brakes on large river systems where obvious river sections are connected to large lakes incorrectly (yes I know, it is legal, but that is something else). These cases need manual intervention. This is yet to be done.</p><p class=MsoNoSpacing>Finally, just to mention, the lakes, riverlines, the planet_land/planet_sea are corrected in the similar way. E.g. the planet_land now contains only simple areas (with no holes at all) and from there the planet_sea (which is now the Global Ocean) is created just in several seconds.</p><p class=MsoNoSpacing>Regards, Sandor.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div></body></html>