Chapter 10 - Evaluation and Submission PDF

Geotagging of Missing Building Points from Processed Post- Census Maps and EA Delineation for the Development of
EARF for the 2022 CAF
CHAPTER 10: EVALUATION AND

SUBMISSION
For the preparation of maps for the 2022 CAF, there will be two (2) sets of
evaluation. The first set will be after the EA delineation activity while the second set will
be done after digitizing the block boundary.
After the enumeration area (EA) delineation activity, the barangay, EA2022, and
geotagged building structure layers shall undergo evaluation by the Map Data Reviewer
(MDR). The quality of the new EA boundary is crucial and must be properly evaluated to
ensure the concordance with the EARF of the 2022 CAF.
After finalizing the EA boundary, the digitization of the block boundary follows and
must be evaluated before proceeding to the generation of PDF maps.
The PFP shall assign the evaluation process to the MDR-PSO. After the evaluation
at the provincial office, the PFP shall submit the maps to the regional office for the conduct
of further evaluation by the MDR-RSSO.
NOTE:
For this activity, it is highly recommended that the field offices use their Desktop
Supercomputer for the digitization and processing phases.
Chapter 10 Evaluation and Submission |381

10.1 SUBMISSION PROCESS FLOW OF SUBMITTED GIS-BASED CENSUS MAPS
EA Delineation for the Development of the EARF for 2022 CAF
START
PSO
PSO GIS Unit
Evaluation
NO
Passed QA?
YES
Archive
RSSO GIS Unit RSSO
Evaluation
NO YES Archive
Passed QA?
CO Mapping Unit CO
Census Mapping Submission
Facility
Evaluation
NO YES
Passed QA? Recoding and Renumbering Archive
Send to RSSO
RSSO Send to PSO
382| Chapter 10 Evaluation and Submission

Listed below are the specific measures to be done to ensure the quality of GIS-
based census maps before submitting to the RSSO and CO, respectively.
1. For the Enumeration Area Boundary Layer (ppmm_ea2022)
i. Check if the boundaries are properly digitized (snapped) with no

gaps, overlaps and error in the vertices of polygons.
ii. Check the geocodes of the enumeration area for uniqueness.
There should be no duplicate geocodes.
iii. Check if the first seven digits of the geocode of the EA matches
the geocode of the barangay it belongs to.
iv. Check if the geocode in the ppmm_ea2022 match with the EARF
and vice versa.
v. Check if there are gaps and overlaps with adjacent
city/municipality.
2. For the Barangay Boundary Layer (ppmm_bgy)
i. Check if the geocode of the barangay matches with the first seven
digits of the geocode of the EA.
ii. Check if there are gaps and overlaps with adjacent
city/municipality.
3. For the Geotagged Building Structures Layer (ppmm_bldg_point)
i. Check if the verified true destroyed/demolished buildings and

verified false new buildings are deleted.
ii. Check if there are geotagged building structures outside the
municipal/barangay boundary. If this is the case, the affected
geotagged building structures points should be transferred to
their respective municipalities.
IMPORTANT NOTICE
The MDR-PSO and MDR-RSSO are tasked to conduct a 100% evaluation of
the barangay, geotagged building point, and EA2022 layers (delineated and not).

Block Mapping for 2022 CAF
A BLOCK MAPPING
PSO
PSO GIS Unit
Evaluation
NO
Passed QA?
YES
Archive
RSSO GIS Unit

RSSO
Evaluation
NO YES
Passed QA? Archive
CO Mapping Unit
CO
Census Mapping Submission
Facility
Evaluation
Archive
NO YES
Passed QA? Finalize
END

Listed below are the specific measures to be done to ensure the quality of GIS-
based census maps before submitting to the RSSO and CO, respectively.
1. For the Block Boundary Layer (pppmm_block)
i. Check if the boundaries are properly digitized (snapped) with no gaps,

overlaps and error in the vertices of polygons.
ii. Check the block number per enumeration area for uniqueness. There
should be no duplicate block number.
iii. Check for the completeness of the attribute table.
iv. Check if the block layer covers all the geotagged building structures.
10.2 HOW TO ACCOMPLISH THE PSO AND RSSO EVALUATION FORM
The PSO and RSSO Evaluation Form will serve as a monitoring facet in assuring
the quality of the output GIS-based maps after the digitization, field validation, and
post-processing phases of this undertaking in the regional and provincial offices.
The PSO and RSSO Evaluation Form consist of four columns: Column 1(Quality
Assurance Number); Column 2 (Description); Column 3 (Indicative Measure); and
Column 4 (Evaluation Status).
The Map Data Reviewer (MDR-PSO and MDR-RSSO), with the guidance of the
Provincial Focal Person (PFP) and the Regional Focal Person for Mapping (RFP),
respectively, is tasked to conduct a 100% review and evaluation of the accomplished
GIS-based map output of the Map Data Processors (MDPs) before its submission to
the Central Office (CO). After thorough review and evaluation, the PFP and the RFP
with the help of the MDR, shall consider the indicative measures and determine
whether the measure based on the evaluation is either acceptable or needs further
modification.

An indicative measure with status of 1 (Acceptable) signifies that the specific

measure was duly accomplished with satisfaction, whereas an indicative measure
given a status of 2 (Needs Modification), might pose further problems in the map and
may require immediate intervention from the PFP/RFP for mapping or from the FO/CO
supervisors.
Provincial Statistics Office (PSO) Standard Review

The initial evaluation of the processed GIS-based maps shall be done at the
provincial office by the Map Data Reviewer (MDR) under the supervision of the Provincial
Focal Person (PFP) for Mapping.
Listed below are the specific criteria/measures to consider upon conducting the
evaluation of the GIS-based maps before its submission to the regional office:
Evaluation
Status
Quality
Description Indicative Measure 1 – Acceptable
Assurance
2 – Needs
Modification
1.1 EA boundaries are properly

snapped without gaps and/or
Refer to
overlaps with its adjacent EAs
instruction on
and/or the same is properly
pages 405
snapped with the roads and/or
EA Boundaries (#3) to 407
rivers used as boundaries.
are properly (#5).
Moreover, the EA boundary shall
digitized, field have no invalid geometry/s.
QA 1 validated, and
assigned with a
proper 1.2 EA boundary updates are
geocode. verified in the field and the updates
are reflected on the ea2022 layer.
1.3 Each EA has a corresponding Refer to

geographic code with no duplicates. instruction on
pages 409

Evaluation
Status
Quality
Assurance
2 – Needs
Modification
(#6) to 410
(#7).
Refer to
1.4 EA geoID match with the instruction on
barangay. page 411
(#8).
Refer to
1.5 EA geocode match with the instruction on
Enumeration Area Reference File pages 411
(EARF) and vice versa. (#9) to 412
(#10).
2.1 The geotagged building

structures have undergone pre- Refer to
processing. The verified true instruction on
demolished buildings and verified page 415
Geotagged false new buildings (7000-series (#3).
building structures BSN) are deleted.
QA 2 are processed
and within 2.2 The geotagged building
boundary. structures are within the Refer to
municipality/barangay boundary. instruction on
Thus, no geotagged building page 415
structures outside corresponding (#4).
municipal boundary.
Proper and 3.1 The PSA-GIS/Province name

complete storage file structure and proper naming of
of GIS mapping subfolders is strictly followed.
files in the
QA 3 appropriate 3.2 The necessary GIS mapping
folders for files are complete and located in the
referencing. proper folder.
QA 4 Employs an 4.1 All GIS mapping files and

effective file materials are properly stored for

Evaluation
Status
Quality
Assurance
2 – Needs
Modification
backup scheme archiving for easy retrieval and
and efficient future referencing.
archiving
mechanism to
protect from data
loss and prevent 4.2 A back-up copy of all GIS
damage to mapping files used.
important GIS
Mapping files.
Evaluation
Status
Quality
Assurance
2 – Needs
Modification
1.1 Block boundaries are properly

Refer to
overlaps with its adjacent blocks
instruction on
pages 421
(#3) to 422
(#5).
Block Moreover, the block boundary shall
Boundaries are have no invalid geometry/s.
properly
QA 1 digitized and Refer to
assigned with a 1.2 Each block has a corresponding instruction on
proper geocode and block number with no pages 423
information. duplicates. (#6) to 424
(#7).
Refer to
1.3 The block layer must cover all instruction
the geotagged building structures. page 425
(#8).

Evaluation
Status
Quality
Assurance
2 – Needs
Modification

files in the
Employs an 3.1 All GIS mapping files and

archiving
QA 3 mechanism to
protect from data
important GIS
Mapping files.
In addition to the criteria/indicative measures that the PSO shall consider during
evaluation, the PSO is expected to strictly follow the instructions below:
1. Evaluate and resolve the gaps/overlaps between municipalities and the

adjacent province/s.
2. Follow the time period for the submission/re-submission of maps to RSSO.
a. The return/re-submission of evaluated maps between the RSSO and
PSO shall be limited to a maximum of three (3) returns.
b. The maps returned from RSSO back to PSO for correction/adjustment
shall only be allowed a time period of five (5) working days for each
return.
c. The PSO shall immediately address the error/s identified by the RSSO
evaluators and reflect the adjustments on the maps.
d. If the submitted maps from the PSO to RSSO still have errors after the
third re-submission for evaluation, this will reflect in the RSSO’s
grade/rating for the Field Awards.

Regional Statistics Office (RSSO) Standard Review
The second evaluation of the processed GIS-based maps shall be done at the
regional office by the Map Data Reviewer (MDR) under the supervision of the Regional
Focal Person (RFP) for Mapping.
Listed below are the specific criteria/measures to consider upon conducting the
evaluation of the GIS-based maps before its submission to the regional office:
Evaluation
Status
Quality
Assurance
2 – Needs
Modification
1.1 EA boundaries are properly

Refer to
overlaps with its adjacent EAs
instruction on
pages 405
(#3) to 407
(#5).
Moreover, the EA boundary shall
have no invalid geometry/s.
EA Boundaries
are properly 1.2 EA boundary updates are
digitized, field verified in the field and the updates
QA 1 validated, and are reflected on the ea2022 layer.
assigned with a
proper Refer to
geocode. instruction on
1.3 Each EA has a corresponding
pages 409
geographic code with no duplicates.
(#6) to 410
(#7).
Refer to
1.4 EA geoID match with the instruction on
barangay. page 411
(#8).

Evaluation
Status
Quality
Assurance
2 – Needs
Modification
Refer to
1.5 EA geocode match with the instruction on
Enumeration Area Reference File pages 411
(EARF) and vice versa. (#9) to 412
(#10).
2.1 The geotagged building

structures have undergone pre- Refer to
processing. The verified true instruction on
demolished buildings and verified page 415
Geotagged false new buildings (7000-series (#3).
building structures BSN) are deleted.
QA 2 are processed
and within 2.2 The geotagged building
boundary. structures are within the Refer to
municipality/barangay boundary. instruction on
Thus, no geotagged building page 415
structures outside corresponding (#4).
municipal boundary.

files in the

QA 4 archiving
mechanism to
protect from data 4.2 A back-up copy of all GIS
loss and prevent mapping files used.
damage to

Evaluation
Status
Quality
Assurance
2 – Needs
Modification
important GIS
Mapping files.
Evaluation
Status
Quality
Assurance
2 – Needs
Modification
1.1 Block boundaries are properly

Refer to
overlaps with its adjacent blocks
instruction on
pages 421
(#3) to 422
(#5).
Block Moreover, the block boundary shall
Boundaries are have no invalid geometry/s.
properly
QA 1 digitized and Refer to
assigned with a 1.2 Each block has a corresponding instruction on
proper geocode and block number with no pages 423
information. duplicates. (#6) to 424
(#7).
Refer to
1.3 The block layer must cover all instruction
the geotagged building structures. page 425
(#8).

QA 2

Evaluation
Status
Quality
Assurance
2 – Needs
Modification
files in the
appropriate 2.2 The necessary GIS mapping

archiving
QA 3 mechanism to
protect from data
important GIS
Mapping files.
In addition to the criteria/indicative measures that the RSSO shall consider during
evaluation, the RSSO is tasked to strictly follow the instructions below:
1. Evaluate the gaps/overlaps between provinces.

2. Monitor and follow-up the submission/re-submission of maps from the PSO.
a. The return/re-submission of evaluated maps between the RSSO and
PSO shall be limited to a maximum of three (3) returns.
b. The maps returned from RSSO back to PSO for correction/adjustment
shall only be allowed a time period of five (5) working days for each
return.
c. The RSSO shall immediately follow-up the submission of the returned
maps if the PSO has not submitted within the allowed time period of five
(5) working days.
d. If the submitted maps from the PSO to RSSO still have errors after the
third re-submission for evaluation, this will reflect in the RSSO’s
grade/rating for the Field Awards.

Central Office (CO) Standard Review Procedures

The final evaluation of the processed GIS-based maps shall be done at the Central Office
by the SOID-Mapping staff.
1. For the EA Delineation for the Development of the EARF for 2022 CAF, the CO
shall consider:
a. QA 1 (except 1.2) QA 2, and QA 3 (refer to the evaluation form for EA
delineation) upon conducting the evaluation of the GIS-based maps.
b. Gaps and overlaps between province/region. If the boundary problem
cannot be resolved by the RSSO/PSO, the CO shall intervene and define
an operational boundary.
2. For the Block Mapping for 2022 CAF, the CO shall consider QA 1 (refer to the
evaluation form for Block Mapping) upon conducting the evaluation of the GIS-
based maps.
In addition to the criteria/indicative measures that the CO shall consider during the
evaluation, the CO is tasked to grade or rate the quality of GIS-based maps submitted by
both the PSO and RSSO.
1. The return/re-submission of evaluated maps between the RSSO and CO shall be

limited to a maximum of three (3) returns.
2. The maps returned from CO back to RSSO for correction/adjustment shall only
be allowed a time period of five (5) working days for each return.
3. The CO shall immediately follow-up the submission of the returned maps if the
RSSO has not submitted within the allowed time period of five (5) working days.
As part of the standard evaluation procedures, the GIS-based maps submitted by the
PSO and RSSO will be graded/rated for its quality by the CO evaluators. Listed below are
the guidelines on how the submitted maps will be graded/rated:
1. The CO will only rate the PSO/RSSO after the maps had been submitted for a
maximum of three (3) returns for evaluation.
2. Quality of the submitted shapefiles will be based on the errors identified by CO

evaluators.

3. The rating on quality shall apply to all updated shapefiles submitted in the
PhilSys Cloud Server.
4. Percentage is based on the number of EAs with error and timeliness of submission.
Quality
Grade % of Errors
5 0% to 5% errors
3 6% to 10% errors
1 More than 10% errors
Timeliness
EA Delineation Block Mapping
Grade Early Bird Late Early Bird Late
5 Submitted to CO Submitted to Submitted to CO Submitted to CO
at least 10% of CO beyond end at least 10% of beyond end of
the total of operation the total operation 0%-
City/Municipality 0%-5% of the City/Municipality 10% of the total
per Region within total per Region within City/Municipality
1st and 2nd week City/Municipality 1st and 2nd week per Region
per Region (12 days of
operation)
4 Submitted to CO Submitted to
at least 10% of CO beyond end
the total of operation
City/Municipality 6%-10% of the - -
per Region within total
3rd and 4th week City/Municipality
per Region
3 Submitted to CO Submitted to Submitted to CO Submitted to CO
at least 10% of CO beyond end at least 10% of beyond end of
the total of operation the total operation 11%-
City/Municipality 11%-15% of the City/Municipality 20% of the total
per Region within total per Region within City/Municipality
5th and 6th week City/Municipality last weeks (after per Region
per Region 2nd week: last 8
days of the
operation)
2 Submitted to CO Submitted to
at least 10% of CO beyond end
the total of operation - -
City/Municipality 16%-20% of the
per Region within total

last week of City/Municipality

operation (after per Region
the 6th week)
1 Submitted less Submitted to Submitted less Submitted to CO
than 80% of the CO beyond end than 80% of the beyond end of
total of operation total operation 21%-
City/Municipality 21%-above of City/Municipality above of the total
per Region by the total per Region by end City/Municipality
end of operation City/Municipality of operation per Region
per Region

10.3 PROCEDURES IN REVIEWING THE GIS-BASED CENSUS MAPS TO BE DONE

BY THE MDR
I. EA Delineation for the Development of the EARF for 2022 CAF
A. Evaluation of the Enumeration Area Layer (ppmm_ea2022)
1. Prepare the accomplished EARF worksheet of the municipality to be

evaluated.
a. Browse to the 2022 List of EAs for Delineation Worksheet.xlsx and
open the file.
b. Copy the geographic codes of the 2022 List of EAs for Delineation
Worksheet.

c. Browse to :\PSA-GIS\Siquijor\CAF\2022 CAF\Temporary Files\Map

Updates Template folder and open the ppmm_EARF TEMPLATE
FOR MATCHING.xlsx.
d. Paste it in the EARF TEMPLATE FOR MATCHING sheet.

e. Save the worksheet as 6106_EARF FOR MATCHING.xlsx in :\PSA-

GIS\Siquijor\CAF\2022 CAF\Temporary Files folder.
2. Load the required layers in a blank project and generate the evaluation
result for the EA2022 layer
a. Open QGIS 3.4 application.
b. Click the New Project button.
c. Click Layer>Add Layer>Add Vector Layer.
d. Click the browse button to locate the folders of the shapefiles.

e. Browse to :\PSA-GIS\Siquijor\CAF\2022
CAF\Projects\Siquijor\Shapefiles folder.
NOTE:
For demonstration purposes, access the 6106_ea2022 shapefiles to be used in the

following steps from the Training Materials for the 2022 CAF Mapping and
Geotagging F2F3/Hands On Exercise/Shapefiles with Errors (for evaluation use
only)/ea with vertex error folder to show error output for
EA2022_VERTEX_ERRORS.
f. To select the files, press Ctrl and then click the following files:
i. 6106_bldg_point.shp
ii. 6106_bgy.shp
iii. 6106_ea2022.shp
g. Click Open.
h. In the Data Source Manager window, click Add.
i. Wait for the layers to be loaded in the map canvas before proceeding
to the next step.
j. Click Layer>Add Layer>Add spreadsheet layer.

k. Browse the 6106_EARF FOR MATCHING.xlsx in the :\PSA-

l. Check the Header at first line and End of file detection.
m. Click OK.

n. Check the (1) geometry; (2) gaps; (3) overlaps; (4) geocode
attributes; (5)duplicate geocode; (6) unmatched geoid with
barangay; and (7) unmatched geocode with the EARF worksheet of
the EA layer using the EA_layer_eval_v2 process model.
i. Open the File Explorer and browse the :\PSA-GIS\Map

Legends folder. Make sure that the File Explorer is not in full
screen mode.
ii. Select EA_layer_eval_v2.model3 and drag it on the map

canvas of the QGIS project.

o. In the EA2022 BOUNDARY EVALUATION window, set the

following parameters:
• EA2022 Layer: 6106_ea2022

• BGY LAYER: 6106_BGY

• BLDGPOINT LAYER: 6106_bldg_point

• EARF WORKSHEET: 6106_EARF FOR MATCHING
• Leave the other tabs with their default settings.
p. Click Run and wait for the process to finish.
q. Close the EA2022 BOUNDARY EVALUATION window after the

process is finished. The following output layers will be loaded in the
Layers panel: (no particular order)
• EA2022_VERTEX_ERRORS
• EA2022_GEOCODE NOT 13 DIGITS
• EA2022_GAPS
• EA2022_OVERLAPS
• EA2022_DUPLICATE GEOCODE
• EA2022_UNMATCHED GEOID WITH BGY
• EA2022_UNMATCHED GEOCODE WITH EARF
• EARF_UNMATCHED GEOCODE WITH EA2022
Error Output Description

Displays the exact location where the
invalid geometry is. It may be a
EA2022_VERTEX_ERRORS
duplicate vertex and/or intersecting line
segment.
Displays the EA/s with geocode not in
EA2022_GEOCODE NOT 13 DIGITS
13-digit length.

Displays the gaps within the EA2022

layer. The gaps considered for
modification are those that affect the
EA2022_GAPS
geotagged building structures. If the
gaps are not recognizable when viewed
in the map, no action needed.
Displays the overlapping portion/s of
the EA2022 boundary. If the overlaps
EA2022_OVERLAPS
are not recognizable when viewed in
the map, no action needed.
Displays the EA/s with duplicate
EA2022_DUPLICATE GEOCODE
geocode.
Displays the EA/s with unmatched
EA2022_UNMATCHED GEOID WITH geoid (ppmmbbb000000) with respect
BGY
to the barangay.
Displays the EA/s with unmatched
EA2022_UNMATCHED GEOCODE geocode (ppmmbbbeeeeee) with
WITH EARF
respect to the EARF worksheet.
Displays the unmatched geocode in the
EARF_UNMATCHED GEOCODE EARF worksheet with respect to the
WITH EA2022
geocode in the EA2022 layer.
3. To evaluate the errors caused by invalid geometries:
a. In the Layers panel, right-click EA2022_VERTEX_ERRORS and

select Open Attribute Table.
b. If there are no features in the attribute table, it means that there are
no error with the vertices of 6106_ea2022 layer. Write ‘1’
(acceptable) in the EA Delineation for the Development of the EARF
for 2022 CAF Evaluation form for QA 1.1.

c. If there is/are features in the attribute table, Write ‘2’ (needs

modification) in the EA Delineation for the Development of the EARF
d. Close the attribute table.
e. If there are invalid geometries, notify the PFP and MDP to make the
necessary modifications.
4. To evaluate the gaps in the EA boundary:
NOTE:
When there is/are invalid geometries, the output for gaps may not be processed. To
generate result for the EA2022_GAPS, fix the invalid geometry first and then, run the
EA evaluation modeler again.
For demonstration purposes, access the shapefiles to be used in the following steps
from the Training Materials for the 2022 CAF Mapping and Geotagging
F2F3/Hands On Exercise/Shapefiles with Errors (for evaluation use only)/ea
without vertex error folder to show error output for EA2022_GAPS.
a. In the Layers panel, right-click EA2022_GAPS and select Zoom to

layer.
b. Zoom in and/or out if necessary.
c. If there are no excess vertices inside the polygon, write ‘1’

d. If the suspected gap is minor and can be neglected, write ‘1’

for 2022 CAF Evaluation form for QA 1.1. These can be gaps caused
by unsnapped vertices and does not affect any geotagged building
points.
e. If upon zooming and the gap is pronounced and cannot be neglected

and if there are geotagged building points that happen to be within
the gap, write ‘2’ (needs modification) in the EA Delineation for the
Development of the EARF for 2022 CAF Evaluation form for QA 1.1.
f. If there are gaps, notify the PFP and MDP to make the necessary
modifications.
5. To evaluate the overlaps in the EA boundary:
a. In the Layers panel, right-click EA2022_OVERLAPS and select

Open Attribute Table.

no overlapping boundary in the 6106_ea2022 layer. Write ‘1’
c. If there is/are features in the attribute table, select each feature/row

and then, click the Zoom map to the selected rows button .
d. Check if the overlap is minor and can be neglected. These can be

overlaps caused by unsnapped vertices and does not affect any
geotagged building points. Write ‘1’ (acceptable) in the EA
Delineation for the Development of the EARF for 2022 CAF
Evaluation form for QA 1.1.
e. If upon zooming and the overlap is pronounced and cannot be

neglected and if there are geotagged building points that happen to
be within an overlapping EA boundary as stated in the REMARKS,

write ‘2’ (needs modification) in the EA Delineation for the

f. Close the attribute table.

g. If there are overlaps, notify the PFP and MDP to make the necessary
modifications.
6. To evaluate the uniqueness of the EA geocode:
a. In the Layers panel, right-click EA2022_DUPLICATE GEOCODE

and select Open Attribute Table.
no duplicate geocode in the 6106_ea2022 layer. Write ‘1’



e. If there is/are duplicate geocode, notify the PFP and MDP to make
the necessary modifications.
7. To evaluate the entries in the EA geocode:
a. In the Layers panel, right-click EA2022_GEOCODE NOT 13 DIGITS

b. If there are no features in the attribute table, it means that the

geocode of 6106_ea2022 are 13 digits in length. Write ‘1’


e. If there are errors in the geocode entries, notify the PFP and MDP to
make the necessary modifications.

8. To evaluate if there are unmatched geoID between the EA2022 and

barangay boundary layer:
a. In the Layers panel, right-click EA2022_UNMATCHED GEOID

WITH BGY and select Open Attribute Table.
b. If there are no features in the attribute table, it means that the geoID
(barangay geocode) in the 6106_ea2022 and the 6106_bgy are all
matched. Write ‘1’ (acceptable) in the EA Delineation for the
c. If there is/are features in the attribute table, there are unmatched

geoID. Write ‘2’ (needs modification) in the EA Delineation for the

e. If there are unmatched geoID, notify the PFP and MDP to make the
9. To evaluate if there are unmatched geocode between the EA2022 boundary

layer and EARF worksheet:
a. In the Layers panel, right-click EA2022_UNMATCHED GEOCODE
WITH EARF and select Open Attribute Table.


geocode in the 6106_ea2022 and the EARF worksheet are all
matched. Write ‘1’ (acceptable) in the EA Delineation for the

geocode. Write ‘2’ (needs modification) in the EA Delineation for the

e. If there are unmatched geocode, notify the PFP and MDP to make
10. To evaluate if there are unmatched geocode between the EARF worksheet
and EA2022 boundary layer:
a. In the Layers panel, right-click EARF_UNMATCHED GEOCODE
WITH EA2022 and select Open Attribute Table.

geocode in the EARF worksheet and 6106_ea2022 are all matched.
Write ‘1’ (acceptable) in the EA Delineation for the Development of
the EARF for 2022 CAF Evaluation form for QA 1.5.


geocode. Write ‘2’ (needs modification) in the EA Delineation for the

e. If there are duplicate block number, notify the PFP and MDP to make
11. Remove the error output layers in the Layers panel after evaluation.
B. Evaluation of the Geotagged Building Structures (ppmm_bldg_point)
After the evaluation of the EA2022 boundary layer, evaluate the

geotagged building structures layer.
1. Make sure that the 6106_bldg_point and 6106_ea2022 layers are loaded
in the Layers panel.
2. Check if there are existing (1) new and destroyed geotagged buildings that
are verified false and true, respectively; and (2) geotagged buildings

outside/not within the boundary using the

EA_Delineation_BldgPoint_layer_eval_v1 process model.
a. Open the File Explorer and browse the :\PSA-GIS\Map Legends

folder. Make sure that the File Explorer is not in full screen mode.
b. Select EA_Delineation_BldgPoint_layer_eval_v1.model3 and

drag it on the map canvas of the QGIS project.
c. In the GEOTAGGED BUILDING POINTS EVALUATION window,

set the following parameters:
• BLDGPOINT LAYER: 6106_bldg_point

• EA2022 Layer: 6106_ea2022
d. Click Run and wait for the process to finish.
e. Close the GEOTAGGED BUILDING POINTS EVALUATION

window after the process is finished. The following output layers will
be loaded in the Layers panel: (no particular order)
• BLDGPOINT_UPDATE NOT DELETED

• BLDGPOINT_OUTSIDE BOUNDARY


Displays the verified false – new
buildings and/or verified true -
BLDGPOINT_UPDATE NOT destroyed/demolished buildings during

DELETED the 2020 CPH enumeration. These
points should have been deleted before
the EA delineation.
Displays the geotagged building points
BLDGPOINT_OUTSIDE BOUNDARY
outside/not within the boundary.
3. To check if the geotagged building structure points have undergone pre-

processing:
a. In the Layers panel, right-click BLDGPOINT_UPDATE NOT

DELETED and select Open Attribute Table.
b. If there are no features in the attribute table, write ‘1’ (acceptable) in
the EA Delineation for the Development of the EARF for 2022 CAF
c. If there are features, write ‘2’ (needs modification) in the EA
Evaluation form for QA 2.1 and then, notify the PFP and MDP to
a. Close the Attribute Table.
4. To check if there are geotagged building structure points outside the

EA2022 boundary:
a. In the Layers panel, right-click BLDGPOINT_OUTSIDE

BOUNDARY and select Open Attribute Table.

b. If there are no features in the attribute table, write ‘1’ (acceptable) in

the EA Delineation for the Development of the EARF for 2022 CAF
c. If there are features, write ‘2’ (needs modification) in the EA
Evaluation form for QA 2.2 and then, notify the PFP and MDP to
d. Close the Attribute Table.
5. Close the QGIS application after evaluation.

II. Block Mapping for 2022 CAF - Evaluation of the Block Boundary
(pppmm_block)
1. Load the required layers in a blank project and generate the evaluation
result for the BLOCK layer
a. Open QGIS 3.4 application.

b. Click the New Project button.
c. Add the GIS-based census maps in the project

d. Click Layer>Add Layer>Add Vector Layer.
e. Click the browse button to locate the folders of the shapefiles.
f. Browse to :\PSA-GIS\Siquijor\CAF\2022
CAF\Projects\Siquijor\Final Layer - 03-14-2022 folder.
NOTE:
For demonstration purposes, access the 06106_layers.gpkg > 06106_block layer to

be used in the following steps from the Training Materials for the 2022 CAF Mapping
and Geotagging F2F3/Hands On Exercise/Shapefiles with Errors (for evaluation
use only)/block with errors folder.

g. Select 06106_layers.gpkg.
h. In the Data Source Manager window, click Add.
i. In the Select Vector Layers to Add dialog box, Ctrl + select the
following layers:
i. 06106_bldg_point
ii. 06106_block
j. Uncheck Add layers to a group.
k. Click OK.
l. Wait for the layers to be loaded in the map canvas before proceeding
to the next step.
2. Check the (1) geometry; (2) gaps; (3) overlaps; (4) geocode attributes; (5)
completeness of “blocked” geotagged building points; and (6) duplicate
block number/s of the block layer using the Block_layer_eval_v1 process
model.
a. Open the File Explorer and browse the :\PSA-GIS\Map Legends

b. Select Block_layer_eval_v1.model3 and drag it on the map canvas

of the QGIS project.
c. In the BLOCK LAYER EVALUATION window, set the following

parameters:

• BLDG POINT LAYER: 06106_layer 06106_bldg_point

• BLOCK LAYER: 06106_layer 06106_block
• BLOCK LAYER TABLE (select “geocode” AND
“BLOCKNUM”): select “geocode” and “BLOCKNUM”
fields
d. Click Run and wait for the process to finish.

e. Close the Block Boundary Evaluation window after the process is

finished. The following output layers will be loaded in the Layers
panel: (no particular order)
• BLOCK_VERTEX_ERRORS
• BLOCK_GAPS
• BLOCK_OVERLAPS
• BLOCK_DUPLICATE BLOCKNUM
• BLOCK_GEOCODE NOT 14 DIGITS / BLOCKNUM NOT 2
DIGITS
• BLDGPOINT NOT INSIDE A BLOCK

Displays the exact location where the
invalid geometry is. It may be a
BLOCK_VERTEX_ERRORS
duplicate vertex and/or intersecting line
segment.
Displays the block/s with geocode and
BLOCK_GEOCODE NOT 14 DIGITS / block number not in 14- and 2-digit
BLOCKNUM NOT 2 DIGITS
length, respectively.
Displays the gaps within the block
layer. The gaps considered for
modification are those that affect the
BLOCK_GAPS
geotagged building structures. If the
gaps are not recognizable when viewed
in the map, no action needed.
Displays the overlapping portion/s of
BLOCK_OVERLAPS
the block boundary. The overlaps

considered for modification are those

that affect the geotagged building
structures. If the overlaps are not
recognizable when viewed in the map,
no action needed.
Displays the blocks with duplicate block
BLOCK_DUPLICATE BLOCKNUM
number with respect to the EA.
Displays the geotagged building
BLDGPOINT NOT INSIDE A BLOCK structure/s that are not inside/within the
block boundary.
3. To evaluate the errors caused by invalid geometries:
a. In the Layers panel, right-click BLOCK_VERTEX_ERROR and

select Open Attribute Table.
no error with the vertices of 06106_block layer. Write ‘1’ (acceptable)
in the Block Mapping for 2022 CAF Evaluation form for QA 1.1.

modification) in the Block Mapping for 2022 CAF Evaluation form for
QA 1.1.
e. If there are invalid geometries, notify the PFP and MDP to make the

4. To evaluate the gaps in the block boundary:
NOTE:
When there is/are invalid geometries, the output for gaps may not be
processed. To generate result for the BLOCK_GAPS, fix the invalid geometry first
and then, run the block evaluation modeler again.
a. In the Layers panel, right-click BLOCK_GAPS and select Zoom to

layer.
b. Zoom in and/or out if necessary.
c. If there are no excess vertices inside the polygon, write ‘1’
(acceptable) in the Block Mapping for 2022 CAF Evaluation form for
QA 1.1.
d. If there are excess vertices inside the polygon, it indicates the
presence of gaps. Gaps are caused by not using the snapping tool
during digitization. Write ‘2’ (needs modification) in the Block
Mapping for 2022 CAF Evaluation form for QA 1.1.
e. If there are gaps, notify the PFP and MDP to make the necessary
modifications.
5. To evaluate the overlaps in the block boundary:
a. In the Layers panel, right-click BLOCK_OVERLAPS and select

Open Attribute Table.
no overlapping boundary in the 06106_block layer. Write ‘1’
QA 1.1.


QA 1.1.
Each feature represents an overlap between block

boundaries. Also, refer to the remarks if there are geotagged building
points that happen to be within an overlapping block boundary.
e. If there are overlaps, notify the PFP and MDP to make the necessary
modifications.
6. To evaluate the uniqueness of the block number:

a. In the Layers panel, right-click BLOCK_DUPLICATE BLOCKNUM
no duplicate block number in the 06106_block layer. Write ‘1’
QA 1.2.


QA 1.2.

e. If there is/are duplicate block numbers, notify the PFP and MDP to
7. To evaluate the entries of the geocode and block number:

a. In the Layers panel, right- BLOCK_GEOCODE NOT 14 DIGITS /
BLOCKNUM NOT 2 DIGITS and select Open Attribute Table.

geocode and block number are in 14 digits and 2 digits in length,
respectively. Write ‘1’ (acceptable) in the Block Mapping for 2022
CAF Evaluation form for QA 1.2.

QA 1.2.

e. If there are duplicate block number, notify the PFP and MDP to make
8. To evaluate if there are geotagged building points that are not blocked (not
enclosed/within a block boundary):
a. In the Layers panel, right-click BLDGPOINT NOT INSIDE A BLOCK

b. If there are no features in the attribute table, it means that all the
geotagged building points are enclosed by a block boundary. Write
‘1’ (acceptable) in the Block Mapping for 2022 CAF Evaluation form
for QA 1.3.

QA 1.3.

e. If there are geotagged building points not within a block boundary,
notify the PFP and MDP to make the necessary modifications.
IMPORTANT NOTICE
All city/municipality GIS-based census maps submitted in the PSO should be
evaluated and thoroughly modified, if needed, before submission to the RSSO.

10.4 MODIFICATION OF THE SUBMITTED CENSUS MAPS TO BE DONE BY THE

MDP
NOTE:
The procedures for the modification/correction of the INVALID GEOMETRY, GAPS,
OVERLAPS, GEOCODE ERRORS of the ppmm_ea2022 layer is also applicable for
the pppmm_block layer.
A. To remove the vertex error, apply the following procedures:
1. Open the QGIS 3.4 application.
2. Load the required layers in a blank project
a. Click Layer>Add Layer>Add Vector Layer.

b. Click the browse button to locate the folders of the shapefiles.
c. Browse to :\PSA-GIS\Siquijor\CAF\2022
NOTE:

only)/ea with vertex error folder to show error output for
EA2022_VERTEX_ERRORS.
d. To select the files, press Ctrl and then click the following files:
ii. 6106_bgy.shp
e. Click Open.
f. In the Data Source Manager window, click Add.

g. Wait for the layers to be loaded in the map canvas before proceeding to the
next step.
h. Click Layer>Add Layer>Add spreadsheet layer.
i. Browse the 6106_EARF FOR MATCHING.xlsx in the :\PSA-
j. Check the Header at first line and End of file detection.
k. Click OK.
3. Open the File Explorer window and browse to :\PSA-GIS\Map Legends
4. Select EA_layer_eval_v2.model3 and drag it on the map canvas of the QGIS

window.
5. In the EA2022 BOUNDARY EVALUATION window, set the following

parameters:
▪ EA2022 LAYER: 6106_ea2022
▪ BGY LAYER: 6106_bgy
▪ BLDG POINT LAYER: 6106_bldg_point
▪ EARF WORKSHEET: 6106_EARF FOR MATCHING
▪ Only the EA2022_VERTEX_ERRORS should be with a check in the
outputs
6. Click Run and wait for the process to finish.
7. Close the EA2022 BOUNDARY EVALUATION window after the process is

finished. The EA2022_VERTEX_ERRORS layer will be loaded in the Layers
panel.
8. In the Layers panel, select EA2022_VERTEX_ERRORS and open the

attribute table.

If there is an error, then it is expected that there will be a feature in the attribute
table. The feature points out the exact location of the error.
9. In the attribute table of the EA2022_VERTEX_ERRORS, select a feature and

then, click the Zoom map to the selected rows button .
10. Uncheck the EA2022_VERTEX_ERRORS and zoom in, if necessary, to locate

the error.
11. In the Layers panel, select the 6106_ea2022 layer.
12. Click the Toggle editing button if necessary and then, the Vertex tool
button .
13. In the map canvas, right-click the vertex where the error is located.
The Vertex Editor displays all the vertex in the shapefile layer.

14. Click and drag-select the vertex causing the error. It will select all the error
vertices.
15. Press the Delete button on the keyboard to delete the selected vertices (blue
point in the map and the highlighted features in the Vertex Editor).
The ppmm_bgy layer can also be use as guide to know where the vertices
should be snapped.

NOTE:
The vertex error (invalid geometry) may be an intersecting segment of a polygon,

duplicate vertex, etc. Apply the necessary steps to fix the error. Add and/or delete
vertices if necessary. Enable snapping if necessary.
Other examples:
16. Apply the same procedure if there are other features in the attribute table of the
EA2022_VERTEX_ERRORS layer until all are deleted.
17. Remove the EA2022_VERTEX_ERRORS layer in the Layers panel.
18. Save the edits made in the 6106_ea2022 layer.

B. To snap the boundaries, apply the following:
1. Open the QGIS 3.4 application if necessary.

NOTE:

only)/ea without vertex error folder to show error output for EA2022_GAPS.
ii. 6106_bgy.shp
iv. 6106_river.shp
v. 6106_road.shp
e. Click Open.
g. Wait for the layers to be loaded in the map canvas before proceeding
to the next step.
k. Click OK.

NOTE:
The ppmm_bldg_point is loaded as an input for the modeler and guide when snapping the
boundaries to make sure that no geotagged building will be affected in the process of
modification.

folder. Make sure that the File Explorer window is not in full screen mode.

window.
5. In the EA2022 BOUNDARY EVALUATION window, set the following

parameters:
▪ EA2022 LAYER: 6106_ea2022
▪ Only the EA2022_GAPS and EA2022_OVERLAPS should be with

a check in the outputs

finished. The following output layers will be loaded in the Layers panel:
▪ EA2022_GAPS
▪ EA2022_OVERLAPS
8. In the Layers panel, uncheck the EA2022_GAPS layer.
9. Enable Snapping
a. If the Snapping Toolbar is not present, right-click on the empty spaces

in the toolbars section and then, check the Snapping Toolbar.

b. Click the Enable Snapping button .
c. On the All Layers button drop down list, select Open Snapping
Options.
d. On the Project Snapping Settings dialog box, select All

Layers>Advanced Configuration.
e. Set the following parameters:
▪ Layer: check the 6106_ea2022, 6106_bgy, 6106_river, and

6106_road
▪ Type: vertex
▪ Tolerance: 0.00001
▪ Units: meters
▪ Topological Editing: click to enable

10. In the Layers panel, select the 6106_ea2022 layer.
11. Click the Toggle editing button and then, the Vertex Tool button .
12. Snapping the overlapping boundaries of the 6106_ea2022 layer
a. Open the attribute table of EA2022_OVERLAPS.
b. Select an overlap feature, then, click Zoom map to the selected rows
button . The selected feature will be zoomed in your map view.
NOTE:
If the gap/overlap is minor and negligible (caused by unsnapped vertices) and there are
no geotagged building points affected, no action needed.
c. Uncheck the EA2022_OVERLAPS layer in the Layers panel.
d. Snap the EA boundary where the overlap is located.
NOTE:
Use the barangay boundary and geotagged buildings as guide in correcting the
overlapping boundaries.

If necessary, add a vertex or delete excess vertices.
e. Repeat the steps until all the overlaps are closed.
f. Save the edits made in the 6106_ea2022 layer.
g. Remove the EA2022_OVERLAPS in the Layers panel.
13. Snapping the gaps between the boundaries of the 6106_ea2022 layer
a. Unhide EA2022_GAPS layer.
b. Locate excess vertices in the EA2022_GAPS layer that lies along the
6106_ea2022 boundary.
NOTE:
If the gap/overlap is minor and negligible (caused by unsnapped vertices) and there
are no geotagged building points affected, no action needed.
c. In the Layers panel, uncheck the EA2022_GAPS.
d. Click the vertex of the 6106_ea2022 where the excess vertex is located
and snap to appropriate vertex to close the gap.

NOTE:
Use the geotagged buildings as guide in correcting the overlapping boundaries.
e. Repeat the steps until all the gaps are closed.
f. Save the edits made in the 6106_ea2022 layer.
g. Remove the EA2022_GAPS in the Layers panel.
C. To correct the geocode, apply the following procedures:


NOTE:

only)/ea without vertex error folder.
ii. 6106_bgy.shp
e. Click Open.
g. Wait for the layers to be loaded in the map canvas before proceeding to
the next step.


k. Click OK.


window.
5. In the EA Boundary Evaluation window, set the following parameters:
▪ EA2022 LAYER: 6106_ea2022

▪ Only the EA2022_GEOCODE NOT IN 13 DIGITS and/or
EA2022_DUPLICATE GEOCODE should be with a check in the
outputs

finished. The EA2022_GEOCODE NOT IN 13 DIGITS AND/OR
EA2022_DUPLICATE GEOCODE layer will be loaded in the Layers panel.
8. To correct the geocode that is not 13 digits in length:
a. Open the attribute table of EA2022_GEOCODE NOT IN 13 DIGITS.

b. Right-click the cell of the geocode and select “Copy cell content”.
c. In the Layers panel, select the 6106_ea2022 layer and open the attribute
table.
d. Enable editing if necessary.
e. Click the Select/filter features using form button .
f. In the “geocode” tab, right-click and select Paste.
g. At the lower right corner of the attribute table, click the Filter features button
h. Click the Switch to table view button located just below the Filter
features button.
i. Check the geocode for the error and inform the PFP regarding the
issues/concern.
j. Once approved or verified by the PFP, supply/delete the necessary values

to correct the geocode.
k. Save the edits made in the 6106_ea2022 layer.
9. To correct the geocode with duplicates:
a. Open the attribute table of EA2022_DUPLICATE GEOCODE.
b. Right-click the cell of the geocode and select “Copy cell content”.
c. In the Layers panel, select the 6106_ea2022 layer and open the attribute
table.
d. Enable editing if necessary.

e. Click the Select/filter features using form button .
f. In the “geocode” tab, right-click and select Paste.
g. At the lower right corner of the attribute table, click the Filter features button
h. Click the Switch to table view button located just below the Filter
features button.
i. Select a feature and click the Zoom map to the selected rows button
to locate the EA in the map.
j. If an error occurs as shown below, inform the PFP. Delete the selected
feature in the attribute table of the 6106_ea2022.
This type of error means that the feature in the attribute table is not present
in the map. (Data with no representation in the map.)
k. If a feature is zoomed on the map canvas but have separate polygon

features, inform the PFP to verify the corresponding geocode and polygon.
Do not delete any of the duplicate map features without informing the PFP.
l. Once approved or verified by the PFP, supply/delete the necessary values

to correct the geocode.
m. Save the edits made in the 6106_ea2022 layer.
D. To correct the geocode of the EA with respect to the (1) barangay boundary; and
(2) EARF; and (3) vice versa, apply the following procedures:


NOTE:

only)/ea without vertex error folder.
ii. 6106_bgy.shp
e. Click Open.
g. Wait for the layers to be loaded in the map canvas before proceeding to
the next step.
k. Click OK.


window.
5. In the EA Boundary Evaluation window, set the following parameters:
▪ EA2022 LAYER: 6106_ea2022


▪ Only the EA2022_UNMATCHED GEOID WITH BGY and/or
EA2022_UNMATCHED GEOCODE WITH EARF and/or
EARF_UNMATCHED GEOCODE WITH EA2022 should be with a
check in the outputs

finished. The EA2022_UNMATCHED GEOID WITH BGY layer will be loaded
8. Open the attribute table of EA2022_UNMATCHED GEOID WITH BGY.
9. Right-click the cell of the geocode and select “Copy cell content”.
10. In the Layers panel, select the 6106_ea2022 layer and open the attribute
table.
11. Enable editing if necessary.
12. Click the Select/filter features using form button .
13. In the “geocode” tab, right-click and select Paste.
14. At the lower right corner of the attribute table, click the Filter features button
15. Click the Switch to table view button located just below the Filter features
button.
16. Select a feature and click the Zoom map to the selected rows button to
locate the EA in the map.

17. Check the geocode of the barangay the EA in question belongs to.
a. Click the Identify features button.
b. In the Layers panel, select 6106_bgy.
c. In the map canvas, click the barangay where the EA is located.
d. In the Attribute Form, check the geocode of the barangay.
e. Compare the geocode of the EA (up to the 7th digit of the EA geocode –
ppmmbbb) and inform the PFP in which geocode is the correct one.
i. It can be that the geocode of the EA is correct and the geocode

of the barangay is wrong.
ii. It can also be that the geocode of the EA is wrong and the
barangay geocode is the correct.
18. Once approved or verified by the PFP, apply necessary steps to correct the
geocode.
19. Apply the necessary steps to correct the unmatched geocode between the
EARF and 6106_ea2022 and vice versa.
20. Save the edits made in the 6106_ea2022 layer.
E. To correct the geotagged building structures with existing verified false – new
buildings and verified true – destroyed/demolished buildings:
Refer to CHAPTER 8: GIS-Based EA Delineation Procedures page 212, D.

F. To transfer the geotagged building structures outside the barangay/EA

boundaries:
1. Make sure that geotagged building structures, barangay, and satellite image
layers of the city/municipality subject for modification as well as its adjacent
city/municipality are loaded in the QGIS map canvas.
2. Locate and zoom to the geotagged building structure points located outside the
barangay boundary.
3. Check in the satellite image if the corresponding building structures of the

building points outside the boundary are also geotagged or already existing in
the adjacent city/municipality.

4. Inform the PFP regarding the identified geotagged building structures. The PFP
will decide the appropriate action to be taken before making the modifications.
The geotagged building structures outside the barangay boundary will not be
renumbered properly and will automatically not show in the printed maps.
a. If geotagged building structure points are already existing in the adjacent

city/municipality and decided to be deleted:
i. In the Layers panel, select 6106_bldg_point and then, click the
Toggle editing button .
ii. Select the geotagged building structure points outside boundary.
a) To select the geotagged point features, click the Select
Feature(s) or Select Features by Polygon (depending on
which method the MDP is comfortable on using).
b) Click the geotagged features outside the boundary.

In the example, the adjacent municipality is Larena (6102).
iii. Click the Delete Selected button or the Delete button in the
keyboard.
iv. Click the Toggle editing button > Save.
b. If geotagged building structure points are not existing in the adjacent

city/municipality and decided to be transferred:
i. Load the ppmm_bldg_point of the adjacent city/municipality.

In the example, the adjacent municipality is San Juan (6105).
ii. In the Layers panel, select 6106_bldg_point and then, click the
Toggle editing button .
iii. Select the geotagged building structure points outside boundary.
iv. Cut the selected geotagged building structure points by clicking

the Cut Features button in the Digitizing toolbar or Ctrl + X
in the keyboard.

v. In the Layers panel, select the 6105_bldg_point layer of the

adjacent municipality where the selected geotagged building
structure points will be transferred.
vi. Click the Toggle editing button .
vii. Paste the selected geotagged building structure points by clicking
the Paste Features button in the Digitizing toolbar or Ctrl +

V in the keyboard.
A pop-up message will appear once the features are pasted

in the adjacent municipality.
viii. Click the Toggle editing button > Save.

ix. In the Layers panel, select 6106_bldg_point and then, click the
Toggle editing button > Save.

G. To correct the duplicate BLOCKNUM of the pppmm_block layer, apply the

following procedures:
2. Load the required layers in a blank project and generate the evaluation result
for the BLOCK layer
a. Add the GIS-based census maps in the project.
b. Click Layer>Add Layer>Add Vector Layer.
c. Click the browse button to locate the folders of the shapefiles.
d. Browse to :\PSA-GIS\Siquijor\CAF\2022 CAF\Projects\Siquijor\Final

Layer - 03-14-2022 folder.
NOTE:

e. Select 06106_layers.gpkg.
g. In the Select Vector Layers to Add dialog box, Ctrl + select the following
layers:
i. 06106_bldg_point
ii. 06106_block

h. Uncheck Add layers to a group.

i. Click OK.
j. Wait for the layers to be loaded in the map canvas before proceeding to
the next step.
3. Run the 06106_block layer to the Auto_Block_Attribute_Modifier modeler
to correct the duplicate block number/s.
Refer to the instructions in CHAPTER 9: BLOCK MAPPING pages 348 (#18)

to 351 (#21).
H. To correct the geotagged building structures not inside/within the pppmm_block

layer, apply the following procedures:
2. Load the required layers in a blank project and generate the evaluation result
for the BLOCK layer
a. Add the GIS-based census maps in the project.
b. Click Layer>Add Layer>Add Vector Layer.
c. Click the browse button to locate the folders of the shapefiles.
d. Browse to :\PSA-GIS\Siquijor\CAF\2022 CAF\Projects\Siquijor\Final

Layer - 03-14-2022 folder.

NOTE:

e. Select 06106_layers.gpkg.
g. In the Select Vector Layers to Add dialog box, Ctrl + select the following
layers:
i. 06106_bldg_point
ii. 06106_block
h. Uncheck Add layers to a group.

i. Click OK.
j. Wait for the layers to be loaded in the map canvas before proceeding to
the next step.
3. Open the File Explorer and browse the :\PSA-GIS\Map Legends folder. Make
sure that the File Explorer is not in full screen mode.
4. Select Block_layer_eval_v1.model3 and drag it on the map canvas of the

QGIS project.
5. In the BLOCK LAYER EVALUATION window, set the following parameters:
• BLDG POINT LAYER: 06106_layers 06106_bldg_point

• BLOCK LAYER: 06106_layers 06106_block

• BLOCK LAYER TABLE (select “geocode” and “BLOCKNUM”): select
“geocode” and “BLOCKNUM” fields
• Only the BLDGPOINT NOT INSIDE A BLOCK should be with a check in
the output.
7. Close the Block Boundary Evaluation window after the process is finished.
8. In the Layers panel, open the attribute table of BLDGPOINT NOT INSIDE A
BLOCK.
9. Select all the features in the attribute table and then, click the Zoom map to
the selected rows button to locate the geotagged building structures in the
map.
10. Apply the QML of the layers to better visualize the block and to make sure that
the BSN of the geotagged building structures are readable.

11. Adjust the block or create a new block polygon.
12. After creating or adjusting the block boundary, repeat instruction #3 to #8 to

make sure that all the geotagged building structures are within a block.
13. If there are no features in the attribute table, it means that all the geotagged
building points are enclosed by a block boundary.
14. Run the 06106_layers 06106_block layer to the

Auto_Block_Attribute_Modifier modeler to reflect the changes in the attribute
table such as the BLOCKNUM.
Refer to the instructions in CHAPTER 9: BLOCK 348 (#18) to 351 (#21).

10.5 Determination of City / Municipality Boundary Gaps and Overlaps
Overview of Process
MDR
A. Merging of all EA2022 and BLDG_POINT layers (output: temporary / scratch

layer)
B. Generation of City / Municipal layer from merged layer EA2022 with the
municipal boundary gaps and overlaps with the affected building points using
Modeler3 automated process.
Output: (temporary / scratch layer)
• bldgpoints affected by gaps
• bldgpoints affected by overlaps
• mun_gaps
• mun_overlaps
• mun_count
Note: The layers which will be generated by the Modeler in process B will be
used only as indicator or locator and not to be edited.
MDP
C. Loading and Display settings of the MODEL3 generated layers

D. Loading all the necessary layers for modification and satellite image (gpkg) as
base map.
E. Modification / snapping of the Municipal common boundaries of the original
overlapping EA2022 layers to be done by the Map Data Processor (MDP)

Operational Procedure
A. Merging of All ea2022 Layers and bldg_point Layers

output: temporary / scratch layer
1. Open the QGIS 3.4.7
2. In the Menu toolbar, click Layer > Add Layer > Add Vector Layer.
3. Browse to :\PSA-GIS\…\Shapefiles folder, load all the ppmm_ea2022.shp

only.
4. Merge all the ppmm_ea2022 layers to make it one (1) EA layer for the entire
province:
a. In the Menu toolbar, click Vector > Data Management Tools > Merge
Vector Layers.
b. Click the Input layers > Select All > OK.
c. Click Run.
d. Close the Merge Vector Layers window.


5. Rename the temporary layer. On the Layers panel, right-click Merged layer
then Rename Layer as pp00_ea2022 (2100_ea2022 for this demonstration).
OPTIONAL:
To save a copy of the temporary layer:
a. Right-click the 2100_ea2022 layer, select Export > Save Features As.
b. In the Save Vector Layer as pop-up window, set as follows:
i. Format: ESRI Shapefile
ii. File name: browse to :\PSA-GIS\…\Shapefiles then rename as
2100_ea2022
iii. Tick Add saved file to map .
c. Click OK.
d. Remove layer the temporary layer .
6. Remove all the ppmm_ea2022 layers except the merged layer pp00_ ea2022.
a. Select 2101_ea2022 up to 2123_ea2022 (except 2100_ea2022) in the
Layers panel.

b. Right-click then select Remove Layer > OK.

7. In the Menu toolbar, click Layer > Add Layer > Add Vector Layer.
8. Browse to :\PSA-GIS\…\Shapefiles folder, load all the
ppmm_bldg_point.shp only.
9. Merge all the ppmm_bldg_point layers to make it one (1) bldg._point layer for
the entire province:
a. In the Menu toolbar, click Vector > Data Management Tools > Merge
Vector Layers.
b. Click the Input layers > Select All.

c. In the Multiple Selection, scroll down to the bottom and uncheck

pp00_ea2022 (2100_ea2022).
d. Click OK.
e. Click Run.
f. Close the Merge Vector Layers window.
10. Rename the temporary layer. On the Layers panel, right-click Merged layer
then Rename Layer as pp00_bldg_point (2100_bldg_point for this
demonstration).
OPTIONAL:
To save a copy of the temporary layer:
a. Right-click the 2100_bldg_point layer, select Export > Save Features As.
b. In the Save Vector Layer as pop-up window, set as follows:
i. Format: ESRI Shapefile
ii. File name: browse to :\PSA-GIS\…\Shapefiles then rename as
2100_bldg_point
iii. Tick Add saved file to map .
c. Click OK.
d. Remove layer the temporary layer .
11. Remove all the ppmm_bldg_point layers except the merged layer pp00_
ea2022.

a. Select 2101_bldg_point up to 2123_bldg_point (except 2100_bldg_point)

b. Right-click then select Remove Layer > OK.
B. Generation of City/Municipal layer from merged EA2022 layer with the

municipal boundary gaps and overlaps with the affected building points
using Modeler3 automated process.
1. In the Layers panel space, right-click > Add Group.
2. Select the group1.

3. Browse to :\PSA-GIS\…\Map Legends folder, drag and drop the

ea2mun+gaps_&_overlaps.model3 into the project.
4. In the Ea2mun window, set the parameters as follows:
5. Click Run.
6. Close the Ea2mun window.
7. Uncheck the tick box beside ppmm_bldg_point (2100_bldg_point) and
ppmm_ea2022 (2100_ea2022) layers to hide.
8. Re-arrange the output layers accordingly:
9. Select (press CTRL key to multiple select) the output layers.

10. Right-click and select Show Feature Count.
11. Check the feature count:

• bldgpoints affected by overlaps – subject for modification if count is not
zero [0].
• bldgpoints affected by gaps – subject for modification if count is not zero
[0].
• mun_overlaps – subject for modification if count is not zero [0].
• mun_gaps – default feature count is [1], subject to scrutiny of the MDR .
• mun_count – City / municipality total count for MDR’s reference.
12. Export the temporary layers subject for modification:
a. Right-click the temporary layer subject for modification, select Export >
Save Features As.
b. In the Save Vector Layer as pop-up window, set Format as ESRI
Shapefile.
c. In the File name, browse to destination folder path and set name same as
its temporary layer name.
d. Click OK.
13. The MDR must delegate the error output of this process to the MDP for
modification.

C. Loading and Display settings of the MODEL3 generated layers (to be done by
the MDPs)
1. Open the QGIS 3.4.
2. Load the following layers delegated by the MDR (Model3 output layers):
• mun_overlaps
• mun_gaps
• ppmm_mun (MDPs’ reference in identifying the city or municipality)
3. Arrange the layers as illustrated:
4. In the Map Navigation Toolbar, click the Zoom Full icon.
5. Display the labels of mun_count layer:

a. Right-click the mun_count layer then select Properties.

b. In the Labels tab, click the dropdown list and select Single labels.
c. Set Label with to geo_mun.
d. Set Placement to Free (slow).
e. Click OK.
Map Canvas: mun_count layer with labels

6. Zoom-in manually the buildings affected by the gaps and overlaps:

a. In the Map Navigation Toolbar, click the Zoom In icon.
b. To zoom in, click and drag the area around the target object enclosing it
in a box.
c. To show the common boundary and labels of the two (2) municipalities
involved in the overlap: uncheck the mun_gaps layer to hide.

7. In the Layers panel, right-click on any space and select Add Group. Name the
Group as Locator.
8. Select all layers, drag and drop inside the “Locator” Group…
9. Add another group and name as Original layers.
10. Select the Original layers group…

D. Load all the necessary (original) layers for modification.

1. Browse to :\PSA-GIS\…\Shapefiles folder:
a. Select the Original layers group .
b. In the Menu toolbar, select Layer > Add Layer > Add Vector Layer, load
the two (2) original ppmm_ea2022 overlapping layers (2102_ea2022 and
2108_ea2022).
c. Load their respective bgy, bldg point, road and river shapefiles in the
project under Original layers.
d. Add the satellite images geopackage (ppmm_img.gpkg) as the
bottommost layer in the Layers Panel for MDP’s reference during the
modification.
e. Uncheck all layers under the Locator group to hide.
f. Arrange the layers. (See illustration)

E. Modification / snapping of the Municipal common boundaries of the original

overlapping EA2022 layers to be done by the Map Data Processor (MDP)
1. Application of the PSA-GIS preset layer display properties (QMLs) is NOT

recommended during the modification. Instead, use the suggested simple
display properties settings as listed below:
• ppmm_bldg_point – Color / Size: default
• ppmm_road – Color: orange; Stroke width: 1.26
• ppmm_river – Color: cyan / light blue; Stroke width: 1.26
• ppmm_bgy – Fill color: transparent; Stroke Color: green, Stroke width:
default
• ppmm_ea2022 – Fill Color: transparent; Stroke Color: red, Stroke width:
default
2. Activate/enable snapping:
a. Click Project > Snapping Options.
b. Click the Enable Snapping icon .

c. Set as follows:
3. Verify first the EA location of the overlapping building points.

In this case scenario, the overlapping building points belongs to ppmm = 2102.
Therefore, 2102_ea2022 will not be the subject for modification.
Layers subject for modification:

• 2108_ea2022 boundary – to be snapped to 2102_ea2022

• 2108_road – to be snapped / aligned to 2102_road
• 2102_road – to be snapped / aligned to 2108_ea2022 and 2108_road
4. Adjust the Satellite Imagery transparency to 50-70%.
5. To start the modification, select 2108_ea2022 layer, click Toggle Editing ,
followed by the Vertex Tool .

6. Align the vertices of 2108_ea2022 with the vertices of 2102_ea2022 to fix the
overlap.
See modification result:

7. Click the Toggle Editing then Save.
8. For road layers, click Toggle Editing then Vertex Tool .

a. 2108_road
b. 2102_road
Start editing / snapping the roads as illustrated…

9. When done, select 2108_road click Toggle Editing then Save. Likewise,
select 2102_road click Toggle Editing then Save.
10. Repeat Step 9 to Step 10 to river layers (2102_river, 2108_river) with similar
scenario.
11. Roads / Rivers must be snapped if in case they lie along the boundaries.
12. Modify and update the 2102_bgy and 2108_bgy layers.
a. Edit 2102_bgy boundary according to the shape of the 2102_ea2022
boundary (if there were any changes made in 2102_ea2022).
b. Edit 2108_bgy boundary according to the shape of the 2108_ea2022
boundary (if there were any changes made in 2108_ea2022).

NOTE:
Negligible gaps and overlaps – viewed as fine LINE even to the maximum or
nearest zoom-in level. See illustration:
In full extent or zoomed-out When zoomed-in to the

maximum level
10.6 Determination of Provincial Boundary Gaps and Overlaps Affecting Building

Points
Overview of Process
A. Storing of all shapefiles in one folder.

B. Merging of all EA2022 and BLDG_POINT layers (output: temporary / scratch
layer) into one Provincial EA layer.
C. Generation of Provincial gaps and overlaps and affected building points layers
from merged original layers EA2022 using the Modeler3 automated process.
Output: (temporary / scratch layer)
• prov_gaps
• prov_overlaps
• prov_count
Note: The layers which generated by the Modeler in process C will be used only
as indicator or locator and are not subject for modification.
D. Layer arrangement (order) and Display settings of the MODEL3 generated
layers.
E. Identification of the specific EAs where the gaps and overlaps are located

IMPORTANT
• This procedure is mainly for the determination of the Gaps and Overlaps along the
Provincial boundary line.
• Ignore the gaps if located inside the mid-area / section of a province or far from the
Provincial boundary line.
• The Rsso MDR must be aware of the complete count of EAs, City/Municipality and
Provinces for of the entire Region.
Operational Procedure
A. Store all the shapefiles in one storage folder for easy retrieval loading in QGIS
project.
Shapefiles of all the Provinces
B. Merging of all EA2022 and BLDG_POINT layers (output: temporary / scratch

layer)
12. Open the QGIS 3.4.7
Merge all the ppmm_ea2022 layers to make it one (1) EA layer of the entire
province…

To merge: click Vector => Data Management Tools => Merge Vector Layers…
…click menu button…
…click Add File(s) and brose to Shapefiles folder where

all the shapefiles of the provinces are stored.
Select ANY of the “ppm_ea2022.SHP”…
…replace ‘1020_’ with

asterisk (*)…

…click Open…
…only the “ppmm_ea2022.shp“ are

displayed.
…select all… …click Open…
…click OK…
…”142 elements selected”…
…click Run… … click Close when done.

…in the Layers Panel,

rename the temporary
layer from “Merged” to
“rr_ea2022”…
Where:
rr = region code
13. Do the same process in merging all the building points up to this point...
…click OK…
…”142 elements selected”…

…all are selected (checked)
except the “ppmm_ea2022”…
…click Run… …click Close when done.
…in the Layers Panel,

rename the temporary
layer from “Merged” to
“rr_bldg_point”…

C. Generation of Provincial gaps and overlaps and affected building points layers
from merged original layers EA2022 using the Modeler3 automated process.
Recommended: Hide (uncheck) rr_bldg_point and rr_ea2022 layers before

running the Modeler3.
1. In the Layers Panel:
…right-click => Add Select the Group…

Group…and press enter.
2. From the Map Legends folder, drag and drop the

ea2prov+gaps_&_overlaps.model3 into the project…
…drag…
… and drop here…
Select the required layers and click Run…
…wait for few minutes…

D. Order of Layers and Display properties of MODEL3 generated layers.
…the arrangement of the output layers may • Re-arrange these layers as illustrated
vary upon running the modeler… • Change the display colors of these
layers if necessary.
Showing the Feature Count of layers

• Select the Model3 output layers
• Right-click => Show Feature Count…
Note: The “[5]” after the “prov(count)_gaps” is

the number or count of the “prov”, and NOT of
Note: The “[5]” after the “prov(count)_gaps” is
the “gaps”.
the number or count of the “prov”, and NOT of
the “gaps”.

Result layers (Generated by Model3) sample images
bldgpoints affected by gaps – bldg points located in holes or outside the landmass
(polygon). Zoom-in for detailed viewing.
bldgpoints affected by overlaps - bldg prov_overlaps – the extracted

points located in overlapping areas. overlapping portion (polygon).
Zoom-in for detailed viewing. Zoom-in for detailed viewing.

prov(count)_gaps – are “holes” inside the dissolved area (polygon) due to:
• lacking of some necessary contiguous areas
• failure in snapping the contiguous areas
Zoom-in for detailed view
prov(count)_gaps – total province count of the entire region.
F. Identification of the inclusive EAs where the gaps and overlaps are located.
In the Layers panel:

• Unhide (check) and select the 04_ea2022 layer
• Display the “geocode” labels (right-click =>
Properties…)
Follow the Symbology settings… Follow the label settings, click OK when done.

• The Layer “04_ea2022” can be hide or unhide from time to time as needed
during the identification or when locating the gaps and overlaps problem.
• In the Map Canvas, zoom-in manually to locate each gaps / overlaps problem
• Set the best view before capturing the gaps / overlaps (See sample illustrations)
Capture the gap and the inclusive EAs to be reported to the PSO Focal Persons of the involved provinces.
Capture method:
• Print screen
• Snipping Tool
Gap without building points but Overlap with building points. To be determined by
still needed to be modified / PSO Focal Person / MDP
snapped.

10.7 SUBMISSION OF SHAPEFILES AND EVALUATION FORMS
All PFP for mapping are required to submit the GIS-based census map shapefiles to
the Regional Statistical Service Office (RSSO) through the Chief Statistical Specialist of
the Provincial Statistical Office (PSO). Thus, submission must be done once all the maps
for all geographic areas for a City/Municipality have been reviewed completely as evident
from the accomplished PSO-Evaluation form.
Procedures in Submitting the Updated and Evaluated Shapefile Layers
A. For the Geotagging of Missing BSN Based on CPH Form 2 and 3 Output
1. The PFP for mapping must upload the geotagged building structures map files:
a. Open the link provided by the RSSO and enter the password.
b. Open the folder of the specific mapping activity – Geotagging F2F3.

c. Rename the Municipality1 folder into its corresponding municipality/city
name.
*If the folder cannot be renamed, create another folder for the municipality.
d. Open the municipality folder and then, rename the mm-dd-yyyy folder with
the date of submission of the shapefiles.
*If the folder cannot be renamed, create another folder.
e. Open the renamed folder and upload the required files, click the add button
(+) and then, select Upload file.
f. Browse the files for uploading on :\PSA-GIS\Province/HUC\2022

CAF\Projects\Municipality\Shapefiles folder. The files must include the
following:
i. For the bldg geopackge:

ppmm_bldg.gpkg
Where: pp = province code

mm = municipality code
g. Create the folders for the other municipalities.

2. After uploading the files, the PSO shall inform the RSSO through email regarding
the submitted files.
3. The RSSO shall inform the CO through email sent to psa.geospatial@gmail.com,

mapping.cpcd@gmail.com cc: m.dy@psa.gov.ph, a.trazo@psa.gov.ph, and
m.centeno@psa.gov.ph regarding the submitted shapefiles.
(Refer to the email template at the last page of this chapter.)
4. The Central Office will consolidate the submitted files for archiving.
B. For the EA Delineation Output
1. The PFP for mapping must upload the following updated and evaluated GIS-based
map files:
b. Open the folder of the specific mapping activity – 2022 CAF>EA

Delineation.
c. Rename the Municipality1 folder into its corresponding municipality/city
name.
*If the folder cannot be renamed, create another folder for the municipality.
d. Open the municipality folder and then, rename the mm-dd-yyyy folder with
the date of submission of the shapefiles.
*If the folder cannot be renamed, create another folder.
e. Open the renamed folder and upload the required files, click the add button
(+) and then, select Upload file.
f. Browse the files for uploading on :\PSA-GIS\Province/HUC\CAF\2022

CAF\Projects\Municipality\Shapefiles folder. The files must include the
following:

i. For the bldg_point shapefiles:

ppmm_bldg_point.dbf
ppmm_bldg_point.shp
ppmm_bldg_point.shx
ii. For the bgy shapefiles:

ppmm_bgy.dbf
ppmm_bgy.shp
ppmm_bgy.shx
iii. For the ea2022 shapefiles:

ppmm_ea2022.dbf
ppmm_ea2022.shp
ppmm_ea2022.shx
iv. For the road shapefiles:

ppmm_landmark.dbf
ppmm_landmark.shp
ppmm_landmark.shx
v. For the road shapefiles:

ppmm_road.dbf
ppmm_road.shp
ppmm_road.shx
vi. For the river shapefiles: (if available)

ppmm_river.dbf
ppmm_river.shp
ppmm_river.shx
vii. For the bridge shapefiles: (if available)

ppmm_bridge.dbf
ppmm_bridge.shp
ppmm_bridge.shx
viii. For the railroad shapefiles: (if available)

ppmm_railroad.dbf
ppmm_railroad.shp
ppmm_railroad.shx
Where: pp = province code

g. Create the folders for the other municipalities.

2. After uploading the files, the PSO shall inform the RSSO through email regarding
the submitted files and attach the corresponding scanned PSO evaluation forms.

m.centeno@psa.gov.ph regarding the submitted shapefiles.
(Refer to the email template at the last page this chapter.)
4. The Central Office will evaluate, renumber the EA geocode and the BSN of the
geotagged building structures; recode the GIS-based census maps based on the
new PSGC; and consolidate the submitted files for archiving.
5. The Central Office will send the recoded and renumbered GIS-based maps (in
geopackage format) – pppmm_layers.gpkg - that will be used in the block
mapping activity, through email, to the RSSO.
6. The RSSO will upload the renumbered and recoded maps in the Cloud Submission
Facility - PSA-GIS/2022 CAF/EA Delineation/Municipality1 folder.
a. Create new folder and name as Final Layer - mm-dd-yyyy.
b. Upload the recoded and renumbered GIS-based maps –
pppmm_layers.gpkg - sent by the Central Office.
7. The RSSO must inform the PSO, through email, once the recoded and
renumbered GIS-based maps are uploaded in the Cloud Submission Facility.
8. After receiving the recoded and renumbered GIS-based maps - Final Layer - mm-
dd-yyyy containing the pppmm_layers.gpkg, the PSO must download and
extract the file folder and place it inside :\PSA-GIS\Province/HUC\CAF\2022
CAF\Projects\City/Municipality folder and may proceed to the block mapping
activity.

C. For the Block Mapping Activity Output
1. The PFP for mapping must upload the following updated and evaluated GIS-based
map files:
b. Open the folder of the specific mapping activity – 2022 CAF>Block.

c. Open the municipality folder and then, create another folder and rename to
mm-dd-yyyy (the date of submission of the shapefiles).
d. Open the folder and upload the required files, click the add button (+) and
then, select Upload file.
e. Browse the files for uploading on :\PSA-GIS\Province/HUC\2022
CAF\Projects\City/Municipality\Final Layer - mm-dd-yyyy folder. The
files must include the following:
For the block layer:

pppmm_layers.gpkg
Where: ppp = province code

NOTE: pppmm_block is included in the pppmm_layers.gpkg
2. After uploading the required file, the PSO shall inform the RSSO through email
regarding the submitted files and attach the corresponding scanned PSO
evaluation forms.
m.centeno@psa.gov.ph regarding the submitted shapefiles and attach the
corresponding scanned RSSO evaluation forms.
(Refer to the email template at the last page of this chapter.)
4. The Central Office will evaluate and consolidate the submitted files for archiving.

10.8 BACK-UP OF DATA SETS AND PROJECT FILES USED IN 2022 CAF
Once all of the phases of the activity had been successfully executed, a back-up of files
should be done in order to efficiently preserve the outputs from the undertaking. Securing
a back-up of files enables the field office to gain access to the map outputs which can be
used as reference for future mapping and census operations.
1. For Provinces/HUCs with only one MDP

a. In the back-up medium of choice, browse to the folder where the backup
files are located.
b. Open the folder and click New Folder.
c. Rename the new Folder as ‘2022 CAF Backup’
d. Copy all the project folders containing the complete and updated
shapefiles in a Desktop Computer inside the “2022 CAF Backup” folder.
The project folders shall be grouped by City/Municipality name.
2. For Provinces/HUCs with more than one MDPs

a. In the back-up medium of choice, browse to :\CAF\2022 CAF folder.
b. Open the folder and click New Folder.
c. Rename the new Folder as ‘2022 CAF Backup’
d. The FIRST MDP shall back up all the project folders containing the
complete and updated shapefiles in a desktop computer under the
“CAF\2022 CAF Backup” folder.
The project folders shall be grouped by City/Municipality name.

NOTE:
The PFP for mapping should also prepare back-up copy of the same data set
files in a File Server, if server is not available, data set files must be backed-up in
a separate desktop computer or external hard disk.

Email Template
Subject: Shapefiles for Evaluation – Geotagging F2F3 (for submission of

Missing Geotagged Points)
Shapefiles for Evaluation –2022 CAF-EA Delineation (for submission
of EA Delineation output shapefiles)
Shapefiles for Evaluation –2022 CAF-Block (for submission of Block
Mapping output shapefiles)
(Email Content)
Region: (Region Name)
For evaluation
• Province/HUC 1:
1. Municipality1 > mm-dd-yyyy
• Province/HUC 2:
(Closing)
Name of Regional Focal Person for Mapping

Chapter 10 - Evaluation and Submission PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 10 - Evaluation and Submission PDF

Uploaded by

Copyright:

Available Formats

Geotagging of Missing Building Points from Processed Post- Census Maps and EA Delineation for the Development of

EARF for the 2022 CAF

CHAPTER 10: EVALUATION AND

Chapter 10 Evaluation and Submission |381

10.1 SUBMISSION PROCESS FLOW OF SUBMITTED GIS-BASED CENSUS MAPS

EA Delineation for the Development of the EARF for 2022 CAF

PSO GIS Unit

RSSO GIS Unit RSSO

RSSO Send to PSO

382| Chapter 10 Evaluation and Submission

1. For the Enumeration Area Boundary Layer (ppmm_ea2022)

i. Check if the boundaries are properly digitized (snapped) with no

2. For the Barangay Boundary Layer (ppmm_bgy)

3. For the Geotagged Building Structures Layer (ppmm_bldg_point)

i. Check if the verified true destroyed/demolished buildings and

Chapter 10 Evaluation and Submission |383

Block Mapping for 2022 CAF

RSSO GIS Unit

384| Chapter 10 Evaluation and Submission

1. For the Block Boundary Layer (pppmm_block)

i. Check if the boundaries are properly digitized (snapped) with no gaps,

10.2 HOW TO ACCOMPLISH THE PSO AND RSSO EVALUATION FORM

Chapter 10 Evaluation and Submission |385

An indicative measure with status of 1 (Acceptable) signifies that the specific

Provincial Statistics Office (PSO) Standard Review

EA Delineation for the Development of the EARF for 2022 CAF

1.1 EA boundaries are properly

1.3 Each EA has a corresponding Refer to

386| Chapter 10 Evaluation and Submission

2.1 The geotagged building

Proper and 3.1 The PSA-GIS/Province name

QA 4 Employs an 4.1 All GIS mapping files and

Chapter 10 Evaluation and Submission |387

Block Mapping for 2022 CAF

1.1 Block boundaries are properly

388| Chapter 10 Evaluation and Submission

Proper and 2.1 The PSA-GIS/Province name

Employs an 3.1 All GIS mapping files and

1. Evaluate and resolve the gaps/overlaps between municipalities and the

Chapter 10 Evaluation and Submission |389

Regional Statistics Office (RSSO) Standard Review

EA Delineation for the Development of the EARF for 2022 CAF

1.1 EA boundaries are properly

390| Chapter 10 Evaluation and Submission

2.1 The geotagged building

Proper and 3.1 The PSA-GIS/Province name

Employs an 4.1 All GIS mapping files and

Chapter 10 Evaluation and Submission |391

Block Mapping for 2022 CAF

1.1 Block boundaries are properly

Proper and 2.1 The PSA-GIS/Province name

392| Chapter 10 Evaluation and Submission

Employs an 3.1 All GIS mapping files and

1. Evaluate the gaps/overlaps between provinces.

Chapter 10 Evaluation and Submission |393

Central Office (CO) Standard Review Procedures

1. The return/re-submission of evaluated maps between the RSSO and CO shall be

2. Quality of the submitted shapefiles will be based on the errors identified by CO

394| Chapter 10 Evaluation and Submission

Chapter 10 Evaluation and Submission |395

last week of City/Municipality

396| Chapter 10 Evaluation and Submission