Exports don't say when they drop control characters (KML, GPX), when text is cut at a NUL (Shapefile), or KML fields named like its own columns

Open
#2,415 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
data

Research direction

Start by reading the related issue #1907 and the work in #2414, then trace the KML and GPX writers through interop::xml() and the Shapefile .dbf reader. Check how export notices count changed values and report affected fields. Done means each of the three silent losses produces a notice with a count and field names, consistent with #1907.

Written by the indexing model from the issue text.

Description

Three more silent losses on export, found while working on #1907 (#2414). Each changes text with no notice:

  • Control characters (KML, GPX): the writer drops control characters from names and data values (interop::xml()). So "a\u{1}" is written as a, and the change isn't said. It also hides the #1907 notices: "a \u{1}" is written as a and read back as a, but the export counts the value before the characters are dropped, so the trim isn't counted either.
  • NUL bytes (Shapefile): reading a .dbf cuts text at the first NUL byte, so "ab\0cd" reads back as "ab" and "\0x" as null.
  • KML fields named like the reader's own columns: a field called folder or style whose values all match the reader's column of that name is dropped on read.

Each needs an export notice with a count and the fields, like the #1907 notices.

Dominant language
Rust
Stars
1.9k
Forks
268
Avg merge
11h 1m
Merged PRs (30d)
942

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from opengeos/RustGIS

All issues in opengeos/RustGIS

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.