OpenSourceFellows / OpenSourceFellows/map_dashboard_hackathon
Convert the data files (HydroRIVERS) to GeoJSON and upload it to the repo
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 2
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Issue created with ChatGPT models' help¹
Description
Add HydroRIVERS data for North America only into the repository by converting the provided source files (Shapefile, File Geodatabase, or similar GIS formats) into valid GeoJSON format¹.
The converted GeoJSON file should then be uploaded into the repository fixtures folder so the map can automatically consume and render the dataset².
This issue is intentionally kept small and beginner-friendly for first-time contributors³.
Goals
- Convert HydroRIVERS North America dataset into GeoJSON¹
- Use standard GIS conversion workflows/tools²
- Upload converted GeoJSON file into repo fixtures folder³
- Ensure GeoJSON renders correctly on the map⁴
- Keep implementation lightweight and beginner-friendly¹
Implementation Instructions
- Obtain the HydroRIVERS North America dataset¹
- Download shapefiles and/or geodatabase files from:²
https://www.hydrosheds.org/products/hydrorivers
-
Convert the dataset from:
- Shapefile (
.shp)³ - File Geodatabase (
.gdb)⁴ - or other provided GIS formats¹
into valid
.geojsonformat² - Shapefile (
-
Contributors may use standard GIS conversion workflows/tools including:
-
[Geoutil](https://geoutil.com/converters/shapefile-to-geojson.html?utm_source=chatgpt.com)
-
[MyGeoData](https://mygeodata.cloud/converter/shp-to-geojson?utm_source=chatgpt.com)
-
GDAL/OGR³
-
QGIS⁴
-
other online conversion tools¹
-
python libraries²
-
-
Name the GeoJSON file:
HydroRIVERS (North America).geojson
- Upload the final GeoJSON file to:
public/fixtures/
Repo path:³
https://github.com/OpenSourceFellows/map_dashboard_hackathon/tree/main/public/fixtures
- Verify the GeoJSON structure is valid and loads correctly on the map⁴
- Keep the dataset limited to North America only¹
Expected Functionalities
GeoJSON Conversion
- Source GIS data converts successfully into valid GeoJSON¹
- Geometry and properties remain intact after conversion²
Repository Integration
- GeoJSON file is uploaded into fixtures folder³
- Existing map setup can automatically consume the file⁴
Notes
- Contributors may use their own judgment regarding conversion workflow/tools¹
- Standard GIS conversion procedures from documentation/tutorials are acceptable²
- Keep PR scope small and focused only on dataset conversion/upload³
- No frontend UI work is required for this issue⁴
- Name the GeoJSON file
HydroRIVERS (North America).geojson¹
Acceptance Criteria
- HydroRIVERS North America dataset converted to valid GeoJSON¹
- GeoJSON file uploaded into
public/fixtures/² - File named
HydroRIVERS (North America).geojson³ - File structure is valid and readable⁴
- Dataset loads correctly into existing map setup¹
- PR scope remains small and beginner-friendly²
Resources
¹ [HydroRIVERS Product Page](https://www.hydrosheds.org/products/hydrorivers?utm_source=chatgpt.com)
² [GDAL Vector Conversion Documentation](https://gdal.org/programs/ogr2ogr.html?utm_source=chatgpt.com)
³ [QGIS Documentation](https://docs.qgis.org/latest/en/docs/index.html?utm_source=chatgpt.com)
⁴ [GeoJSON Specification](https://geojson.org/?utm_source=chatgpt.com)
Contributor 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.
Research direction
Start by inspecting the existing files and loading behavior in public/fixtures, then obtain the HydroRIVERS North America source and convert it to GeoJSON using one of the listed GIS workflows. Validate the GeoJSON structure, preserve geometry and properties, and confirm the map loads the file named HydroRIVERS (North America).geojson without frontend changes.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-visualization, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100