-
Notifications
You must be signed in to change notification settings - Fork 9
20171106 Palmerston North
The SWG met during the OGC meeting in Palmerston North on 20171206 and discussed several topics.
The primary source of the terminology in this standard is the ISO Terminology Spreadsheet published 20171019. Reese Plews has volunteered to check the terminology against this source and to add the correct sources into this document.
The correct syntax for the terminology references is: [SOURCE: ISO 19111:2007, definition 4.8].
Emmanuel Devys identified several terms related to coverages that are defined, but not used in the document. We will delete definitions for items that are not in the document.
There is a significant amount of information in this document that refers to EPSG information that is now obsolete. Roger Lott will identify this information and delete it and note those deletions in an informative annex to the standard. This should be done in a way that minimizes changes in the standard.
The current standard is inconsistent with community practice with regard to Axis order (see http://www.opengis.net/spec/GeoTIFF/0.0/GTModelTypeGeoKey.geographic). This issue is also in the repository (https://github.com/opengeospatial/geotiff/issues/1).
We decided to address this issue (and others in the git repository) in revisions that are expected to happen after the current version of the standard is in the OGC process.
cf. https://github.com/opengeospatial/geotiff/issues/10 A requirement class should be added to express the rules on combination or these tags (and Cardinality of TiePPoints), including tags that can't be used together (e.g. ModelPixelScaleTag + ModelTransformation). Even and Emmanuel have agreed to elaborate a proposal for this additional requirement class Note: this is also (at least in part) related to the topic below.
Even recently added an issue to the git repository about incompatible tag combinations and priorities (https://github.com/opengeospatial/geotiff/issues/13). I suggest that we use that issue to collect examples (one is already there).