City Based Demand User Interface

[Sami]

Hey, let's talk about user interface and City Based Demand.

For passenger-based CBD to be of any use, we need to improve the route planning interface to make the CBD model and competing airports more understandable. Currently it's a bit of a pain to see who and where is stealing your Potential Demand away from your airport.

There has been talk of this in the longer thread, and I have plans on this myself, but I'm opening this thread for small and quick discussion on the matter.

Let me know how and where you'd like the info on CBD to be presented so that you can learn better that the other airports will affect your demand.


My plan is to keep the demand chart like it is now (with cargo), but to add a "Competing Airports" segment to the route planning pages, which broadly show the airports competing of the same demand. There are still a few issues to resolve with this, especially when there may be multiple competing airports at BOTH ends of the route.

[Continental Sky]

when there may be multiple competing airports at BOTH ends of the route.

Something like this?

[NovemberCharlie]

Something like this?

Great suggestion, on my phone so can't edit. But might it not be easier to combine this to one table? Demand/supply in one cell (5000/8500 for the LHR/JFK cell) and then perhaps the ratio as a color coded background only.

How assymetrical will pax demand be? I always find it rather annoying having to check the planning page for both sectors.

[coopdogyo]

Here are my thoughts:

It needs to be graphical, and there can't be more than two- three graphs bars. Even for cargo right now I find there are too many bars.

My idea is to use bar graphs overlayed on each other and only two bars total. The overall bar graph would show the max potential demand for the catchment area, the second overlay would show the max potential for the airport to capture of that route. Lets be honest, a secondary airport will not be able to steal the entire demand for the airport. Then the last overlay would show the current demand at the airport.

The second bar would show overall the amount of supply for all airports in the catchment area with an overlay showing the current supply for that airport and another showing my supply to all airports and a final overlay showing my supply at the airport

Showing econ, business and first could be done with either a pie chart or possibly textures?

Finally the airlines on this route section would have two options one that shows just flights between the two airports in question and one showing all flights between the two catchment areas.

Very poor mock-up attached. There are probably some oversupply edge cases that would make it look weird but I think keeping it as simple as possible is ideal.

[JumboShrimp]

My old post from 2017.

Just copying the pictures

Details in the posts:
https://www.airwaysim.com/forum/index.php/topic,74722.msg437937.html#msg437937

[JumboShrimp]

Something like this?

I think the problem is that your grid can really expand to infinity in both directions.

I think it needs to start from the route that you are starting from, the catchment areas on both ends, and only consider airport pairs that are in any way taking demand from the 2 catchment areas.

In my example, I have JFK and ORD.  So the potential is that of JFK squares to ORD squares.

Then the breakdown of the demand would not have any other squares.  Say EWR has another demand square.  That should be excluded from the breakdown of the JFK-ORD demand.