In `.geojson` parsed, the index should be parsed from `.geojson`
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by reading spatialdata.models.ShapesModels.parse(), which currently parses the .geojson and is planned to move to spatialdata-io. Compare its behavior with the incoming seqFISH reader in issue #227, where the index is taken from the table. Done means the parser obtains each object's index from the .geojson rather than assuming it matches the table index.
Written by the indexing model from the issue text.
Description
The .geojson parsed (currently in spatialdata.models.ShapesModels.parse(), which will be moved to spatialdata-io, doesn't try to parse the index of the object from the .geojson file.
This behavior should be implemented. For instance in the incoming seqFISH reader #227 the index is assumed to match the index from the table (which is reasonable and expected), but more robust parser would read it from the .geojson.
CC @LLehner @quentinblampey
- Dominant language
- Python
- Stars
- 103
- Forks
- 64
- Avg merge
- 1h 8m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No 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 scverse/spatialdata-io
-
documentation
Difficulty 2/5 Half a day Newbie friendliness 65/100
scverse/spatialdata-io#161 · 13 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
scverse/spatialdata-io#422 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
scverse/spatialdata-io#419 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 48/100
scverse/spatialdata-io#409 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
scverse/spatialdata-io#408 ·
All issues in scverse/spatialdata-io
Similar issues
-
Layers of type "3D Unknown" and "3D Measured Unknown" are refused, so FileGDB multipatch layers can't be readPossibly taken @aidannewsome claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
quantization
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/vllm#59904 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mikf/gallery-dl#9791 ·
-
Speaker custom-fields CSV export returns 404 instead of downloading dataPossibly taken @techvoyager-varun claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
fossasia/eventyay#6151 · 1 comment ·
Maintainers usually reply within 1 day
-
P4: low tooling
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
jeffknupp/association#318 ·