Reference - GGP File Types and Extensions

This article describes the file types and extensions used by GGP for Windows. Understanding these files helps with managing overlays, configurations, and troubleshooting.

Common File Types and Their Descriptions

File Extension / Filename	Description
*.ADT	Definition file for Arc/Ungenerate files.
*.API	Import/Export ASCII file for database and geometry collections.
*.CDX	FoxPro compound index for overlay DBF files.
*.CSV	Comma Separated Variable text file for attribute data export/import.
*.DBF	Database table for an overlay (FoxPro format) with system and user fields.
*.DEF	Definition file for API files (field names, types, lengths).
DEPARTMENT.INI	Department directory settings and client defaults. Located in Department Control Directory.
*.DXF	AutoCAD drawing file format used for import/export.
*.ECW	Compressed raster images referenced by raster category tables.
*.EMF	Enhanced Metafile for exporting graphics and saved prints.
*.FDT	Definition file for fixed format ASCII files.
*.FR3	Report script file created with Fast Reports generator.
*.GFM	Field specification and form layout file for overlays.
GGPDEPT.LST	List of GGP departments; assigns users to departments. Located in User Control Directory.
GGP.INI	Local initialization file containing machine startup info; user info is loaded from here.
GGPLOCKS.LOG	Log of all overlay record transactions; located in User Control Directory.
GGPOTB.INI	List of available overlays in Home, Group, Department, and Corporate directories.
GGP.PLY and GGP.PLX	Files defining user permissions on system components.
*.GIL	Import/Export text file containing database/graphics data (GGP Interface Language).
*.GPT	Printing/Plotting template files.
*.GSC	Script file holding saved session details (replaces *.SCR).
*.GS2	Symbol table file supporting bitmap and vector symbols.
LOCK.INI	Key file pointing to License Directory; contains license settings.
LOCKTABLE.DAT	Table of active file and record locks; located in User Control Directory.
LOG.CSV	Logins log (successful and failed) in CSV format; located in User Control Directory.
MAPDB.RDB and IDX	Land-Line map database master table and index.
MASTEROVERLAY.DBF	Global list of all shared overlays; located in User Control Directory.
MASTERMAP*.INI	Settings files for MasterMap (not user-editable).
*.MID, *.MIF	MapInfo Exchange format files.
*.nnn	User-specified indexes on user-defined fields (001 to 128).
*.OGR	Proprietary binary overlay graphics file.
OVERLAY.INI	Overlay properties in INI file format; stored with overlay files.
OVERLAY_SR.XML and OVERLAY_SRT.XML	Files created during spatial database migration of overlays.
PERSONAL.INI	User preference file located in Department Control Directory.
*.POL, *.POI, *.LIN	Arc/Ungenerate Polygon, Point, and Line files.
*.QRY	Overlay-specific query files.
QRYDATA.TMP	ASCII file with spatial query results.
RASCATDB.RDB and IDX	Raster database master table and index.
PRINTDB.DBF and FPT, REPRINT.DBF and FPT	Tables and references to saved prints (Department Control Directory).
*.ROS	Compressed Land-Line map tiles.
*.SCH	Definition files associated with ASCII CSV import/export.
SCRIPT.LSC	Local script files overriding shared scripts; stored in user’s Home directory.
SCRIPT.SCR / SCRIPT.GSC	Script files holding saved session details (*.GSC replaces *.SCR).
*.SHP	ArcView ShapeFile format for import (usually with DBF files).
*.SRW	Saved report generator scripts (being replaced by FastReports .FR3).
*.SYM	Symbol table files; default is GGP.SYM. Overlay-specific versions possible.
USERTABLE.DBF / USERSTABLE.DBF	User database files in User Control Directory.
*.VBS	Visual Basic Script files for standard functions.
*.XSD	Schema files for GIL export and MasterMap.

---

Important Notes

• DBF Files: Do not place temporary or exported DBF files in the same folder as the original overlay files to avoid conflicts.

• Log Files like GGPLOCKS.LOG and LOG.CSV grow over time — deleting regularly is recommended.

• Configuration Files such as LOCK.INI, GGP.INI, and other INI files control system behavior and user settings.

• Scripts with .GSC extensions replace older .SCR script files and store session and map configurations.