opengeospatial / opengeospatial/CoverageJSON
Do we need a PolygonArray or PolygonCollection domain type?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 15
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
I think we have agreed (#202) that the interpretation of MultiPolygon should be as a single domain element, with a single associated range value that applies collectively to all the constituent Polygons. (This is currently inconsistent with the Playground, which would need to be fixed.) But this leaves an obvious question - how should we encode a situation where we want to associate different range values with each individual polygon? For example, recording the population of each of the countries of Europe.
Maybe we need a new domain type - perhaps PolygonArray or PolygonCollection? The domain would look structurally similar to a MultiPolygon but the associated range would be different.
This would also imply a need for a PolygonCollectionSeries.
Contributor guide
No contributing guide indexed for this repository
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 reading issue #202 and the current MultiPolygon interpretation, then inspect the Playground behavior mentioned here. Determine whether PolygonArray or PolygonCollection is needed for per-polygon range values and whether that also requires PolygonCollectionSeries. Done means the domain model and Playground behavior have an agreed, documented direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100