TRACES import error · EUDR

TRACES GeoJSON import: "Expected double-quoted property name in JSON" — how to fix it

If your GeoJSON is rejected with SyntaxError: Expected double-quoted property name in JSON at position 149 (line 6 column 77), the file is not valid JSON — the import fails in the browser before TRACES even looks at the geometry. The position numbers move with your file; the constant part is Expected double-quoted property name in JSON. Verified verbatim-identical on acceptance builds 8.2.0.1 and 8.2.0.2.

Fix your file — free

EUDR is mandatory for medium & large operators from 30 December 2026 — get your supplier files TRACES-ready now.

Files never leave your browser · no upload

Why you get "Expected double-quoted property name in JSON"

JSON requires every property name to be wrapped in double quotes and forbids trailing commas. Files exported or hand-edited from Excel, Python dictionaries or JavaScript often use single quotes, unquoted keys, or a stray comma after the last item. The browser's JSON.parse stops at the first offending character — the reported position — and TRACES surfaces the raw SyntaxError.

Because it fails at parse time, there is no map, no area, no partial import — just the error.

Fix it in DDSpass

DDSpass runs the file through jsonrepair: it adds the missing double quotes, removes trailing commas and closes brackets, then validates the result against the EUDR GeoJSON File Description. You get a TRACES-ready file plus a report of what was broken. Stuck on a format instead? See Excel, KML and Shapefile imports. Nothing is uploaded — the repair happens in your browser.

Questions

What does "Expected double-quoted property name in JSON" mean?

Your JSON has a property name that is not wrapped in double quotes (or a trailing comma before it). It is a syntax error, so the file cannot be parsed until it is repaired.

The position number is different in my error — does it matter?

No. The position (and line/column) just points at where parsing failed in your specific file. The fix is the same: repair the JSON syntax.