Error ".geojson files having no features" while running docker run command
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, shell
- Domain
- data, devops, machine-learning
Research direction
Start by reproducing the Docker run command from the linked gist and inspect the dataset paths, including /spacenet/processedData/3band/3band_Rio_OUTLINE_Public_AOI.geojson.tif. Trace the GeoJSON inputs and rio rasterize step to determine why features are empty or the TIFF is absent; done means documenting the required inputs, their locations, and whether a direct TIFF ground-truth workflow is supported.
Written by the indexing model from the issue text.
Description
Hey, I am new to docker and wanted to play around with the spacenet code for segmentation.
Unfortunately when I try to run your docker script, I face the following issues ->
1> An error pops up while running the docker run command as reproduced in the gist link below:
https://gist.github.com/PraveerSINGH/b8104d218d238732babccfbe89b00399.
Why are the .geojson files having no features ?
Also regarding rio rasterize error in the above link, I don't find this file in my local machine even though I downloaded the dataset from AWS link: /spacenet/processedData/3band/3band_Rio_OUTLINE_Public_AOI.geojson.tif
Is this present in the docker container or somewhere else ?
2> I am also new to the OpenStreetMap + Satellite Imagery training data generation using .geojson files. Is there any workaround that simply gives me tiff ground truth images of segmentation maps for each color images in the 3-band ?
Thanks in advance.
- Dominant language
- Shell
- Stars
- 43
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No 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 developmentseed/spacenet-data
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
All issues in developmentseed/spacenet-data
Similar issues
-
electron tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
alunduil/alunduil-chezmoi#870 ·
Maintainers usually reply within 1 day
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
oSoWoSo/vOid_Community_repOsitory#268 · 1 comment ·
Maintainers usually reply within 1 day
-
feature good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dsx-ai-factory/infra-controller#7298 · 1 comment ·
Maintainers usually reply within 1 day
-
rebrand-literal-gutter: uhttpd section-vocabulary check trips on a COMMENT (uhttpd.luci in 92-tollgate-admin-setup:178)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenTollGate/tollgate-module-basic-go#723 ·
Maintainers usually reply within 1 day