> ## 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.

# My coordinates were rejected

> My coordinates were rejected — Polygon One

1. Read the message beside the file or affected row.
2. Check the coordinate columns. Manual entry uses latitude, longitude; GeoJSON uses longitude, latitude.
3. Check the actual reference system (WGS 84 for import), decimal degrees, production country and hectares for points.
4. For insufficient precision, obtain original data at its full available precision. Correct the source and review the import again.

## Message and safe fix

<table>
  <thead>
    <tr><th scope="col">Message</th><th scope="col">What it means</th><th scope="col">What to do</th></tr>
  </thead>

  <tbody>
    <tr id="geo-save-reason-parseError"><td>The row could not be read\
    `parseError`</td><td>The importer could not interpret the content of this row.</td><td>Check the original row's format, separator and coordinate fields, then upload the corrected file again.</td></tr>
    <tr id="geo-save-reason-precisionRejected"><td>Coordinate precision too low\
    `precisionRejected`</td><td>The reported coordinates have too few decimal places. At least four are required; coordinates with four or five decimal places are accepted with a warning, and six (the EUDR format) are recommended. If your customer requires six decimal places, four or five are rejected as well. Trailing zeros do not count.</td><td>Use a more precise original source or redraw the plot from a reliable source. Do not append zeros.</td></tr>
    <tr id="geo-save-reason-decisionRequired"><td>Needs a decision before it can be imported\
    `decisionRequired`</td><td>The flagged row requires an explicit review before import.</td><td>Review the row in the import preview and make the requested decision before saving again.</td></tr>
    <tr id="geo-save-reason-missingGeometry"><td>The row has no usable coordinates\
    `missingGeometry`</td><td>No point or polygon could be built from the row.</td><td>Check the coordinate columns, order and value ranges, then upload the corrected source again.</td></tr>
    <tr id="geo-save-reason-missingArea"><td>Point coordinate without an area in hectares — add the area or upload a polygon\
    `missingArea`</td><td>A point has no area of its own, and the real positive area is missing.</td><td>Enter the actual hectares from your source or upload the plot's real boundary as a polygon.</td></tr>
    <tr id="geo-save-reason-pointAreaCap"><td>Area too large for a point coordinate — above 4 ha (20,000 ha for cattle) EUDR requires a polygon\
    `pointAreaCap`</td><td>One point is not sufficient for the plot's actual area.</td><td>Upload the real plot boundary as a polygon. Do not reduce the area to get past the check.</td></tr>
    <tr id="geo-save-reason-productionPeriodMissing"><td>The plot has no production period — set the production start and end dates\
    `productionPeriodMissing`</td><td>No production period for this row (EUDR Art. 9(1)(d)).</td><td>Add a date in the file or in the import. One date is enough.</td></tr>
    <tr id="geo-save-reason-productionPeriodInverted"><td>The production period ends before it starts\
    `productionPeriodInverted`</td><td>The row's end date is earlier than its start date.</td><td>Correct both dates from the actual production period, then upload the file again.</td></tr>
    <tr id="geo-save-reason-invalidRow"><td>The row is incomplete or invalid\
    `invalidRow`</td><td>At least one required value cannot be used; this message does not name a more specific field.</td><td>Check every required value in the row against the original source, correct it and upload again.</td></tr>
    <tr id="geo-save-reason-precisionMixed"><td>This row has a mixed-precision classification and is rejected by the supplier import.\
    `precisionMixed`</td><td>This legacy classification can result from coordinate formatting or number normalization; it does not by itself prove that the source coordinates use inconsistent precision.</td><td>Return to the original source or export the coordinates again at their full available precision. Never invent or append digits.</td></tr>
    <tr id="geo-save-reason-unknownError"><td>This row could not be processed. No specific cause is available.\
    `unknownError`</td><td>The importer did not return a reliable, more specific reason.</td><td>Check the original row and upload it again. If it still fails, give help the message, format and row number — not the invitation link.</td></tr>
  </tbody>
</table>

Do not change the production country or area merely to get past the check. Do not append zeros or invented digits. Rounding coordinates is not a repair for a precision message.

Still unclear? Contact help with the message, format and row numbers, never the invitation link.

No visible plots means the import did not succeed: check the result and open required fields.

## Related help

* [I have an Excel or CSV list](https://help.polygon-one.com/en/lieferanten/daten-formate/excel-csv.md)
* [I have coordinates in degrees, minutes and seconds](https://help.polygon-one.com/en/lieferanten/daten-formate/dms.md)
* [Get help with your request](https://help.polygon-one.com/en/lieferanten/hilfe.md)
* [Open your customer's request](https://help.polygon-one.com/en/lieferanten/start.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.