> ## Documentation Index
> Fetch the complete documentation index at: https://help.polygon-one.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Plot Import & Review Workflow

> Upload, review, and safely import CSV, Excel, and GeoJSON files

## Overview

The current plot import in Polygon One is a **staged review workflow**. You do not simply upload a file; instead, before the final import you see a structured preview with notes on precision, country plausibility, and individual problematic rows.

You usually open this workflow via **Plots → Import areas**. The supplier portal uses the same technical core, but there with stricter restrictions for suppliers.

## Supported File Formats

* **GeoJSON** and `.json`
* **CSV**
* **Excel** (`.xlsx`, `.xls`)

Depending on the file, Polygon One recognizes, among other things:

* GeoJSON geometries
* WKT geometry columns
* Point lists with latitude and longitude
* Properties such as area name, country, producer, and production data

## The Process in Detail

<Steps>
  <Step title="Assign supplier and articles">
    First, assign the import to a **supplier** and the affected **articles**. This assignment controls which supplier-article combination the areas are later available for in compliance, the map, and the DDS.
  </Step>

  <Step title="Upload the file">
    Upload the file. Polygon One accepts GeoJSON, CSV, and Excel and first processes the upload into a prepared preview rather than directly into the production inventory.
  </Step>

  <Step title="Review detected columns and mapping">
    The system largely detects the file format and columns automatically. If necessary, you adjust the mapping, for example for:

    * Area name
    * Country
    * Producer
    * Production start and production end
    * Area size for point geometries
    * Coordinate order or geometry column
  </Step>

  <Step title="Read the review panel and make decisions">
    After staging, you see a review interface with:

    * **Country plausibility check** for coordinates outside the expected production country
    * **Precision histogram** for the coordinates
    * **Normalization warnings**, such as automatically corrected coordinate order or removed polygon holes
    * **Issue register** with error rows and precision rows
    * **Search, tabs, and export** for the issue list
  </Step>

  <Step title="Confirm the import">
    Before the final import, you see a summary of how many areas:

    * are imported cleanly and directly
    * are imported with confirmed low precision
    * are deliberately skipped
  </Step>
</Steps>

## Row-Level Decisions

For flagged rows, the following decisions are available depending on the data situation:

| Decision                    | When it makes sense                                                            | Effect                                                                                                        |
| --------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------- |
| **Confirm & pad**           | The coordinates are technically correct but stored with too few decimal places | Polygon One accepts the row and technically pads the coordinates to the EUDR format when the DDS is submitted |
| **Skip this area**          | The row should deliberately not be imported                                    | The area remains excluded from this import run                                                                |
| **Buffer point to polygon** | Point geometries should be converted into a small area                         | For certain point data, a polygon can be derived from the center point                                        |

<Info>
  Low precision does not automatically mean incorrect geodata. The preview deliberately distinguishes between **technical plausibility** and **format/precision questions**.
</Info>

## Bulk Actions and Issue List

For larger files, the workflow offers additional bulk actions:

* **Confirm & pad all flagged**
* **Skip imprecise areas under 2 ha**
* **Reset decisions**
* **Export issue list**

The export is especially helpful when you want to clean up problematic rows with your supplier or data provider outside the platform.

## After the Import

After a successful import, you manage the areas in two places:

<CardGroup cols={2}>
  <Card title="Plots" icon="table-cells" href="/en/eudr/optional/plots">
    Table view with filters, precision check, bulk actions, and exports.
  </Card>

  <Card title="Map" icon="map" href="/en/eudr/optional/karte">
    Geographic control, detailed review, and risk assessment on the map.
  </Card>
</CardGroup>

<Tip>
  If a file contains many problematic rows, first export the issue list, clean up the source outside of Polygon One, and re-upload the corrected batch. This is usually faster than a fully manual row-by-row reconciliation.
</Tip>