Skip to content

Import Parcels

The parcel importer supports two formats:

  • GeoJSON
  • GeoCSV

General Requirements

The file size limit for files is 95MB. If your file exceeds this, you must split your file up.

Only parcels being imported into the parcel table are currently supported.

GeoJSON

The GeoJSON must be projected to EPSG:4326/WGS 84.

Each geometry must, at a minimum, have a property that contains the APN data for each parcel. The GeoJSON file should be a GeoJSON FeatureCollection which contains an array of GeoJSON Polygon or MultiPolygon objects.

A very basic example might look like this:

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {"apn": "someapnvalue"},
      "geometry": {
        "type": "Polygon",
        "coordinates": [
          [
            [
              -80.85937499999999,
              35.496456056584165
            ],
            [
              -80.37597656249999,
              35.496456056584165
            ],
            [
              -80.37597656249999,
              35.99578538642032
            ],
            [
              -80.85937499999999,
              35.99578538642032
            ],
            [
              -80.85937499999999,
              35.496456056584165
            ]
          ]
        ]
      }
    }
  ]
}

We do not currently support individual Polygon or MultiPolygon uploads at this time.

GeoCSV

GeoCSV is a standard CSV file.

Ours must have two columns:

  • One column with the parcel's APN data
  • One column with the parcel geometry (as in WKT format)

    • The WKT must be projected in EPSG:4326/WGS 84. Each WKT should be a Polygon or MultiPolygon. An example GeoCSV might look like this:

      apn,geometry

      "someapnvalue","POLYGON ((-80.85937499999999 35.496456056584165, -80.37597656249999 35.496456056584165, -80.37597656249999 35.99578538642032, -80.85937499999999 35.99578538642032, -80.85937499999999 35.496456056584165))"