Integrated GIS Project: Boundary Survey Data Package

Integrated GIS Project: Boundary Survey Data Package

Why This Lesson Matters

A professional surveyor or GIS technician rarely hands a client a single file. Instead, they deliver a complete, organized data package: a clean geodatabase, exported standard formats, a publication-ready map, and documentation that lets anyone reproduce or audit the work. This lesson walks you through every stage of that workflow—from raw GNSS import to final deliverable—mirroring what you will do on the job and what employers will expect from day one.

Step 1 — Importing and QA/QC of GNSS Points

Your starting material is a comma-separated values (CSV) file exported from a GNSS receiver. Before any analysis begins, verify the data:

• Check coordinate fields. Confirm which columns hold latitude, longitude (or Northing/Easting), and ellipsoidal height. Mixing these up produces points in the ocean or inside a building.
• Verify the source datum. Field-collected GNSS typically comes in WGS 84 (EPSG 4326). Note it in your QA/QC log.
• Look for outliers and nulls. Sort by X and Y. Any coordinate far outside the project area is a blunder; flag and investigate before deleting.
• Check point identifiers. Each control monument and parcel corner should have a unique ID matching your field notes.

In ArcGIS Pro, use Add XY Data (or the XY Table To Point geoprocessing tool) to convert the CSV to a point feature class. In QGIS, use Layer → Add Delimited Text Layer, specifying the correct X and Y fields and the source CRS.

Step 2 — Reprojecting to State Plane

All deliverables for boundary surveys in the US are expected in a defined projected coordinate system—almost always the appropriate State Plane zone for your area. State Plane coordinates are in US Survey Feet or meters, which makes distance and area calculations meaningful and legally defensible.

Use Project (Data Management) in ArcGIS Pro or Reproject Layer in QGIS to transform your points from geographic (WGS 84) to the correct State Plane zone (NAD83). Store the reprojected feature class inside your project geodatabase—never overwrite the raw import.

Step 3 — Joining Assessor Data and Spatial Analysis

The assessor CSV contains parcel attributes (owner name, APN, acreage). Join it to your parcel polygon shapefile using the shared parcel number field: Add Join in ArcGIS Pro or Join Attributes by Field Value in QGIS. After the join, run a Buffer on the road centerline shapefile at 50 feet (using the State Plane layer so the units are correct). Then use Select by Location (or the equivalent spatial query) to identify which parcel polygons intersect or fall within that 50-foot right-of-way buffer. Document each tool, input, and parameter in your workflow summary as you go—it is far easier to write it live than to reconstruct it later.

Step 4 — Producing the Final Map Layout

A boundary survey map at 11×17 inches must include specific cartographic elements to meet professional standards:

| Required Element | Notes |

|---|---|

| Title block | Project name, date, preparer, scale |

| North arrow | Clearly oriented |

| Scale bar | Matches stated map scale |

| Legend | All symbols and colors explained |

| Coordinate system note | State Plane zone, datum, units |

| Parcel boundary | Bold, labeled with APN and dimensions |

| Control monuments | Distinct symbol, unique IDs |

| Right-of-way buffer | Semi-transparent fill |

| Terrain contours | From 1-m DEM; labeled at appropriate intervals |

| Neatline and border | Clean frame |

Choose a scale that fits the parcel on the page without crowding labels. Common choices for residential parcels are 1:600 or 1:1200. Use your cartographic standards checklist to verify every element before export.

Step 5 — Assembling the Project Data Package

Organize your geodatabase with a clear, logical structure: one feature dataset per theme (Survey_Control, Parcels, Transportation, Analysis). Export a Shapefile set and a georeferenced PDF map. For each feature class, complete a one-page metadata record using the provided template; at minimum, record the feature class name, geometry type, CRS, source data, date created, and field definitions.

Your written workflow summary (300–500 words) should describe every processing step in plain language: what tool you ran, what inputs you used, what outputs you created, and why you made each decision. A colleague who was not present should be able to reproduce your work exactly.

Safety and Professional Conduct

Although this lesson is office-based, two safety points apply:

• Data integrity is a safety issue in surveying. Incorrect boundary data can cause legal disputes, construction encroachments, or unsafe utility work. Never alter source data; always work on copies inside the geodatabase.
• File hygiene prevents data loss. Save frequently, maintain backups to a second location, and never store the only copy of a deliverable on a removable drive.

Keep your workspace organized and version your files clearly (e.g., `Parcels_QC_v1`, `Parcels_QC_v2`). Professional offices are audited; sloppy file management is a liability.