You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove "Inc." from the Patent Call. The use of "Inc." in OGC standards stopped a couple of years ago. "Inc" was not in the Foreward in the 2014 edited version. Inc was in the Patent Call. In the published version, the Foreward was removed and the Patent call clause was kept.
Remove the duplicate paragraph from the introduction. The paragraph starts with, "This OGC Encoding Standard . . .". The words are the same as in the abstract.
I would suggest changing the first sentence in the Abstract. I have been struggling with the wording. The standard actually specifies SQLite rules and extensions that allow the creation and use of a container we call a GeoPackage. I will think some more about this.
In section 1.1.1. change GeoPackage specification to "GeoPackage standard"
Observation: Requirement 2 will need to be more generalized if and when there is a new version (1.1, 1.2, 2.0).
Requirement 4. Suggesting changing sentence, "SQLite databases that use constructs from the GeoPackage specification but extend that to contain any of these elements are referred to as Extended GeoPackages throughout this specification." to "SQLite databases that use constructs from the GeoPackage standard but extend those constructs to contain elements not specified in the core GepPackage standard are referred to as Extended GeoPackages throughout this standard."
A general suggestion. All the footnote references are at the end of the entire document. This makes navigation a bit of a pain at times. Perhaps informative clarifications should simply be embedded in the main text and not a footnote. And references to external documents should also just be links to the document and not included in a footnote. An example would be for Requirement 6 and 7. Instead of having the reader jump to footnote 4 at the end of the document, simply put that text in the main document. I would also add an informative statement and reference/link; e.g. "The PRAGMA statement is an SQL extension specific to SQLite and used to modify the operation of the SQLite library or to query the SQLite library for internal (non-table) data. (https://www.sqlite.org/pragma.html)"
Observation: In requirement 11, "Cartesian coordinate reference systems" and "geographic coordinate reference systems" are not defined.
Section 2.1.1 - "International specifications" should be "International standards". Whether the OGC document says "spec" or not, the references are ISO standards.
Section 2.1. - "closed topology". I think you need a definition. When I quickly think of closure, I think of a closed polygon boundary. However, in topology, "closure of a subset S in a topological space consists of all points in S plus the limit points of S". Now this will mean about absolute nothing to the average reader. Perhaps a link to a reference or some English words?
Section 2.2.1 - The sentence/paragraph " Unfortunately, no applicable existing consensus, national or international specifications have standardized practices in this domain." may need to be changed when DGGS becomes an OGC standard.
Requirement 45: Expand WMTS to Web Map Tile Service as this is the first instance.
Section 2.5.1 (sort of) to a few OGC staff and members, the GeoPackage Extension template(s) cannot be normative as they have never been independently presented, discussed, and approved by the OGC Membership. I would suspect that the majority of Members who voted on the document never saw the extension templates. This is actually my fault. I should have caught this back in early 2014. As TC Chair, I would have raised a red flag at that time and asked that the templates be presented at a DocTeam SC meeting and then go through a formal OGC vetting process. Individual SWGs should not be defining document templates. The can make recommendations.
Extensions. Perhaps the extensions should be in a separate document.
The text was updated successfully, but these errors were encountered: