Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Italians Airport Rome Fiumicino (LIRF) and Milano Linate (LIML) #695

Closed
Mlandone opened this issue Oct 16, 2016 · 2 comments
Closed

Italians Airport Rome Fiumicino (LIRF) and Milano Linate (LIML) #695

Mlandone opened this issue Oct 16, 2016 · 2 comments

Comments

@Mlandone
Copy link

Mlandone commented Oct 16, 2016

With this airports the Simulation will encrease the "moviment" in Europe.
For Rome Fiumicino (biggest airport in Italy)
https://en.wikipedia.org/wiki/Leonardo_da_Vinci%E2%80%93Fiumicino_Airport
For Milano Linate
https://en.wikipedia.org/wiki/Linate_Airport

@eliuuk
Copy link
Contributor

eliuuk commented Oct 16, 2016

What about the Asian airports? :P

I'll have a look at this at a later date.

On 16 Oct 2016, 12:54 +0100, Mlandone notifications@github.com, wrote:

With this airports the ATC will encrease the "moviment" in Europe, as there are not too many European Airports in the simulator.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (#695), or mute the thread (https://github.com/notifications/unsubscribe-auth/ASgmWO2qHi8ft5F0B-6PGYuytK7sZxgmks5q0hCMgaJpZM4KX9BH).

@erikquinn erikquinn changed the title [Airport Request] Italians Airport Rome Fiumicino (LIRF) and Milano Linate (LIML) Italians Airport Rome Fiumicino (LIRF) and Milano Linate (LIML) Nov 13, 2016
@erikquinn
Copy link
Collaborator

The ATC repository is being migrated to it's new home at https://github.com/openscope/openscope,
and thus, all issues are being closed. If this is still an issue with the latest version of the sim
(accessible at http://www.openscope.co), or is a feature you still think we are lacking,
please reopen the issue at the new repo.

Please note that the vast majority of these issues have been copied to the new repository, or else are covered by other issues created there. See the below screenshot for what it looks like when your issue is known in the new repo:

image

Thank you!

Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants