PlotProof · Starter migration centre

File formats and sample records.

Compare the browser checker's tested inputs with matching synthetic files. These examples explain file structure; they do not import records into a PlotProof workspace.

Persistent import status

File import is not available in this Starter slice.

The plot checker reads a selected file in your browser tab and can offer a separate cleaned download after review. It does not create or update workspace records. The current Starter has no file-to-workspace migration path or imported-record external ID field.

Browser checks

Three tested file inputs

These are checker inputs, not persistent import formats. No other format behavior is claimed here.

.geojson

GeoJSON

The browser checker accepts a FeatureCollection, a Feature, or a supported geometry object.

Expected structure

{
  "type": "FeatureCollection",
  "features": [{
    "type": "Feature",
    "properties": {
      "plot_id": "SAMPLE-001",
      "external_id": "SAMPLE-SOURCE-001",
      "sample_data": true,
      "description": "Synthetic sample data for trying file checks only. Not supplier data, a real plot, or evidence of geographic or legal eligibility."
    },
    "geometry": {
      "type": "Polygon",
      "coordinates": [[
        [12.345678, 50.123456],
        [12.355678, 50.123456],
        [12.355678, 50.133456],
        [12.345678, 50.133456]
      ]]
    }
  }]
}

Synthetic sample · not supplier or real-plot data

Download .geojson sample

.json

JSON containing GeoJSON

The file contents must be a GeoJSON FeatureCollection, Feature, or supported geometry object.

Expected structure

{
  "type": "Feature",
    "properties": {
    "plot_id": "SAMPLE-001",
    "external_id": "SAMPLE-SOURCE-001",
    "sample_data": true,
    "description": "Synthetic sample data for trying file checks only. Not supplier data, a real plot, or evidence of geographic or legal eligibility."
  },
  "geometry": {
    "type": "Point",
    "coordinates": [12.345678, 50.123456]
  }
}

Synthetic sample · not supplier or real-plot data

Download .json sample

.csv

CSV

Include plot_id, longitude and latitude. Use one row per plot vertex; rows with the same plot_id are grouped as one plot.

Expected structure

plot_id,longitude,latitude,external_id,sample_data
SAMPLE-001,12.345678,50.123456,SAMPLE-SOURCE-001,true
SAMPLE-001,12.355678,50.123456,SAMPLE-SOURCE-001,true
SAMPLE-001,12.355678,50.133456,SAMPLE-SOURCE-001,true
SAMPLE-001,12.345678,50.133456,SAMPLE-SOURCE-001,true
SAMPLE-001,12.345678,50.123456,SAMPLE-SOURCE-001,true

Synthetic sample · not supplier or real-plot data

Download .csv sample

Identifier fields

Keep the sample IDs visible

The examples include a synthetic plot_id and external_id. In GeoJSON they are feature properties; in CSV, plot_id, longitude and latitude are required columns, while external_id is an additional field. The browser checker carries parsed properties into its separate cleaned output. This does not persist an external ID in workspace records because this Starter slice has no file importer.