VPFEXPORT loses certain coverage projection parameters

1. When converting coverages that must comply with a particular VPF product specification, convert the coverage with VPFEXPORT and allow ArcInfo to write the 'INFO' version of the georeference table.

2. When the georeference table has been created, use VPFIMPORT with the table option to import the georeference table back into ArcInfo.

3. Manually edit the metadata fields in the georeference table 'INFO', according to the VPF product specification.

4. Once the georeference table is updated, run VPFEXPORT with the table option to return it to the VPF database. The procedures remain the same if a CCF is not used during the initial VPFEXPORT and the VPF data is not meeting a particular VPF product specification.

Notes

· If the georeference table is modified to more accurately reflect the projection information, new data cannot be converted into the VPF library. ArcInfo interprets this as an attempt to convert data in one projection into a library with another.

· Another VPF file, sometimes confused with the georeference table, is the Library Attribute Table (LAT). The LAT is located at the VPF Database level. The LAT only contains the name and extent for each library in the database. There can be multiple libraries within one VPF database and each library can be in a different projection. However, the LAT only stores the minimum bounding rectangle for each library in geographic coordinates, latitude and longitude, with units of decimal degrees.