opengeospatial / opengeospatial/CRS-JSON-Encoding
Consistency with ISO 19115-4
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 0
- Forks
- 2
- Avg merge
- 1h 36m
- Merged PRs (30d)
- 3
Description
The ISO 19111 model contains at least 3 metadata elements from ISO 19115-1: Citation, Extent and PositionalAccuracy. A JSON encoding for metadata is being defined as ISO/AWI TR 19115-4 – MetadataPart 4: JSON schema implementation of metadata fundamentals (currently under development). If a standard metadata encoding is defined, we may want to avoid inventing another standard inside CRS JSON. We may also consider defining other CRS elements using the same pattern as ISO 19115-4 for consistency.
ISO 19115-4 is not ready yet, but progress have been reported during the OGC meeting at Montreal. We may use the current state, and update the CRS JSON draft as needed when ISO 19115-4 draft changes.
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
No repository file or test is named. Start by reviewing the current CRS JSON draft and the linked ISO 19115-4 work, then determine whether Citation, Extent, PositionalAccuracy, and other CRS elements should follow the same metadata pattern; done means the project has an agreed consistency decision and an updated draft if needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100