File Management, Geodatabases, and Data Organization

Why File Organization Matters in Professional Surveying

When a surveying or GIS project changes hands—between field crew and office staff, between your firm and a client, or between yourself and a future coworker—the person receiving the data must be able to find every file, understand what each layer represents, and trust that the spatial reference is correct. A disorganized project folder forces the recipient to reverse-engineer your work, introduces errors, and can delay deliverables. Professional data management is not optional; it is part of the finished product.

This lesson teaches you to create and manage the two most common geospatial container formats—Esri file geodatabases and OGC GeoPackages—and to build the folder structures and metadata records that make project handoff reliable.

File Geodatabases (ArcGIS Pro)

A file geodatabase (FGDB) is a folder with the extension `.gdb` that stores feature classes, tables, rasters, and relationship classes in a structured way. Each feature class holds one geometry type (point, line, or polygon) and its attribute table. The file geodatabase supports topology rules, domains, and subtypes, making it the standard container for professional ArcGIS workflows.

To create one in ArcGIS Pro:

1. Open the Catalog pane.

2. Right-click your project folder → New → File Geodatabase.

3. Name it using your project naming convention (see below).

4. Right-click the new `.gdb` → New → Feature Class for each layer you need.

5. In the Feature Class wizard, set the geometry type and, critically, the coordinate system (spatial reference) before you click Finish.

Always set the spatial reference at creation time. Changing it later requires a projection or reprojection step that can introduce small coordinate shifts if done carelessly.

GeoPackages (QGIS)

A GeoPackage (`.gpkg`) is a single SQLite file defined by the Open Geospatial Consortium (OGC). It stores multiple vector and raster layers in one portable file, works across platforms, and requires no proprietary software. QGIS reads and writes GeoPackages natively.

To create one in QGIS:

1. Go to Layer → Create Layer → New GeoPackage Layer.

2. Choose a file path and name.

3. Define the geometry type and CRS for the first layer, then click OK.

4. To add more layers to the same `.gpkg`, right-click the file in the Browser panel → New Layer, or use Database → DB Manager for more control.

GeoPackages are especially useful for field collection with mobile apps and for sharing data with clients who do not use Esri software.

Naming Conventions

Consistent names prevent confusion. A common professional convention uses underscores (no spaces or special characters), descriptive terms, and version numbers:

• Project folder: `ProjectID_ClientName_Year` → `2024_SmithFarm_BoundarySurvey`
• Geodatabase: `2024_SmithFarm_Survey.gdb`
• Feature class: `ControlPoints_NAD83`, `ParcelBoundary_NAD83`, `Easements_NAD83`
• Documents: `2024_SmithFarm_DataManagementPlan_v1.pdf`

Rules to follow: no spaces, no leading numbers in feature class names, capital letters only at the start of each word (CamelCase or Title_Case), always include the coordinate system abbreviation in the layer name.

Recommended Folder Structure

A standard project folder for a boundary survey might look like this:

```

2024_SmithFarm_BoundarySurvey/

├── 01_Raw_Data/

│ ├── CSV/

│ └── Shapefiles/

├── 02_GDB/

│ └── 2024_SmithFarm_Survey.gdb

├── 03_Maps/

├── 04_Reports/

├── 05_Photos/

└── 06_Deliverables/

```

Numbered prefixes force folders into logical order regardless of the operating system's sort behavior.

Metadata and the FGDC Standard

Metadata is structured information about your data. The Federal Geographic Data Committee (FGDC) Content Standard for Digital Geospatial Metadata defines the fields that government agencies and many private clients require. Minimum fields for a professional handoff include:

• Title and abstract — what the dataset is and why it was created
• Publication date
• Originator / Point of contact — who created it and how to reach them
• Spatial reference — coordinate system and datum
• Horizontal accuracy — positional accuracy statement
• Use constraints — any licensing or redistribution limits

In ArcGIS Pro, open the Catalog pane, right-click a feature class → View Metadata → Edit to enter FGDC fields. In QGIS, use Layer → Properties → Metadata tab.

Incomplete metadata is one of the most common deficiencies cited in geospatial project audits. Make it a habit to fill metadata at creation time, not after the project is complete.

Backup Strategy

A professional data management plan must specify backup. A practical minimum is the 3-2-1 rule: keep 3 copies of the data, on 2 different media types, with 1 copy stored off-site or in cloud storage. For a surveying project this might mean: working copy on your workstation SSD, daily backup to a network drive, and weekly sync to cloud storage.

Safety Considerations

Data management is an office task, but safe computing practices still apply. Maintain clean cable management at workstations to prevent trip hazards. Use password-protected accounts and encrypted storage for any project data that contains personally identifiable client information. Never store the only copy of survey control data on a single device; loss of raw control point coordinates can require expensive re-observation in the field.