Modify

Opened 3 months ago

Closed 3 weeks ago

Last modified 6 days ago

#17133 closed defect (fixed)

boundary=national_park relation is not rendered

Reported by: mkoniecz Owned by: team
Priority: normal Milestone: 19.02
Component: Internal mappaint style Version:
Keywords: template_report Cc:

Description (last modified by mkoniecz)

What steps will reproduce the problem?

  1. Load https://www.openstreetmap.org/way/30268505

What is the expected result?

https://www.openstreetmap.org/relation/2658152#map=8/40.939/-123.608 is rendered (like boundary=national_park on way is rendered)

What happens instead?

Nothing.

Please provide any additional information below. Attach a screenshot if possible.

Validator is not complaining about anything.

Rendering

Tag data

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2018-12-17 22:42:01 +0100 (Mon, 17 Dec 2018)
Build-Date:2018-12-18 02:32:19
Revision:14575
Relative:URL: ^/trunk

Identification: JOSM/1.5 (14575 en) Linux Ubuntu 16.04.5 LTS
Memory Usage: 435 MB / 869 MB (113 MB allocated, but free)
Java version: 1.8.0_191-b12, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Screen: :0.0 1920x1080
Maximum Screen Size: 1920x1080
Dataset consistency test: No problems found

Plugins:
+ OpeningHoursEditor (34535)
+ buildings_tools (34724)
+ continuosDownload (82)
+ imagery_offset_db (34641)
+ measurement (34529)
+ reverter (34552)
+ todo (30306)

Last errors/warnings:
- W: java.net.SocketTimeoutException: connect timed out
- E: java.net.SocketTimeoutException: connect timed out
- E: org.openstreetmap.josm.io.OsmTransferException: Could not connect to the OSM server. Please check your internet connection.. Cause: java.net.SocketTimeoutException: connect timed out
- E: IO Exception - org.openstreetmap.josm.gui.widgets.HtmlPanel[,0,0,0x0,invalid,layout=java.awt.BorderLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=9,maximumSize=,minimumSize=,preferredSize=]
- W: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: connect timed out
- W: Already here java.net.SocketTimeoutException: connect timed out
- W: java.net.SocketTimeoutException: connect timed out
- W: Already here java.net.SocketTimeoutException: connect timed out
- W: java.net.SocketTimeoutException: Read timed out

Attachments (2)

Selection_002.png (6.1 KB) - added by mkoniecz 3 months ago.
Selection_001.png (73.9 KB) - added by mkoniecz 3 months ago.

Download all attachments as: .zip

Change History (10)

Changed 3 months ago by mkoniecz

Attachment: Selection_002.png added

Changed 3 months ago by mkoniecz

Attachment: Selection_001.png added

comment:1 Changed 3 months ago by mkoniecz

Description: modified (diff)

comment:2 Changed 3 months ago by mkoniecz

Description: modified (diff)

comment:3 Changed 3 months ago by Don-vip

Component: Core mappaintInternal mappaint style

comment:4 Changed 3 weeks ago by mkoniecz

Is there any missing information that I can provide?

comment:5 Changed 3 weeks ago by Klumbumbus

Milestone: 19.02

comment:6 Changed 3 weeks ago by Klumbumbus

Resolution: fixed
Status: newclosed

In 14806/josm:

fix #17133 - support rendering of boundary on relation ways for all boundary types not just administrative

comment:7 Changed 7 days ago by anonymous

what about boundary=civil ?

comment:8 Changed 6 days ago by mkoniecz

Not covered by "boundary=national_park relation is not rendered" ticket.

From look at https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dcivil it also seems like data not suitable for OSM and fortunately rarely added.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.