hitching_post vs hitching_rail vs horse_parking
I wonder if hitching_post is a good tag name, most of the places for hitching horses seem to be rails. In the article you wrote that "It can be thought of as a counterpart to amenity=bicycle_parking but for horses." So we should perhaps better use amenity=horse_parking (which is already in the database, see below) or something like that and define it similarly; this would
- allow a subtag horse_parking=post|rail|box|... (for "box" see photo on page trail_riding_station)
- make it easier for mappers to learn the tag (if they already know bicycle_parking)
@Hufkratzer: At least in Ohio (what I'm familiar with), "hitching post" is considered an umbrella term referring to both posts and rails. That may differ from other places. You have a point that the amenity=*_parking pattern may be more discoverable to some mappers, particularly non-English-speakers. However, English speakers would find amenity=horse_parking undiscoverable, since it takes a modicum of head-scratching to realize that it is, after all, a form of parking. "Hitching post" and "hitching rail" are well-established, even everyday terms in many English dialects.
If anything, it would be great to consolidate the sprawling set of amenity=*_parking tags into a single amenity=parking, using access tags to clarify the intended mode(s) of transportation. As it is, more obscure vehicle types end up parking at amenity=parking while much more common bicycle parking ends up at a specialized amenity=bicycle_parking.