Proposal talk:Drive-Through Elements

Your comments are welcome!

Add established tags to the proposal?

As the established tags drive_through=* and service=drive_through were never validated in a proposal, you may want to add them here. Discostu36 (talk) 05:35, 9 April 2025 (UTC)

I don't have an issue with these tags, both are in "de facto" status so can be built upon. --GA Kevin (talk) 14:43, 9 April 2025 (UTC)

tourism?

I don't think that we should continue to use tourism=information for boards that have nothing to do with tourism. Maybe we can find a better tagging. Discostu36 (talk) 05:39, 9 April 2025 (UTC)

Proposal:Top-level information tag
—— Kovposch (talk) 07:21, 9 April 2025 (UTC)

Yeah, I agree it shouldn't be tourism, unfortunately until the proposal Kovposch linked gets approved, I have to follow what is already laid out in the wiki. --GA Kevin (talk) 14:43, 9 April 2025 (UTC)

height restriction

Hey! For height restriction (#2 in table) you may want to use already existing barrier=height_restrictor on a node along with changes to highway line after the barrier. --Javnik (talk) 07:20, 9 April 2025 (UTC)

Thanks! I'll add this as an example tag. --GA Kevin (talk) 14:43, 9 April 2025 (UTC)

Problem persisting with another previous proposal

parking_space=pickup is unclear whether it's for passenger and other non-food online shopping orders, and for delivery workers. Would simply use *=drive_through directly. Proposal talk:Parking space=collection
Personally, I don't like how parking_space=* mixes up the design vehicle and purpose. Eg for parking_space=charging , amenity=parking has restriction=charging_only now. restriction=drive_through would be more ideal if parking_space=* is reformed.
—— Kovposch (talk) 07:22, 9 April 2025 (UTC)

It is purposely generic to include pickup order spots as well as these types for drive throughs. This is a proposal to formalize common drive-through elements but tagging can be used elsewhere. Another example being the clearance indicator, maxheight certainly already exists, it's just covered here because it is also relevant to the drive-through.

I suppose I agree with your form vs function parking space critique, however some spaces are designated for different vehicles or different activities or even different occupants (i.e. Police parking or people with babies in addition to disabled parking). In the case of fast food, these spots are often combined with a "curbside pickup" option so it can be used to designate a drive through waiting spot or mobile ordering pickup. --GA Kevin (talk) 14:43, 9 April 2025 (UTC)

You should mention if you plan for uses other than drive-thru. At the same time, parking_space=collection has already been proposed. As I have commented there, parking_space=pickup may be interpreted as for passenger pickup.
—— Kovposch (talk) 03:20, 10 April 2025 (UTC)

Formalities of order in approving

Eg Key:window is only "in use" now. It isn't procedural to vote on window=drive_through before window=* . On the other hand, if it's "de facto", voting on it is not very meaningful.
—— Kovposch (talk) 07:40, 9 April 2025 (UTC)

window=* should be de facto at this point if you ask me, it has thousands of uses and 2 3D renderers that use the key. Since drive-through isn't listed on the wiki page, this will just solidify another use for this key. Much akin to how board_type does not have a menu option that this proposal aims to add. I imagine this is rather uncontroversial but wanted it to be documented with support. --GA Kevin (talk) 14:43, 9 April 2025 (UTC)

Cover

man_made=canopy is unclear. There's no requirement on when building=roof should be used. Talk:Tag:building=roof#A_clarification_is_needed_for_difference_between_man_made=canopy_and_building=roof
—— Kovposch (talk) 07:41, 9 April 2025 (UTC)

I agree that covered=* and building=roof should be used and a new tag is not needed. Discostu36 (talk) 07:49, 9 April 2025 (UTC)

man_made=canopy and building=roof already exist, this proposal is just stating that they also apply in the drive-through. --GA Kevin (talk) 14:43, 9 April 2025 (UTC)

man_made=canopy isn't established, or documented clearly. You are further adding your own definition "particularly large or attached to the building" for their difference. This is proposing and voting on it.
It's unknown how it came to be described as "thin steel rather than thick columns or sturdy beams". I would rather guess it's for flexible fabric covers. In either case, it's not quite applicable to the case of rigid cantilever covers with a significant thickness.
—— Kovposch (talk) 03:15, 10 April 2025 (UTC)

Speaker post, and menus

man_made=speaker_box is not intuitive whether it's for ordering. When I search the term, audio speakers show up. It could be used for show speakers outdoors. man_made=speaker
Perhaps as mentioned before, I prefer the "intercom" terminology to show it's for communication. There are already 1 man_made=intercom , amenity=intercom , and 38 man_made=speaker , that could be adapted with man_made=intercom + intercom=drive_through here.
When the menu and speaker are installed together, the speaker should be the main feature, not the menu. But there's no conflict with information=board + man_made=* either. On the other hand, intercom=* is already used as an attribute on entrance=* and barrier=* now.
—— Kovposch (talk) 07:49, 9 April 2025 (UTC)

Agreed, something like

``` man_made=intercom intercom=drive_through ``` for freestanding or menu board mounted intercoms? Agreed, that shouldn't conflict with ``` information=board board_type=menu ``` --GA Kevin (talk) 14:43, 9 April 2025 (UTC)

parking_space=pickup may include more than drive-through holding areas

I have seen some parking spaces which I called parking_space=pickup in the past (though there's apparently also some traction for parking_space=collection for these instead) which aren't really for "drive-through", but do involve "someone brings what you ordered to your car". I think both use cases, of "order online, park here, and someone brings you your order" and "order in a drive-through lane, then if it's not ready yet, park here and someone brings you your order" could use the same parking_space tagging, but the documentation should probably be clear that it covers both if so. And if they're intended to be different tagging, then that should be clear as well. --PeterCooperJr (talk) 13:49, 9 April 2025 (UTC)

Thanks Peter, it is meant to be generic to cover several use cases such as curbside pickup, drive-through waiting, and mobile ordering. I will make it clear that the tag is purposely generic to be expandable in other cases. --GA Kevin (talk) 14:43, 9 April 2025 (UTC)