Add more barrier presets

[arch0345]

This PR adds presets for the following barriers listed on the wiki:

• barrier=bump_gate
• barrier=bus_trap
• barrier=cable_barrier
• barrier=full-height_turnstile
• barrier=hampshire_gate
• barrier=jersey_barrier
• barrier=motorcycle_barrier
• barrier=planter
• barrier=rope
• barrier=wicket_gate

I used the default barrier icon for most of these, but ideally those should get their own icons. For example, barrier=jersey_barrier could have an icon similar to this image depicting the general outline:

The preset for full-height_turnstile could have an icon similar to the one used in OSM carto:

Since the wiki article for barrier=bus_trap recommends also using maxwidth, I created a field for it using the same field type used for maxheight since their values are similar.

I also added barrier=ditch, barrier=handrail, and barrier=log as unsearchable presets. For barrier=ditch, waterway=ditch has a lot more uses and having making both of these searchable might be confusing for some users. The wiki article for barrier=handrail mentions that there's an "Unclear difference from fence". Although barrier=log is an approved tag, I made it unsearchable to prevent mappers from adding fallen trees that don't obstruct a passage.

Closes #505

[danieldegroot2]

barrier=planter should not be confused with man_made=planter;

See also man_made=planter One object can be tagged both with man_made=planter and barrier=planter, planters that are not barriers should be tagged with just man_made=planter.

[arch0345]

One object can be tagged both with man_made=planter and barrier=planter, planters that are not barriers should be tagged with just man_made=planter.

Because of this, I decided to change the preset to use man_made=planter and added a field (planter_barrier) to add barrier=planter, similar to how the crossing_raised field adds traffic_calming=table to the crossing presets.

[tyrasd]

Because of this, I decided to change the preset to use man_made=planter and added a field (planter_barrier) to add barrier=planter, similar to how the crossing_raised field adds traffic_calming=table to the crossing presets.

That sounds like a good approach 👍

But could you please rename the field to data/fields/barrier_planter.json (the first part of the field's file name should be the tag key it operates on)?

[tyrasd]

planter preset

I just noticed that, unfortunately, this approach doesn't allow us to show the access field for planter objects when they the barrier=planter tag is set. In 87e795f I've now added a non-searchable preset called Planter (Barrier) (for vertex nodes only) which affords this. Do you think that solution is acceptable?

[arch0345]

Good thinking, looks good to me

[1ec5]

Does this tag refer to the way the gate is constructed (small), its purpose (pedestrian access), or its location (secondary), or some combination? I’m finding the preset difficult to translate due to this ambiguity.

[tyrasd]

As far as I understand, the term refers only to a secondary gate for pedestrians near (or in¹) a larger gate.

Footnotes

1. I would say that in OSM the barrier=wicket_gate probably only applies to the situation where the wicket is actually a separate entrance (as in this example), and not for wicket doors which are built directly into a large gate (example). The latter should probably be modeled as an attribute of the main gate (e.g. barrier=gate + wicket=yes), I assume. ↩

[RudyTheDev]

Although barrier=log is an approved tag, I made it unsearchable to prevent mappers from adding fallen trees that don't obstruct a passage.

Perhaps it is better to rename it to something obvious like "Barrier (Fallen Tree)" rather than hide it from the search? As someone who surveys a lot of forests, this is a common item to add on paths.