#23188 closed defect (needinfo)
Need adding/correction of value couplings:type=UNI related to fire_hydrants
Reported by: | SekeRob | Owned by: | SekeRob |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | |
Keywords: | Cc: |
Description
The value of UNI is flagged by JOSM Validator as 'unknown property value'. This is a seeming exclusive to Italy (bar 2 abroad) with 8.1K uses. The preset does offer 'uni' but no one uses that. Could this please be corrected.
thanks
Attachments (0)
Change History (4)
comment:1 by , 19 months ago
Owner: | changed from | to
---|---|
Status: | new → needinfo |
comment:2 by , 19 months ago
Summary: | Need adding/correction of value coupling:type=UNI related to fire_hydrants → Need adding/correction of value couplings:type=UNI related to fire_hydrants |
---|
@SekeRob: couplings:type
was removed from the JOSM preset for fire hydrants in r14608.
fix #17149, see #15774 - remove couplings:type from hydrant preset due to suspect values
The message I get is Presets do not contain property key - Key 'couplings:type' not in presets.
.
You are likely using a custom preset or an ancient version of JOSM.
comment:3 by , 7 months ago
Resolution: | → needinfo |
---|---|
Status: | needinfo → closed |
comment:4 by , 7 months ago
Since I've always been running latest stable, an 'ancient' version is kind of out of the question, to boot, only got JOSM first time aug-2022 from official. Anyway, created a dummy hydrant, not having a custom preset', used standard and did not see the coupling:type question. Added the tag manually with =UNI, loaded preset again and see no line that has the UNI value i.e. not in the current preset. Running validator it does not balk at the tag/value so guess this can be closed.
Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.
Please add all needed information according to this list:
To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Help →
Report Bug.
Remember: This is a generic notice so we don't need to write the same stuff again and again. It may only apply in parts to the specific case!
Please at least give the version number for reference in case it's getting forgotten.