GeoJSON (RFC 7946) → Darwin Core
What you are seeing — your records are a FeatureCollection and you need decimalLatitude and decimalLongitude columns.
GeoJSON is straightforward to convert, with one trap that is responsible for a lot of misplaced records. RFC 7946 fixes the coordinate order as [longitude, latitude] — longitude first. Darwin Core, and almost every conversation about coordinates, says latitude first. Anything that reads a GeoJSON position as a lat/long pair produces records that are confidently in the wrong hemisphere, and the values are legal so nothing complains.
The other half of the conversion is that your attributes live under properties on each feature, and the geometry lives beside it under geometry. A flat table needs the properties as columns plus two coordinate columns lifted out of the geometry.
RFC 7946 also fixes the coordinate reference system: GeoJSON is WGS 84, full stop. The crs member from the older 2008 specification is gone. If your file carries one naming something else, that file predates the standard and its coordinates need reprojecting before you trust them as latitude and longitude.
We read a FeatureCollection directly and take the coordinate order from the specification rather than from a header. Non-Point geometries we refuse by name. A polygon has no single coordinate, and reducing it to a centroid would invent a point the surveyor never recorded — for a crescent-shaped or ring-shaped site the centroid is not even inside it.
We take the coordinate order from RFC 7946 rather than guessing, lift the properties into columns, and tell you plainly if any features carry a geometry we will not reduce to a point. Free until 1 September, no account, and your records are discarded after the check — we keep the column mapping, never the rows.
Check the file you have →We audited a file GBIF had already accepted and served. Their validator answers will this load; these had loaded. Figures read from ops/data.json, not typed into this page. We do not issue a rating of any kind — every finding names the rule it applied and where that rule comes from.