Modify

Opened 3 years ago

Last modified 3 years ago

#21911 new enhancement

Add support for boundary=forest and boundary=forest_compartment

Reported by: Penegal Owned by: team
Priority: normal Milestone:
Component: Internal preset Version:
Keywords: forest compartment feature deprecation Cc:

Description

Hello, there!

A recently approved proposal created the boundary=forest tag and standardized boundary=forest_compartment. The first tag is brand new, but the second one is already used some thousands of times. Until now, boundary=forest_compartment lacked widespread support likely because of the concurrent boundary=forestry_compartment tag, but this concurrent tag has been deprecated by the same proposal.

boundary=forest_compartment could be supported alone, but it is now part of a forest-related tagging scheme, as a subdivision of boundary=forest entities, so it would be better to add support of the two approved tags instead of just one, even if boundary=forest just starts to be used.

By the way, it would be great, should this feature request be granted, to have JOSM warn about boundary=forestry_compartment being deprecated and ask for its replacement with boundary=forest_compartment.

Feel free to ask additional details (I'm the author of the proposal creating this tagging scheme).

Kind regards.

Attachments (0)

Change History (1)

comment:1 by skyper, 3 years ago

Component: CoreInternal preset

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user.
Next status will be 'needinfo'. The owner will be changed from team to Penegal.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from team to anonymous. Next status will be 'assigned'.

Add Comment


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