id summary reporter owner description type status priority milestone component version resolution keywords cc 16803 Validator: Wrong warning Highway link is not linked to adequate highway/link GerdP team "==== What steps will reproduce the problem? 1. Open attached sample OSM file 2. Run validator ==== What is the expected result? No warning ==== What happens instead? Highway link is not linked to adequate highway/link ==== Please provide any additional information below. Attach a screenshot if possible. It is a common mapping method to draw one way which describes two separate link roads and I think it is correct. When I split the way at the node on the primary road the warning disappears. Maybe the validator code could ""simulate"" that split? [[Image(16803.png)]] {{{ URL:https://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2018-10-01 23:59:36 +0200 (Mon, 01 Oct 2018) Build-Date:2018-10-01 22:08:47 Revision:14289 Relative:URL: ^/trunk Identification: JOSM/1.5 (14289 en) Windows 10 64-Bit OS Build number: Windows 10 Home 1803 (17134) Memory Usage: 2665 MB / 5376 MB (1522 MB allocated, but free) Java version: 1.8.0_162-b12, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM Screen: \Display0 1920x1080 Maximum Screen Size: 1920x1080 Dataset consistency test: No problems found Plugins: + OpeningHoursEditor (34535) + apache-commons (34506) + buildings_tools (34572) + download_along (34503) + ejml (34389) + geotools (34513) + jts (34524) + measurement (34529) + merge-overlap (34664) + o5m (34405) + opendata (34675) + pbf (34576) + poly (34546) + reverter (34552) + utilsplugin2 (34506) Last errors/warnings: - W: Conflicts detected - There were 8 conflicts detected. - W: Conflicts detected - There was 1 conflict detected. - W: Conflicts detected - There was 1 conflict detected. - W: Unsaved changes - The relation has been changed.

Do you want to save your changes? - E: Handled by bug report queue: java.awt.IllegalComponentStateException: component must be showing on the screen to determine its location - E: org.openstreetmap.josm.io.OsmApiException: ResponseCode=504, Error Header=, Error Body=< - E: Communication with OSM server failed - ResponseCode=504, Error Header=<timeout. The server is probably too busy to handle your request.>, Error Body=<<?xml version=""1.0"" encoding=""UTF-8""?> - W: java.net.SocketException: Unexpected end of file from server - E: org.openstreetmap.josm.io.OsmTransferException: java.net.SocketException: Unexpected end of file from server. Cause: java.net.SocketException: Unexpected end of file from server - E: Network exception - Failed to open a connection to the remote server
'https://api.openstreetmap.org/api/0.6/'.
Please check your internet connection. }}} " defect new normal Core template_report