Join GitHub today
Inconsistency in Figure 6. GeoPackage Minimal Tables for Tiles #117
In my understanding as the primary key of
An other possibility is to have
I talked this over with @pdaisey today and we determined that the associations in question should be 1..0-1. The reason for the '0-' is because a gpkg_contents entry doesn't necessarily correspond to a gpkg_tile_matrix_set entry (it might be features instead). We suspect that the '*' multiplicity is an oversight that was not corrected when we prohibited multiple geometry columns per feature table.
It will take me longer to acquire and install the software used to make this diagram than it will to make the actual changes.