While the metadata file can be prepared by the user, it's format and
contents are strictly defined. An alternative is to use the interface
program, v.sdts.meta, with which the user can prepare and install a
correctly formatted metadata file.
The format of the metadata source file is rather highly specified. Following is a list of the items that can be included in the file. Note that each item is preceded by a particular code. The code, and the following ':' must be entered intact for each included metadata item. The colon is then immediately followed by the user-supplied information:
IDEN_MPDT:(creation date of original source map; YYYY or YYMMDD format)
IDEN_TITL:(general title for contents of transfer, for TITL field in IDEN module. If not specified, vector header "map_name" will be used)
IDEN_COMT:(general comment on transfer, for IDEN module's COMT field)
XREF_HDAT:(name of geodetic datum to which export data are referenced, for HDAT fieid in XREF module.)
DDSH_ENT_NAME:(for Dictionary/Schema module; name of kind of entity that dig_att and dig_cats values represent. If not specified, map name will be used.)
DDDF_GRASS_ENT:(definition for entity in "DDSH_ENT_NAME", for Dictionary/ Definition module. if not supplied, simple default is used.)
DDDF_ATTR_NUM:(definition for dig_att values, for Dictionary/Definition module; if not specified, simple default is used.)
DDDF_ATTR_LABEL:(definition for dig_cats values, for Dictionary/Definition module; if not specified, simple default is used.)
As noted above, the metadata file can be prepared, and installed, without the user having to worry about format details, with v.sdts.meta.
m.sdts.read,
v.in.sdts,
v.out.sdts,
v.sdts.dp.cp,
v.sdts.meta.cp,
v.sdts.meta
David Stigberg, U.S.Army Construction Engineering
Research Laboratory
Tin Qian, University of Illinois