List of required front-end changes (not exhaustive):
create new pmtiles layer from shapefile (done)
create new pmtiles layer for zone unit labels based on centroid of polygons (done)
field names in the new pmtiles files differ from the old files, so updating field names in order to access
property values on the front-end is required
No longer using the 'mof fire zone id' field, instead use 'objectid'
Calls to our API using the mof fire zone id will now need to use the objectid
Potentially update interfaces in fbaAPI.ts including FireZone and FireZoneArea
Update ShapeTypeEnum to include value of 'fire_zone_unit'
Drop rows from Shape table (ie. advisory_shapes). Populate Shape table from geojson (derived from the shape file using QGIS). Note that source-Identifier will now be the OBJECTID values.
Alternatively, just add new rows to the Shape table using the OBJECTIDs and new shape type enum value of fire_zone_unit
rename FireZoneArea schema to FireShapeArea and change mof_fire_zone_id property name to fire_shape_id (front-end work required to match this change when parsing API responses
rename FireZoneHighHfiAreas to FireShapeHighHfiAreas' and change name of mof_fire_zone_id' property
As a person issuing or receiving fire behaviour advisories
I need the scale of analysis to be fire zone units
So That the advisory aligns with current BCWS practices and do not get influenced by disparate geographies like Fraser Zone and Haida Gwaii.
Acceptance Criteria
Additional Context