add support for other GeoJson types (LineString, MultiLineString)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 18.3k
- Forks
- 2k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 28
Description
From: Screen Shot 2023-01-24 at 10.40.45 AM
Note that we only accept GeoJSONs of type "FeatureCollection" or "Feature" with geometries of type "Polygon" or "MultiPolygon".
I see a few references to LineString and MultiLineString here but I'm uncertain if they are actually support or if the docs are old?
Here is a CodePen that should work if this feature was supported.
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 src/lib/geojson_utils.js and reproducing the linked CodePen example to trace how Feature and FeatureCollection geometries are handled. Determine the existing support for LineString and MultiLineString, then verify that both GeoJSON types render correctly alongside Polygon and MultiPolygon inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100