This is the first field I looked at and it seems that this is only available in the original out of date supplied data from VAM. For my initial entry for this I set a default of 'airport' which makes some sense. However later on providing i have enough data that matches back to the VAM data I can update this to their values such as 'small_airport' , 'large_airport' etc. This is one of the more difficult fields to get the correct data from as many airports change their name and sometimes they change the ICAO code if available. Remember my test case of Jan Smuts Airport in South Africa that was FAJS becoming OR Tambo and FAOR. I needed a set of data that was correct with the names of Airports associated with the ICAO code if possible. It so happens if you are careful you can get a free set of data using an API KEY from a real world website in fact it is ICAO themselves https://www.icao.int/safety/iStars/Pages/API-Data-Service.aspx For free
Since I found that the supplied airport data in Virtual Airlines Manager was not suitable for several reasons , I had to think of what data do I need and where can I get what I feel is better data. I sat back and looked at how I use flight simulation and how what I needed from that to accomplish my needs. I found it easy to think about this , I fly with the X-Plane flight simulator with various aircraft some of which are payware. When I fly I like to use the auto-pilot and thus follow a flight route in the FMC computer. Thus I have a subscription to Navigraph to update my FMC data each month on their release cycle and I create my flight plans using SIMBRIEF. So I looked into what I get from Navigraph and I found that I can get a list of all the Airports and Latitude and Longitude in a text file NZSP-89.981947-144.063631 Where NZSP is the ICAO code and the Latitude and Longitude co-ordinates. This is a starting point as with this file I get nearly 13500 airports that I co