Proposal talk:Loading dock details

Door vs Dock Width?

Resolved

Nice job!

One point to discuss / mention? The loading dock that I used to work at, had an external gate ~5m wide, but because of internal areas being used for both storage & a walkway, the actual usable space of the raised loading dock itself was only 3m wide. Do cases like that need to be mentioned? --Fizzie41 (talk) 03:48, 26 March 2022 (UTC)

Good point, I think we should add a photo of this. This is a case where dock:width=* could be useful. --Kylenz 23:46, 26 March 2022 (UTC)

Number of vehicles?

Resolved

Following on from the case above, despite having a 5m wide entrance, we could only accommodate 1 vehicle at a time. Once again, should we specify the number of vehicles that can use the dock at any time? The normal capacity=* would probably work for that? --Fizzie41 (talk) 03:50, 26 March 2022 (UTC)

Makes sense, I'll add a note about capacity=* --Kylenz 23:46, 26 March 2022 (UTC)

To formally approve tag

Resolved

1. Should *=loading_dock be amenity=*? What do you think about eg Talk:Tag:amenity=loading_dock#Amenity vs entrance??
2. Related to the representation in 1, defining max*=* to be for vehicles seems to not handle the case if there are smaller limits allowed through the door than its dimension. Currently Tag:amenity=loading_dock#Additional_tags describes them as "allowed to enter the loading dock" which doesn't seem to be your "no change" by dimension "of a vehicle that wants to use the dock". As a comparison, you suggested example 3 File:Loading_dock_dimensions_3.jpg to be maxwidth=* because "blocking the adjacenet road is not allo0wed" (no clue from the photo), but this is more about the physical width of the dock. dock:width=* doesn't appear to be "not needed" here. Adding a tag for perpendicular vs parallel docking would be useful for such case too.
3. Should I be able to use amenity=loading_dock on the entire area including the raised platform and parking spot instead? Maybe also enclosing multiple ones? (might be tedious to draw every one of them)
4. Related to 2 and 3, capacity=* was added by Talk:Tag:amenity=loading_dock#Capacity for multiple docks, but there may also be other "capacity" viz weight allowed on a variable height dock, which further creates a conflict on maxweight=* in referring to goods (would be inconsistent with the aforementioned max*=* definitions) vs vehicle (leaves dock weight limit undefined, and not the most helpful). Indeed example 3 shows "SWL 2000KG" on the right.

--- Kovposch (talk) 04:29, 26 March 2022 (UTC)

1. I somewhat agree, in most cases a loading dock is effectively an entrance, but there are edge cases where this is not true, so it would be confusing to always treat it as an entrance, even if it usually is. Some examples:
   • The loading dock might underneath the building or within the building's underground car park, so it's not an entrance to the building=* itself.
   • The entrance=* tag is somewhat 'orthogonal':
     • a service entrance might also be the loading dock (some places are even designed like this).
     • Particularly in small buildings, the loading dock can also be an official emergency exit
   • The dock might be on an underground service lane, and/or the building might have a different footprint below ground, so you couldn't tag the dock as an entrance on the building=* area.
   I don't have a strong opinion, but since it's become established as an amenity (10,000 uses) it might make sense to keep the current tag since there are flaws with always treating it as an entrance
2. maxwidth=*/maxheight=*/maxlength=* always refer to restrictions on vehicles, so I don't want to break the current consistency. I agree, dock:width=* could be useful as mentioned above.
3. My initial thinking is no, because that's what amenity=parking_space + parking_space=delivery is for.
4. Like other tags, you could use capacity=7 to avoid mapping 7 identical features, but if the some of those 7 features have different characteristics then you should map them as different elements. For example, if half of a car park is access=private and half is access=yes, then you would map them as two separate features to properly convey the access restrictions. Same thing for maxweight=* on loading docks, right?

--Kylenz 23:46, 26 March 2022 (UTC)

Hi, I'm going to mark this as "resolved" since I didn't hear back from you. I think I've answered all you questions above (?) --Kylenz 21:27, 12 September 2022 (UTC)

Variable height

Resolved

Would be better to tag this explicitly. Looking for range in dock:height=* makes interpreting more difficult and expensive. Then one may add whether it is inclined or raised entirely to be flat, structure being scissor lift or hinged, and held by hydraulic vs air bag vs coil spring. --- Kovposch (talk) 05:23, 26 March 2022 (UTC)

Do you have an example of how this could be tagged? If you're suggesting something like dock:min_height=*/dock:max_height=*, what happens if a feature has dock:min_height=*, dock:max_height=*, and dock:height=*? --Kylenz 23:46, 26 March 2022 (UTC)

Hi, I'm going to mark this as "resolved" since I didn't hear back from you. I think we can stick with just dock:height=*. --Kylenz 21:27, 12 September 2022 (UTC)

door:width definition

Resolved

It should be made clear if door:width refers to the width of the door, or the width of the opening when the door is fully opened. These can be quite different, e.g. sliding doors are wider than the opening in the wall; or swinging doors are blocking part of the opening (like in the third example). --Mueschel (talk) 10:37, 28 March 2022 (UTC)

Good point, I've clarified this --Kylenz 03:29, 2 April 2022 (UTC)

Replace dock:x with loading_dock:x namespace

I don't like the shorter dock:x=* key namespace. Why not the same as the parent loading_dock:x=*? When you google images of dock, you get sea docks for ships, and maybe that tag will be used for that. This will clear any possible clashes with different tags in the future. Janko (talk) 10:49, 15 September 2022 (UTC)

Hi, dock is an interesting word, it used to only refer to ships but it's now used for vehicles, spacecraft, and even computers/phones. We almost need a retronym for maritime docks :) Perhaps this depends on which dialect of English you speak (?) I'm happy to change this but I personally think dock:*=* is fine since dock:width=* etc. could be adapted in the future for any facility where two thinks dock together. --Kylenz 23:58, 27 September 2022 (UTC)