Title

GIS Data Submittal Standards

Body

Purpose

This document outlines the digital Geographic Information Systems (GIS) data submittal requirements for all contractors, consultants, and third parties providing spatial data to the City of Santa Barbara. Adherence to these standards ensures consistency, compatibility, and accuracy across the City's enterprise GIS system.

Scope

These standards apply to any digital spatial data submitted to the City of Santa Barbara in support of planning, development, engineering, environmental, utility, transportation, public works, or other municipal projects that include GIS deliverables.

General Requirements

Data Format

  • All spatial data must be delivered in ESRI File Geodatabase format (.gdb).
  • The file geodatabase should be compatible with ArcGIS Pro 3.x or newer.
  • Avoid using personal geodatabases (.mdb) or shapefiles unless explicitly requested.

Coordinate System and Projection

All spatial data must be projected to:

  • Coordinate System: NAD 1983 (2011) StatePlane California V (FIPS 0405)
  • Projection: State Plane Coordinate System, Zone 5, US Survey Feet
  • WKID: 64295
  • Unit: US Foot

Data Organization

  • Data should be organized logically in the geodatabase (e.g., feature datasets for different themes like utilities, parcels, transportation, etc.).
  • Feature classes should be clearly named, using descriptive and intuitive naming conventions.
  • Include metadata or a data dictionary that describes each dataset, including field definitions, domain values, and data sources.

Attribute Standards

All feature classes must contain relevant and accurate attribute data:

  • Fields should follow consistent naming conventions (e.g., no special characters or spaces; use underscores).
  • Use standard field types appropriate to the data (e.g., Date, Double, Text).
  • Coded value domains or subtypes should be used when applicable to enforce data integrity.

Topology and Geometry Requirements

Data must be topologically clean:

  • No gaps, overlaps, or dangles (for polygons and lines).
  • No duplicate features or null geometries.
  • Polygons must be properly closed and lines properly snapped.
  • Geometry must be valid (e.g., no self-intersecting polygons).

Metadata

Each dataset must include basic metadata, at minimum:

  • Title
  • Description/Purpose
  • Data source
  • Date of creation and last update
  • Contact information
  • Coordinate system/projection
  • Metadata should conform to FGDC or ISO 19115 standards when possible.

Delivery Method

Deliverables must include:

  • Data should be delivered via secure file transfer (e.g., SharePoint, FTP, or USB).
  • File geodatabase (.gdb) packaged in a ZIP file.
  • Accompanying documentation (e.g., metadata, readme file).
  • Any relevant symbology files (.lyrx) if applicable.

QA/QC and Review

  • Data will be reviewed by City GIS staff upon submission.
  • Submissions not meeting these standards will be returned for revision.
  • It is the responsibility of the submitter to correct and resubmit any issues identified.

Optional/Recommended Best Practices

  • Include a map document or layout (PDF or .pagx) showing the data visually.
  • Provide a change log if the data is a revision of a previously submitted dataset.
  • Use of domains, relationship classes, and attachments when appropriate is encouraged for richer data models.