Modify ↓
Opened 8 years ago
Closed 8 years ago
#14240 closed enhancement (wontfix)
landuse port, harbour not treated as areas
Reported by: | testter | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Internal preset | Version: | latest |
Keywords: | Cc: |
Description
What steps will reproduce the problem?
- landuse port doesn't highlight in JOSM
- landuse port isn't rendered as area in OSM
- landuse harbour ( https://wiki.openstreetmap.org/wiki/Harbour ) doesn't highlit as area in JOSM when tagged
- landuse harbour ( https://wiki.openstreetmap.org/wiki/Harbour ) isn't rendered as area in OSM
Example: https://www.openstreetmap.org/changeset/45164358#map=17/0.55132/101.46243
What is the expected result?
What happens instead?
Please provide any additional information below. Attach a screenshot if possible.
URL:http://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2017-01-02 00:53:29 +0100 (Mon, 02 Jan 2017) Build-Date:2017-01-02 02:33:21 Revision:11427 Relative:URL: ^/trunk Identification: JOSM/1.5 (11427 en) Windows 7 64-Bit Memory Usage: 2149 MB / 2731 MB (485 MB allocated, but free) Java version: 1.8.0_111-b14, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM Screen: \Display0 1920x1200 Maximum Screen Size: 1920x1200 Dataset consistency test: No problems found Plugins: + BuildingGeneralization (1010) + ColorPlugin (11) + CustomizePublicTransportStop (0.3) + ElevationProfile (33004) + FastDraw (33004) + FixAddresses (33004) + ImproveOsm (90) + ImproveWay (9) + SimplifyArea (33004) + alignways (33088) + areaselector (1478814827) + auto_tools (1479831713) + buildings_tools (33004) + contourmerge (1030) + czechaddress (33033) + download_along (32946) + editgpx (33004) + graphview (33004) + gson (32680) + indoorhelper (33088) + jogl (1.0.46) + junctionchecking (33088) + kendzi3d (1.0.192) + kendzi3d-resources (0.0.1) + kendzi3d_Improved_by_Andrei + log4j (32699) + mapdust (33044) + measurement (33088) + merge-overlap (33004) + osm-obj-info (1468276210) + osmarender (33004) + public_transport (33088) + public_transport_layer (33088) + reltoolbox (33088) + reverter (33088) + routing (33004) + scoutsigns (90) + splinex (33007) + tageditor (33021) + terracer (33088) + tofix (1480446304) + turnlanes (33088) + turnlanes-tagging (254) + turnrestrictions (33088) + utilsplugin2 (33088) + wikipedia (33098) Last errors/warnings: - W: java.io.IOException: Attribution is not loaded yet - W: java.io.IOException: Attribution is not loaded yet - W: java.io.IOException: Attribution is not loaded yet - W: java.io.IOException: Attribution is not loaded yet - W: java.io.IOException: Attribution is not loaded yet - W: java.io.IOException: Attribution is not loaded yet - W: java.io.IOException: Attribution is not loaded yet - W: java.io.IOException: Attribution is not loaded yet - W: java.io.IOException: Attribution is not loaded yet - W: Terracer: node problem
Attachments (0)
Change History (2)
comment:1 by , 8 years ago
Component: | Core → Internal preset |
---|---|
Keywords: | landuse port doesn't highlight area removed |
Type: | defect → enhancement |
comment:2 by , 8 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
landuse=port and landuse=harbour are not well documented in the wiki and have very low usage numbers. They don't fulfill the josm guidelines for new preset items (DevelopersGuide/DefaultPresets)
Regarding the default rendering on osm.org this is handled at https://github.com/gravitystorm/openstreetmap-carto