|This tag outlines known errors in respect to this seamark which|
|Used on these elements|
|Tools for this tag|
seamark:fixme=* is used in combination with OpenSeaMap/Lights Data Model to describe errors which are known and should be corrected manually. Many lights of Openseamap are imported automatically (see OpenSeaMap/List_of_Lights_Import). During parsing the raw data several errors may occur. Some of them are detected automatically but cannot be corrected by software. The reason for those errors is either because the parser incorrectly detected something or because of syntax errors within the original data. The data source of all lights is the List of Lights published by the US NGA as PDF documents. In the following we will refer to this list just as the LoL.
Note that the original documents are republished once a year thereby containing corrections. Thus, errors may change or may be fixed. All tagged errors refer to a specific version of the original documents. The origin and date of issue is kept within the source=* tag.
In JOSM SeaMapEditor all unverified lights objects are marked with a yellow star. This requires that the SeaMapEditor be loaded:
JOSM Edit menu, select "Settings" icon "socket" (plugins), click plugin "SeaMapEditor" check-box, "OK" and restart JOSM.
The positions items in the List of Lights are given to the nearest 1/10 minute, so they may have a positional error of 180m or more. Sometimes the data is not based on WGS84, and can result in positional errors of several hundred metres.
In the Lights-FIXME-Chart you find all lights waiting for the right position...
Walk aroud the coast:
- from z=6 you will see the light
Change to OpenSeaMap to look for lights:
- in z=10..18 you will see the lights
- in z=14..18 you will see "Check Position" (if there is)
Zoom in to z=18, select in the OpenSeaMap-menu (JOSM already started) "Edit by JOSM remote"
Select in JOSM in the menu "background" the "Bing" aero photos.
Move the light to the right position,
and delete the tag "please fix position".
The chart will be updated weekly.
Where there is already a mapped feature such as a man_made=lighthouse but without any OpenSeaMap tags, it must be merged with the imported lights object. In this case, the man_made=lighthouse can be taken to be in the correct position, and the imported seamark:type=light_major would have the correct seamark tagging:
- Search the coast for a man_made=lighthouse.
- Check with aerial photographs, whether the position is exact.
- Look for the matching "yellow star" it will most likely be a seamark:type=light_major very often it may have a seamark:longname=* tag which helps to compare or the tower height in a seamark:landmark:height=* tag or the height of the light in seamark:light:height=* may help.
If there are other yellow stars within 1-2km, examine them all to be certain that the correct match has been made.
- be sure to have closed the sector window, if not close it.
- Copy the yellow star with
- Select the man_made=lighthouse and use
<Shift-Ctrl-v>to add all the properties automatically.
- When you have verified that the position accuracy is within 20m (from accurate aerial images, local knowledge or survey), then delete the tag seamark:fixme=please_fix_position in the completed light and this will change the icon from the yellow star to light_major or light_minor black star.
- Erase the star no longer needed, and upload the result.
The errors sould be listed as a comma separated list.
|beacon_guess||If a seamark is detected to be a lateral mark but not class (buoy, beacon,
float,...) was found it is assumed to be a beacon but this may be wrong.
|height||The height according to column 5 of LoL seems to be detected incorrectly.|
|intdup||Column 1 of the LoL contains more then 1 light with this international
|name_incomplete||All names within the LoL end with a period otherwise it is tagged like
this. The names are contained within column 2 of LoL.
|please_fix_position||The LoL has a data accuracy of not more than 185 meters, hence, all lights
should be positioned accurately by hand. This attribute is set by default as long as it was not repositioned accurately.
|rem_incomplete||This is the same as name_incomplete but in respect to the Remarks
which is column 8 of LoL.
|usldup||Some lights have no international reference ID assigned but just an internal
number of the US NGA. If several lights with the same number exist, they are tagged like this.
If you like to care for an area:
|Malcolm||Pub114 (Great Britain, North Sea)||114|
|Date||Lights||FIXME||diff FIXME||cum||OK %||Remarks|
|2013-01-04||46'845||28'211||1671||1671||39,8||400 new lights|
|2013-08-01||46'063||25'380||89||4502||44,9||lights coninouesly decreasing|
|2014-01-28||44.985||23.406||129||6476||48,0||100 new lights|
|2014-04-23||41.663||19.223||3965||10.659||53,9||3281 lights deleted in 2 months|
|2014-05-21||41.369||18.700||523||11.182||54,8||294 lights deleted|
|2014-06-04||41.196||18:345||355||11.537||55,5||173 lights deleted|
|2014-06-30||41.171||17.707||648||12.175||57,0||25 lights deleted|
|2014-08-10||40.480||16.187||1520||13.695||56,3||691 lights deleted|
|2014-08-30||39.361||14.148||2039||15.734||58,9||1119 lights deleted|
|2014-10-17||39.311||13.3418||807||16.541||64,0||50 lights deleted|
|2014-11-08||39.146||13.086||255||16.796||65,9||165 lights deleted|
|2014-11-24||38.866||12.680||460||17.202||66,3||280 lights deleted|
|2015-01-07||38.331||11.704||976||18.178||66,9||535 lights deleted|
|2015-02-01||38.076||11.394||310||18.488||69,3||255 lights deleted|
|2015-03-11||27.982||1.258||10.136||28.684||59,3||10.094 lights deleted|
|2016-03-031||30.068||9||1.116||29.873||96,3||2.000 new lights|
|Date||Lights||FIXME||diff FIXME||cum||OK %||Remarks|
|diff FIXME||seamark:fixme=please_fix_position (old) - seamark:fixme=please_fix_position (new)|
|cum||Fixed lights since import|
|OK %||(lights - seamark:fixme=please_fix_position) / lights|
During the OSM-licence change 2012 there was deleted som lights by a bot "OSMF Redaction Account".
See this Example
We lost more than 7000 lights by some unknown deleters. See Progress.