The AFAcodes-softwareGen generates the fwg_cm extension, which provides the structure needed to generate the CM grid. This issue refers to the table structure (columns, partitions, etc.) and the SQL scripts used to materialize the grid.
Parameters for the grid to be built:
- Grids from L0 to L16 (cells of 1.05 km²)
- Basic columns:
<gid, gid_prefix, geocode_sci, geocode_logstc, jurisdictions, geom>.
geocode_sci is the scientific code, e. g. a330c (or universal CM+a330c in a VIEW).
geocode_logstc is the "minimal" logistic code (e. g. M) and jurisdictions array {BE1~S,DNG~}, so, when we has more than one jurisdiction, each has its concatenation: BE1~SM, DNG~M.
gid_prefix is a smallInt column with the first 8 bits of the cell_id of all grids.
PARTITION BY RANGE (gid_prefix), perhaps 2 or 4 ranges, for L16 not need many.
The AFAcodes-softwareGen generates the
fwg_cmextension, which provides the structure needed to generate the CM grid. This issue refers to the table structure (columns, partitions, etc.) and the SQL scripts used to materialize the grid.Parameters for the grid to be built:
<gid, gid_prefix, geocode_sci, geocode_logstc, jurisdictions, geom>.geocode_sci is the scientific code, e. g.
a330c(or universalCM+a330cin a VIEW).geocode_logstc is the "minimal" logistic code (e. g.
M) and jurisdictions array{BE1~S,DNG~}, so, when we has more than one jurisdiction, each has its concatenation:BE1~SM,DNG~M.gid_prefix is a smallInt column with the first 8 bits of the cell_id of all grids.
PARTITION BY RANGE (gid_prefix), perhaps 2 or 4 ranges, for L16 not need many.