#22401 closed enhancement (wontfix)
Warn about fire_hydrant without fire_hydrant:position
Reported by: | Timonade | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core validator | Version: | |
Keywords: | fire_hydrant | Cc: |
Description (last modified by )
Please add in trunk/resources/data/validator/combinations.mapcss?rev=18546 line 178 this
node[emergency=fire_hydrant][!fire_hydrant:position]
Timonade
Attachments (0)
Change History (6)
comment:1 by , 3 years ago
Component: | Core → Core validator |
---|---|
Description: | modified (diff) |
Keywords: | fire_hydrant added |
Milestone: | Longterm |
Summary: | Add a line in combinations → Warn about fire_hydrant without fire_hydrant:position |
Type: | defect → enhancement |
comment:3 by , 3 years ago
You got it right, I just think it's better if this is displayed as an error than that the map is incomplete.
comment:4 by , 3 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
I'm going to close this as wontfix
for now.
Currently, we don't do that with any other primary feature, with a few specific exceptions where the feature is not terribly useful without an additional tag (a major highway
with no name
or ref
, for example). We don't even prompt users to add surface
, lane
, maxspeed
, or any other useful information to highway
objects.
I would absolutely add a warning if fire_hydrant:position
existed but emergency=fire_hydrant
did not, since the primary tag is emergency=fire_hydrant
.
If you feel like it, it would be trivial for you to write your own validator style (i.e., Incomplete Object Warnings
) and add it to wiki:Rules.
meta { title: "Incomplete Object Warnings"; version: "[[revision]]_[[date]]"; description: "Checks for incomplete data"; author: "Timonade"; } node[emergency=fire_hydrant][!fire_hydrant:position] { throwWarning: tr("{0} without {1}.", "{0.tag}", "{1.key}"); group: tr("incomplete data"); }
comment:6 by , 3 years ago
I modified wiki:Rules/IncompleteObjectWarnings in wiki:Rules/IncompleteObjectWarnings?action=diff&version=2 , if that helps.
I fail to see what adding
node[emergency=fire_hydrant][fire_hydrant:position],
is supposed to accomplish. You want to have the validator show a warning whenemergency=fire_hydrant
+fire_hydrant:position=sidewalk
? Maybe you meantnode[emergency=fire_hydrant][!fire_hydrant:position],
instead.Anyway, I don't think we want to add that to the default warnings.
emergency=fire_hydrant
is valid withoutfire_hydrant:position
, just incomplete. If you have a specific use case, you can put it in a customfire_hydrant.validator.mapcss
file.