LandCode
Paulding County › Unified Development Ordinance

Title 3 — Development Regulations, Chapter 420 — Geospatial Information System (GIS)

Code as publishedas of 2026-04-14
Our copyPaulding County's file changed after 2026-10-19 · our copy does not yet carry it
StatusOfficial
official source ↗3 sections · full chapter
§ 420-10

Purpose

Paulding County has adopted Geospatial Information Systems (GIS) technology for the management and analysis of spatial data. The GIS requirements are designed to support data maintenance, data accuracy, and data compatibility relating to the County’s Enterprise GIS.

These requirements shall apply to all site plans for re-zoning applications, development plans (subdivision developments, multi-family residential developments, commercial developments and industrial developments) and design plans (for County Projects). It is the intent of these requirements to:

420-10.01 Aid the process of updating the spatial data stored within the County’s Enterprise

GIS with the inclusion of new developments and projects as described above, thus helping to ensure the currency of the system’s data through a more efficient data maintenance program; and to

420-10.02 Perpetually increase the accuracy of the spatial data stored within the Enterprise

GIS; and to

420-10.03 Ensure that the data, which must be submitted in a digital file, meets specifications

ensuring its compatibility with the County’s Enterprise GIS.

§ 420-20

Geodetic Control

420-20.01 Geodetic Control Network.

The County has established a Geodetic Control Network to provide accurate control as a base for its Enterprise GIS and for use by surveyors, engineers and others. The County will make available all pertinent Geodetic Control Network information.

420-20.02 Coordinate Systems.

The County has adopted the Georgia State Plane Coordinate System (West Zone) and the 1983 North American Datum (NAD83) for horizontal georeferencing and the North American Vertical Datum of 1988 (NAVD88) for vertical georeferencing within its Enterprise GIS and its Geodetic Control Network (Note: NAD83 GA State Plan West FIPS 1002). Orientation shall be to Grid north. The adopted units are U.S. survey feet. All site plans, plats, as-builts and design plans shall be based on these coordinate systems, data, orientation and units.

420-20.03 Required Ties to Geodetic Control

All site plans, plats, as-builts and design plans shall have a minimum of two separate boundary points tied to at least one of the County’s Geodetic Control Network monuments if they are located within 500 feet. The basis of bearing for the plans shall conform to Section 420-20.04.

420-20.04 Identification & Description of Tie-In Points.
A.The two boundary points tied to the County’s Geodetic Control Network shall be identified on the plat as CTR1 and CTR2.
B.Each site plan, plat, as-built and design plan shall include a Geodetic Control Table as shown in Table 420.1:

Table 420.1 Geodetic Control Table Geodetic Control Boundary Tie-In Points ID Northing Easting Bearing Distance ID Northing Easting Elevation CTR 1 CTR 2

C.The bearings and distances provided in the table shall describe the bearings and distances from the Geodetic Control Network monument to the boundary tie-in points, and shall conform to Section 420-20.04.
420-20.05 Maintenance & Densification of Geodetic Control Network.

The County will ensure the proper maintenance of its Geodetic Control Network, including the replacement of destroyed monuments, and will pursue ongoing densification of the network as needed. Missing or destroyed monuments shall be reported to the Information Technology Department’s GIS Division.

§ 420-30

Digital Submission Standards

420-30.01 Scope.

Development and design plans are created using Computer Aided Design (CAD) software. It is the goal of Paulding County to leverage these advanced technologies to expedite the design and plan review processes and to enhance the maintenance operations for the County’s GIS data.

Digital data files, conforming to the following standards, shall be submitted to the County for all site plans, plats, as-builts and design plans as specified in Section 420-30.02.

420-30.02 Required Files.
Digital files must be submitted for the following items:
A.Boundary Surveys for Rezoning Applications
B.Preliminary Plats
C.Construction Plans (including Site Plans, Utility Plans and Landscape Plans)
D.Final Plats
E.Design Plans for all County Projects (including Right-of-Way Plans)
420-30.03 General Requirements.
A.The digital data must be mapped to scale and georeferenced to the County’s adopted coordinate systems and datum described in Section 420-20.02.
B.The digital data must be tied to the County’s Geodetic Control Network as described in Sections 420-20.03 and 420-20.04 if located within 500 feet.
C.The digital data shall include all available features and corresponding layer names indicated in Table 420.2 shown below, and shall be organized by layer in the order shown.
D.Features other than those defined by the layer name shall not be included in the same layer. Such features may be included in layers beyond those required.
E.No annotation shall be included in any feature layer and no feature shall be included in any annotation layer. Annotation for each layer shall be placed in annotation layers as recommended in the Table 420.2.
F.No polylines or annotation shall be stored in blocks. Any blocks that exist must be exploded in order to eliminate data migration problems. XRefs must be bound prior to resubmittal.
G.All points shall be stored as “POINT” or “BLOCK REFERENCE” (cannot be Softdesk Point or AECC_point or any other feature type).
H.Parcel boundaries must support polygon generation. All partial parcel boundaries shown for reference must be included in the PARCREF layer.
420-30.03 Naming Convention.

Digital data files shall be named using the development name and phase/s in the following way: bentwater_phaseG.

420-30.04 Data Format.

Digital data files shall be provided to the County in one of the following formats:

A.DXF (AutoCAD Drawing Exchange File)
B.DWG (AutoCAD Drawing File)
C.DGN (Microstation)
D.SHP (ESRI Shape File)
E.Personal Geodatabase File (ESRI ArcGIS File)

Table 420.2 Recommended Digital Layering Structure

Table 420.2
Layer #Layer NameFeature TypeLayer Description
1ROWPolylinePublic/Private Street Right-of-Ways
2PARCELPolylineParcel/Lot Boundaries
3PARCREFPolylineParcel/Lot Boundary References
4SUBDIVPolylineSubdivision/Development Boundaries
5BLDGPolylineBuilding/Structure Footprints or Outlines
6LANDLOTLPolylineLand Lot Lines
7LANDLOTCPointLand Lot Corners
8
9
10COUNTYPolylineCounty Boundary
11MUNICIPALPolylineMunicipal Boundaries
12
13
14HYDROLPolylineLinear Hydrography (creeks,streams,etc)
15HYDROPPolylinePolygonal Hydrography (ponds, lakes, etc)
16WETLANDPolylineWetlands
17FLOODPPolylineFlood Plain
18FLOODWPolylineFlood Way
19
20
21CNTRLINEPolylineStreet Centerlines (paved and unpaved)
22EOPPolylineEdge of Pavement
23CURBPolylineCurb/Gutter
24SIDEWLKPolylineSidewalks
25RRROWPolylineRailroad Right-of-Ways
26RRCNTRLNPolylineRailroad Centerlines
27
28
29EASEMENTPolylineEasements (other than utility)
30EASEUTILPolylineEasements (utility – electric, gas, phone, cable)
31SETBACKPolylineBuilding Setback Lines
32BUFFERPolylineBuffers (riparian, vegetation, etc.)
33
34
35WTRLINKPolylineWater Pipes
36WTRNODEPointWater Junctions, Fittings, etc.
37WTRVALVEPointWater Valves
38WTRMTRPointWater Meters
39FIREHYDPointFire Hydrants
40WTRTEXTTextAnnotation describing water (WTR) features
41WTREASPolylineWater Easements
42
43SSLINKPolylineSanitary Sewer Pipes

44 SSNODE Point Sanitary Sewer Manholes, Pumps, Junctions, etc.

45 SSVALVE Point Sanitary Sewer Valves 46 SSTEXT Text Annotation describing sanitary sewer (SS) features 47 SSEAS Polyline Sanitary Sewer Easements 48 49 SDLINK Polyline Storm Drain Pipes, etc.

50 SDNODE Point Storm Drain Manholes, Junction Boxes, etc.

51 SDTEXT Text Annotation describing storm drain(SD) features 52 SDPOND Polyline Detention/Retention Ponds 53 SDEAS Polyline Storm Drain Easements 54

Table or figure — shown as printedverify at source ↗
55        RWLINK         Polyline         Reuse Water Pipes
Table or figure — shown as printedverify at source ↗
56        RWNODE         Point            Reuse Water Junctions, Fittings, etc.
Table or figure — shown as printedverify at source ↗
57        RWVALVE        Point            Reuse Water Valves
Table or figure — shown as printedverify at source ↗
58        RWMTR          Point            Reuse Water Meters

59 RWHYD Point Reuse Water Hydrants, Blow-Off Assemblies, etc.

60 RWTEXT Text Annotation describing reuse water (RW) features 61 RWEAS Polyline Reuse Water Easements 62

Table or figure — shown as printedverify at source ↗
63        GAS            Polyline         Gas Features
Table or figure — shown as printedverify at source ↗
64        ELECTR         Polyline         Electrical Features
Table or figure — shown as printedverify at source ↗
65        TELCO          Polyline         Telephone Features
Table or figure — shown as printedverify at source ↗
66        CTV            Polyline         Cable TV Features
Table or figure — shown as printedverify at source ↗
67        CTVACC         Point            Cable TV Access Points
Table or figure — shown as printedverify at source ↗
68        FIBER          Polyline         Fiber Datacom Features
Table or figure — shown as printedverify at source ↗
69        FIBERACC       Point            Fiber Datacom Access Points
Table or figure — shown as printedverify at source ↗
70        WIRLACC        Point            Wireless Datacom Access Points

71 UTTEXT Text Annotation describing features 63 through 70 72 73

Table or figure — shown as printedverify at source ↗
74        LOTNUM         Text             Lot Number Text
Table or figure — shown as printedverify at source ↗
75        LOTDIM         Text             Lot Dimension Text
Table or figure — shown as printedverify at source ↗
76        SUBNAME        Text             Subdivision Name Text
Table or figure — shown as printedverify at source ↗
77        STRNAME        Text             Street Name/Number Text
Table or figure — shown as printedverify at source ↗
78        RRNAME         Text             Railroad Name Text
Table or figure — shown as printedverify at source ↗
79        HYDTEXT        Text             Hydrographic Features Text
Table or figure — shown as printedverify at source ↗
80        EASETEXT       Text             Easement Text (for items 29, 30, 31, 32, 41, 47, 53,  61)

Additional layers not identified in Table 420.2 above may be included on any open layer beyond the 80 reserved layers. As outlined in the Geospatial Information Systems (GIS) Requirements, a list of these layers shall also be submitted, conforming to Section 420-30.07 of those requirements.

420-30.05 Media.

Digital files shall be submitted to the County on removable media (flash drive for example) or via the internet through an online submission application and shall be appropriately identified. An open standard data compression, including but not limited to WinZip, may be used if necessary.

420-30.06 Required Data Layers and Documentation.

Each digital file submitted shall include Digital Layering Structure as recommended in able 420.2. A text file (in a County approved format) identifying and describing all data layers included with the submission shall accompany each digital data file.

Such files shall follow the naming convention described in Section 420-30.03 with ‘_layers’ added at the end. (Example: bentwater_phaseG_layers)

420-30.07 Required Metadata.

A text file (in a County approved format) containing the information {metadata} outlined in Table 420.3 shall accompany each digital data file. Metadata files shall follow the naming convention described in Section 420-30.03 with ‘_meta’ added at the end. (Example: bentwater_phaseG_meta)

Table 420.3 Required Metadata

Table 420.3
Digital Data Metadata
Submittal Date:
Development Name:
Phase/s:
Creation/Revision Date:
County:
City:
Parent Parcel Number/s:
Number of Lots:
Geodetic Control:
Paulding County Geodetic Control Monument/s Referenced (ID#):
GPS Used (Y/N)?:
GPS Unit Type:
PDOP of Control Points:
Correction Method (postprocessing, RTD, RTK):
Prepared By (Firm Name):
Engineer or Surveyor of Record:
Telephone Number:
Address:
Drawing File Name:
Drawing File Format:
Reading grid · rebuilt for display · verify at source (p. 424) ↗