GENERAL ORGANISATION FOR PHYSICAL PLANNING
Support to GOPP in Planning and GIS
GEOGRAPHICAL
INFORMATION SYSTEM
FOR REGIONAL PLANNING:
ORGANISING THE DATA
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
TABLE OF CONTENTS
Geographical Information system for regional planning: organising the data .................................... 1
PREFACE TO THE BETA VERSION ................................................................................................. 3
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT 4
INTRODUCTION ..................................................................................................................................... 4
STRUCTURE OF THE DOCUMENT .................................................................................................. 4
There may be additional explanatory notes. ....................................................................................... 5
THE REGIONAL PLANNING CONTEXT ....................................................................................... 5
GETTING STARTED ............................................................................................................................... 6
STANDARDS .............................................................................................................................................. 7
LEGAL ISSUES .......................................................................................................................................... 8
RECOMMENDED INPUT SCALES FOR EGYPT’S REGIONS .................................................. 8
RECOMMENDED FILE STRUCTURE............................................................................................... 8
DESCRIPTION OF THE STUDY AREA ............................................................................................ 9
THE REGIONAL BASE MAP ................................................................................................................ 9
Boundaries / Administrative Units.......................................................................................................... 10
PART II: PRESENT SITUATION ........................................................................................................ 12
NATURAL RESOURCES AND THE ENVIRONMENT .............................................................. 12
Climate ......................................................................................................................................................... 12
Landscapes .................................................................................................................................................. 15
Spot Heights ................................................................................................................................................ 16
Contours ...................................................................................................................................................... 16
Surface Geology.......................................................................................................................................... 17
HYDROLOGY .......................................................................................................................................... 18
Drainage ....................................................................................................................................................... 18
ECOSYSTEMS AND HABITATS ........................................................................................................ 23
Special Habitats........................................................................................................................................... 23
(Nature) Conservation Areas .................................................................................................................... 24
DEMOGRAPHIC CHARACTERISTICS AND TRENDS.............................................................. 25
SOCIO-ECONOMIC FEATURES AND TRENDS ......................................................................... 34
EMPLOYMENT AND LABOUR FORCE ......................................................................................... 34
Main Land Use and Land Cover .............................................................................................................. 38
Mining and Quarrying Licences ............................................................................................................... 39
INFRASTRUCTURE ............................................................................................................................... 40
Roads ............................................................................................................................................................ 40
Ports and Airports ...................................................................................................................................... 42
Waterlines .................................................................................................................................................... 43
Water source ............................................................................................................................................... 44
Water source ............................................................................................................................................... 45
Sewerage ...................................................................................................................................................... 45
Treatment .................................................................................................................................................... 46
Waste ............................................................................................................................................................ 47
Telephone lines ........................................................................................................................................... 47
Energy (power plants and sub-stations) .................................................................................................. 48
Power lines .................................................................................................................................................. 49
SERVICES .................................................................................................................................................. 49
Service Facilities: ......................................................................................................................................... 49
SUITABILITY FOR SETTLEMENT ................................................................................................... 53
FUTURE WORK ...................................................................................................................................... 55
2
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
PREFACE TO THIS VERSION
This version of “Geographical Information systems for Regional Planning in Egypt” is the
product of much hard work and many sessions of the Regional Planning Working Group in the
General Organisation for Physical Planning.
It is still “work in progress.” There are known shortcomings. There are outstanding issues that
need to be resolved. Several of these lie outside the responsibility of the Working Group, and
depend on decisions taken elsewhere. There probably shortcomings that are not apparent now.
The next step therefore is to test the advice provided in at least one real case. This could be an
exercise using data already collected for an earlier regional plan. This will reveal some problems,
while providing practical solutions.
In the meantime, steps will continue to be taken to address known issues, and to work with other
staff in GOPP to solve those issues that lie outside the responsibility of the Regional Planning
Working Group. These are primarily concerned with data storage structure and the interface
between databases and the user.
The Working Group Members are: Eng. Nagwa El Marsafy, General Manager, Regional
Planning, GOPP Cairo, Team Leader; Dr. Eng. Maha Fahim; Eng. Lamiaa Adel; Eng. Mervat
Zaki; Eng Dalia Anis; Eng. Adel Basily; Eng Elham Anwar; Eng. Nagwa Mohamed; Eng.
Moamed Awad (Infr. HQ); Eng Tagrid; Eng. Sherin; Mr Alaa Elhifnawi; Mrs. Soheir el Hady;
Mr. Mohamed El Khubiery; Mrs Iman Mohamed supported by Dr. Hany Ayad of University of
Alexandria and Tim Greenhow of SIPU International, Sweden.
3
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
BETA VERSION
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL
PLANNING IN EGYPT
2005-07-20
INTRODUCTION
A geographical information system will be used in regional planning in the General
Organisation for Physical Planning (GOPP) for analytical as well as presentation
purposes.
This document describes a model system that can be used as a starting point. Every
region is unique, and each regional plan has its own special character and demands.
Therefore there will be a need to modify this model in some way for every planning
exercise. Even then the model will provide examples of how to set up the components to
satisfy such cases.
GOPP has chosen Arcview/ArcGIS (products of ESRI) as its GIS software. As a result
the approaches and methods presented here derive in part from the system that ESRI has
adopted in creating this software. This differs from other software. However, all the
processes described here can be accomplished in other software of equivalent
sophistication.
The ArcGIS approach links tables of information to graphic layers that have geographical
dimensions. There are three basic types of vector layers, showing points, lines or
polygons. There are also raster layers that show data that vary rapidly over an area. Some
of these are images, such as satellite images or orthophoto maps. Others may be created
to allow certain types of analysis.
Any information in the tables that can be linked to these points, lines or polygons can be
used in the GIS. These layers can be laid on top of one another as long as they share the
same locational and geographical characteristics. This allows various types of visual and
mathematical analyses to be done.
The layers can be placed on each other in various combinations to create “maps” that can
then be saved as graphic objects, or printed out as paper maps. It is very important when
working with GIS in planning projects to maintain the distinction between “layers,”
linked to tabular data, and “maps,” which are final presentations of combinations of
layers.
STRUCTURE OF THE DOCUMENT
The document first presents the context for which it is produced – that is for regional
planning. It then describes some of the fundamental prerequisites of the GIS. A working
catalogue and file structure is proposed.
Following this more general section, the document then describes the datasets that are
most likely to be used in the various parts of the Regional Planning document. In this
edition the concentration is on the description of the current situation. The development
of development alternatives, the selection of recommended alternative and the proposal
4
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
itself are heavily dependent on the outcome of the analysis of the current situation and
already planned projects of different government authorities. Some maps will be created
that use existing layers with graphic objects placed on them for illustrative purposes.
The common presentation format is as follows:
● Proposed Name for the vector shape file (*.shp) that is the heart of the layer.
● The potential Usage of the layer, in presentation and /or in analysis.
● The Feature Class. For vector data this will normally be point, line, or polygon.
Images will be indicated as being raster data.
● The Basic Dataset. This is a *.dbf file with the same name as the *.shp file that
contains automatically generated geometric information for each of the objects in the
layer. This document presents the additional fields that should be added to the base
dataset to allow it to work usefully on its own, and/or be linked to other datasets.
● Codes and Look Up Tables For The Basic Dataset. In many cases codes are used
in fields in the basic dataset, and in the associated datasets. Look up tables contain a
field with the codes and some explanatory fields. The Label field contains a short
explanation that can be used in map legends to explain symbols.
● Associated Datasets. These are presented as tables of data that can be linked to the
objects in the shape file. To allow the linkage one field in the basic dataset and one
field in the associated dataset must be the same.
● Codes and Look Up Tables for the Associated Datasets. There may be several
fields in the associated datasets that use codes. Each one will have its own dataset. The
convention used here is to give the name of the coded field in the dataset to its Look
Up Table.
There may be additional explanatory notes.
THE REGIONAL PLANNING CONTEXT
The Regional Plan that is published is generally based on a number of special studies.
These may, or may not, appear as appendices. They are not treated in these guidelines
because they are normally very region or sub-region and sector specific.
The model Regional Plan has a fairly traditional structure with six main parts, each one
further elaborated in many sub-sections, as illustrated below:
I
INTRODUCTION
1. Description of the study area
2. Description of the planning process, including participation of stakeholders
3. National goals
4. Identify (national) priorities (for the region) for the coming 5 years
5. Vision for the region
6. Objectives to be addressed in the Regional Plan
7. Development Indicators
a. Economic
b. Social
c. Environmental
d. Etc.,
5
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
e. Human Development Index (Composite of indicators)
II PRESENT SITUATION
2. Natural Resources and the Environment
a. Potentials
b. Issues, constraints, problems
3. Demographic Characteristics and Trends
a. Potentials
b. Issues, constraints, problems
4. Socio-Economic Features and Trends
a. Potentials
b. Issues, constraints, problems
5. Infrastructure
a. Potentials
b. Issues, constraints, problems
6. Services
a. Potentials
b. Issues, constraints, problems
7. Settlement Distribution and Hierarchy
a. Potentials
b. Issues, constraints, problems
8. Summary and Problem network analysis
III ALTERNATIVE PROPOSALS
1. Current, Approved Project Proposals
2. Growth Scenario 1
3. Growth Scenario 2
4. Growth Scenario 3
5. Evaluation of Alternatives (measured against Objectives, using a point system), and
Final Selection
IV DEVELOPMENT PLAN
The selected scenario in more detail.
V IMPLEMENTATION PROGRAMME
Will include a monitoring programme.
These guidelines will concentrate on Introduction and Current Situation, which are the
two parts that can be best standardised. Some attention will be given to the other parts,
but this will be more tentative as every region and development plan will be specific.
GETTING STARTED
When starting on the GIS component of a planning exercise, it is very important to have
a clear understanding of the end product.
What map or maps am I trying to produce?
How will they be used? What will they be used for?
Who will use them?
In this manual, most of the usual kinds of maps used in regional planning will be
described, so the first question is not difficult, though it must still be answered.
The second question may give answers that have important implications for how the
original data is compiled and treated. Regional plans are usually produced in the form of
6
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
paper documents, seldom larger than A4 in size. At this size, maps will either have to fit
on an A4 or A3 (foldout) size paper, or alternatively printed separately in larger size,
folded and kept in a pocket in the back cover. This usually means that maps of regions
must be presentable in small scales. At the same time, the consultation and approval
processes involved in regional planning may require large poster-sized maps, using much
larger scales.
One advantage of digital mapping is that different scale paper maps can be technically
produced from the same digital map. However, the scale and resolution at which data is
added to the project affects the accuracy and visual quality of the final output.
Presentations should not be at scales too far removed from the input scale. If there must
be compromises, it is better to have larger input than presentation scales, because with
reduction in scale, geometric errors are also reduced, and generalisation processes can deal
with “clutter” on the map. But the errors involved in enlarging data cannot be so easily
compensated.
Another consideration is whether or not users will want to make copies of the maps.
Most copying machines still only copy in black and white / grey scale. This means that
even when maps are produced originally in colour, the colours should be chosen in such a
way that the maps will still remain useable after being copied to black and white / grey
scale. One way to overcome this problem is to use patterns together with colours.
Maps may also be published on the intra- or internet. The needs will be different if they
are to be available for download in Adobe Acrobat.pdf format, or if they are to be part of
an interactive site where viewers can select items to show, and be able to zoom and pan.
STANDARDS
The quality of the product is directly related to the quality of the data used to produce it. Data
from different sources, and from different dates or periods, is often of different levels of quality.
To a large extent this cannot be avoided. The user should be aware of the quality differences and
the way in which mixing the data affects the quality of the product. Products of varying quality
can be used for decision-making, as long as the level of quality is known and its implications
understood.
There it is important to maintain metadata (information about information) on the data and
information used and produced. Metadata should be provided for both geometric data (the
points, lines, polygons, or raster data) and the datasets. GOPP has a standard basic metadata
form that should be compiled for each dataset.
When data or information is requested by a supplier, whether a government agency or a private
consultant or company, a copy of the metadata form should be provided to the supplier and it
should be a specification of the order that this form be filled in and returned together with the
data or information. Unless this is done, there may be significant questions of the quality of the
data. The impacts of using it with other data will mean that no reliable quality statement can be
made about the product.
At the present time, GOPP has not established its own quality standards in terms of geometric
data – that is the levels of accuracy and precision that should be applied to digitisation or creation
of maps. It does have some standards with respect to symbols. These are presented in the GOPP
Glossary. They should be used. If there are practical problems using them, these should be noted,
and submissions made to the Standing Committee on Standards indicating the nature of the
problem and proposing an alternative, or a solution. If the glossary does not include a symbol for
7
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
the feature to be presented, the same procedure should be applied, this time with a feasible
suggestion for an appropriate symbol.
LEGAL ISSUES
Some types of data and information come with conditions on its use, distribution and
publication. It is important that users know what these conditions are. Stolen data is considered
by the law and the courts in the same way as any other stolen property. This is why there is a
special entry in the metadata form requiring information on the conditions of use. These
conditions should be accepted and applied. It is particularly important that legal considerations be
considered before any product is made available on the Internet.
It is possible for GOPP to impose its own conditions on its products. In such cases it is
especially important that any material from outside GOPP is acknowledged and reviewed with
respect to its legal use.
RECOMMENDED INPUT SCALES FOR EGYPT’S REGIONS
It is recommended that for both regions and sub-regions the input scale of data should be
1:100000.
The output scale will vary according to the size of the area being covered and the size of
the paper on which it is presented.
RECOMMENDED FILE STRUCTURE
This document recommends the creation of many datasets, each related to a GIS layer. It is
vitally important that all of these files and those that are created automatically by ArcGIS or
ArcView are organised systematically so that they can be found when needed.
What is recommended here is directed primarily for the working files, and especially for the pilot
test case. While this is being done, other decisions concerning the long term database structures
and filing systems will be made. When the test is completed, and those decisions are finalised this
document will be revised to conform to the new system.
A folder should be created named for the specific planning
project. Under that folder, create a number of sub-folders, as in
the diagram here. When creating datasets and GIS shapefiles,
place them in their proper folder. If several GIS “projects” are
created put the project files (e.g. ,prj or .mxd) in the
‘02_Projects’ folder, even if the shapefiles are placed elsewhere.
Text documents (the plan itself and any related written material
should go into 12_Documents. Most of the natural resource
datasets should go under ‘04_NatResources’ The
‘settlements.shp’ should be placed under ‘05_SocioEconomic’
and so on.
8
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
PART I: INTRODUCTION (of the Regional Plan)
DESCRIPTION OF THE STUDY AREA
The Regional Plan begins with an introduction to the region to be studied and presented.
The Introduction will be illustrated with a map showing the main features of the region,
together with a small graphic inset showing the map of Egypt and the region’s location
within the country.
The map will be also provide the base map upon which other maps in the document will
be based.
THE REGIONAL BASE MAP
Traditionally, plans that included many illustrative maps, used a common base map, on
which other thematic maps were drawn.
The GIS does not work in quite the same way. Viewed from the GIS this base map is
actually made up of several distinct layers. At the same time, it is common that certain
layers are combined very frequently with other layers to produce maps.
1. a layer showing boundaries, either of the region, the study area, or all
administrative units of a certain level (such as Governorates) is very commonly
combined with other thematic layers. This will based on a selection of the desired
administrative units from AdmUnits.shp. At regional level the selection will be for
Governorates; at sub-regional for Govenorate, markhaz and city.
2. a layer showing settlements needed for orientation purposes. These will be
Governorate capitals in most cases. For the base map, a selection is made from the
Settlements.shp file for Capital=True.
3. a layer showing the major roads. This is based on Roads.shp, selected for
Type_Code=2 (regional roads).
4. a layer showing selected surface water courses. For base map purposes select
Dr_Type=“1” OR “7” OR “8” from Drainage.shp file. This selects for all
perennial rivers, lakes and wetlands.
5. in some cases a layer or layers showing other physical features that are needed for
orientation purposes. Generally, the number of orientation features should be kept
to a minimum.
Most of the rest of the maps in the regional plan will have this “base map” with other
layers added to it.
The shape files referred to above are described in detail in the sections listed below:
AdmUnits.shp
Settlements.shp
Roads.shp
Drainage.shp
Immediately following this section.
Present Situation: Settlement Distribution and Heirarchy
Present Situation: Infrastructure
Present Situation: Natural Resources and the Environment
9
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Boundaries / Administrative Units
Proposed Name: AdmUnits
Usage
This dataset will provide the basis for many maps in which data is linked to administrative units,
whether these are national regions, Governorates, markhaz, or lower units.
This dataset is closely related to the Settlements dataset. The Set_ID is a nested coding system
that includes national regions, Governorates, markhaz and lower administrative units. This means
that all datasets that are linked to settlements basic dataset can also be linked to this
Administrative Units dataset. Demographic data, labour force data, service data are all available to
this layer by linking through Set_ID and/or Name.
The base map requires some administrative boundaries for orientation purposes. These are
selected from admunits.shp . Boundaries can be shown as such by ensuring that the polygons’ fill
colour is set to “no fill.”
There are several types of boundaries that can be used in a regional planning exercise:
● national border
● regional boundary
● Governorate or sub-regional boundary
● Markhaz boundary
● City boundary
The line symbols to use for each category of boundary should be taken from the GOPP data
Glossary.
Feature class: Polygons
Basic Dataset
AdmUnit
Column Heading
Data type
Length
Definitions
Set_ID
Alphanumeric
16
Name
ArName
Alphanumeric
Arabic
alphanumeric
Numeric code
16
25
Unique ID number for every administrative unit at all
levels.
Name of the administrative unit
Name of administrative unit in Arabic
AdType
2
The level of administration, eg region, Governorate,
markhaz, etc. Codes are defined in the look up table
LUT_AdType.
Codes and Look-up Tables for Basic Dataset
LUT_AdType
Code EnLabel
1
2
3
4
5
6
7
The nation
Region
Governorate
County
City
District
Neighbourhood
ArLabel
Definition
Ekleim
Muhafza
Markhaz
Medina
Hai
Sheakha
The entire country
Refers to the seven planning regions in Egypt
Governorate
In rural areas, this is the admin unit below the Governorate.
Cities with special legal status, distinct from urban Governorates.
Normally an urban administrative unit
Normally an urban administrative unit, originally designed as
10
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Code EnLabel
ArLabel
8
Local Council
9
Village
Wehda
Mahalia
Karea
10
Satellite village
Nagaa
Definition
voting districts (i.e. there should be a polling station in each
sheakha).
Normally a rural administrative unit, below the markhaz in the
hierarchy.
A “mother” village, with a council that is subordinate to the
Wehda Hahalia council.
Small hamlets, usually reflecting property boundaries that are
directly linked to a “mother” village.
11
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
PART II: PRESENT SITUATION
NATURAL RESOURCES AND THE ENVIRONMENT
Climate
Precipitation, Ave Max, Ave Min, Ave Temp, Solar Radiation, Relative humidity, wind speed, wind
direction, Evapo-transpiration
Proposed Name: Climate
Usage
Climate maps are used to illustrate basic environmental information about a region. Normally,
isolines showing different parameters are generated from point source data representing synoptic
weather stations. This is a process that should be directed and carried out by qualified
meteorologists. It is not advisable that non-meteorologists try to construct climate maps from
raw data. Isoline maps at regional level cannot be enlarged to give accurate climate maps at subregional or urabn level.
For the purposes of regional planning it is recommended that compiled maps, either digital
(preferred) or analogue be obtained from the Meteorological Authority. If analogue maps are
used, they will need to be digitised.
When data is received from the Meteorological Authority, ensure that the period of measurement
is stated, and the number of stations used to generate the climate maps. Of particular importance
is to check the scale at which the data can be used reliably. Climate data generated to show
national climatic patterns are not suitable for use at Governorate or lower levels.
All parameters except wind direction are included in one associated dataset. This means that the
user must select records for a particular parameter for display. Each parameter can be selected in
turn and the saved as a *.lyr file, rather than a *.shp file. This also avoids multiplication of the
dataset. The Iso_ID will link the basic dataset with the associated dataset.
The wind rose must be drawn in digital format based on information provided by the
Meteorological Authority. Each wind rose will be stored as a graphic that can be placed on the
map. It could appropriately be placed on the same map as wind speed. Each wind rose should be
placed at the location at which the measurements were taken.
Graphs can also be generated and placed on the map at appropriate locations. The graphs can be
generated from data in the MetStationData dataset.
Feature class:
This is a line feature layer.
Basic Dataset
Climate
Column Heading
Data type
Iso_ID
Parameter
Alphanumeric 8
Alphanumeric
code
Length Definitions
Unique ID number for each isoline on the complete map.
The parameter that is being represented: The code
explanations are provided in the LUT_Parameter Look up
table. (Precipitation, average annual Max, Ave Min, Ave
Temp, Solar Radiation, Relative humidity, wind speed,
wind direction, Evapo-transpiration)
12
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
ValUnit
Alphanumeric 8
Value
Alphanumeric 8
The unit in which the parameter is measured, e.g. degreee
C, millimetres, etc. The lookup table is LUT_ValUnit
The value of the isoline for example “45” (degrees C)..
This would servce as the label on the map.
Codes and Look-up Tables for Basic Dataset
LUT_Parameter.dbf
Code
EnLabel
ArLabel
1
Average annual precipitation
2
Average daily maximum
temperature
Average daily minimum
temperature
Average annual temperature
Average annual solar
radiation
Average annual relative
humidity
Average annual wind speed
Average annual
evapotranspiration
3
4
5
6
7
8
Definition
The average amount of precipitation that falls
in a year.
Associated Datasets
Iso_line.dbf
Column Heading
Data type
Iso_ID
Parameter
Alphanumeric 8
Alphanumeric
code
Number
5
Numerical
2
code
Value
ValUnit
Length Definitions
Unique ID number for each isoline on the complete map.
The parameter that is being represented: The code
explanations are provided in the Parameter Look up table.
The value of the parameter for the isoline in question.
The unit of measurement for the parameter, for example
“mm,” “degrees Centigrade”
MetStationData
Column Heading
Data type
Set_ID
AveMaxTJan
AveMaxTFeb
AveMaxTMar
AveMaxTApr
AveMaxTMay
AveMaxTJun
AveMaxTJul
AveMaxTAug
AveMaxTSep
AveMaxTOct
AveMaxTNov
AveMaxTDec
AveMinTJan
…
AveMinTDec
Alphanumeric
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
Length Definitions
Unique ID for each settlement listed in this dataset
Average daily maximum temperature for January
Average daily maximum temperature for February
Average daily maximum temperature for March
Average daily maximum temperature for April
Average daily maximum temperature for May
Average daily maximum temperature for June
Average daily maximum temperature for July
Average daily maximum temperature for August
Average daily maximum temperature for September
Average daily maximum temperature for October
Average daily maximum temperature for November
Average daily maximum temperature for December
Average daily minimum temperature for January
Average daily minimum temperature for each month to
Average daily minimum temperature for December
13
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
AvePrecJan
…
AvePrecDec
AveWinDirJan
…
AveWinDirDec
AveWinSpdJan
…
AveWinSpdDec
AveEvapJan
…
AveEvapDec
number
number
number
number
number
number
number
number
number
number
number
number
Average precipitation for January
Average precipitation for each month to…
Average precipitation for each month to December
Average wind direction for January
Average wind direction for each month …
Average wind direction for December
Average wind speed for January
Average wind speed for each month to …
Average wind speed for December
Average evapotranspiration rate for January
Average evapotranspiration rate for each month to …
Average evapotranspiration rate for December
Codes and Look-up Tables for Associated Datasets
LUT_ValUnit
Code ShortLabel EnLabel
1
2
3
Mm
M
mps
4
5
Km
Kph
6
7
8
Fn
Ha
M3
millimetres
metres
metres per
second
kilometre
kilometres per
hour
fedaan
hectares
cubic metres
9
Oz
ounce
10
Gm -
gram
11
Ton
Tons
12
Br
Barrels
13
14
LE
USD
Egyptian Pound
Dollar
15
16
L
litres
ArLabel
Definition
Millimetres, as used in precipitation
Metres, as used in depths, elevations or lengths
Mps, as used in wind speed
Metric measure of distance. 1000 m.
Speed. Usually applied to permissible speeds on
public roads.
Traditional unit of areal measurement in Egypt
Metric unit of areal measurement
Metric unit of volume often used in volumes of
oil and gas, or other resources, or of production
Unit of weight often used in measuring gold and
other precious metals
Unit of weight often used in measuring precious
metals
(Metric) ton, unit of weight often used in
production or capacity, or resource reserves
A common measure used with volumes of oil
production and consumption
Unit of monetary value for Egypt
Unit of monetary value used internationally,
equal to the United States Dollar
Unit of volume
This Look-up Table can be used with other datasets! Other value units can be entered as
required.
14
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Landscapes
Proposed name: Landscape
Usage:
Landscapes as classified here are generalised over relatively large areas. They are not suitable for
detailed site selection, but can be used in identifying areas which should be investigated in more
detail, or which should be excluded from detailed studies.
The landscape shapefile is one of several layers that is used in describing the natural environment.
It is particularly applied to the process of identifying the suitability of specific areas for
settlement, and for indicating some of the physical conditions and constraints that may apply to
development in specific areas.
A future edition of these guidelines may supplement this layer with one directed specifically at
coastal land forms, for the purpose of classifying sensitivity (to oil and other chemical spills and
land based pollution) and vulnerability (especially to sea level rise).
Feature class:
Landscapes are shown as polygons.
Basic Dataset
Landscape.dbf
Column Heading
Data type
LanSc_ID
LanSc_Type
Alphanumeric 3
Numeric
2
code
Length Definitions
A unique ID for each polygon on the layer
A code to identify the type of landscape. The codes are
described in the LUT_LanSc_Type Look Up Table
Codes and Look-up Tables for Basic Dataset
LUT_LanSc_Type
Code
EnLabel
0
Unknown, uncertain
1
Rocky coasts
2
Eroding soft coast
line
Depositional coast
line
Delta and alluvial
islands
Coastal wetlands
3
4
5
6
Coastal sand dune
belts
7
Broad incised river
valley
8
Narrow V-shaped
valleys
ArLabel
Definition
The landscape is of an unkown type or is difficult to
classify
Coasts consisting of rock, especially headlands and
coastal cliffs
Areas of coast made up of sand, silt, and loose
material, that is subject to marine erosion.
Areas of coast along which sediment is being actively
deposited.
Areas of land formed from silt deposited by rivers.
Lagoons and salt marshes close to coasts. Mangrove
forests are a subset of this class.
Sand dune areas along the coast, with local source of
material. These dune belts are characteristically
different from desert sand dune fields.
Broad river valleys in which the river has cut into the
surrounding areas. Much of the Nile valley is of this
type.
Valleys found in many mountainous areas. Can be
subject to flash floods which because of the valley
shape are particularly hazardous.
15
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Code
EnLabel
ArLabel
9
Sand dune fields
10
Stoney and hard
surface desert
Flat to gently
sloping landscape
11
12
Definition
Desert areas dominated by sand dunes, where there is
active movement of the dunes.
Wide desert areas not subject to sand dune fields
Areas with gentle slopes, often of very old origin,
including ancient river terraces. This category should
not be confused with the broad river flood plains in
incised valleys.
Mountainous areas with steep slopes, heavily eroded.
Rugged and broken
landscapes
Spot Heights
Proposed Name: SpotHght
Usage
This is used to show points with known elevation. It is used with other layers to show
topography. If the density of points is high and regular enough it can be used to generate surfaces
for showing slope and aspect. There are few places in Egypt where this can be done presently.
Feature class:
This is a point feature layer.
Basic Dataset
SpotHght.dbf
Column Heading
Data type
Spot_ID
Spot_Type
Alphanumeric
Numeric Code
Elevation
Number
Length
Definitions
Unique number for each point on the layer
Code for the type of triangulating point.
Codes explained in Spot_Type Look Up
Table
The elevation above mean sea level
Contours
Proposed name: contours
Usage
This layer shows elevations about mean sea level, and so it useful to illustrating topography. It
can also be used to generate slope and aspect maps. For greater effect, contours can be laid on
satellite imagery.
Feature class:
This is a Line feature layer.
Basic Dataset
Contours.dbf
Column Heading
Data type
Length
Definitions
16
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Value
number
6
The elevation expressed in meters above or
below mean sea level.
Important note! Elevation is best presented as a continuous surface. If elevation data is available
in raster format, it can be used directly to generate contours, slope and aspect layers.
Surface Geology
Proposed Name: Geology
Usage
This layer will display the surface geology of the region. Not all parts of Egypt are covered by
geological maps at the scale of 1:100000. Some parts are covered by digital data at 1:250000. It is
advisable to consult knowledgeable staff at the Geological Survey Authority about the limits of using
this digital material at a larger scale. One alternative is to use it for presentation purposes only,
and to advise the reader of its limitations.
If GIS ready digital data is provided by the Geological Survey Authority it is recommended that the
datasets included should be used, rather than the suggestions made here. If GOPP must produce
its own datasets, the following descriptions cover the minimum needs.
Usually the surface geology is used in a general descriptive way in regional planning. Some other
layers can be derived from original maps, including the alignment of fault lines, and generalised
indications of potential groundwater infiltration areas. Certain geological strata and formations
may indicate relative probability of finding useful quarry and building material, and other
minerals.
Feature class:
This is a polygon layer.
Basic Dataset
Geology.dbf
Column Heading
Data type
Length
Definitions
Geo_ID
Geo_type
Geo_age
Alphanumeric
alphanumeric
Numeric code
6
25
25
A unique ID number for each polygon displayed
Description of the type of strata or rock formation
Code for the Name of the period of origin. Codes are
explained in LUT_Geo_age Look Up Table
Codes and Look-up Tables for Basic Dataset
LUT_Geo_age.dbf
Code
1
2
3
4
5
6
7
8
9
10
EnLabel
ArLabel
Definition
Recent
Quarternary
Tertiary
17
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Code
EnLabel
ArLabel
Definition
11
12
13
14
15
16
HYDROLOGY
Drainage
Surface drainage encompasses small ephemeral streams to inland lakes. As a result it must be
shown in two layers, one a line for small watercourses, the other a polygon for wide rivers and
lakes. Both are presented below.
Proposed name: Streams
Usage
This layer shows surface drainage features that are very narrow.
Feature class:
This is a line feature layer.
Basic Dataset
Stream.dbf
Column Heading
Data type
Length
Definitions
Strm_ID
Alphanumeric
6
Dr_type
Numeric code
2
Name
ArName
alphanumeric
alphanumeric
25
25
A unique ID number for each line shown on the
layer.
A code for the type of water course or surface
water feature. The codes are explained in the
LUT_Dr_type Look Up Table.
Name of the stream, if any, in English
Name of the stream, if any, in Arabic
Codes and Look-up Tables for Basic Dataset
LUT_Dr_type.dbf
Code EnLabel
0
2
Unknown, or
unclear
Ephemeral
stream
Perennial river
3
Lake
4
Wetland
5
6
Salt pan
Trunk canal
1
ArLabel
Definition
The nature of the watercourse is unknown or uncertain.
A small water course that does not flow constantly, i.e. it is dry
for at least part of every year.
A watercourse that does not dry up. Suez canal should be
coded as a perennial river.
A larger body of surface water, it can be either fresh or salt
water.
A shallow area of water, often of seasonal variation in depth,
and often associated with hydrophilic plants (marsh grasses,
papyrus, rushes).
An ephemeral lake
A main man made canal taking water from a river or lake for
distribution to settlements or irrigation works.
18
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
7
8
Distributor
canal
Collector drain
9
Main drain
Man made canals transferring water from trunk canals to
irrigated fields.
Man made drainage canal taking water from the fields to the
main drain.
Man made drainage canal that receives water from the collector
canals and carries it to an outlet.
Proposed name: SurfWat
Usage
This layer shows larger surface water features, such as rivers, major distributaries, large canals,
lakes and wetlands. These are shown as polygons because of their size.
Feature class:
This is a polygon feature layer. This basic dataset shares the same look up table (LUT_Dr_type)
as Streams.
Basic Dataset
Stream.dbf
Column Heading
Data type
Length
Definitions
Surf_ID
Alphanumeric
6
Dr_type
Numeric code
2
Name
ArName
Alphanumeric
Alphanumeric
25
25
A unique ID number for each polygon
shown on the layer.
A code for the type of watercourse or
surface water feature. The codes are
explained in the LUT_Dr_type Look Up
Table above.
The name of the water body.
The name of the water body in Arabic
If it is found necessary to provide data on flow measurements, such as volume and current, an
associated table should be created. In such a case, the water body will be divided into many
polygons, each representing the length of the river or canal over which the measurement applies.
In other words the river or canal polygon must be divided at each dam or weir or gauge where
flow measurements are made. The attributes can then be illustrated using fill patterns or colours
for different categories of measurements.
Proposed name Dams
Usage
This layer shows all the dams, barrages, weirs and other man-made obstructions made in
watercourses. It is used with other layers related to hydrology and drainage.
Feature class:
This is a line feature layer.
19
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Basic Dataset
Dams.dbf
Column Heading
Data type
Dam_ID
Dam_type
alphanumeric 6
Numeric
2
code
Length Definitions
Name
ArName
Alphanumeric 25
Alphanumeric 25
A unique ID for each line shown on this layer.
A code for each type of obstruction. The
explanations for the codes are given in
LUT_Dam_type Look Up Table.
Name of the dam, if any, in english
Name of the dam, if any, in Arabic
Codes and Look-up Tables for Basic Dataset
LUT_Dam_type.dbf
Code EnLabel
0
1
Unknown or
unclear
Dam
2
Barrage
3
Weir
4
Locks
ArLabel
Definition
Type unknown or unclear
A man-made structure designed to hold back water for
purposes of controlling seasonal variations in water flow and
minimise flooding, and / or to generate power
A man-made structure designed to control flow in a
watercourse, and often to prevent a tidal flow upstream
A usually submerge wall in a watercourse designed to maintain
a water level high enough to extract or divert water
A special construction to allow boats to pass up or down
stream past rapids or falls or dams.
If additional information is needed and available on water flow, they can be stored in an
associated dataset, linked both to dams.dbf and to SurfWat.dbf.
20
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Proposed Name: Aquifers
Usage
The purpose of this layer is to show where there are useable subterranean water resources. It
does not seek to identify individual aquifers in areas where they might lie above one another but
separated by impermeable layers. Nor is it intended that saline or other unsuitable aquifers should
be shown.
Water at acceptable cost is essential for local development. Information about sub-surface water
can be an important factor in assessing development potential for both the short and long term.
Feature class:
Polygon, showing the surface extent of key underground aquifers.
Basic Dataset
Aquifer.dbf
Column Heading
Data type
Length
Definitions
Aq_ID
Alphanumeric
8
A unique ID for the polygon showing an
aquifer, which will provide a link to the
associated dataset that describes the aquifer.
Associated Datasets
Groundwater.dbf
Column Heading Data type
Length Definitions
Aq_ID
Alphanumeric
8
Aq_Name
ArAq_Name
Up_depth
Alphanumeric
Alphanumeric
Number
25
25
5
Lo_depth
Number
5
Volume
Number
9
ExistVol
Number
9
Extract
Number
9
Recharg
Number
9
Sus_Cap
Number
9
A unique ID for the polygon showing an aquifer, which
will provide a link to the associated dataset that describes
the aquifer.
Name of the Aquifer if any, in English
Name of the aquifer, if any, in Arabic
Depth to upper surface of the aquifer, measured in
metres
Depth to lowest surface of the aquifer, measured in
metres.
Estimated volume, or capacity of the aquifer as a
geological formation. Measured in cubic metres.
Amount of water confirmed in the aquifer, measured in
cubic metres.
The volume of water currently extracted from the
aquifer. Measured in cubic metres.
The recharge rate, i.e. the amount of water that flows
into the aquifer to replace that taken out, measured for a
period of time. Measured in cubic metres.
Amount of water that can be extracted without
jeopardising the long term viability of the aquifer.
Measured in cubic metres.
21
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Proposed Name: Infilter
Usage
This layer is connected very closely to geology, since geological structures and rock strata affects
infiltration rates. It is also related to agriculture as a major land use. Communities that depend on
ground water need the assurance that the infiltration areas recharging their aquifers are not going
to pollute them. Specialists in the appropriate authorities usually carry out special studies. In
regional planning infiltration areas should be protected from urban development or other uses
that may pollute ground water.
Feature class:
This is a polygon feature layer.
Basic Dataset
Infiltration.dbf
Column Heading
Data type
Inf_ID
Rate
alphanumeric
number
Length Definitions
A unique ID for each polygon shown on the layer
The rate at which water can enter (infiltrate) the surface of
the land
Proposed Name: basins
Usage
River basins, or rainwater catchment areas, or watersheds, are useful units for calculating total
potential runoff through specific points in a drainage system. The actual runoff is affected by
many factors including vegetation coverage, surface type and slopes, geology, soil characteristics
and infiltration rates, and even climatic and weather factors such as rainfall intensity and storm
duration.
River basins can often be nested within one another and flow gauges in water courses are
frequently located where they can provide the most useful measurements, often at the lowest
point of a definable river basin.
Hydrologists should select the appropriate level of river basin within the nested hierarchy to serve
the purposes sought in the regional plan.
Feature class:
This is a polygon feature class.
Basic Dataset
Basins.bdf
Column Heading Data type
Length Definitions
Basin_ID
alphanumeric 15
A unique ID for each polygon in the layer.
Name
alphanumeric 25
The name of the main watercourse defining the
basin
ArName
Arabic
alphanumeric
25
Name of settlement in Arabic
Note: Basin_Ids should be designed for nested features, so that different levels of basins can be
selected as needed. This will be considered in more detail in the pilot test exercise.
22
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
ECOSYSTEMS AND HABITATS
Special Habitats
Proposed Name: Habitat
Usage
This layer presents special ecological habitats and sensitive environments. It is not the same as
protected areas, as there are many such habitats that are not under special protection.
The layer is used together with other layers to show areas where development should be
forbidden or permitted only under strict control measures. Some sensitive habitats are of high
tourism value (e.g., coral reefs), others are crucial to the continued survival of economical
valuable communities of plants and animals (e.g. fish hatching and nursery areas). They therefore
provide attractive investment focus, while needing close control of exploitation.
Feature class:
This layer is a polygon feature. Even habitats normally presented as linear should be entered as
narrow polygons.
Basic Dataset
Habitat.dbf
Column Heading
Data type
Length Definitions
Hab_ID
Hab_type
alphanumeric 6
Numeric code 2
A unique ID for each polygon in the layer
Code for type of habitat. Codes are explained in the
LUT_Hab_type Look Up Table
Codes and Look-up Tables for Basic Dataset
LUT_Hab_type.dbf
Code
EnLabel
0
Unknown, unclear
1
2
3
Coral reef
Marine mud banks
Fish spawning
areas
Marine coastal
wetlands
Turtle nesting sites
Rare bird nesting
areas
Sensitive riverine
habitats
Sensitive lacustrine
habitats
Sensitive mountain
habitats
4
5
6
7
8
9
ArLabel
Definition
Known to be a sensitive area, but details unclear or
unknown so classification is withheld.
Coral reefs of all types
Sensitive Mud banks on marine coasts
Areas important for fish reproduction
Coastal wetlands along sea coasts, including
mangroves and salt marshes, lagoons.
Beaches where turtles breed and hatch
Areas where endangered birds nest.
Important and sensitive habitats along river banks.
Include sensitive areas of importance along wadis
Important and sensitive habitats in or around lakes.
Areas of ecological importance in mountainous
areas.
23
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Associated Datasets
Ecosystems.dbf
Column Heading
Data type
Hab_ID
Status
Alphanumeric 6
Numeric code 1
Length Definitions
Descrip
Alphanumeric 256
Species
Alphanumeric 256
Risk
Alphanumeric 256
A unique ID for each polygon in the layer
Code indicating the protection status given. See
LUT_Status Look Up Table for explanations
A brief description of the habitat and its rare species,
justifying its value.
A list of important flora and fauna species inhabiting
the ecosystem.
A description of the nature of the threat or risk to the
area or the species dependent on it.
Codes and Look-up Tables for Associated Dataset
LUT_Status.dbf
Code
EnLabel
0
Unknown
1
2
No protection
Species listed
only
3
4
Under
investigation
In process
5
Proclaimed
6
Protection in
place
ArLabel
Definition
It is not known whether or not any protection is extended to
the areaIt is known that no protection is provided.
Species depending on this habitat are protected in law, but
the habitat itself is not. The species is therefore still at high
risk.
Protective measures are being investigation
Investigations are complete, legal measures for protection
are in process.
The area is protected by law, but no physical protection in
place
Protective measures are in place and enforced.
(Nature) Conservation Areas
Proposed Name: conserve
Usage
This layer shows areas that have been declared as protected areas for their natural or
environmental value (not cultural or historical). It is related to habitats layer. Together with other
layers denoting restricted areas, it shows areas in which development is forbidden or permitted
only under strict conditions. Conservation areas may constitute features of interest to tourism,
but in Egypt’s generally sensitive environment, even tourism must be controlled.
Feature class:
This is a polygon feature layer.
24
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Basic Dataset
Conserve.bdf
Column Heading
Data type
Cons_ID
Cons_type
Alphanumeric 6
Numeric code 2
Length
Definitions
A unique ID for each polygon shown on the layer
A code denoting the type of protection provided. The
codes are explained in LUT_Cons_type Look Up
Table.
Codes and Look-up Tables for Basic Dataset
LUT_Cons_type.dbf
Code
EnLabel
ArLabel
0
1
Unknown
Nature Reserve
2
National Park
3
World heritage
site
Definition
The legal status is not known or is unclear
Protected, with limited use of resources under strict
control
All development except research and control tourism
forbidden
A site designated by UNESCO for its natural value (note:
not its archaeological, historical or cultural value)
Note: the various types of conservation administrative practiced in Egypt needs more research to
complete this list.
Associated Datasets
Parks.dbf
Column Heading
Data type
Length
Definitions
Cons_ID
Name
ArName
Alphanumeric
alphanumeric
Arabic
alphanumeric
alphanumeric
6
35
25
A unique ID for each polygon shown on the layer
Name of the conservation area
Name of conservation area in Arabic
256
Brief description of the reason for protection, i.e.
species, landscapes, etc justifying its conservation
Desc
DEMOGRAPHIC CHARACTERISTICS AND TRENDS
Demographic characteristics will be presented both in tabular and graphic form. In the maps,
they will be shown as distributions across the region or sub-region. To do this the data is linked
to settlements and / or administrative units.
Therefore the settlements layers become an important base for displaying many different socioeconomic statistics.
Demographic information is collected through surveys of various kinds, including the periodic
census. Trends are based on comparing similar features over a period of time. This means that
there is regular repetition of attribute type (fields). From a database point of view it is better to
add records of the units (governorate, markhaz, et) downwards, even though they must be
repeated, than to repeat fields each census and thereby change the structure of the database.
25
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Set_ID
Name
Date
Pop
3400001 chds
1996
1234567
3400002 sdfgaeg
1996
3435679
3400001 chds
2006
2345678
…
Repeat admin units
with new dates
Repeat attribute
fields every census
Proposed names
The polygon feature layer should be named: SetPoly
The point feature layer should be named: SetPoint
Usage
A great deal of information and analysis in the Regional Plan focuses on settlements. The
settlement layer(s) will be linked to several different datasets including:
● Population / demography
● Economic characteristics
● Labour force
● Services: education, health, and so on.
Feature classes:
There are two layers for settlements, a polygon layer and a point layer. Many maps provided by
the Egyptian Survey Authority (ESA) or the National Authority for Remote Sensing and Space
Science (NARSS) include settlements as polygons. This has the advantage that the GIS can
calculate and record the size of the built up area automatically.
The point layer can be generated from the polygon layer. This process permits the transfer of
specified fields in the polygon’s basic dataset (*.dbf) to the point shapefile’s .dbf. In this case, we
are most interested in transferring the Set_ID and the Name fields. In Arcview execute the
following Script with the settlement polygon layer being active:
' Get the View
v = av.getactivedoc
if (v.is(view).not) then
Exit
End
' Get the Active Themes
ths = v.getactivethemes
If (ths.count = 0) then
Exit
End
' Get the first Active theme
t = ths.Get(0)
If (t.is(FTheme).Not) Then
av.ShowMsg("Active layer was not feature type ")
Exit
End
26
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
' Get the theme's FTab
tb = t.GetFtab
If (tb.GetShapeClass.GetClassName <> "polygon") then
av.ShowMsg("Active layer was not polygon type")
Exit
End
_theProjection = v.GetProjection
isProjected = _theProjection.IsNull.Not
'true if projected
' Create the output file
fln =
FileDialog.Put(FileName.GetTmpDIR.MakeTMP("point","shp"),"*.shp",
"Create the output Shapefile:")
If (fln = Nil) Then
Exit
End
ntb = FTab.MakeNew(fln,Point)
' Get the fields from the input Ftab
fls = tb.GetFields.deepclone
fls.Remove(0)
' Add the Fields to the new Ftab (minus the shapefield)
ntb.SetEditable(true)
ntb.AddFields(fls)
' Get the new fields list (minus the shapefield)
nfls = ntb.getfields.deepclone
nfls.remove(0)
nmes = {}
for each f in nfls
nmes.add(f.getname)
end
' Loop through each Polygon record and populate the new shapefile
For each r in tb
' Get the Polygon
shp = tb.ReturnValue(tb.findFIeld("Shape"),r)
' Create the center point from the polygon
'if (isProjected) then
' myPoint = shp.ReturnCenter.ReturnProjected(_theProjection)
'else
myPoint = shp.ReturnCenter
'end
' Make a new record in the new shapefile
newR = ntb.AddRecord
' Set the shape
ntb.SetValue(ntb.FindField("Shape"),newR,myPoint)
' Loop through the fields
For each nme in nmes
' Get the value from the polygon Ftab
val = tb.Returnvalue(tb.findfield(nme),r)
27
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
' Set the value into the polyline ftab
ntb.setvalue(ntb.findfield(nme),r,val)
End ' - of fields loop ' Update the progress bar...
av.SetStatus((r/tb.getnumrecords) * 100)
av.ShowMsg("Converting Polygons To Center Points ...")
End ' - of polygon records loop ' Stop Editing
av.setStatus(100)
av.clearStatus
av.clearmsg
ntb.SetEditable(False)
' Create the New FTheme
ft = Ftheme.Make(ntb)
ft.Setvisible(true)
' Add the new FTheme to the view
v.Addtheme(ft)
' Redraw the view
v.invalidate
' Report the conversion
av.ShowMsg("Converted '" +
tb.getnumrecords.setformat("d").asString + "' polygons into
center points")
system.Beep
In ArcGIS the Script is as follows:
Attribute VB_Name = "GetPolyInfo"
Option Explicit
Private m_pEditor As IEditor
Private m_pEditLayers As IEditLayers
Public Sub Transfer_Data()
'**** Change the parameters below to match your data
GetPolyInfo_ForSelectedFeatures "Parcels", "RENUM", "wMeter",
"RENUM"
'****
End Sub
Public Sub GetPolyInfo_ForSelectedFeatures(sPolyLayer As String,
sFieldinPoly As String, PointLayer As String, sFieldInPoint As
String)
'This routine is run manually when needed to reset the values for
selected features
Dim pPoint As IPoint
Dim intNextId As Integer
Dim sPolygonValue As String
28
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Dim
Dim
Dim
Dim
Dim
Dim
Dim
Dim
Dim
iPointID As Integer
iPointGRID As Integer
pMap As IMap
pMxDoc As IMxDocument
pFLayer As IFeatureLayer
pFSel As IFeatureSelection
pFeature As IFeature
pPointCursor As IFeatureCursor
iPointField As Integer
'Get edit env
Dim pUID As New UID
pUID = "esriCore.Editor"
Set m_pEditor = Application.FindExtensionByCLSID(pUID)
If m_pEditor Is Nothing Then Exit Sub
If m_pEditor.EditState <> esriStateEditing Then
MsgBox "Please start editing"
Exit Sub
End If
m_pEditor.StartOperation
Set m_pEditLayers = m_pEditor
Set pMxDoc = Application.Document
Set pMap = pMxDoc.FocusMap
'Get the Feature layer
Set pFLayer = m_pEditLayers.CurrentLayer
If pFLayer Is Nothing Then
MsgBox "Could not find " & m_pEditLayers.CurrentLayer.Name &
" layer"
Exit Sub
End If
Set pFSel = pFLayer
If pFSel.SelectionSet.Count < 1 Then
MsgBox "Please select at least one feature from " &
m_pEditLayers.CurrentLayer.Name
Exit Sub
End If
pFSel.SelectionSet.Search Nothing, False, pPointCursor
Set pFeature = pPointCursor.NextFeature
'Verify that this is point feature
If pFeature Is Nothing Or Not TypeOf pFeature.Shape Is IPoint
Then
MsgBox "This routine requires a point feature."
Exit Sub
End If
'Find field to calculate in the point layer
iPointField = pFeature.Fields.FindField(sFieldInPoint)
If iPointField < 0 Then
MsgBox sFieldInPoint & " field in point layer not found.",
"Exiting GetPolyInfo..."
Exit Sub
End If
Do Until pFeature Is Nothing
29
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Set pPoint = pFeature.Shape
'Get the value of the intersecting polygon
sPolygonValue = FindPolygonValueAtPoint(pPoint, sPolyLayer,
sFieldinPoly)
'Store value in point
pFeature.Value(iPointField) = sPolygonValue
pFeature.Store
Set pFeature = pPointCursor.NextFeature
Loop
m_pEditor.StopOperation ("GetPolyInfo_ForSelectedFeatures")
End Sub
Public Sub GetPolyInfo_WhileEditing(pEditor As IEditor, pFeature
As IFeature, sFieldInPoint As String, sPolyLayer As String,
sFieldinPoly As String)
Dim
Dim
Dim
Dim
Dim
Dim
pPoint As IPoint
intNextId As Integer
sPolygonValue As String
intPointLayerIdFieldPos As Integer
intPointLayerPolygonFieldPos As Integer
pEditLayers As IEditLayers
Set m_pEditor = pEditor
Set m_pEditLayers = pEditor
'Verify that a point feature was passed to this routine
If pFeature Is Nothing Or Not TypeOf pFeature.Shape Is IPoint
Then
MsgBox "This routine requires a point feature."
Exit Sub
End If
Set pPoint = pFeature.Shape
'Find fields to calculate in the point layer
intPointLayerPolygonFieldPos =
pFeature.Fields.FindField(sFieldInPoint)
'Verify that the ID field exists in the Point Layer
If intPointLayerPolygonFieldPos < 0 Then
MsgBox sFieldInPoint & " field in point layer not found.",
"Exiting GetPolyInfo ..."
Exit Sub
End If
'Get the value of the intersecting polygon
sPolygonValue = FindPolygonValueAtPoint(pPoint, sPolyLayer,
sFieldinPoly)
'Store Value in Point
pFeature.Value(intPointLayerPolygonFieldPos) = sPolygonValue
End Sub
Public Function FindPolygonValueAtPoint(pPoint As IPoint,
sPolygonLayerName As String, sPolygonFieldName As String) As
String
Dim pFLayer As IFeatureLayer
30
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Dim intFieldPos As Integer
Dim pSFilter As ISpatialFilter
Dim pFCursor As IFeatureCursor
Dim pFeature As IFeature
Dim svalue As String
'Get the feature layer
Set pFLayer = UTIL_FindFeatureLayer(sPolygonLayerName)
If pFLayer Is Nothing Then
MsgBox "Could not find " & sPolygonLayerName & " feature
layer."
Exit Function
End If
If pFLayer.FeatureClass.ShapeType <> esriGeometryPolygon Then
MsgBox sPolygonLayerName & " layer does not contain
polygons."
Exit Function
End If
intFieldPos =
pFLayer.FeatureClass.Fields.FindField(UCase(sPolygonFieldName))
If intFieldPos < 0 Then
MsgBox sPolygonFieldName & " field not found in layer " &
sPolygonLayerName
Exit Function
End If
Set pSFilter = New SpatialFilter
Set pSFilter.Geometry = pPoint
pSFilter.GeometryField = "Shape"
pSFilter.SpatialRel = esriSpatialRelIntersects
Set pFCursor = pFLayer.FeatureClass.Search(pSFilter, False)
Set pFeature = pFCursor.NextFeature
If Not pFeature Is Nothing Then
svalue = pFeature.Value(intFieldPos)
Else
svalue = "NoValue"
End If
FindPolygonValueAtPoint = svalue
End Function
Public Function UTIL_FindFeatureLayer(DatasetName As String) As
IFeatureLayer
Dim
Dim
Dim
Dim
Dim
Dim
Dim
pMxDoc As IMxDocument
pMap As IMap
pFeatureLayer As IFeatureLayer
pCompositeLayer As ICompositeLayer
pDataset As IDataset
i As Integer
j As Integer
Set pMxDoc = Application.Document
Set pMap = pMxDoc.FocusMap
With pMap
For i = 0 To .LayerCount - 1
'Group layer check
If TypeOf .Layer(i) Is ICompositeLayer Then
Set pCompositeLayer = .Layer(i)
31
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
For j = 0 To pCompositeLayer.Count - 1
If TypeOf pCompositeLayer.Layer(j) Is IFeatureLayer Then
Set pFeatureLayer = pCompositeLayer.Layer(j)
Set pDataset = pFeatureLayer.FeatureClass
If UCase(pDataset.Name) = UCase(DatasetName) Then
Set UTIL_FindFeatureLayer = pFeatureLayer
Exit For
End If
End If
Next j
ElseIf TypeOf .Layer(i) Is IFeatureLayer Then
Set pFeatureLayer = .Layer(i)
Set pDataset = pFeatureLayer.FeatureClass
If UCase(pDataset.Name) = UCase(DatasetName) Then
Set UTIL_FindFeatureLayer = pFeatureLayer
Exit For
End If
End If
Next i
End With
End Function
Most of the data from the associated datasets will be presented as proportional dots (population
distribution) or as proportionally sized pie charts (employment by sector). These are best shown
using the point layer. The base map, however, especially at the sub-regional scale, will want to
show the polygon of the capital city.
Basic Dataset
SetPoly.dbf AND SetPoint.dbf
Column Heading
Data type
Length
Definitions
Set_ID
Alphanumeric
16
Name
ArName
Alphanumeric
Arabic
alphanumeric
25
25
Unique number for each built up area. This will provide
the link to several other socio-economic datasets.
Name of built-up area.
Name of settlement in Arabic
Set_Type
Number
2,0
GovCap
True/False
(Boolean)
The category or basic type of settlement. A code number
is inserted here. Refer to the Lookup table to see the
codes for settlement types.
For any Governorate capital city enter “True,” all others
will be “False.” For the base map select for
“GovCap=True’.
The Set_ID is a unique number for every settlement in Egypt. It is built up on a series of digits or
letters, whose position and nature indicate the markhaz, Governorate and region within which it
lies.
Codes and Look-up Tables for Basic Dataset
LUT_Set_Type
Code
0
EnLabel
Unknown or
unclear or in
transition
ArLabel
Definition
Settlements whose main functions are unknown,
unclear, hard to determine, or clearly in transition.
32
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Code
1
2
3
4
5
EnLabel
6
7
Port and transport
8
Mining Settlement
9
Industrial Town
10
Administrative
Centre
Trade and services
12
Definition
Agricultural satellite
village
Agricultural village
Oasis Community
Bedouin settlement
Residential
Community
Tourist Centre
11
ArLabel
The smallest size hamlet or community in agricultural
areas
Village primarily based on agriculture
Oases – distinguished from other agricultural
communities because of the special type of agriculture,
and their additional related, but non-agricultural
functions.
Community of typically Bedouin origin and character
A community that primarily serves as a residential area
for another, usually larger centre.
A settlement in which the primary economic activity is
focused on the tourist and recreational sectors.
A settlement that derives its livelihood primarily from
port or shipping functions or from its
transport/transhipment roles.
A settlement whose basic function is exploitation of
mineral, oil, gas, or quarry resources.
A settlement in which industry is the primary driving
sector
A settlement in which administration is the most
important function.
A settlement whose primary economic base is in
wholesale, retail, and service provision, whether these
are private or public.
A settlement in which no one function dominates, but
many are present.
Multi-functional
City
Associated Datasets
Pop.dbf
Column
Heading
Data type
Length
Definitions
Set_ID
Alphanumeric
16
Name
ArName
Year
TotPop
TotMales
TotFem
Mal0_5
Fem0_5
Mal6-10
Fem6_10
Mal11-15
Fem11_15
Mal16_20
Fem16_20
Mal21_25
Fem21_25
Mal26-30
Alphanumeric
Arabic alphanumeric
Number
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
25
25
4
9
8
8
8
8
8
8
8
8
8
8
8
8
8
Unique number for each built up area. This will
provide the link to several other socio-economic
datasets.
Name of settlement
Name of settlement in Arabic
Year of Census
Total population of this settlement in the Census
Total males,
Total Females
Number of males and females for each 5-year
cohort for the settlement.
33
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Column
Heading
Data type
Length
Fem26_30
Mal31_35
Fem31_35
Male36_40
Fem36_40
Mal41_45
Fem41_45
Mal46_50
Fem46_50
Mal51_55
Fem51_55
Mal56_60
Fem56_60
Mal61_65
Fem61_65
Mal66_70
Fem66_70
MalOver70
FemOver70
AveBirth
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, no decimals
Number, percent, 2
decimals
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
6
AveDeath
Number, percent, 2
decimals
7
AveLifeMale
Number, 1 decimal
5
AveLifeFem
Number, 1 decimal
5
AveNatGrowth Number, percent, 1
decimal
NetMigr
Number, percent, 1
decimals
AveHhSize
Number, 2 decimals
5
5
5
Definitions
Average birth rate per thousand population for this
settlement – either as calculated for the latest interCensus period and presented in the Census report,
or as more recently calculated by CAPMAS.
Average death rate per thousand for this settlement
– either as calculated for the latest inter-Census
period and presented in the Census report, or as
more recently calculated by CAPMAS.
Average male life expectancy at birth, number of
years.
Average female life expectancy at birth, number of
years
Average annual growth rate for the latest interCensus period
Ave Net migration rate for the latest inter-Census
period
Average household size
SOCIO-ECONOMIC FEATURES AND TRENDS
EMPLOYMENT AND LABOUR FORCE
Socio-economic information is collected through surveys of various kinds, including periodic
census. Trends are based on comparing similar features over a period of time. This means that
there is regular repetition of attribute type (fields). From a database point of view it is better to
add records of the units (governorate, markhaz, et) downwards, even though they must be
repeated, than to repeat fields each census and thereby change the structure of the database.
34
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Set_ID
Name
Date
Pop
…
3400001 chds
1996
1234567
3400002 sdfgaeg
1996
3435679
3400001 chds
2006
2345678
Repeat attribute
fields every census
Repeat admin units
with new dates
Proposed name: SectEmp
Usage
This dataset is used for showing the distribution of employees by economic sector and location.
Sectors can be displayed individually, or pie charts can be generated showing all sectors for all
settlements or selected settlements. This is done by linking the dataset to settlement.shp.
Calculated fields can be generated, but they should be created after the link is established.
Feature class
The dataset does not have its own shape file. Rather it is linked to either SetPoly or SetPoint,
depending on whether a point or polygon settlement background is wanted.
The dataset can also be linked to different levels of administrative units (AdmUnits.shp) by
selecting for the appropriate Set_ID codes.
Dataset
SectEmp.dbf
Column Heading
Data type
Length
Definitions
Set_ID
Name
ArName
Alphanumeric
Alphanumeric
Arabic
alphanumeric
Number
Number
Number
Number
Number
Number
Number
Number
Number
Number
Number
Number
Number
Number
Number
Number
16
25
25
The unique settlement identifier
The name of the settlement
Name of settlement in Arabic
4
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
The date when the data was collected
Total employment in the year specified
Male working in agriculture, hunting and fishing
Females working in agriculture, hunting & fishing
Total working in agriculture, hunting and fishing
Males working in mining and quarrying
Females working in mining and quarrying
Total working in mining and quarrying
Males working in manufacturing
Females working in manufacturing
Total working in manufacturing
Males working in electricity, gas and water
Females working in electricity, gas and water
Total working in electricity, gas and water
Males working in Construction
Females working in construction
Date
TotalEmp
AgHuntMal
AgHuntFem
AgHuntTot
MinMal
MinFem
MinTot
ManMal
ManFem
ManTot
EGWMal
EGWFem
EGWTot
ConMal
ConFem
35
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Column Heading
Data type
Length
Definitions
Set_ID
ConTot
RestMal
RestFem
RestTot
TransMal
Alphanumeric
Number
Number
Number
Number
Number
16
8
8
8
8
8
TransFem
Number
8
TransTot
Number
8
FinMal
Number
8
FinFem
Number
8
FinTot
Number
8
SocMal
Number
8
SocFem
Number
8
SocTot
Number
8
TradeMal
Number
8
TradeFem
Number
8
TradeTot
DefMal
DefFem
Number
Number
Number
8
8
8
DefTot
EdMal
EdFem
EdTot
HealthMal
HealthFem
HealthTot
OtherMal
OtherFem
Number
Number
Number
Number
Number
Number
Number
Number
Number
8
8
8
8
8
8
8
8
8
OtherTot
Number
8
The unique settlement identifier
Total working in construction
Males working in restaurants and hotels
Females working in restaurants and hotels
Total working in restaurants and hotels
Males working in transportation, storage &
communications
Females working in transportation, storage &
communications
Total working in transportation, storage &
communications
Males working in financing, real estate and business
services
Females working in financing, real estate and
business services
Total working in financing, real estate and business
services
Males working in community, social and personal
services
Females working in community, social and personal
services
Total working in community, social and personal
services
Males working in wholesale, retail trade and
repairing
Females working in wholesale, retail trade and
repairing
Total working in wholesale, retail trade and repairing
Males working in general administration for defence
Females working in general administration for
defence
Total working in general administration for defence
Males working in education
Females working in education
Total working in education
Males working in health and social work
Females working in health and social work
Total working in health and social work
Males working in activities not adequately described
Females working in activities not adequately
described
Total working in activities not adequately described
Proposed name: OccupEmp
Usage
This dataset is used for showing the distribution of employees by occupation and location.
Occupations can be displayed individually, or pie charts can be generated showing all occupations
for all settlements or selected settlements. This is done by linking the dataset to settlement.shp.
Calculated fields can be generated, but they should be created after the link is established.
36
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Feature class
The dataset does not have its own shape file. Rather it is linked to either SetPoly or SetPoint,
depending on whether a point or polygon settlement background is wanted.
The dataset can also be linked to different levels of administrative units (AdmUnits.shp) by
selecting for the appropriate Set_ID codes.
Dataset
OccupEmp
Column Heading
Data type
Set_ID
Year
Total
Alphanumeric 16
number
16
number
8 ,0
Length Definition
Unique ID number for settlement
The year the data was collected
Total males and females in economic activity
TotMal
TotFem
LegTotMale
number
number
number
8 ,0
8 ,0
8 ,0
LegTotFem
number
8 ,0
LegTotal
ProfTotMale
ProfTotFem
ProfTotal
TechTotMale
TechTotFem
TechTotal
ClkTotMale
ClkTotFem
ClkTotal
SalesTotMale
SalesTotFem
SalesTotal
FFHTotMale
FFHTotFem
FFHTotal
CraftTotMale
CraftTotFem
CraftTotal
ProdTotMale
ProdTotFem
ProdTotal
UnskTotMale
UnskTotFem
UnsTotal
OthTotMale
OthTotFem
OthTotal
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
8 ,0
Total males in economic activity
Total females in economic activity
Total males in Legislature, administrative & managerial
work
Total females in Legislature, administrative & managerial
work
Total in Legislature, administrative & managerial work
Total males in professional work
Total females in professional work
Total in professional work
Total male technicians and assistants
Total female technicians and assistants
Total technicians and assistants
Total male clerks and related workers
Total female clerks and related workers
Total clerks and related workers
Total male sales and service workers
Total female sales and service workers
Total sales and service workers
Total male farmers, fishers and hunters
Total female farmers, fishers and hunters
Total farmers, fishers and hunters
Total male craftsmen and related workers
Total female craftsmen and related workers
Total craftsmen and related workers
Total male production and related workers
Total female production and related workers
Total production and related workers
Total male unskilled workers
Total female unskilled workers
Total unskilled workers
Total male workers not reporting any occupation
Total female workers not reporting any occupation
Total workers not reporting any occupation
37
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Proposed name: EconEnt
Usage
This dataset is used for showing the distribution of economic enterprises by sector and location.
Number of enterprises per sector can be displayed individually, or pie charts can be generated
showing all sectors for all settlements or selected settlements. This is done by linking the dataset
to settlement.shp.
Calculated fields can be generated, but they should be created after the link is established.
Feature class
The dataset does not have its own shape file. Rather it is linked to either SetPoly or SetPoint,
depending on whether a point or polygon settlement background is wanted.
The dataset can also be linked to different levels of administrative units (AdmUnits.shp) by
selecting for the appropriate Set_ID codes.
Dataset
EconEnt
Column Heading
Data type
Length Definition
Set_ID
Farms
Mining
ManNum
ManQuant
HotelsRest
Sales
Financial
ProfServ
Alphanumeric
number
number
number
number
number
number
number
number
6
6
6
6
6
6
6
6
6
TranServ
number
6
Unique ID for each settlement and administrative unit.
Number of mines
Number of manufacturing enterprises
Number of tons of produce
Number of hotels and restaurant
Number of wholesale, retail enterprises
Number of banks and other financial enterprises
Number of professional service enterprises (private
lawyers, private doctors, dentists, real estate agents,
engineers, architects, etc)
Number of transport-related enterprises: carriers, bus,
taxi, shipping, and transport repair services.
Main Land Use and Land Cover
Proposed name: landuse
Usage
This layer shows the main land uses at regional level. At subregional level, it is possible to
combine this layer with the settlement polygon layer linked to type. This will provide a little more
detail regarding the major economic activities that may affect land use within settlements.
Feature class:
This is a polygon feature layer.
Basic Dataset
Landuse.dbf
Column Heading
Data type
Length
Definitions
Lnd_ID
alphanumeric
6
Unique ID for each polygon shown on the layer
38
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
LndUse
Numeric code
3
Codes for major land use types, as explained in
LUT_LandUse Look Up Table
Codes and Look-up Tables for Basic Dataset
LUT_LandUse
Code EnLabel
ArLabel
0
1
2
3
Unknown, unclear
Agriculture
Forest
Desert / wilderness
4
Protected – natural
environment
5
Protected – antiquities
6
Restricted – security
7
8
9
Built-up areas
Transportation
Rivers, lakes, marine
Definition
The land use or land cover is unknown or unclear.
All forms of arable agriculture
Woodlands, mangrove forests, etc
All types of desert land, and wilderness areas, including
unutilised but unprotected mountain areas.
Conservation areas, national parks, etc., and areas that
should be protected because of their ecological
sensitivity
Areas that need to be protected for their archaeological
value
Areas that are subject to restricted access for security
areas, e.g. old mine fields
Settlements
Road and rail reserves, sea lanes, port and airport areas
Areas covered by water, fully or partially, permanently or
seasonally.
Mining and Quarrying Licences
Proposed name: mines
Usage
This layer belongs to the category of economic activities. It shows areas that are subject to
mineral, oil, gas and quarrying exploration and exploitation. Thus it shows where extraction
industries are presently working, and where there are potentials for future extraction resulting
from successful exploration.
Feature class:
This is a Polygon feature layer
Basic Dataset
Mines.dbf
Column Heading
Data type
Length
Definitions
Min_ID
Name
ArName
alphanumeric
alphanumeric
Arabic
alphanumeric
12
25
25
A unique ID for each polygon object shown on the layer
The name of the object – license holder, or area.
Name of object in Arabic
Associated Datasets
Mining,dbf
Column Heading
Data type
Length
Definitions
Min_ID
Name
ArName
alphanumeric
alphanumeric
Arabic
alphanumeric
12
25
25
A unique ID for each polygon object shown on the layer
The name of the object – license holder, or area.
Name of object in Arabic
39
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Column Heading
Data type
Length
Definitions
Lic_Type
Numeric code
2
Resource
Alphanumeric
25
Lic_start
Lic_end
Prod_vol
Date
Date
number
10
Reserve
number
12
ValUnit
Numerical
code
2
The type of licence granted, codes explained in the
LUT_Lic_Type Look Up Table
Name of the resource. Name one resource only, then
add a new row, with the same Min_ID for each
additional mineral. This allows for the possibility for
giving specific data on reserves and production for each
resource.
Date of the start of the period of licence
Date of the end of the period of licence
Average annual volume of production from mine or
production unit.
Estimated volume of the resource reserve, in the same
units as Prod_vol
The unit in which the production volume and reserves
are measured (cubic metres, barrels, ounces, tons, etc)
See LUT_Val_Unit Look-up Table for explanation of
specific codes.
LUT_ValUnit Look Up Table was created under Climate, above.
Codes and Look-up Tables for Associated Dataset
LUT_Lic_Type
Code EnLabel
0
1
2
3
4
ArLabel
Unknown, unclear
Exploration
Extraction
Exploration and
Extraction
Remediation,
rehabilitation
Definition
The nature of the licence is unknown, unclear, or unreported.
Licence to explore for physical resource
Licence to extract physical resource
Licence to both extract and continue to explore for extractable
resources.
Areas subject to active rehabilitation and remediation after the
closure of mining activities.
INFRASTRUCTURE
Roads
Proposed Name: roads
Usage:
This layer shows all roads. It can be combined usefully with many other layers. In the Base Map
only major roads are selected for orientation purposes. It is also combined with other transport
infrastructure to give a picture of connectiveness within the region.
Feature class:
This is a line feature layer
Basic Dataset
Roads.bdf
Column Heading
Data type
ID_rd
number
Length
Definitions
Unique number for every section of the road
40
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Rd_Type
Numeric code
Code for the type of road. Codes are explained in
LUT_Rd_type Look Up Table.
Codes and Look-up Tables for Basic Dataset
LUT_Rd_Type
Code EnLabel
0
1
2
3
4
Unknown
Freeway
Main
Regional
Sub-Regional
Ring Road
5
Main Urban
6
7
Arterial
Collector
8
Local
9
Graded track
10
Ungraded
track
ArLabel
Definition
The type of road is unknown
Limited access, usually inter-urban.
Inter-urban, limited access, but more than freeway. Sometimes toll
road.
Links freeways or main regional roads with urban road network
Usually urban by-pass roads (may encircle an urban centre), linking
higher level roads with urban road network
Transfer high traffic movement between major points within an
urban agglomeration
Links main urban roads
Collects traffic from local areas and feed it to higher levels, and
vice versa.
Serves land parcel users, connecting them to the rest of the
network.
Tracks that are shaped and maintained, but not surfaced with
gravel of asphalt
Earth tracks that are not engineered in any way.
Associated Datasets
RoadInf
Column Heading
Data type
ID_rd
Rd_Type
Surface
Rd_width
Number of lanes
Speed_limit
Numeric
Numeric code
Numeric code
Number
Number
Numeric code
Av_traffic_dens
Number
Length Definitions
LUT_Surface
Total road width in meters (R.O.W)
The designed speed for the road. See LUT_Speed_limit
Look Up Table for explanations.
The average traffic density (vehicles per day)
Codes and Look-up Tables for Associated Dataset
LUT_Surface.dbf
Code EnLabel
0
1
2
3
4
ArLabel
Unknown, unclear
Paved
Engineered gravel
Unengineered
gravel
Earth
Definition
Surfaced with asphalt or concrete
Surfaced with gravel and maintained on a regular basis
Surfaced with gravel but not shaped or maintained
No surface.
LUT_Speed_limit.dbf
Code EnLabel
ArLabel
0
Unknown, unclear
Definition
Speed limit not known or unclear
41
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
1
2
3
4
5
30 kph
40 kph
60 kph
80 kph
Differentiated
30 kilometres per hour
40 kilometres per hour
60 kilometres per hour
80 kilometres per hour
Differentiated speeds for cars (100 kph), buses (90 kph),
trucks (80 kph)
Ports and Airports
Proposed name: ports
Usage
These layers will be used in presenting transportation features and statistics. They will be
combined with layers showing roads and railways.
Feature class:
Ports and airports will be entered preferably as polygons, creating a polygon layer with the basic
dataset below. This will then be used to generate a point layer with the same basic dataset. The
scripts for doing this generation are provided under Settlements.
Basic Dataset
Ports.dbf
Column Heading
Data type
Length Definitions
Pt_ID
Pt_Name
Pt_Type
Alphanumeric
Alphanumeric
Numeric code
16
35
2,0
Set_ID
Alphanumeric
16
A unique ID number for the port or airport
The name of the port or airport.
A code for each type of port or airport. Details are
provided in LUT_Pt_Type look up table.
The unique ID for the settlement in which the port or
airport is located.
Codes and Look-up Tables for Basic Dataset
LUT_Pt_type
Code EnLabel
10
11
12
Port of unknown type
Domestic cargo and
passenger port
International cargo
and passenger port
13
Repair harbours
14
Recreation harbours,
marinas
Fishing ports and
harbours
Naval yards
15
16
20
21
Airport of unknown
type
Domestic airport
ArLabel
Definition
Unknown or uncertain
Ports and harbours catering to domestic cargo and
passengers only (no customs or immigration services).
Ports and harbours catering to international trade and
travel. Customs clearing and immigration services are
present.
Ports and harbours primarily for boat construction and
repair.
Ports and harbours designed primarily for recreational
use, including private international recreational yachts.
Ports and harbours primarily used by fishermen,
including artisanal fishermen.
Sea ports used primarily for security purposes (navy and
coastguard)
Airports handling only domestic connections both cargo
42
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Code EnLabel
ArLabel
22
International airport
23
Security related
airport
Definition
and passengers.
Airports handling both domestic and international
connections, cargo and passengers
Airports used for security purposes.
Sea and river ports are coded as 1*; airports as 2*.
Associated Datasets
As with demographic and other socio.economic information, repeat the port ID, name and
type for each year of available data, extending the table downward rather than sideways. To
get trends select all records for one Pt_ID. This will result in all years for which data is
available for that port.
PortData.dbf
Column Heading
Data type
Length Definitions
Pt_ID
Pt_Name
Pt_Type
16
35
2,0
Year
Ex_tons
Alphanumeric
Alphanumeric
Numeric
code
Date
Number
Im_tons
Number
9
Dep_Pass
Number
8
Arr_Pass
Number
8
Dep_Vess
Number
6
Arr_Vess
Number
6
9
A unique ID number for the port or airport
The name of the port or airport.
A code for each type of port or airport. Details are
provided in LUT_Pt_Type look up table.
The year during which the data was collected
Number of tons of cargo loaded and shipped out of the
port or airport in the year
Number of tons of cargo off-loaded and brought into the
port or airport in the year.
Number of passenger departures from the port or airport
in the year
Number of passenger arrivals to the port or airport in
theyear
Number of vessels (ships or planes) departing from the
port or airport in the year
Number of vessels (ships or planes) arriving at the port or
airport in the year.
Waterlines
Proposed Name: Waterln
Usage
This layer will show the main water distribution lines outside of built-up areas. It is used together
with water source point data.
Feature class:
This is a Line feature layer.
Basic Dataset
Waterln.dbf
Column Heading
Data type
Length
Definitions
Water_ID
alphanumeric
6
Unique ID for each line shown on the layer
43
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Water_type
Numeric code
2
Code for the type or function of water pipeline. See
LUT_water_type Look Up Table for explanations of the
codes
Codes and Look-up Tables for Basic Dataset
LUT_Water_type.dbf
Code
EnLabel
0
1
Unknown
Collector
ArLabel
2
Trunk
3
Distributor
Definition
A pipeline is known to exist, but its type is not known.
Line taking water from source(s) to a central storage site, or
treatment plant
Main line taking water from central storage site to treatment plant
or from treatmant plant to distributor holding tanks
Lines taking water from storage tanks to users.
Associated Datasets
WaterpipeInfo.dbf
Column Heading
Data type
Length Definitions
Wat_ID
Size
Pressure
Capacity
alphanumeric
number
number
number
6
6
6
6
Unique ID for each line shown on the layer
Diameter size of pipeline in millimetres
Pressure of water in the pipe in kilopascals
Throughput capacity of the pipeline in litres per sec
Water source
Proposed Name: sources
Usage
This layer shows water wells and the dataset indicates the sustainable production capacity. The
layer will be used with waterln.shp which shown the water pipelines, and with waterfac.shp which
shows water facilities such as pumping stations, desalinisation and treatment plants, and water
storage tanks.
Feature class:
This is a Point layer
Basic Dataset
Sources.dbf
Column Heading
Data type
Length
Definitions
Source_ID
Alphanumeric
5
Unique ID for each point on the layer
Associated Datasets
Well.dbf
Column Heading
Data type
Length
Definitions
Source_ID
Capacity
Alphanumeric
number
5
6
Depth
number
5
Unique ID for each point on the layer
The sustainable capacity of supply from this source
in cubic meters per hour
The depth to water level in the well or borehole in
meters
44
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Water source
Proposed Name: waterfac
Usage
This layer shows water supply facilities such as pumping stations, purification plants and storage
tanks and the dataset indicates the capacity. The layer will be used with waterln.shp which shown
the water pipelines, and with sources.shp.
Feature class:
This is a Polygon layer
Basic Dataset
Waterfac.dbf
Column Heading
Data type
Length
Definitions
Source_ID
Watfac_type
Alphanumeric
Numeric code
5
1
Unique ID for each point on the layer
Code desribing the type of facility. The explanations are
provided in LUT_Waterfac_type Look Up Table.
Codes and Look-up Tables for Basic Dataset
LUT_Waterfac_type
Code
EnLabel
0
1
2
Unknown
Pumping station
Purification
plant
Storage tank
3
ArLabel
Definition
A facility is observed, but its type is not known
A facility for pumping water
A facility for purifying water
A facility for storing water and / or providing enough head
to provide supply pressure
Associated Datasets
Wfacilities.dbf
Column Heading
Data type
Length
Definitions
WatFac_ID
Capacity
Alphanumeric
number
5
5
Unique ID for each point on the layer
The sustainable capacity of throughput in cubic
meters per hour.
Sewerage
Proposed Names: Sewers
Usage
This layer incorporates sewerage lines. It will be used together with Treatment.shp to show
complete liquid waste systems. These layers are seldom used at regional level, sometimes at suregional level.
Feature class:
This is a line layer.
45
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Basic Dataset
Sewers.dbf
Column Heading
Data type
Length
Definitions
Sew_ID
alphanumeric
3
Sew_role
Numeric code
2
Sew_size
Numeric code
1
A unique ID for each of the line objects shown in the
layer.
A code for the role or function of the line object, code is
explained in LUT_Sew_role Look Up Table
Code for the size of the sewer. Standard sizes are used.
Codes are explained in LUT_Sew_size Look Up Table
Codes and Look-up Tables for Basic Dataset
LUT_Sew_role
Code
EnLabel
0
1
2
Unknown
Collector lines
Transmission line under
pressure
ArLabel
Definition
Role or level in network is unknown
LUT_Sew_size
Code
EnLabel
0
1
Unknown
Up to 10 in diameter
ArLabel
2
12 and greater
diameter
Definition
Size of sewer is unknown
Pipes, usually within settlements that are up to 10 in
diameter, transferring liquid under gravity
Pipes, usually outside urban areas, that transfer the
sewage under pressure from the pump station to the
treatment plant.
Treatment
Proposed Names: Treatment
Usage
This layer incorporates sewage treatment plants and sewage pump or collector stations. It will be
used together with Sewers.shp to show complete liquid waste systems.
Feature class:
This is a polygon layer. At regional scale features will be seen as points.
Basic Dataset
Treatment.dbf
Column Heading
Data type
Length
Definitions
Treat_ID
alphanumeric
3
Treat_cap
Fac_type
Number
Numeric code
6
1
A unique ID for each of the polygon objects shown in
the layer.
The capacity of the facility
The type of facility. See fac_type Look Up Table for
explanation of the codes.
Codes and Look-up Tables for Basic Dataset
fac_type
46
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Code
ArLabel
0
1
Unknown
Pump station
2
Treatment plant
Definition
ArLabel
The type of facility is unknown.
Facilities where sewage is collected, then pumped to sewage
treatment.
Waste
Proposed Name: Waste
Usage
This layer will present the various (solid) waste sites and allow comparison of existing sites with
criteria for new ones. The main types considered are normal household solid waste, industrial
waste, hazardous waste, and incinerators. Liquid waste is treated under Sewerage.
Feature class:
This is a polygon layer.
Basic Dataset
Waste.dbf
Column Heading
Data type
Length Definitions
Waste_ID
Waste_type
Alphanumeric
Numeric code
2
1
Unique code for the polygons shown on the layer
A code for each type of waste treated in the waste site.
LUT_Waste_type
Codes and Look-up Tables for Basic Dataset
LUT_Waste_type
Code
Label
Definition
0
1
2
3
Unknown
General waste
Industrial waste
Hazardous waste
4
Medical waste
Type of waste is not known.
Most common, domestic and urban waste
Waste generated in bulk by industries
Dangerous waste that must be treated and handled in special way.
Includes nuclear waste from medical and research facilities.
Incinerator primarily for medical waste
Telephone lines
Proposed name: Telelines
Usage
This layer simply shows where there are telephone land lines. It will be shown together with
other infrastructure layers, particularly those presenting transport and communications.
Feature class:
This is a line feature layer
Basic Dataset
Telelines.dbf
Column Heading
Data type
Tele_ID
alphanumeric
Length
Definitions
Unique ID for each line shown in the layer
47
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Energy (power plants and sub-stations)
Proposed name: power
Usage
This layer shows electricity generating plants. It should be displayed together with pwrline.shp to
show the electricity generation and distribution systems.
Feature class:
It is a polygon. At regional level the polygons may appear as points.
Basic Dataset
Power.dbf
Column Heading
Data type
Length Definitions
En_ID
Name
Alphanumeric
Alphanumeric
8
25
A unique number identifying the power plant
The name of the power plant
Associated Datasets
Energy.dbf
Column Heading
Data type
Length
Definitions
En_ID
Name
ArName
Alphanumeric
Alphanumeric
Arabic
alphanumeric
8
25
25
A unique number identifying the power plant
The name of the power plant
Name of settlement in Arabic
EnType
Numeric code
2
Code for the type of plant or facility. The interpretation
of the code is provided in LUT_EnType Look Up Table
Codes and Look-up Tables for Associated Dataset
LUT_EnType
Code
EnLabel
0
Unknown, unclear,
unreported
Hydropowered
Solar powered
Wind powered
Coal powered
Oil / Diesel
powered
Gas powered
Nuclear powered
Substation
Transformer station
1
2
3
4
5
6
7
8
9
ArLabel
Definition
Energy source is not known, or unclear, or available
information does not state is.
Plant powered by falling water
Plant powered by the sun
Plant powered by the wind
Plant using coal as a source of energy.
Plant using oil or diesel as a source of energy
Plant using gas as a source of energy
Plant powered by nuclear fusion
A substation on the network for switching primarily
Step-down or step-up transformer on the network,
usually from high tension to 22 or 11 KV
48
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Power lines
Proposed name: PwrLine
Usage
This layer can be combined with Power stations (power.shp) to show the electricity grid system.
It can also be combined with other infrastructure to show physical infrastructure features. Only
high voltage lines are included in the regional and sub-regional levels.
Feature class:
This is a line feature layer.
Basic Dataset
Column Heading
Data type
Length Definitions
Pl_ID
Volts
Alphanumeric
Number code
8
5
A unique identifier for each section of a power line.
The network level of the line, as expressed in voltage.
The codes are explained in LUT_Volts Look Up Table
Codes and Look-up Tables for Basic Dataset
LUT_Volts
Code
EnLabel
0
1
Unknown
High voltage
network
11 KV network
0.38 KV network
2
3
ArLabel
Definition
Lines of unknown voltage
High tension lines carrying power long distances
Main distribution net
Three phase power for distribution to neighbourhoods
SERVICES
Service Facilities:
Education, health, recreation, security (police and prisons), post, social welfare facilities.
Usage
These datasets do not have shapefiles of their own but will be linked to the settlements shape-file
so that the distribution of facilities can be portrayed. They can be shown on individual layers
(using .lyr rather than .shp files) or on one combined layer, or on a smaller number of layers on
each of which several types of services will be shown. The choice will depend on the purpose of
the map, the number of facilities to be shown and the appearance of the result. Education and
health almost certainly will be shown on their own, separate layers.
Feature class:
Most frequently these datasets will be portrayed through a point shapefile, using specific symbols.
49
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Basic Dataset
The basic dataset is the settlement shapefile (either point or polygon feature class can be used,
but point is preferable.) This basic dataset is linked to individual associated datasets using the
Set_ID and Name fields.
Associated Datasets
Summary dataset, all facilities: ServSum.dbf
Column Heading
Data type
Length
Definitions
Set_ID
Name
ArName
16
25
25
The unique id number for the settlement
Name of the settlement
Name of settlement in Arabic
Nursery
Kindergarden
PrimSch
PrepSch
SecSch
2YrInst
Alphanumeric
Alphanumeric
Arabic
alphanumeric
number
number
number
number
number
number
5
5
4
4
4
4
Univ
Research
MobHeal
HealUnit
CharHeal
DistHsp
MarkHsp
GenHsp
UnivHsp
SpecHsp
SpecInst
Recreat
number
number
number
number
Number
Number
Number
Number
Number
Number
Number
Number
2
2
2
4
3
2
2
2
2
2
2
4
RegiSoc
Number
5
Police
Prison
PrivSec
Posts
PrivPost
Number
Number
Number
Number
Number
4
2
2
3
3
Number of nurseries
Number of kindergardens
Number of primary schools
Number of preparatory schools
Number of secondary schools of all types
Number of post-secondary educational institutions
providing 2-year, non-degree programmes
Number of institutions providing university level degrees
Number of institutions specialising in research
Mobile health units
Number of stationary, permanent health units
Number of Charity health units
Number of district hospitals
Number of Makhaz hospitals
Number of General hospitals
Numbterof University Hospitals
Number of specialist hospitals
Number of specialist health institutes
Number of recreational facilities – sports fields, arenas,
stadiums, sports clubs, public swimming pools, etc.
Number of registered societies and NGOs. See RegiSoc
Look Up table for definitions of specific types of
societies included here.
Number of Police Stations
Number of prison facilities
Number of Private Security firms
Number of Post Offices
Number of private couriers, (DHL, Western Union, etc.)
Education.dbf
Column Heading
Data type
Length
Definitions
Set_ID
Name
ArName
Alphanumeric
Alphanumeric
Arabic
alphanumeric
alphanumeric
Arabic
alphanumeric
Numeric code
16
25
25
The unique id number for the settlemet
Name of the settlement in English
Name of the settlement in Arabic
50
25
Name of School
Name of School in Arabic
2
Type of school according to codes listed in
LUT_SchType
SchName
ArSchName
SchType
50
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Column Heading
Data type
Length
Definitions
PubPriv
Numeric code
1
Year
MalStud
FemStud
Staff
Class
Alphanumeric
Number
Number
Number
Number
8
5,0
5,0
4, 0
Describes whether the school is a public or
private sector school, according to the codes
given in PubPriv
The year of any statistics provided in the table
Number of male students
Number of female students
Number of teaching staff
Number of classrooms, in post secondary
institutions and research institutes include
laboratories.
Codes and Look-up Tables for Associated Datasets
LUT_SchType
Code
EnLabel
0
Unknown,
uncertain
Nursery
Kindergarden
Primary School
Al-Azhar Primary
School
Preparatory School
Al-Azhar
Preparatory School
General Secondary
School
Technical
Secondary School
Al-Azhar Secondary
School
2-year post
secondary institutes
1
2
3
4
5
6
7
8
9
10
11
12
13
ArLabel
Definition
Facilities whose category is uncertain or not known.
Facility for youngest children
Preschool facility
Government or private primary school
Government or private preparatory school
Government or private general secondary school
Government or private technical secondary school
Educational institutions that offer less than full
university level degrees. Includes special training
institutes
Tertiary level institutions that give recognised degrees
Institutions specialised in the training of nurses
Institutions dedicated primarily to research and where
teaching is at best a minor activity.
University
Nursing Schools
Research institutes
Health Facilities.dbf
Column Heading
Data type
Length
Definitions
Set_ID
Name
FacName
HealType
Alphanumeric
Alphanumeric
Alphanumeric
Alphanumeric
16
25
25
25
PubPriv
Alphanumeric
25
Numbeds
Numdoc
Number
Number
6
6
The unique id number for the settlement
Name of the settlement
Name of facility
Type of facility according to LUT_Healthtype
Look up table
Category of facility according to LUT_PubPriv
Look up Table.
Number of beds
Number of doctors
Column Heading
Data type
Length
Definitions
Name
Alphanumeric
50
Name of the society, or NGO
Societies.dbf
51
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
Column Heading
Data type
Length
Definitions
RegiSoc
Numeric code
2
Empl
Members
Set_ID
Number
Number
Alphanumeric
5
5
16
Name
Alphanumeric
25
The type of society given as a code. The codes
are listed in the LUT_RegiSoc Look Up Table
Number of employees
Number of registered members
The unique id number for the settlement in
which the society’s headquarters lies.
Name of the settlement in which the
headquarters lies.
LookUp Tables
LUT_Healthtype.dbf
Code
EnLabel
0
Unknown,
unreported,
uncertain
Mobile health
service
Health Unit
1
2
3
Charity Health
Unit
4
District Hospital
5
Markhaz
Hospital
6
7
General Hospital
University
Hospital
Specialised
hospital
Specialized
health
institutions
8
9
ArLabel
Definition
Facility is known to exist but its type is unknown
Mobile service provided to remote communities on a
scheduled basis, but no permanent presence
Most basic health service provided on a permanent basis,
including individual doctors, dentists, opthalmologists, etc.
Basic health provided by charitable organisation, such as
mosque or church or other organisation. Usually a limited
number of beds, especially for maternity purposes.
Doctors and beds permanently available – criteria: To serve a
population of xxx within an area of yyy
Doctors and beds permanently available, larger than District
hospital – criteria: To serve a population of xxx within an area
of yyy
Large generalised hospital, with some specialised doctors.
Hospital will medical training functions
Hospitals with specialisations - eg liver, maternity care, etc.
Health institutions with specialisations, such as hearing, cancer,
diabetes, cardiac, etc.
In LUT_Healthtype no categorisation of ownership is considered, only type and scale of service
provided. LUT_PubPriv Look Up Table will address the issue of owner/operator.
LUT_PubPriv.dbf
Code
EnLabel
0
1
2
Unknown
Government
Parastatal
3
4
Private
Public-private
partnership
NGO, charitable
organisation
5
ArLabel
Definition
The ownership status is not known
Facility is operated by government, regardless of branch.
Facility is operated by a government-owned authority or
organisation, such as Suez Canal Authority or Egypt
Railways
Facility is operated by the private sector
Facility in which both public and private sectors share
responsibility
Facility operated by a non-governmental or charitable
organisation, not for profit.
LUT_RegiSoc.dbf
Code
Label
Definition
0
Unknown
Society is known but its category is not.
52
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
1
2
3
4
5
6
7
8
9
10
11
12
13
Child care
Family care
Social aid
Care for the elderly
Care for special groups
Cultural and scientific services
Literacy activities
Management and organisation services
Care for prisoners
Family planning
International friendship societies
Development Societies
Environmental NGOs
Societies devoted to welfare of children.
Societies devoted to family well being
Societies devoted to providing social support
Societies devoted to the care of the elderly
Societies devoted to care for special groups
Societies devoted to cultural issues
Societies devoted to spreading literacy
Societies devoted to care for prisoners
Societies devoted to family planning
Societies devoted to development
Societies devoted to environmental issues
SUITABILITY FOR SETTLEMENT
Suitability for settlement is dependent on many different factors that interact with each other in
different ways. It may be simplest to create a number of classes ranging from “highly suitable,” to
“totally unsuitable” and to address different components separately before combining them. This
allows us to conduct a type of sensitivity analysis in which different components are given
different weights. Areas that are suitable to highly suitable irregardless of the weights allocated
would then have a high probability of in fact being suitable.
An initial list of components would include:
● Slope and ruggedness, derived from landscape analysis;
● Proximity to water;
● Groundwater level;
● Soil factors (soil depth, load bearing capacity, and other characteristics important to
engineering)
● Proximity to other natural resource(s), individually and collectively;
● Proximity to existing transportation, especially roads of at least “highway” (two lane, tarred
road);
● Proximity to high voltage power line or other reliable energy source;
● Proximity to telecommunication systems;
● Proximity to other settlements, especially those of higher order where services are available;
A buffering mechanism is used on each component based on the assumption that costs are
ultimately the most important factor, and that costs of providing important infrastructural
together make up the majority of the total cost. A modern settlement also depends on access to
other settlements so that road transportation and telecommunications are both important.
Before applying the buffering process, all known “totally unsuitable” areas should be removed.
These include:
areas that are excluded by fiat, such as protected conservation areas
areas with high natural or anthropogenic hazards (flash floods, sand dunes, mine fields, military
areas, especially military exercise areas).
Earthquake zones are not necessarily excluded entirely, but proximity to such areas would be
classified on the following scale:
Highly suitable
Moderately suitable
Unsuitable
Totally unsuitable
The general pattern to apply on each component layer is as follows:
53
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
1.
2.
3.
4.
Convert the component layer to a raster layer;
Ensure that the pixel values are appropriate to the layer;
Apply the appropriate “rule” for assigning suitability (see the “rules” below);
Display the resulting layer and check for reasonableness.
When all components have been treated, a final layer must be created by “raster calculation”
while introducing the appropriate weights for each component.
Component
Slope and ruggedness, derived
from landscape analysis;
“Rule”
A maximum percentage slope
must be chosen as well as a
degree of ruggedness. The latter
may be difficult to apply on a
regional scale.
Comment
Steep slopes and very rough
terrain is unsuitable to urban
development, through cost
considerations. Stability of the soil
and the risk of landslides are also
factors.
Proximity to water;
Critical to the calculation is the
Access to sustainable water
Both surface water, possibly
degree to which capital and
supplies are essential for
supplied by pipeline, and
recurrent costs can be recovered settlements. At the same time the
groundwater with sustainable
through user fees. This should be sustainable extraction of water
quantities.
combined with a rough distance- and the degree of recycling of
related capital cost for
waste water will affect how large a
infrastructure. This will determine settlement can be provided.
the width of the four suitability
classes.
Proximity to other natural
Compatible and incompatible
The proximity to multiple
resource(s), individually and
resources need to be identified.
resources, except where their
collectively;
Three distance factors need to be exploitation is basically
decided to apply to the buffering incompatible can be an advantage.
exercise.
Where there are incompatibilities,
this multiple proximity will be a
negative factor.
Proximity to existing
Three distance factors from a
The cost of connecting the new
transportation, especially roads of main road need to be determined site to the existing main road net
at least “highway” (two lane,
for application of the buffer
is the major cost factor here.
tarred road);
exercise.
Proximity to high voltage power Three distance factors from a
The cost of connecting to a high
line or other reliable energy
main high voltage line need to be voltage power line is the main
source;
determined for application of the relative cost here. The cost of a
buffer exercise.
step-down transformer can be
assumed to be approximately
constant in all cases, so does not
need to be included for relative
suitability analysis.
Proximity to telecommunication Three distance factors from a
Distance affects the cost of
systems;
main telephone line or mobile
infrastructure whether land lines
phone network need to be
or mobile phone relay systems are
determined for application of the installed.
buffer exercise.
Proximity to other settlements,
Three distance factors from a
The new settlement will need
especially those of higher order
other medium to higher order
access to higher order services
where services are available
settlements need to be determined within a reasonable distance
for application of the buffer
(measured in cost), but will not
exercise.
grow rapidly itself if it is too close.
54
GEOGRAPHICAL INFORMATION SYSTEM FOR REGIONAL PLANNING IN EGYPT
FUTURE WORK
This document is a Beta Version. This means that it continues to be a work in progress. The
initially defined datasets will be created and a test plan undertaken. This will highlight the need
for changes, new datasets. Bu above all it will produce the specific steps that will be taken to carry
out individual types of analysis. These will be presented individually. The “models” will also be
developed in the software context and made available on the GOPP intranet.
Comments and suggestions on this current edition are particularly welcome.
55