i'm adding GA parking to KRDU for my GA Ai Traffic... i'm also cleaning up the ground net and refining it a little...

• started with existing WIP of KRDU ground net
• editing it with portreekid's new tool
• have added ~22 GA parking places... most are currently reserved for ficticious(?) LandMark Aviation that used to be based at KRDU
• refining some taxiways

Will start on the upgrade of Oslo Gardermoen next week

Revamping OMAA Abu Dhabi groundnet (and WED layout at the same time)

Cleaning Up Sheremetyevo which had a lot of isolated nodes (missing Parking INS)

It appears that the Localizers are facing the wrong way. At any rate, KJFK needs some work that I cannot do. I've never been able to get WED set up to edit the airports.

It's a horrible autoconverted groundnet.

Being updated

Work started on building SKBO Bogota El Dorado groundnet as I am pushing an update for LATAM AI traffic to sourceforge, next week.

• Unconnected Runway Nodes
• Overlapping Parkings

Here's a list of my old groundnets that are showing errors in the Broken Airports list, I'll be gradually updating these.
Please let me know you are working on, or intend to work on, any of them so I can remove them from my to do list, thanks.

EGAA - Fixed
EGAC - Fixed
EGBB - Fixed
EGGP - Fixed
EGGW - Fixed
EGHI - Fixed
EGJB - Fixed
EGJJ - Fixed
EGPH - Fixed
EGSH - Fixed
EHBK - Fixed
EKAH - Fixed
ENRY - Fixed
EPKK - Fixed
GCFV - Fixed
GCLP - Fixed
GCRR - Fixed
GCTS - Fixed
GMMX - Fixed
LEAL - Fixed
LFBE - Fixed
LFMU - Fixed
LIME - Fixed
LIPH - Fixed
LIRP - Fixed
LIRZ - Fixed
LROP - Fixed

Working on KPHL (--pb321). Have also started KCLE and KIAD.

Started reviewing and fixing the Italian airports triggering a lot of console errors

LIPZ LIPE LIML LIRN LIMF LIRA LIRQ LIBD LIPO

John Glenn International, Columbus, Ohio. In testing...

i'm doing KCLT...

• started with existing "parking only" KCLT ground net
• have added/edited ~91parking places
• full taxiways to all runways

refining it now... so far, i'm really liking the new tool by portreekid... has a few quirks but still quite usable...

KSEA Update coming this week

Getting your groundnet merged does not mean it is functional.
It only means you have made it everyone else’s problem if it’s not.

Getting your groundnet validated by FGA, Travis or Taxidraw is not enough.
FGA, Travis or Taxidraw can only check the structural validity of a groundnet, this is not a guarantee that AI traffic using the groundnet will behave properly.

FGA is still under development and not all structural tests are yet in place. Typical examples of issues not picked up by any verification tools include:

• Clogging at intersections
• Clogging at runway access points
• Erratic pushbacks
• Inadequacy of gates (Number or Type)

It is your responsibility to test and fix your groundnet.
Only you can ensure your groundnet provides a smooth AI experience to Flightgear users by testing it thoroughly on your machine before sharing it with the rest of the community.

Issues encountered during your testing should still be raised and discussed in the FG AI forums where a larger number of users will benefit from your findings and will be able to help.

Like for any other code/data submitted to the project you are expected to maintain and fix your own groundnets if anyone reports an issue with them.

Submission to Groundweb/Terrasync is optional.
Do not request for an upload when your work will not benefit the community or improve the overall Flightgear experience, Always keep the ‘general user’ in mind.

This includes groundnets for local airports hosting no scheduled commercial traffic, abandoned airports (KaiTak, Templehof, Gaza) and military bases.

Custom groundnets should be made available, as usual, via download links in the FG Scenery Forum, for the benefit of users sharing the same niche interest.

Use the same forum download link mechanism when you are struggling to make your groundnet ‘work’ and want other users’ help and advice for troubleshooting

Help is available in Wiki
Work has started on the update of http://wiki.flightgear.org/AI_Traffic.

A lot of tips and tricks, covering issues not picked up by verification tools are already explained there.
The page update will continue based on the information and findings shared in the forums.

Git Hub Tickets are for FGA only
Keep (this) FGA Terrasync repo FGA specific and limited to announcing Work in Progress.

General discussions and questions related to groundnets (not tool specific) continue to live in FG AI Forums where you can reach and help the largest number of contributors.

Started work on a groundnet for Baku Heydar Aliyev International

These airports do not currently have working groundnets. I've started work on them.

Starting OJAI for FGA 0.13 testing.

i'm only doing the commercial parking and taxiways... KCHS is a dual purpose airport serving also as an USAF base as well as a Boeing maint/build site...

• created the 15 parking places around concourses A and B at the commercial terminal
• restricted concourse A to Delta
• restricted concourse B to American (AAL), JetBlue (JBU), and United (UAL)...
  SouthWest (SWA) also flies here but is not in the list of available airlines currently using KCHS so cannot add them to the restriction list yet
• created basic taxiway paths for commercial craft to reach either end of either runway
• requested the removal of two shared object craft that were blocking parking A1 and A4

i'm not planning on doing the military parking or taxiways and i do not mind if someone else takes this ground net and enhances it with them...

aside: i know that parking can be limited to certain airline codes... can taxiways also be restricted in the same way?

Just realized I never committed migrated my existing Singapore taxidraw groundnet . Will update and push to FG Airport

Stockholm Arlanda update in progress

Started work on fixing AI routing (flow) and Runway usage/segregation.

Halifax Stanfield International - have started this groundnet.

KORD has invalid runways.

KORD defines a runway 10 in the threshold file. There isn't any such runway - there is 9L / 9R and 10L / 10C / 10R.

I believe this is the cause of an exception in the traffic manager, would be glad if this could be updated :)

Routing of Aircrafts between terminals and runways (Flow) under review/update In light of changes made to RWYUSE yesterday.

Working my way through KLAX. Los Angeles International is a mess. The new RL terminal construction has left the FG taxiways and parking positions hella wonky. If I knew how I would also work on the actual scenery modeling.

groundnet almost finished, but the scenery does not match RL ie the Terminal building is not modelled to real-live dimensions.
i will resize the Terminal and relocate the other scenery objects, then upload/submit all in one go.

Groundnet update started for LIMC Milan Mapensa

Work in progress to update Santiago de Chile groundnet to

• Accommodate extra AI traffic from newly merged LATAM and Avianca files
• Add gates for the new international terminal

WIP : Refreshing LFPO with additional parking positions and a new flow.

Starting the "update" of Rome Fiumicino which is, weird enough, not developed at all (One gate and no network)

When outdated airports do not match reality, do we just adjust taxiways to match FG scenery? In attached pic, you can see the FG airport structure misaligned. Should we just match FG layout? (taxiways are from current FG groundnetwork)

CYOW:

Turn existing groundnet that doesn't validate into a groundnet that does.

Updating, current version bad.

Started clean up of EPWA

The Des Moines, Iowa airport. Completed this groundnet and submitted today.

Update in progress for Kuala Lumpur International

These are the International Airports for the Hawaiian chain. PHNL, PHOG & PHKO are merged already. They probably could use an expert eye to do a once over and tweak.

I'm starting on PHTO and PHLI.

Starting cleanup of Tokyo Narita Parkings and pushback RJAA

Traffic files for American, Delta and United are now up to date. The last file (AAL) has been pushed to GIT earlier today.

This means we no longer have extra AI aircrafts artificially home based at KORD and KATL.

On resync, the FGA visualisation tool shows the new traffic allocation; We now have enough gates at KLAX, KORD, KMSP and KPHL but Dallas, Atlanta, Charlotte and Miami could use some TLC.

Cheers
Ian

Several of the airports I'm updating have disused runways now being used as taxiways or parking (GCFV, EGSH, EGPH) but they are still flagged as runways in Apt.dat.
When using FGA nodes placed on these are marked as "On Runway", removing the tags is easy enough but then of course they fail the FGA check and I'm assuming they will also fail the Travis checks.

How do you want these uploaded?

https://sourceforge.net/p/flightgear/codetickets/1795/

Confirmed. Tower location should be closer to 7.134279 50.869092

I have existing partial groudnets for the above airports and slowly working my way through them. Listing them here so other contributors know these are already being taken care of

Radius of Terminal_1 & Terminal_3 intersect
Radius of Terminal_1 & GA_1 intersect
Radius of Terminal_2 & GA_1 intersect
Radius of Terminal_3 & Terminal_1 intersect
Radius of Terminal_3 & GA_1 intersect
Radius of GA_1 & Terminal_1 intersect
Radius of GA_1 & Terminal_2 intersect
Radius of GA_1 & Terminal_3 intersect
 
There are unconnected nodes [69, 72]

Working on McCarran starting gates and basic ramps.

Is this repository able to technically process NavData contributions? This mechanism could be used to update airport .dat files. For instance, Jan Mayen is long overdue a fix, as the apt.dat file is badly misplaced, but the TerraSync scenery has the correct airport location.

Name :Arturo Merino Benitez Intl
Airlines :AAL ACA AFR AMX CMP DAL IBE KAL KLM LAN QFA TAM