New with ArcGIS Aviation

[JaimeSF]

Hello,

I'm new to using the Aviation extension, and I have several questions:

From everything I read in the help, tutorials, etc., it always starts with .xml files that are downloaded from any AIP to then be able to import them into the work project to create the aeronautical charts.

In my case, I start with with Feature Classes, which contain information related to Airports, Airspace, Aeroways, Notification Points, etc. but I don't know if that can be easily converted to the AIXM schema and exported like that to create the charts.

I was making a comparison between the fields of the AIXM schema and the fields of my Feature Classes, and it's a lot of trouble to decipher all that.

[KiyoshiYamashita]

Hi there @JaimeSF!

You are right about most of our tutorials, they are focused on the main method (AIXM import) that we use to load data into the AIS geodatabase that is the heart of our ArcGIS Aviation Charting capabilities.  But that is not the only option.  We often have users that are in the same situation as you - they have existing source data in some sort of GIS or GIS-like format.  With source data in feature classes as you've described I see two main options:

1. You can work to load your data directly into the AIS geodatabase using some sort of data loading tool.  For example, you might build a python script, maybe a geoprocessing model or workflow, or perhaps use my preference - Data Interoperability.  In any case, your first step will be to do a bit of a data mapping activity to find a home in the AIS for all of the information in your source data that appears on or affects the appearance of your charts.  You can use the AIS data dictionary in the online help and the detailed schema description provided in our Product Files to help with this activity.  Then you can go about loading the data into the AIS.

2. It may also be possible to use your existing feature classes directly as they are.  We've tried to make many of our tools somewhat agnostic in terms of the data model.  So, while there are definitely several system tables in the AIS that are required, it may be possible to add your feature classes to the geodatabase and use them to start making charts.  You'll need to manually create corresponding carto feature classes to go with your source data so this is a slightly more advanced option, but it should be possible.

In the end, the option you choose really depends on a number of factors like the complexity of the charts and the charting logic/business rules, the complexity of the source data that you have available, and your own skills and areas of expertise in working with ArcGIS.  

Hopefully this helps get you on your way.  If you have additional questions feel free to message directly.

[JaimeSF]

Thanks for your answer @KiyoshiYamashita!! 

I'm trying to do the first option, I've mapped the fields of my feature layers together with the main AIS tables, and although it's quite laborious, I'm sure I've missed something. Should I do the mapping against these layers, or against the cartographic ones, the ones called xxxx_C?

My next step would be to do an append between my layers and the AIS layers to get the attributes. Is this correct? And then I'll start creating the charts, but that's later, we'll go step by step.

Thanks in advance for the help 🙂

Jaime.

[KiyoshiYamashita]

Hi Jaime,

You will do the data mapping against the "main" feature classes (ADHP, Airspace, etc.). The _C feature classes are the cartographic classes that we use for creating the charts later on. If you look closely at the attributes on each class, you'll see that there is more navigational information on the main feature class, and fewer attributes on the corresponding _C feature class.  For airports for example, you'll see things like Ident_Txt, Elev_Val, Name_Txt on the ADHP feature class, but more "cartographic" fields on the ADHP_C feature class, like Label_Txt, and CartoAngle_Val.

And yes, you may be able to use append with the field mapping parameter to load your features into the AIS feature classes as long as your mapping is pretty simple (i.e. one-to-one mapping from source to destination).