First of all, thanks. This is a great tool to have !
As a development idea for it, it would be nice to see that how these connections do in ORS.
Example: I have a hub at HHN. It is pretty easy to figure out how my ORS rating is for HHN-MUC for example. But that is rather pointless as I am the only operator on the route and the point is not to move people between HHN-MUC. I am more interested on how my routing LHR-HHN-MUC rates as a total. This could be an added column after the connection time like 3/69 meaning that I rank 3rd with a ORS score of 69. It would give a nice idea how a certain route might do, if I see something like 124/34 on most columns I would immediately know it has no chance...
Now I need to try each one of these variations manually using the ORS, and if my flight does not rank among the top flights it might be pretty difficult to figure out how it ranks or what is the problem.
You could do it a request based feature. ie. the column only populates if you ask it to. And if you leave out the rank and display only the score, it would not involve ORS at all, it would simply do the ORS rating bit for each connection.
I guess the connection analyzer is not the only view where an ORS view provides valuable information. Having said this, I think it's not only a performance issue, but also providing too much insights.
But in this case the information is publicly available anyway. It is just quite tedious to look it up. The feature would not give any more insight than what is already there.
That is always the fact. So for example in a perfectly transparent AS world, you could use the ORS score in the Flight Number Management to have a feedback on changes on service or price changes.
There is nothing like a public ORS score in reality, that provides you a scored competitive position. Thus integrating the ORS information in wider parts of the game doesn't really looks right from my (!) point of view.
As some have already pointed out, that would be very unwise to do from a performance stand-point. ORS queries are the most expensive thing there is in AS.
I do see in this feature that it has color text indicating good connection times. I have a some incoming flights from external and internal connections indicating green time 2h and 36m. But my hub MCT is only 1h and 30 mins.
So how does this connection analyzer measure "good" "okay" "bad" (i don't know if this is the right term.. lol).
At least, we could identify and expand our arrival and departure times with these indicators instead of cramping it close to hub's tight MCT.
So how does this connection analyzer measure "good" "okay" "bad" (i don't know if this is the right term.. lol).
At least, we could identify and expand our arrival and departure times with these indicators instead of cramping it close to hub's tight MCT.
By the connection time.
P.S. Even though question related to connection analyzer it has nothing to do with OP's question or subject on hand, you should get your own thread as it will be much easier to discuss your question and your issue. (and search later on)
That might be possible, but I do not intend to add it (sorry ;)). I'm very much divided on the topic of visible flight ratings in general because IMO they add too much information that just doesn't exist like this in reality without putting a huge amount of effort into it.
Martin, I hope I understood you wrong, but removing visible flight ratings (meaning the ability to check them in the ORS) would be the famous “last straw” for unimaginable quantity of players. That would be THE thing to make me close down everything. It’s like removing the NSA from the USA … it cannot exist without it.
And what would be the point of having ORS for the players, if they cannot check their overall standing? For the system, ORS is the demand calculation, for the players ORS is the ratings.
Again, I hope I misunderstood the whole meaning of your reply.