See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/339297817

Quality Control and Quality Assurance in GIS Database and Applications

Preprint · February 2020

CITATIONS READS

0 1,840

1 author:

Zakaria Ahmed
Thebes Academy
8 PUBLICATIONS   7 CITATIONS   

SEE PROFILE

Some of the authors of this publication are also working on these related projects:

Geographic Information System View project

NAfcoast View project

All content following this page was uploaded by Zakaria Ahmed on 14 September 2020.

The user has requested enhancement of the downloaded file.

 Quality Control and Quality Assurance in GIS Database and Applications
Dr. Zakaria Yehia Ahmed
GIS Consultant – Ain Shams University
Tel: 24534976
Mobile: 01223384254
zyehia2005@yahoo.com

1 Abstract
This paper presents a focus on Quality Control and Quality Assurance in GIS.The heart of
any spatial system is its powerful and reliable GIS database. This is of great importance in all
geographic information systems projects including Hajj, Umrah, tourism, real estate, and natural
resources. Since the spatial database is inherently complex and requires special technical skills to
maintain, the applications also require special technical skills. The inconsistencies in the database
can be minimized by adopting best practices to maintain the database. The systematic approach
to updating the large spatial database has been described here. Quality procedures have been
discussed. Several preventive mechanisms have been adopted. Various qualitative aspects of the
spatial database such as consistency, completeness, integration, etc. were analyzed and their
interrelationships analyzed. The emphasis is on achieving customer-oriented quality in a spatial
database.
With the general definition of quality, "the degree to which project deliverables meet
requirements", the challenge for GIS projects is to properly define specifications and specific quality
parameters that are appropriate for different types of GIS projects and deliverables. There is a big
demand for digital maps and GIS applications in Egypt. The production process in Egypt employs
manual techniques that are lengthy operational, time consuming and costly, it needs Quality control
and quality assurance procedures. We applied them in ten geological maps of Egypt with scale
1:500,000. It is a project as a cooperation between Cairo university and Ministry of Water
Resources and Irrigation of Egypt. As a training for the students of the faculty of engineering, civil
department.
(Key Words: Quality, Spatial Data, Data acceptance Criteria, Automated Quality Control, Quality
Control, Quality Assurance)

2 Introduction:
With the general definition of quality, "the degree to which project deliverables meet requirements",
the challenge for GIS projects is to properly define specifications and specific quality parameters
that are appropriate for different types of GIS projects and deliverables. In GIS projects, quality can
be defined (and ideally measured and assessed) for specific deliverables such as:
• reports and documents (needs assessment, design documents, plans, etc.);
• conceptual and physical database designs;
• spatial data collected from aerial surveys or satellite images and processed for delivery
to users
• GIS data compiled from field data collection, map digitizing, or other means; and
• GIS applications (custom-designed user interface and functionality from GIS software).

3 Quality Parameters for Typical GIS Project deliverables

Defining quality parameters for GIS project deliverables should be done as part of project planning-
-to provide a basis for project work and quality assurance activities. Documented specifications for

1
project deliverables establish the basis for quality management. Quality criteria associated with
different types of GIS project deliverables is identifies as:

Project Reports, Documents, MAP Products Conceptual and physical database

• Content covers specified areas designs
• Document format, clarity, readability • Completeness and inclusivity
• Design quality and usability of map • Format (adheres to requirements
products for deployment in GIS)
• Grammar, syntax, spelling • Correctness of GIS feature type
• Currency (up-to-date reflecting current • Data dictionary populated
conditions) • Inclusion of required properties,
rules, and metadata
Data Collection Compiled GIS Data
• Adherence to flight and equipment • Map feature completeness*
specifications • Map feature positional accuracy
• Data collection resolution • Graphic and topological
• Adherence to processing requirements connectivity correctness
• Positional accuracy • Features placed in proper file,
• Image quality table, feature class
• Adherence to data delivery file format • Attribute data completeness
• Time for processing and delivery • Attribute data accuracy
• Correctness of annotation
Custom GIS Applications
• Proper functionality
• Usability and adherence to user
interface standards
• Efficiency, performance, response time
• Adherence to coding, programming
standards
• Flexibility and maintainability
• Usability and clarity of map display
design
• Proper access to data sources
• Completeness and clarity of
documentation

In GIS projects, there is considerable focus on quality management for GIS data and custom
application development.

In major GIS database development projects, like the one being launched by the City of
Metropolis, it is common practice to prepare an initial database design and set up database
development procedures (including QC steps) and then initiate a pilot project--a task or sub-project
that is part of the overall database development project. The purpose of the pilot is to test the
design, source material management, data capture and development procedures, QC approach,
etc., and then to use the pilot project results to refine the design and procedures before initiating
production work. In GIS database work, the concept of incremental data improvement is important.
Consider a major GIS database project for a water utility organization which has the objective of
developing a complete GIS database of

2
4 GIS software provides tools for customizing applications that meet the needs of users.
The types of customization work that often come up in GIS projects include:
• automating access, integration with other systems or databases, or import/export of files
with external databases and applications;
• designing and developing “intelligent” interactive forms for attribute or graphic data entry
(includes use of dropdown pick lists, automatic error checking, and other controls);
• developing application scripts that can be launched by a simple menu pick and combining a
number of individual functions;
• designing and creating templates for standard maps and textual reports;
• creating data quality control and quality assurance applications using validation tools
provided by the software package;
• creating a library of standard queries that can be accessed through a menu;
• programming complex analysis functions using basic GIS processing commands; and
• building custom geospatial statistics or analysis models (e.g., network analysis).
The types of quality issues that are important in planning and execution for software and GIS
application development projects are:
• proper functionality;
• usability and adherence to user interface standards;
• efficiency, performance, response time;
• adherence to coding, programming standards;
• flexibility and maintainability;
• proper access to GIS data sources; and
• completeness and clarity of documentation.
Software and application development work can follow a number of formal methodologies, the key
point is that a formal, organized methodology should be put in place and followed during project
execution. As a matter of quality management, key steps in the process (user application needs
assessment, design, prototyping, operational deployment, documentation) should have defined
steps for user review and comment which is used by the development team to incrementally refine
the applications in a process that culminates in deployed applications that meet stated
requirements.

5 Four components for Quality management:

To guide and control an organization, its management must first determine its own quality policy
and the quality objectives associated with that policy, and then define activities related to quality
planning, quality control and quality assurance and improvement.
The goal of Quality Management is to ensure that all the company's activities to improve
customer satisfaction and other stakeholders are implemented effectively and efficiently.
Quality management focuses not only on the quality of the product / service, but also on the
means of delivery.

6 Quality management components

• Quality Planning:
Quality planning is a part of quality management that focuses on setting quality goals and
identifying the processes and resources necessary to achieve quality objectives. Quality planning
is an organized process that translates quality policy into measurable goals and requirements and
sets out a series of steps to achieve them within a defined time frame.
• Quality control.
Quality control is part of quality management focuses on achieving quality requirements .Quality
control helps to evaluate the performance of the actual operation of the process and the product,
3
and also to take appropriate action on deviations that occur if any actual performance is compared
to the planned objectives.
• Quality assurance
Quality assurance is a "part of quality management that focuses on providing confidence that
quality requirements will be met" needs customers and management needs to confirm quality as
they cannot supervise their own operations.
• Quality improvement
Quality improvement is a "part of quality management focuses on increasing the ability to achieve
quality requirements".

The chart shows that quality control is the main activity

in quality management. The quality control within a specific
system increases the quality control to the quality assurance
level. If quality improvement activities are then carried out
based on analysis of the process / product measurement data
as well as customer feedback data, quality management is
transferred. In this context, quality planning remains an
integral part of all quality management steps.
Simply put, the four components of Quality Figure 1: Quality Control Chart
Management mean:
- Quality planning - can we progress well?
- Quality Control - Do We Work Well?
- Quality assurance - will we continue to work well?
- Quality Improvement - Can We Work Better?

7 Adjust the process to achieve product specifications:

It is necessary to adjust some steps of the production method, for example:
• Quality of information.
First, the information can be defined as a set of data that has been operated in a certain
way so that it becomes in the form that leads to the decision-maker's benefit from it and thus to
the uncertainty.
As for the definition of quality of information, it can be said that there is no specific definition of
quality of information. The concept of quality varies according to the views and objectives of
producers and users of information. While the information product focuses on accuracy as a
measure of quality, another user focuses on utility, efficiency and predictability as a measure of
this quality.
Therefore, the concept of quality can be determined by studying and analyzing the general
criteria for measuring it.
• Adjust the size or area of the product and set the time and adjust the response
speed and control.
As well as the establishment and control of such controls.

To achieve this, we must lose the process properly and continue to inspect the product from time
to time.
Appropriate measures should be taken if any deviation is observed after such checks.
In this way, opportunities for producing a flawless product can be improved and access to
performance increases
"True from the first time"

4
The principles on which quality is based
The dimensions of quality passed through several stages during the last century can be
illustrated by:

• Phase 1: Adjusting the quality of the OPERATOR

• Phase 2: FORMAN quality control
• Phase 3: Quality control stage through INSPECTION
• Phase 4: The stage of statistical control of quality (STATISTICAL QUALITY CONTROL)
• Phase 5: The overall quality
control phase (TOTAL
QUALITY CONTROL (T.Q.C))
• Stage 6: Quality Assurance
Phase (QUALITY
ASSURANCE (QA))
• Stage 7: Total Quality
Management (TOTAL
QUALITY MANAGEMENT
(TQM))
Figure 2: stages of development of quality control systems and systems
The figure shows the
stages of development of quality control systems and systems.
There are two concepts of quality that determine the degree of superiority of the product or identical
to the specific uses, namely, the quality of the product indicating the ability to perform the specified
purpose compared to the similar products that perform the same function, and the quality of the
design of the product indicating the conformity of the body and design of the product to the specific
uses.
It is based on the actual experience of the user with the product or service, and measures the
amount of the product meets the requirements of the consumer and it is a moving goal in the
competition market, if the quality of the product or service as the total mix for the characteristics of
the product, service, market, engineering, industrial and maintenance while using the product or
service that meets expectations
There are five approaches that are often used to define quality:
Transcendent approach - Product-Based Approach - User-based approach - Factory-Based
Approach - Value-Based Approach
Quality is defined as the ability to provide products, services or processes that are free from defects
and perform their functions in a way that matches or exceeds the expectations of their users
through a culture of encouraging quality and a range of methods and methods that precede activity
at a reasonable cost.

8 Quality Dimensions:
There are a range of characteristics or qualities that characterize quality in order to be able to
satisfy the needs and desires of users and the identification of these characteristics is an important
process for management that seeks to achieve quality in its products and services.
There are different opinions about the number of these characteristics or characteristics by
researchers, that Garvin's point of view will be addressed in order to determine the dimensions of
quality identified by eight elements:
• Performance: These are the characteristics of the initial operation of the product, ie, the
performance of the specific function.
• Feature: Is the set of accessories available with the primary product.
5
 • Reliability: The ability of the product to continue its function without interruption or the need
for substantial maintenance
• Conformance: Is the degree to which the product conforms to established standards.
• Durability: The number of years represents the expected service of the product before it
deteriorates.
• Maintenance Serviceability: It refers to the ease, speed and low cost of repairing the
product.
• Aesthetics: Refer to the product body and external problem.
• Perceived Quality: It refers to the product's reputation, the trust of users and the
organization.

9 Quality Management:
PMBOK has defined quality management as "all activities undertaken by the organization to define
the policies, objectives and responsibilities that the organization must perform in order to satisfy
the needs of which it operates.”

“Rose” has identified four elements of quality management:

1)Quality Planning, 2) Quality Assurance, 3) Quality
Control, 4) Quality Improvement Quality Improvement.
The four elements of Quality Management represent
the basis of total quality management as the central
point of total quality management is continuous
improvement and the trend towards user satisfaction
and the philosophy of improvement based on the key
quality functions of planning, guaranteeing and quality
control that represent the essence of total quality
management.
Figure 3:Stages of quality development

10 Quality costs
First: Quality Cost Concept
The costs are borne because of the low quality that can exist because of the poor quality.
And is carried to ensure that the quality standards established or because of their inability to
meet them are met and that the cost of quality is defined as the costs incurred to prevent or the
costs incurred as a result of the production of low quality products and the costs arising with the
quality of the defect relating to diagnosis, repair and prevention of damage. Quality Cost Types:
Quality costs are classified into four types:
Prevention costs , Appraisal Costs, Internal failure costs, and External failure costs
Quality costs = prevention costs + calendar costs + internal and external failure costs

Optimal Level of Quality Cost

Product quality is expressed by the proportion of products that fail to conform to specifications.
Therefore, companies seek to determine the optimal level of defects. There are two perspectives
for determining the optimal quality level:

Traditional Perspective

6
The quality level of the products is determined according to the traditional perspective by balancing
the costs incurred for the prevention and evaluation
activities on the one hand and the cost of the failure
activities in conforming to the specifications on the
other. Figure (2) shows the point of separation as a
percentage of the defective units. Total cost costs
constitute the total expenditure for prevention, Internal
and external. The optimal level of product quality is the
point at which total costs are minimized

Figure 4:The traditional perspective of quality

Contemporary Perspective
The quality of the products is achieved at the level
of zero defect where the internal and external failure
costs increase with the increase in the proportion of
defective products, while the costs of prevention and
evaluation is slightly increased at the beginning but
soon begins to decline with the increase in the
proportion of defective products, and therefore the
minimum cost of quality Checks at the zero defective
level

Figure 5:Contemporary perspective of quality

Quality Reporting Report
Quality management requires reporting on quality costs and calculating them in a detailed manner
and for each type of quality cost
At the heart of the management accounting work
should be to summarize the measurement and
analysis of the cost of quality in the best image
visualization reports
The company's business requirements and
quality It may be better to have low quality cost
reports to demonstrate the elements of quality
costs
And how they can be used.
The following QA/QC Overview Flowchart is an
example that represents the process of using
ArcGIS Data Reviewer to perform automated and
visual QC of data received from an outside
contractor
Figure 6: QA/QC Overview Flowchart

11 QUALITY CONTROL in Spatial Data GIS databases:

10.1 Quality in Spatial Data GIS databases evolve constantly.
From paper maps through the digital conversion process to data maintained in a database,
GIS data are being constantly transformed. Maintaining the integrity and accuracy of these data
through a well-designed quality control (QC) plan that integrates the data conversion and
maintenance phases is key in implementing a successful GIS project. Poor data negate the
usefulness of the technology. Sophisticated software and advanced hardware cannot accomplish

7
anything without specific, reliable, accurate geographic data. GIS technology requires clean data.
Looking at this angle the tools used for the updating and maintaining the database must be latest
and most efficient.

10.2 QC Plan review

The fundamentals of quality Control never change. Completeness, validity, logical
consistency, physical consistency, referential integrity, and positional accuracy are the
cornerstones of the QC plan.
10.2.1 Visual QC :
Creating digital data from paper map sources does not make the data more accurate.
Actually this process introduces more or different types of errors into the data. The goal of high-
quality data conversion is to limit the amount of random and systematic error introduced into the
database. Random error will always be a part of any data, regardless of form. Random error can
be reduced by tight controls and automated procedures for data
entry. Systematic error, on the other hand, must be removed
from the data conversion process. A systematic error usually
stems from a procedural problem that, once corrected, usually
clears up the systematic error problem. Random and systematic
error can be corrected by checking data automatically and
visually at various stages in the conversion cycle. A short
feedback loop between the quality assurance and conversion
teams speeds the correction of these problems. At various
stages in the data conversion process visual QC must be
performed. Visually inspecting data can detect systematic errors
such as an overall shift in the data caused by an unusually high
RMS value as well as random errors such as misspelled text.
Visual inspections can detect the presence of an erroneous
date, the absence of data, or positional accuracy of data. Visual
QC can be performed using hard-copy plots or onscreen views.
The hard-copy plotting of data is the best method for checking
for missing features, misplaced features, and registration errors.
On-screen views are an excellent way to verify that edits to the
database were made correctly, but are not a substitute for
inspecting plots. Each error type needs to be evaluated along
with the process that created the data in order to determine the
appropriate root cause and solution.
Figure 7: Data flow in GIS database update cycle

10.2.2 Edge Matching check :

Edge matching, another critical component of the map preparation process, requires that
all features that cross or are near the map edge be reviewed with respect to logical and physical
consistency requirements as well as noted for positional accuracy and duplication.

10.2.3 Conflict Resolution :

Conflicts resulting when the same data coming from two or more sources differ must be
worked out. Map series must be reviewed together to identify duplicated features and resolve
conflicting positional locations and conflicting feature attributes.

10.2.4 Automated QC and Validation :

8
 Visual inspection of GIS data is reinforced by automated QA methods. GIS databases can
be automatically checked for adherence to database design, attribute accuracy, logical
consistency, and referential integrity.

10.3 Data acceptance Criteria

All data acceptance criteria must be clearly started in the Process Manual. Which errors
are acceptable? Are certain errors weighted differently than others? What percentage of error
constitutes a rejection of data? The answers to these questions are not always obvious and
require knowledge of the data model and database design as well as the user needs and
application requirements.

10.4 Categories of quality aspects in GIS database

Completeness means the data adhere to the database design. All data must conform to a
known standard for topology, table structure, precision, projection, and other data model specific
requirements .

12 DATABASE QUALITY CRITERIA

GIS database development is a complex undertaking
and a variety of data quality issues must be addressed
to achieve the ultimate goal of a high-quality database.
Some of the major database quality errors which are the
subject to checks and validation are:
File and Layer Naming, Map Feature Completeness and
Organization, Graphic Quality, Positional Accuracy,
Attribute Completeness, Symbology; Annotation; and
Sheet Format , Image Format and Quality and
Photogrammetric Data Quality and Integrity.
A general work flow in the QA/Acceptance process is
outlined in the following Figure.

Figure 8: Database quality criteria

13 QUALITY ASSURANCE PROCEDURES FOR CONVERTED DATA

This section defines the workflow for the verification of the converted database. The combined use
of random sampling techniques and automated tools will result in accurately measuring the overall
average quality level for each delivery subset. The use of random sampling techniques provides
several advantages. The first advantage is a simple means to ensure that the quality of the
conversion process is maintained at the required high standard. The second benefit is a simple
inspection that provides timely feedback on the quality of the data as measured in smaller subsets.
Random selection of the features for manual inspection gives an indication of the overall quality of
the data being converted. This document is intended to guide the quality assurance process and
to fulfill the requirements of the AM/FM/GIS project.

12.1 METHODOLOGY
The quality assurance procedures methodology for the converted data follows.
12.2 AUTOMATED QUALITY ASSURANCE
The Quality Assurance Supervisor will run each program on each delivery of converted data. Each
automated step in the quality assurance procedures for converted data is described below.
Since the data being checked by these programs is programmatically generated, this check is run
on 100 percent of the data and, in general, must be 99 percent correct for acceptance, although
9
specific error limits may be defined in contractor specifications. Acceptability will be based on the
number of errors reported divided by the number of attributes checked.
The types of automated checks used will vary from project to project, but the database quality
criteria that lend themselves to automated checks include:
Graphic Quality Attribute Completeness/Rule Base Adherence
Attribute Accuracy Symbology, Annotation, and Sheet Format
Photogrammetric Data Quality and Integrity.
12.3 MANUAL QUALITY ASSURANCE CHECKS
Some QA checks cannot easily be automated and require manual checks, usually based on a
sound random sampling approach, although for some criteria, 100 percent checks may be possible.
Quality criteria that are most suited to manual checks include those below. While these checks are
manual in nature requiring operator inspection, they are aided by automated tools to facilitate
access and viewing of automated files and the recording of error notes by QA technicians. In some
cases, manual checking will require the comparison of data to source material using generated
checkplots from the digital data.
File and Layer Naming
Map Feature Completeness and Organization
Positional Accuracy
Symbology, Annotation, and Sheet Format
Image Format and Quality
Photogrammetric Data Quality and Integrity.

Some important details about the manual QA checking process are described below.
12.3.1 Overall Cursory Scan
This general visual scan will be an attempt to identify any missing or incorrectly placed data. This
check will be conducted at the beginning of the random sampling inspection. The QA/QC
Technicians will look over the converted data related to the facility source map currently being
inspected, comparing the converted data to the source maps to verify that all features are captured
and spatially correct.
12.3.2 Random Selection
The QA Supervisor will run the random sampling selection program to generate a report consisting
of a random sample of converted objects based on the total number of populated record attributes
per grid area. The acceptance criteria (allowable errors) are also listed on the report based on the
sample size for each design file.
12.3.3 Missing or Omitted Data
At any time during the inspection process, the QA Technicians will be looking for missing or omitted
data. Missing graphic data identified during the Cursory Inspection will be cause for immediate
failure.
12.3.4 Disposition of Inspected Data
Completion of QA for a data set will be based on standard delineation. QA will be considered
complete based on the full inspection of a standard subset area. Once all tiles in a subset are
accepted, the area will be recorded as “QA Accepted,” and no updates or corrections will be
performed in that area prior to delivery to the client.
12.4 REPORTING
Reporting of errors identified by the QA Technicians will be documented by several means. A brief
description of all errors will be recorded on the QA review report.

14 Quality Control for GIS data

10
13.1. Starting a Quality Assurance Program
How to initiate a QA/QC program (planning stages)
Acknowledge the workflows where the GIS data is used so that data expectation is better
known , Establish criteria on which data can be accepted, as an establish data standards
(ESRI data models can be used). Create QC tasks to compare input data to the established
data standards
Find and record errors
• Check for feature completeness
Missing features geometry - incomplete features geometry

• Check for feature accuracy

checking that the feature properly describes the reality entity it is representing

• Check for attribute value consistency

attribute names conforms to naming conventions, attribute conforms to field types,
attribute conforms to established domain values, no illogical attribute combination is found
and missing required data

• Check for Attribute value precision

determine the real level of precision possible for a field value
Stating a QA Program
1. Create a QA plan as a simple document to record the data criteria and the QC procedures
used to check data against the established criteria, which can later evolve into a complete
guideline for the QA program
2. Develop a method to track and record errors – a spreadsheet or a point feature class
containing errors location and description
3. Create a list of initial QC tasks (as a checklist) to be applied on each dataset, that should
cover the minimal data acceptance level (typically automated methods to automatically
check on basic criteria)
4. Create a list of more intensive QC tasks to check more thoroughly on data (using manual
and visual inspection systems)

13.2. Recording and Tracking Errors

-Why we should record data errors? - Error has an error lifecycle - Data collected during
QA/QC - Error data collection and storage - Initial Quality Control Checks
Reason for Initial data quality checks
The need for cheap (preferably automated) methods is to quickly inspect data status and to
decide if data is sufficient to continue in the QA workflow
Compare database Schema
Should be well defined in the data models or in an explicit data dictionary
Can include:
Names - Attribute relationships - Subtypes, domains, topologies and geometric networks

11
Spatial data location checks can include:
• Projection - Coordinate System & datum - X/Y/Z Domain extent
Create initial checklist on data
• Compare the count of the features from the source and the destination (when checking on
data modification tasks or data migration tasks)

• Look for missing attribute values and unpopulated attribute values

• Confirm that unique values field is indeed using no actual or logical duplication (can use
'Frequency Count' tool)

• Check for badly formed geometry (can use the 'Check Geometry' tool)

• Search for tiny polygons (less than area threshold)

• Search for sliver polygons, which are very thin polygons surrounding parts of bigger
polygons

13.4. Visual Inspection and Quality Control

Managing the inspection space
Employ a visual-inspection tracking layer
• A QA/QC polygon grid can be used to completely cover the inspection area

• A QA grid should be slightly larger than the full extent of the inspected area

• The grid can be non-uniform (can borrow a zoning feature class to track progress using its
polygons)

• Can contain a property to track the visual inspection status (not started – in progress –
completed)
Using the overview and magnifier windows
• Help in keeping the inspector focused on the data without zooming in and out frequently

• Using the magnifier can limit the checking at a specific precision level

13.5. Creating a Quality Assurance Plan

The QA program goal
The main goal of a QA program is to protect and sustain the GIS, as data is the most vital
component in a GIS
QA Plan
The QA plan is the document used to define every aspect of the program
It identifies:
• Data criteria and data quality standards

• Outlines the procedures used to measure input data quality against the data criteria

• Provides guidelines for applying QC tasks to the GIS project

12
QA Plans and GIS Projects
Each GIS project should have its custom-tailored QA plan to specify its input and output
QA Plan Contents
Project management section - Project design section - Project data assessment section - Project
reporting and oversight section
Pilot Project
A pilot project is a required step in the process of creating a QA plan, its main purpose is to check
the applicability of the constrains and checks done in the QC process

15 QA/QC Checklist
Twelve main categories
• Documentation and File Structure • Network Checklist
All pertinent documents Connectivity
- Contain a brief description of the project Loops
▪ What client requested Direction of Flow
▪ How it was completed - Sources or sinks
- Original abstract Rules in place and working
▪ Outline of steps taken Document
- Metadata
- Standardized file structure
- Any other documentation
▪ Spatial references
▪ Specific output types
▪ Any paper documents used
• Project Checklist • Relationship Checklist
Relevant Name Relationships to Other Datasets
Opening the Project - One to one
- Open with no errors - One to many
- Desired location - Database connections
▪ Extent of system Document
▪ Specific location
- Correct drawing order
- Layer States or definition queries
- Symbols
Does the GIS do what it is supposed to do?
• Data Checklist • Annotation Checklist
Relevant Data Visible
Correctly Named - When and where it should be
- Naming Conventions Relative
Proper Location Dynamic or stored in a database
- i.e. C:\AMFM\ABC_Cooperative Multiple copies
Pre-Defined Model Document
- Other billing or staking programs
• Data Structure Checklist • Custom Applications Checklist
Data in Correct Layer Do they load?
- All fuses in fuse layer Do they work on the clients hardware?
- All transformers in transformer layer - Plot Routines
- Etc…
Viewable when it should be
Document
• Attributes Checklist • Wall Map/Map Book Checklist
Actual Data Common Output Formats
Symbolize from an attribute Only contact with GIS for some
• Is that field value complete? - Base opinion of what they think
– Subtype or block - Education
reference? Page Numbering
Label from an attribute - Correct Order
Document Scale
Symbols
- Size
- Color
Effective use of the page
Is annotation visible?
• Data Conversion Checklist • Project Checklist for Clients
Converted or imported to GIS from another platform - Point of Delivery
Check for lost data - Correct File Path
One to one match - All Layers Available

13
 Proper Conversion - Correct View
- Polygon to polygon - Correct Features On or Off
- Point to point - Printers and Other Hardware Configured
- Polyline to polyline - QA/QC Checklist for Client
- Same relative location Document

16 Study Project:
Ten hardcopy geology maps of a scale of 1:500,000 in Egypt, produced by the Egyptian Survey Authority
(ESA) and the Military Survey Department (MSD) are used. The base maps are scanned with resolutions of
400 dpi, transformed to raster format, and then rectified with projection adjustment. The project staff of 10
persons converted the maps to vector format with geographic types. Some errors are founded after making
QC procedure as in the following table:
Ten images: Vector for 10 images: Some shifts:

Missed features and wrong Shift in some Gaps

drawings: features:

Gaps and bad features: Edge Matching: Unnecessary

drawings:

Figure 9: Spatial Errors

Process:
• Evaluate various ways to measure quality.
• Select a random sample of the geology features and test for adherence to specifications.
• Target confidence level determines sample size
• Extracted random features samples
• Evaluated records independently
14
 • We found the errors in the table above.
Results:
• Random sampling process gave consistent results.
• Biggest challenge was creating quality rules
• Choose chick list over classifications and attributes.
• Data quality influences sample size
• Using ANSI/ASQC standard determine an acceptable quality level and related sample size
(E.g. 180 of 40000 features allowing 5 errors)
• Manually and semi-automatic check data using chick list.
• Layers test from 90% to 95% correct
• Quality measures is very repeatable
• Good standards can be used as an editing manual.

Application Testing Checklist (Sample):

A chick list for GIS applications can be made
depending on its functions as the following image.

Figure 10:Application Testing Checklist

17 Conclusions
The following are the most comprehensive conclusions derived from this thesis:
All measurable parameters of the quality must be measured frequently to know the
improvements. The measurement data are analysed initially, additional measurements and
analyses are conducted as necessary, results are reviewed with relevant users, and necessary
revisions for future analyses are noted
Based on data the root causes of the non-conformity, need for corrective action is evaluated to
ensure that non-conformities do not recur .
The corrective actions are determined and implemented consisting of
•A definition of the causes of non-conformities .
•Elimination of causes of non-conformities .
•Appropriate actions to avoid recurrence of non-conformities for Corrective action
•Appropriate actions to avoid occurrence of non-conformities for Preventive action

18 RECOMMENDATIONS
The following recommendations are the most comprehensive recommendations that are suggested
for future research:
1. The quality activities in the company are attributed to a group of departments and activities.
No one is responsible for all quality activities, and the non-adoption of methods of measuring
and managing the costs of quality and consequently its impact on the company's resources
as a result of not measuring these costs and monitoring them.
2. The concentration of management and employees on quality assessment, through the
examination and try to find a lack of conformity with the specifications
3. We have to make QA and QC procedures and checklist in any GIS project and
Geodatabase.
4. Any GIS project should have a part from the total budget of the project.

15
 LIST OF REFERENCES
1. American National Standard , ASOC Z.1.4 Standard ,
https://portal.katespadeconnect.com/documents/10113/23796547/ASOC+Z1.4-
1993
2. Gary J Hunter ,”Issues and prospects for Spatial data quality”
spatial information technology ICORG vol -1
40-45,BSP publications.

3. Hunter G J, Godchild M F 1995a "a methodology of reporting uncertainty in

database products" Journal of urban and regional information systems
association vol 7 no 2 11 - 21.

4. INTERNATIONAL STANDARD ,ISO 9001: 2000

5. ISO 9001:2015 - Quality management systems -- Requirements
6. Matthew McCain,William C. Masters ,Integrating Quality Assurance Into GIS
Project Life Cycle, ESRI ArcNews.

7. Montgomery, Glenn E. and Harold C. Schuch, GIS Data Conversion

Handbook, GIS World, Inc. and UGC Consulting, Fort Collins, 1993.

8. N. P. Hegde a, G.L.Hegde, QUALITY CONTROL IN LARGE SPATIAL

DATABASES MAINTAINANCE

9. Peter Croswell, GIS DATA CONVERSION QUALITY ASSURANCE AND

DATABASE ACCEPTANCE AN OVERVIEW OF CONCEPTS AND
PROCEDURES, PlanGraphics, Inc. 112 East Main Street Frankfort, Kentucky
40601-1806 ,2005

10. Robert D. Borchert, QA/QC: A Checklist for Quality and Control ,

GIS Technician , 2015

11. Sherry Smith & Jay Cary, Developing a Quality Assurance Plan,ESRI,
September 15, 2010

16

View publication stats