Hi List. The terms of usage for the IENC data of the German IENC have finally been modified to fit the needs of OpenStreetMap: Now there has no source note to be attached, especially if the data has been modified.
So we intend to continue the manual insertion of buoys of the large German rivers into OSM from the IENC of the Water and Shipping Administration of the federal government (WSV). Terms of Use: Permission to import has been explicitly granted. The formulation of the Terms of Use has been specially adapted to the requirements of OpenStreeMap. Letter from WSV http://wiki.openstreetmap.org/w/images/c/c6/Terms_of_usage_ienc.pdf Terms of use: https://www.elwis.de/RIS-Telematik/Inland-ENC-der-WSV/index.html Procedure: The insertion is purely manually: From the source data, the relevant data are partially extracted and opened in JOSM. Here each node and each polygon is checked manually, especially if the object is probably already available. Possible duplicate nodes are not imported or merged, landmarks are transferred the on existing buildings. Inserted information: Inserted will be elements relevant for inland navigation such as fairway buoys, navigation signs (traffic signs) and the labeling of buildings as landmarks, e.g. smokestacks. At places where the riverbanks are "raw state" (very long straight lines or rough sawtooth pattern), we adapt the shore course (waterway = riverbank) in balance with the bing satellite image. OSM user: Uploading after manual correction is done with its own user "IENC import". Areas: The data are available for the following subsections waters in Germany: Berlin-Spandauer-Schifffahrtskanal Donau Dortmund-Ems-Kanal Elbe Elbe-Havel-Kanal Elbe-Seitenkanal Havel-Oder-Wasserstraße Main Main-Donau-Kanal Mittellandkanal Mosel Neckar Rhein Rhein-Herne-Kanal Ruhr Saar Spree-Oder-Wasserstraße (Teilabschnitt) Untere Havel-Wasserstraße (Spandau - Plaue) Wesel-Datteln-Kanal Weser Westoder Test: Data, tags and procedure have been tested on the Main. Object types: The following types of objects (seamark: type =) will be inserted: seamark:type=anchorage seamark:type=anchor_berth seamark:type=beacon_cardinal seamark:type=beacon_isolated_danger seamark:type=beacon_lateral seamark:type=beacon_safe_water seamark:type=beacon_special_purpose seamark:type=berth seamark:type=buoy_cardinal seamark:type=buoy_installation seamark:type=buoy_isolated_danger seamark:type=buoy_lateral seamark:type=buoy_safe_water seamark:type=buoy_special_purpose seamark:type=cable_submarine seamark:type=daymark seamark:type=fairway seamark:type=harbour seamark:type=landmark seamark:type=light seamark:type=light_major seamark:type=light_minor seamark:type=light_float seamark:type=light_vessel seamark:type=mooring seamark:type=navigation_line seamark:type=notice seamark:type=restricted_area seamark:type=signal_station_traffic seamark:type=signal_station_warning seamark:type=small_craft_facility seamark:type=topmark The supposed duplication between tags of pure objects (e.g. lighthouse manmade=lighthouse or building=church) and their meaning for navigation (e.g. seamark:type=light_major or seamark:type=landmark) has already been well discussed: Not every such objects has a significance for navigation. So it is not a redundancy, but a supplementary tagging. This applies in particular to harbor=yes/seamark:type=harbor and historic=wreck/seamark: type=wreck. Regards, Christian _______________________________________________ Imports mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports
