Import Metadata (Defense Mapping)

Zusammenfassung

Imports metadata into a Multinational Geospatial Co-production Program (MGCP) database to perform maintenance on cells and subregions.

Verwendung

• The metadata can only be imported into an MGCP database that already contains the MGCP_Metadata feature dataset.

• The input XML files must match the ISO 19139 specification and be compliant with TRD 2 or TRD 3.

• Data is imported into the following feature classes using this tool:

  • The Cell feature class contains metadata about individual 1x1-decimal degree extents with which the data is associated.
  • The Subregion feature class contains metadata about the specific area within the cell where the data meets requirements for a specific purpose.
  • The Source feature class supplies information about the source used in the feature extraction.

Syntax

ImportMetadata_defense (in_files, in_cell_features)

Parameter	Erläuterung	Datentyp
in_files [in_files,...]	The XML files that contain the metadata to import.	File
in_cell_features	The Cell feature class where the metadata will be imported.	Feature Layer

Codebeispiel

Import Metadata example (stand-alone Python script)

In this example, the W118N32.xml file is imported into the MGCP_TRD2 geodatabase.

# Name: ImportMetadata.py
# Description: Imports the metadata dataset from an XML file to a geodatabase
# Author: ESRI
# Date: June 2010

# Import arcpy module
import arcpy

# Check out a DefenseMapping extension license
arcpy.CheckOutExtension("defense")

# Import the Defense Mapping toolbox - you may have to alter this path
arcpy.ImportToolbox(r"C:\Program Files\ArcGIS\Desktop10.0\ArcToolbox\Toolboxes\Defense Mapping Tools.tbx")

# Local variables:
in_files = "C:/Data/Defense/Metadata/W118N32.xml"
in_cell_features= "C:/Data/Defense/MGCP_TRD3.mdb/MGCP_Metadata/Cell"

# Execute Import Metadata function
arcpy.ImportMetadata_defense(in_files, in_cell_features)

# Check in the Defense Mapping extension
arcpy.CheckInExtension("defense")

Umgebungen

Dieses Werkzeug verwendet keine Geoverarbeitungsumgebungen.

Lizenzinformationen

ArcView: Nein

ArcEditor: Nein

ArcInfo: Erfordert Defense Mapping