Guidelines for Creating and Contributing GIS Datasets

Overview

With this guide, we aim to foster cooperation between the City of St. Louis and external organizations to enhance geographic data accuracy, standardization, and accessibility. This collaboration ensures that GIS data supports informed decision-making, infrastructure planning, and public services.

Member Responsibilities

Adhere to established GIS data standards and metadata guidelines.
Share relevant geospatial datasets that contribute to public projects and city planning.
Participate in periodic meetings and data review sessions.
Ensure compliance with data privacy, security, and licensing agreements.

Data Format and Projection

• All submitted data must be in ESRI-compatible formats (e.g., File Geodatabase, Shapefile, GeoJSON).
• The standard projections are:
  • NAD 1983 StatePlane Missouri East FIPS 2401 (US Feet)
  • WGS84 WEB Mercator
• PDF format should be the primary static document. This can be coupled with an editable DOCX/Excel and a web-based interactive version which provides a comprehensive and adaptable solution

City Extents

for NAD 1983 StatePlane Missouri East FIPS 2401 (US Feet)

City + Airport

• Top   1,074,104.73 ftUS
• Left  824,950.24   ftUS
• Right 959,299.2    ftUS
• Down  979,885.98   ftUS

City

• Top     1,071,768.37  ftUS
• Left    833,948.68    ftUS
• Right   961,279.4     ftUS
• Bottom  982,471.5     ftUS

Airport

• Top    1,083,370.04   ftUS
• Left   830,184.58     ftUS
• Right  885,624.58     ftUS
• Down   1,044,490.04   ftUS
   

For WGS84 WEB Mercator

City + Airport

• Top    15,390,233.57 ftUS
• Left  -33,048,227.23 ftUS
• Right -32,872,771.5  ftUS
• Down   15,267,186.69 ftUS

City

• Top    15,385,315.16  ftUS
• Left   -33,039,713.78 ftUS
• Right  -32,877,291.9  ftUS
• Down    15,271,408.91 ftUS

Airport

• Top     15,395,706.3  ftUS
• Left   -33,031,916.18 ftUS
• Right  -32,976,476.18 ftUS
• Down    15,356,826.3  ftUS

Metadata Requirements

Every dataset must include metadata following FGDC or ISO 19115 standards, including:

• Data source and collection methodology
• Accuracy and update frequency
• Data owner and contact information

Data Use, Privacy, and Security

• All data shared within EMCG must comply with local, state, and federal data privacy and security regulations.
• Sensitive datasets (e.g., infrastructure security, emergency response) require appropriate access controls and agreements.
• Data contributors retain ownership but grant the City permission to use, distribute, and modify datasets for public projects.

Submission Process

• Coordinate with the Departmental contact.
• Agree on the how and where to submit the materials.
• Confirm you have all the required documentation (metadata, map description, purpose statement).
• All data use, privacy, and security requirements are met. 

Contact