issues
search
opengeospatial
/
CoverageJSON
Public repo for CoverageJSON project
Apache License 2.0
10
stars
8
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Vote Comment - 1.9 ranges and rangeAlternates
#35
chris-little
closed
2 years ago
5
Vote Comment - 1.7 Alignment with OGC Standards Baseline
#34
chris-little
closed
2 years ago
3
Vote Comment - 1.6 Alignment with OGC Standards Baseline
#33
chris-little
closed
2 years ago
8
Vote Comment - 1.5 Other Factors
#32
chris-little
closed
2 years ago
2
Vote Comment - 1.4 Primary Benefits
#31
chris-little
closed
2 years ago
2
Chris little patch 1 replace standard by specification
#30
chris-little
closed
2 years ago
1
Vote Comment - 1.3 General (Need for Relation with existing Coverage OGC/TC211 standards)
#29
chris-little
closed
2 years ago
2
VoteComment - 1.2 General (CovJSON as an OGC standard)
#28
chris-little
closed
2 years ago
3
VoteComment - 1 to be sub-divided
#27
chris-little
closed
2 years ago
4
Should PROJJSON be used rather than "text" WKT2 for CRS while awaiting an official JSON encoding from CRS SWG?
#26
jerstlouis
opened
2 years ago
6
Comparisons
#25
chris-little
closed
2 years ago
1
Clause 1- Scope should clarify the scope (i.e technical scope) of this OGC standard
#24
EmDevys
closed
2 years ago
4
Comparison of CoverageJSON with ISO19123 (both 2005 and draft 2022)
#23
chris-little
opened
2 years ago
6
Clarify high level goals in preamble
#22
jonblower
closed
2 years ago
1
Create conceptual model?
#21
jonblower
closed
1 year ago
28
Create a downloadable PDF/HTML version of the spec
#20
chris-little
closed
2 years ago
2
How to plan the work, short and longer term
#19
chris-little
closed
2 years ago
3
Update standard_document.adoc
#18
chris-little
closed
2 years ago
0
AsciiDoc formatting and non-display of text
#17
chris-little
closed
2 years ago
1
Registration of CURIE prefixes
#16
chris-little
opened
2 years ago
2
All the spec in the new clause
#15
chris-little
closed
2 years ago
1
Can we separate the specification text into normative or informative?
#14
chris-little
opened
2 years ago
5
Migration to full OGC Standard 4: Switch from IETF normative terminology to ISO terminology
#13
chris-little
opened
2 years ago
3
Conformance tests
#12
chris-little
closed
2 years ago
17
How should we process the 22 outstanding CoverageJSON issues
#11
chris-little
closed
2 years ago
13
How to update the proposed Community Standard
#10
chris-little
closed
2 years ago
3
Representation of multiple time axes
#9
chris-little
opened
2 years ago
0
IPR status needs confirming
#8
chris-little
closed
2 years ago
4
PC04: Editorial Improvements to Justification OGC21-040r2
#7
chris-little
closed
3 years ago
2
PC03: Support coverages as per standard, or rename
#6
chris-little
closed
3 years ago
3
PC02:- CoverageJSON does not support coverages
#5
chris-little
closed
2 years ago
5
PC01: Without prior motion nor discussion in the Coverages WG
#4
chris-little
closed
3 years ago
4
Public Comments on CoverageJSON as an OGC Community Standard
#3
chris-little
closed
2 years ago
1
adopt content from CovJSON community
#2
marqh
closed
4 years ago
2
correct typos
#1
marqh
closed
4 years ago
1
Previous