Preparing your upload

Vectra reads one upload of your parcel and construction data, checks it, and shows you what it found before anything runs. Here is what that upload must contain — and a working sample to compare against.

Download the sample delivery (.zip)

This is the exact dataset our automated pipeline checks render end-to-end — PDF exhibits, KMZ, and shapefiles for every parcel — whenever the pipeline or the dataset changes. Upload it as a project to see the full flow, or open it in your GIS to compare layer names and structure against your own data.

• A GeoPackage (.gpkg), or
• a zipped FileGDB or shapefiles (.zip). Zip the .gdb folder itself — a zip made from inside the geodatabase (loose table files at the zip root) will be rejected at upload.
• Maximum size: 200 MB.

Two layers are mandatory — the data check fails without them:

• Parcels (polygons) — recognized names: Parcels, Parcel, Tracts, Parcels_Input, Parcel_Set (case doesn't matter).
• Centerline (line) — recognized names: Centerline, CL, Center_Line, Route. Without it, crossing lengths cannot be computed.

Each parcel needs an identifier. Vectra detects the field automatically — it looks for PARCEL_ID, PARCEL_NO, TRACT_ID, TRACT_NO and close variants — and shows you its pick (with sample values) for confirmation before anything runs. Blank or duplicated IDs don't block the check, but they're flagged: blanks get placeholder IDs and duplicates are suffixed, so clean IDs make cleaner exhibits. An owner-name field (OWNER, OWNER_NAME, …) is picked up the same way when present.

• Permanent Easement (polygons) — ESMT, Easement, PE, Permanent_Easement
• Temporary Workspace (polygons) — WS, TWS, Workspace, Temporary_Workspace
• Additional Temporary Workspace (polygons) — ATWS, Additional_Workspace
• Access Roads (lines) — Access_Roads, Access, Roads, AR, TAR
• Surface Sites (polygons) — SS, Surface_Sites, Surface, Staging, Staging_Sites
• Survey Points (points) — Survey_Points, Points, Monuments, Control; each point should carry TYPE, CAP, and PARCEL_ID fields.

Layers with other names aren't lost — the data check lists them as unmatched so you can see exactly what was and wasn't recognized.

Use a projected CRS — a US State Plane zone (feet) is the expected case. Vectra detects the zone from where your data actually sits and shows the detection (with alternatives) on the review page; acreage and length tables come from that projected geometry. The data check tolerates unprojected or mixed-CRS layers rather than failing — so look at the detected zone on the review page: an unexpected zone there is the sign of a projection problem, and confirming past it is how wrong-looking acreage numbers happen.

1. Data check (about a minute): layers matched, zone detected, parcel key picked, cross-section measured.
2. Review page: you confirm what was found — nothing renders until you approve it.
3. Processing: per-parcel exhibits, acreage/length tables, and GIS deliverables are generated.

If the check finds a problem, the job page says exactly what was missing — fix the data and upload again, or contact us with the message shown.

Start a project