You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Exports don't say when text is trimmed, blank text becomes null, or an empty field is left out #1907
The never-silent round-trip property (#1904) lists what each export format can't hold. Most entries are format limits, but these change values without a notice, and are listed only until an export says them:
Text trimmed (CSV, Shapefile, KML, GPX): reading trims the spaces around a value, so " lead" comes back as "lead".
Blank text read as null (CSV, Shapefile, KML, GPX): an empty string comes back as null.
A field that is null everywhere left out (KML, GPX): the file has no value for it, so the column isn't read back.
Each needs an export notice with a count and the fields, like the Shapefile notes (shapefile_values_notes); then its entry comes off LIMITS / TEXT_FORMAT_LIMITS in crates/engine/tests/never_silent_roundtrip.rs.
I'm working on this. Each export to CSV, Shapefile, KML or GPX will say how many values reading the file back will trim or turn into nulls, and which fields are empty in every feature, naming the fields. Then those entries come off the round-trip test's list. A draft PR will follow soon.
Activity
fix(data): read text as the file has it: keep spaces, count <Null> re…
flight1973 commentedon Nov 18, 2026
I'm working on this. Each export to CSV, Shapefile, KML or GPX will say how many values reading the file back will trim or turn into nulls, and which fields are empty in every feature, naming the fields. Then those entries come off the round-trip test's list. A draft PR will follow soon.