Show Navigation | Hide Navigation
You are here:
Geoprocessing tool reference > Conversion toolbox > Metadata toolset > Tools

USGS MP Metadata Translator (Conversion)

Release 9.2
Last modified April 2, 2008
E-mail This Topic Printable Version Give Us Feedback

Print all topics in : "Tools"


Related Topics

NOTE: This tool requires the Microsoft .NET Framework 2.0. These tools are installed with the .NET Support install option.


Uses mp to export or validate metadata content created using the FGDC metadata editor. MP, which stands for metadata parser, is a utility created and maintained by the USGS for managing metadata that follows the FGDC Content Standard for Digital Geospatial Metadata (CSDGM). A version of mp is provided with ArcCatalog.


Usage tips

Command line syntax
An overview of the Command Line window
USGSMPTranslator_conversion <source> <config> {none|XML|HTML|TEXT|FAQ|SGML|DIF} <output> {errors}

Parameter Explanation Data Type
<source>

The item whose metadata will be converted, or a stand-alone XML file that will be converted.

Data Element
<config>

A file that defines custom parameters that mp will consider when parsing the source object's metadata.

File
{none|XML|HTML|TEXT|FAQ|SGML|DIF}

The type of conversion that will take place.

    none — No conversion will be performed.
    XML — An XML file will be created as output.
    HTML — An HTML file will be created as output.
    TEXT — A text file will be created as output.
    FAQ — An HTML file in FAQ format will be created as output.
    SGML — An SGML file will be created as output.
    DIF — A DIF file will be created as output.

If a conversion is not specified, the "XML" conversion will be performed.

For all conversion types, the source metadata will be validated according to the FGDC CSDGM rules and any warnings or errors regarding the metadata content will be reported in the log file. If the "none" conversion is specified, the log file will be created with validation information but no additional output will be generated.

String
<output>

The output file, as defined by the conversion type.

File
{errors}

A text file listing the warnings and errors that occurred during the conversion process.

File
Data types for geoprocessing tool parameters


Command line example

USGSMPTranslator_conversion c:\data\states.shp # none # c:\data\FGDC_validation\states.txt

Scripting syntax
About getting started with writing geoprocessing scripts
USGSMPTranslator_conversion (source, config, conversion, output, errors)

Parameter Explanation Data Type
source (Required)

The item whose metadata will be converted, or a stand-alone XML file that will be converted.

Data Element
config (Required)

A file that defines custom parameters that mp will consider when parsing the source object's metadata.

File
conversion (Optional)

The type of conversion that will take place.

    none — No conversion will be performed.
    XML — An XML file will be created as output.
    HTML — An HTML file will be created as output.
    TEXT — A text file will be created as output.
    FAQ — An HTML file in FAQ format will be created as output.
    SGML — An SGML file will be created as output.
    DIF — A DIF file will be created as output.

If a conversion is not specified, the "XML" conversion will be performed.

For all conversion types, the source metadata will be validated according to the FGDC CSDGM rules and any warnings or errors regarding the metadata content will be reported in the log file. If the "none" conversion is specified, the log file will be created with validation information but no additional output will be generated.

String
output (Required)

The output file, as defined by the conversion type.

File
errors (Optional)

A text file listing the warnings and errors that occurred during the conversion process.

File

Data types for geoprocessing tool parameters


Script example

USGSMPTranslator_conversion (c:\data\states.shp, , none, , c:\data\FGDC_validation\states.txt)

Please visit the Feedback page to comment or give suggestions on ArcGIS Desktop Help.
Copyright © Environmental Systems Research Institute, Inc.