Opened 7 years ago
Closed 7 years ago
#14158 closed defect (fixed)
erroneous warning on preferred_channel_* buoys in IALA region A
Reported by: | AdVerburg | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | External rule | Version: | |
Keywords: | template_report | Cc: | malcolmh |
Description
What steps will reproduce the problem?
- open an area containing a "red;green;red" buoy, for instance @ 53.455964, 5.543914 This buoy has the tag seamark:buoy_lateral:system=iala-a
- change something on that buoy, for instance add or remove a radar reflector
- try to upload this change, the warning "Probably wrong category on buoy_lateral, green;red;green colour mean preferred_channel_starboard in iala-a (1)"
- do NOT actually upload this change.
What is the expected result?
an upload and no warning
What happens instead?
An erroneous warning because a red;green;red buoy is a preferred_channel_PORT in iala region A
Please provide any additional information below. Attach a screenshot if possible.
A similar problem for a red;green;red buoy there comes the warning: "Probably wrong category on buoy_lateral, red;green;red colour mean preferred_channel_port in iala-a (1)"
Actually a red;green;red colour means preferred_channel_starboard in iala-a.
This phenomena does not happen with buoys with the tag seamark:buoy_lateral:system='''cevni
The wiki explanation buoyage system: http://wiki.openstreetmap.org/wiki/Seamarks/CEVNI_Lateral_Marks
URL:http://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2016-11-06 20:18:38 +0100 (Sun, 06 Nov 2016) Build-Date:2016-11-06 21:45:03 Revision:11223 Relative:URL: ^/trunk Identification: JOSM/1.5 (11223 en_GB) Linux openSUSE Tumbleweed Memory Usage: 1006 MB / 1756 MB (150 MB allocated, but free) Java version: 1.8.0_111-b14, Oracle Corporation, OpenJDK 64-Bit Server VM Screen: :0.0 1920x1080 Maximum Screen Size: 1920x1080 Java package: java-1_8_0-openjdk:x86_64-1.8.0.111 Dataset consistency test: No problems found Plugins: + ImportImagePlugin (33028) + Mapillary (v1.3.2) + PicLayer (33088) + SeaChart (33007) + SeaMapEditor (33054) + apache-commons (32994) + apache-http (32699) + ejml (32680) + geotools (33042) + graphview (33004) + jts (32699) + log4j (32699) + measurement (33088) + osmarender (33004) + reverter (33088) + tageditor (33021) + turnlanes (33088) + turnlanes-tagging (254) + turnrestrictions (33088) Tagging presets: + https://raw.githubusercontent.com/OpenNauticalChart/josm/master/Presets_Hafen.xml + https://josm.openstreetmap.de/josmfile?page=Presets/OpenSeaMap_bridge&zip=1 + https://raw.githubusercontent.com/OpenNauticalChart/josm/master/INT-1-preset.xml + https://raw.githubusercontent.com/OpenSeaMap/josm/master/Presets_Sport.xml + https://josm.openstreetmap.de/josmfile?page=Presets/OpenSeaMap-PresetForSeamarks&zip=1 + https://raw.githubusercontent.com/yopaseopor/traffic_signs_preset_JOSM/master/NL.zip Map paint styles: + https://raw.githubusercontent.com/OpenSeaMap/josm/master/INT1_MapCSS.mapcss + http://duinoord.home.xs4all.nl/OSM/JOSM/NL_traffic_signs/Styles_Traffic_signs-style.mapcss + https://josm.openstreetmap.de/josmfile?page=Styles/Lane_features&zip=1 - https://josm.openstreetmap.de/josmfile?page=Styles/Lane_features_ryg&zip=1 Validator rules: + https://raw.githubusercontent.com/OpenSeaMap/josm/master/Seamark.validator.mapcss Last errors/warnings: - E: Failed to locate image 'images/icon.png' - W: Mappaint style "standard" (Verkeersborden) icon "images/icon.png" not found. - E: Handled by bug report queue: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException. Cause: java.lang.reflect.InvocationTargetException. Cause: org.openstreetmap.josm.data.osm.DataIntegrityProblemException: Primitive must be part of the dataset: {Node id=-19 version=0 MV lat=-51.386167,lon=3.618333} - E: Handled by bug report queue: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException. Cause: java.lang.reflect.InvocationTargetException. Cause: org.openstreetmap.josm.data.osm.DataIntegrityProblemException: Primitive must be part of the dataset: {Node id=-22 version=0 MV lat=51.386167,lon=3.618333} - E: Handled by bug report queue: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException. Cause: java.lang.reflect.InvocationTargetException. Cause: org.openstreetmap.josm.data.osm.DataIntegrityProblemException: Primitive must be part of the dataset: {Node id=-67 version=0 MV lat=51.38518771209332,lon=3.6197222957518007} - E: Handled by bug report queue: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException. Cause: java.lang.reflect.InvocationTargetException. Cause: org.openstreetmap.josm.data.osm.DataIntegrityProblemException: Primitive must be part of the dataset: {Node id=-68 version=0 MV lat=53.362,lon=5.414167} - E: Handled by bug report queue: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException. Cause: java.lang.reflect.InvocationTargetException. Cause: org.openstreetmap.josm.data.osm.DataIntegrityProblemException: Primitive must be part of the dataset: {Node id=-69 version=0 MV lat=53.359,lon=5.4135} - E: Handled by bug report queue: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException. Cause: java.lang.reflect.InvocationTargetException. Cause: org.openstreetmap.josm.data.osm.DataIntegrityProblemException: Primitive must be part of the dataset: {Node id=-752 version=0 MV lat=53.363,lon=5.4195} - E: Handled by bug report queue: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException. Cause: java.lang.reflect.InvocationTargetException. Cause: org.openstreetmap.josm.data.osm.DataIntegrityProblemException: Primitive must be part of the dataset: {Node id=-756 version=0 MV lat=53.446667,lon=5.561} - E: Handled by bug report queue: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException. Cause: java.lang.reflect.InvocationTargetException. Cause: org.openstreetmap.josm.data.osm.DataIntegrityProblemException: Primitive must be part of the dataset: {Node id=-825 version=0 MV lat=53.447333,lon=5.566333}
Attachments (0)
Change History (2)
comment:1 by , 7 years ago
Cc: | added |
---|---|
Component: | Core → External rule |
comment:2 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Yes, the validator rules were incorrect. Now fixed
probably caused by
https://raw.githubusercontent.com/OpenSeaMap/josm/master/Seamark.validator.mapcss