Modify ↓

Opened 4 years ago

Closed 4 years ago

#22025 closed defect (wontfix)

Adding support for maxheight non-numerical values

Reported by: kapazao Owned by: team
Priority: normal Milestone:
Component: Core validator Version:
Keywords: Cc:

Description

Non-numerical values for maxheight should be supported. See ​https://wiki.openstreetmap.org/wiki/Key:maxheight#Non-numerical_values

This is an example from Osmose: ​http://osmose.openstreetmap.fr/es/issue/9ad70323-c2be-4927-63de-e10148b25508

Regards

Attachments (0)

Change History (5)

comment:1 by Klumbumbus, 4 years ago

Resolution: → fixed
Status: new → closed

See ​https://github.com/osm-fr/osmose-backend/issues/1437#issuecomment-1102594450.

none, default and below_default are allowed as non-numerical values in the validator.
The other ones in the wiki no_indications, no_sign and unsigned have extremely low usage numbers and lack a proper definition.
Wontfix for me.

comment:2 by Klumbumbus, 4 years ago

Resolution: fixed
Status: closed → reopened

Oops, didn't want to close it immediatly

comment:3 by Klumbumbus, 4 years ago

Component: Core → Core validator

comment:4 by kapazao, 4 years ago

Reading OSM Wiki I think that we can use default and avoid using no_indications, no_sign and unsigned. It seems they are almost the same.
Maybe you can close the ticket.

comment:5 by Klumbumbus, 4 years ago

Resolution: → wontfix
Status: reopened → closed

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. Next status will be 'reopened'.

Add Comment
E-mail address and name can be saved in the Preferences .
Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.