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
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
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 asa, and the change isn't said. It also hides the #1907 notices:"a \u{1}"is written asaand read back asa, but the export counts the value before the characters are dropped, so the trim isn't counted either. - NUL bytes (Shapefile): reading a
.dbfcuts 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
folderorstylewhose 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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from opengeos/RustGIS
-
[Bug]: layer.move to the place a layer already has fails and stops a script; with several layers it leaves an empty undo stepPossibly taken @jgregoriorincon claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opengeos/RustGIS#2621 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
opengeos/RustGIS#1446 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
All issues in opengeos/RustGIS
Similar issues
-
文件夹重大BUG:不支持重命名Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
postgresql-rules / queue-rules: implicit KEY SHARE before a parent key update, and job self-overlapOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jonathanong/no-mistakes#3879 ·
Maintainers usually reply within 1 day
-
area:index v0.35.0
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pbakaus/impeccable#1653 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
nautechsystems/nautilus_trader#5741 ·
Maintainers usually reply within 1 day