This support included a GATM performance assessment and a data chain certification of the Air Force Flight Management System (AFFMS) and the digital aeronautical flight information file (DAFIF) it uses. 1913 FLIP Update Africa and CSA Core Data zip files have been updated to include products from FMEE, FSIA, FTTJ, HHAS, and SCIP. Electronic Instrument Procedure Library (E-IPL). (DAFIF, FLIP & so much more) Aero App is available on iPad, Android and Windows tablets.
- Login with a Windows Administrator account.
- Select and download the Mapping and Charting file.
- Double-click the msp file to start the install process.
- When Setup starts, follow the instructions on your screen.
Checksum (Md5) | ||
Desktop | MappingandCharting1041Patch2.msp | ED485B1CFCD9AE1BE6AAA2B0A078875D |
Server | MappingandChartingServer1041Patch2.msp | 3CA3A093B975B0C0F3F151616E1BB13B |
If
![Update Update](/uploads/1/2/6/2/126236771/637711590.jpg)
- Login as a Server Manager by launching https://localhost:6443/arcgis/manager.
- Click Services.
- Stop the map service with Maritime Chart Service capabilities configured.
- Move the controlfiles folder from arcgisserverdirectoriesmaritimeservermaritimechartservicecontrolfiles to a backup location.
- Copy the new controlfiles folder from MaritimeServerServer
maritimechartservice to arcgisserverdirectoriesmaritimeservermaritimechartservice. - If modifications were made to the old control files, they will need to be made to the new control files. The backup control files can be used to consolidate modifications with the new control files. For example Coordinate systems and AutoCellUpdate settings.
- If the map service was configured to read S-63 encrypted datasets, copy the S-63 user-permit.txt file from the backup controlfiles folder to the new controlfiles folder.
- Delete the .senc files from arcgisserverdirectoriesmaritimeservermaritimechartservicesencs. The .senc files must be rebuilt after upgrading. Deleting them will significantly increase creation performance.
- Repeat steps 1 through 8 for each map service with the Maritime Chart Service capabilities configured.
- Login as an administrator by launching https://localhost:6443/arcgis/admin.
- Click Uploads.
- Click Upload.
- Click Choose File and browse to the MaritimeService.soe file located in MaritimeServerServer
Bin. - Click Upload to add the SOE to the site.
- Copy the Item ID for use in the Update step.
- Click Home.
- Click Services.
- Click Types.
- Click Extensions.
- Click Update and paste the Item ID.
- Click Update.
- Click Services (Navigate to Server Manager ->https://localhost:6443/arcgis/manager).
- Click the map service for which you want to enable the Maritime Chart Service.
- Click Capabilities.
- Verify that the datasetsDirectory, controlFilesDirectory, and workingDirectory properties point to the correct locations. For more information about these properties, see the 'Modifying Maritime Chart Service capabilities properties' section of Setting Maritime Chart Service properties.
- Click Save and Restart to make the Maritime Chart Service available.
- Confirm the Maritime Chart Service capabilities are working properly in the map service by verify that the .senc files in the sencs folder are current.
- Repeat steps 22 - 27 for each map service with Maritime Chart Service capabilities configured.
The Import DAFIF Shapefiles Into AIS Geodatabase tool can be used to import Digital Aeronautical Flight Information File (DAFIF) data into the AIS data model. This tool uses cross-reference mapping files to import the data into the proper location in the AIS schema.
Note:
Mapping files are already created to import from DAFIF to AIS. They can be found in the following install directory locations:
- For 32-bit Windows operating systems—<Installation location>Program FilesArcGISAviationChartingDesktop10.7.1DataExchangeDAFIF
- For 64-bit Windows operating systems—<Installation location>Program Files(x86)ArcGISAviationChartingDesktop10.7.1DataExchangeDAFIF
The following table indicates which DAFIF shapefile imports into which AIS feature class. This information is controlled by the entries in the DafifTableMappings.txt file that also contains information about which field is used as the client key for the mapping.
DAFIF shapefile | AIS feature class |
---|---|
ACOM | SERVICE |
ACOMRM | CALLSIGN |
ARPT | ADHP |
ATSH | ATSROUTE |
ATSL | ATSROUTE |
BDRYC | AIRSPACEBOUNDRY |
BDRYH | AIRSPACEBOUNDRY |
BDRYHP | AIRSPACE |
BDRYL | AIRSPACEBOUNDRY |
BDRYLP | AIRSPACE |
GEN | ADDRESS |
HLPT | ADHP |
NAVH | NAVAIDCOMPONENT |
NAVL | NAVAIDCOMPONENT |
NAVT | NAVAIDCOMPONENT |
ORTCA | CLEARANCE |
RUNWAY | ADHPSURFACEAREA |
SUASHP | AIRSPACE |
SUASLP | AIRSPACE |
WPTH_P | DESIGNATEDPOINT |
WPTL_P | DESIGNATEDPOINT |
WPTT_P | DESIGNATEPOINT |
Note:
You will need to create an AIRSPACEBOUNDRY feature class for importing the BDRYL, BDRYH, and BDRYC DAFIF shapefiles.
Additional mapping files also control the following:
- The DAFIF field that is mapped in the target feature class using the entries in the DafifFieldMappings.txt file.
- The domain values that are mapped from DAFIF to domain values in the AIS using the entries in the DafifDomainMappings.json file.
File | DAFIFTableMappings.txt |
Purpose | Maps DAFIF shapefile features to AIS feature classes or tables. |
Format | Source DAFIF shapefile, destination AIS feature class, DAFIF shapefile field or fields used to populate AIS feature class Clientkey_Id value. |
Example |
File | DAFIFFieldMappings.txt |
Purpose | Maps DAFIF shapefile fields to AIS fields. There is one line for each AIS feature class or table with source DAFIF shapefile and destination AIS field names given in subsequent corresponding pairs as needed. |
Format | AIS feature class or table, source DAFIF shapefile field name, destination AIS field name. |
Example |
File | DAFIFDomainMappings.json |
Purpose | Maps DAFIF shapefile domain values to AIS domain values where there may be schema differences. |
Format | |
Example |
File | DAFIFLogic.json |
Purpose | Defines logic used to populate AIS relationship classes, supplemental tables. and special logic for feature creation. |
Format | Varied |
Example |