Talk:Key:aerialway:occupancy

Confusion with capacity

This key looks like a confusion with capacity. However aerialway:capacity=* is used to set the hourly flow, these two should be renamed respectively:

• aerialway:capacity=* => aerialway:flow_rate=* (in regard of original flow_rate=*)
• aerialway:occupancy=* => aerialway:capacity=*

It currently prevent to reuse occupancy for its actual meaning. Fanfouer (talk) 10:55, 16 March 2025 (UTC)

It's not good, but "capacity" is ill-defined here. What you are referring to is vehicle capacity, which isn't described in OSM as individual features. On aerialway=* , or a route=* , it would be system passenger capacity. This is what's usually referred to in transit.
"Flow rate" resembles traffic flow rate, ie traffic volume in the number of vehicles, the inverse of interval=* headway for frequency. This can be said as line capacity in rail terms at the same time.
There's also capacity:persons=* that needs to be considered. cable_car:capacity=* etc may be clearer than aerialway:capacity=* in referring to individual vehicles.
In any case, it would be more difficult to redefine them now. Better add something else entirely new.
—— Kovposch (talk) 16:22, 17 March 2025 (UTC)

Flow rate could also refer to people/hour as average value, while capacity refers to seats per carriage and is constant. The freedom to choose words that match with needs at a given time comes with ability to refine it when necessary. Fanfouer (talk) 22:24, 17 March 2025 (UTC)

Do you know capacity is the term used in transportation? As I said, flow rate could be seen as the number of vehicles. This doesn't solve the difference.
—— Kovposch (talk) 11:24, 18 March 2025 (UTC)