opengeospatial / geopackage

An asciidoc version of the GeoPackage specification for easier collaboration
https://www.geopackage.org
Other
264 stars 71 forks source link

Extension to allow negative zoom levels (potential concern for CDB grid negative levels) #514

Open jerstlouis opened 4 years ago

jerstlouis commented 4 years ago

CDB LODs go down to -10 where tiles are 1x1 pixels.

jyutzler commented 4 years ago

In today's SWG meeting, we approved this request because there is no clear benefit to this requirement, the potential interoperability risk is slight, and it is desirable to support CDB directly.

jyutzler commented 4 years ago

@jerstlouis please propose alternate text for the first paragraph of http://www.geopackage.org/spec121/index.html#zoom_levels in light of this change.

tabinfl commented 4 years ago

Are we making GeoPackage zoom levels equal to CDB LODs? They are not the same in the respective specs and we should consider carefully implications of conflating the two.

jerstlouis commented 4 years ago

In a GeoPackage, zoom levels are integers in sequence that identify tile matrices in a tile matrix set that contain tiles of progressively finer spatial resolution. Adjacent zoom levels immediately precede or follow each other and differ by a value of 1.

Also later in that paragraph it says:

Other "zoom other intervals" conventions use different factors

Is that second other there superfluous?

jerstlouis commented 4 years ago

@tabinfl The idea is to allow encoding content from multiple CDB LODs in a GeoPackage. This is possible with the new TileMatrixSet extension ( https://gitlab.com/imagemattersllc/ogc-vtp2/-/blob/master/extensions/14-tile-matrix-set.adoc ) which supports varying width tile matrices, which can represent both the CDB zones and CDB LODs ( as described here: http://maps.ecere.com/geoapi/tileMatrixSets/CDBGlobalGrid ).

jyutzler commented 4 years ago

Since this change is not sufficient by itself to completely satisfy the CDB LOD requirement, the SWG decided to defer this change until after 1.3. One possibility is rolling it into a new extension as described in #504.