51ExportTemplate

Disponible con licencia de Aviation Charting.

The 51ExportTemplate defines the output Aeronautical Information Exchange Model (AIXM) 5.1 schema for an output AIXM .xml file. The AIXM 5.1 structures are organized by the primary AIS tables, which contain a combination of the related table data and the primary table data. The template maps AIS feature data fields and geometry to AIXM 5.1 elements.

File format

The file format of the 51ExportTemplate is an XML template that contains all AIXM 5.1-compliant structures supported by the Export AIXM 5.1 Message tool. The AIXM 5.1 structures are organized by primary AIS tables. AIS data from the primary table is combined with related table data. The data is populated into associated AIXM structures. The AIXM structures in this template use special markup notation ({}) in the attribute and element values to direct how AIS field data is substituted into the template.

All values in the curly braces, which represent AIS tables and attributes, should be lowercase. All AIXM XML tag names and attributes should match the case in the AIXM specification.

Precaución:

It is recommended that you create backup copies of the outlined configuration files before editing them to avoid data loss.

The following is a sample of the 51ExportTemplate:

<template>
  <primarytable_a>
    <aixm:PrimaryFeature1 gml:id="{primarytable_a.clientkey_id}">
      <aixm:timeslice>
        <aixm:name>{primarytable_a.name}</aixm:name>
        <aixm:relatedField_alpha relatedAttr="{relatedtable_a_1.field_2}">{relatedtable_a_1.field_1}</aixm:relatedField_alpha>
        <aixm:relatedField_beta relatedAttr="{relatedtable_a_2.field_2}">{relatedtable_a_2.field_1}</aixm:relatedField_beta>
      </aixm:timeslice>
    </aixm:PrimaryFeature1>
  </primarytable_a>
  <primarytable_b>
    <aixm:PrimaryFeature2 gml:id="{primarytable_b.clientkey_id}">
      <aixm:timeslice>
        <aixm:name>{primarytable_b.name}</aixm:name>
        <aixm:relatedField_gamma relatedAttr="{relatedtable_b_1.field_2}">{relatedtable_b_1.field_1}</aixm:relatedField_gamma>
        <aixm:relatedField_delta relatedAttr="{relatedtable_b_2.field_2}">{relatedtable_b_2.field_1}</aixm:relatedField_delta>        
      </aixm:timeslice>      
    </aixm:PrimaryFeature2>
  </primarytable_b>
</template>

Code sample

The code sample below is an example definition of the aixm:AirportHeliport feature. It demonstrates how data from the adhp primary table populates the feature. It also shows how data from the orgauth and address related tables populate the theOrganisationAuthority and contact subelements, which match each pair in order.

Nota:

To illustrate where the fields from the primary table originate, the fields are prefixed with a table name.

<aixm:AirportHeliport gml:id="{adhp.clientkey_id}">
    <aixm:responsibleOrganisation>
        <aixm:AirportHeliportResponsibilityOrganisation  gml:id="{guid}">
            <aixm:theOrganisationAuthority xlink:href="{orgauth.clientkey_id}"/>
        </aixm:AirportHeliportResponsibilityOrganisation>
    </aixm:responsibleOrganisation>    
    <aixm:ARP >
        <aixm:ElevatedPoint srsName="urn:ogc:def:crs:EPSG::4326" gml:id="{guid}" >
            <gml:pos>{adhp.shape}</gml:pos>
        </aixm:ElevatedPoint>
    </aixm:ARP>    
    <aixm:contact duplicate="address.clientkey_id">
        <aixm:ContactInformation  gml:id="{guid}">
            <aixm:name>{address.name_txt}</aixm:name>
            <aixm:title>{address.title_txt}</aixm:title>
        </aixm:ContactInformation>
    </aixm:contact>    
</aixm:AirportHeliport>