You are on page 1of 24

SWEDESURVEY GIS STRATEGY FOR

RLUDMP

Metadata specification for Environment feature class.

Metadata
Identification
Description
Title: Title should include theme and location.
NATIONAL PARKS; D\CENTRAL
GOVERNMENT\03_EN\01_PROTECTED NATURAL AREAS\GIS.
File name: The name of the file.
parks_WGS84_TM
Custodian: The organisation responsible for having created the data and has
the responsibility to maintain and update.
N/A
Abstract: A short description or summary of the contents of the data,
including the original data source. Preferably also an explanation
of why the data was created.
The shape file is a geometrical polygon feature that shows parks in
the Republic of Rwanda.
Theme, Common-use word or phrase used to describe the subject of the
Keywords: data set.
Park, Tourism, Protected Area, Environment
Metadata
Reference
Contact Details about the person who has created the metadata; name of
Information: Individual and Organization, email address, the role in the
Organization.
Name: Umuraza Angeline.
Organization: Swedesurvey
E-mail address: angeloa33@yahoo.fr
Role: GIS Technician
Date: The date when the metadata was created.
October, 2010.
Data Quality
Information
Date of Insert the date when the dataset was prepared.
Capture: N/A

Positional Assessment of the expected error or range of error, of the data


Accuracy: objects location. Described as the difference (in meters) between
measured quantities and true positions (horizontal and vertical
when applicable). Method to assess depends on data type, e.g.,
RMS for image and grid data, GPS techniques. If accuracy cannot
be precisely determined, an intuitive accuracy based on
experience may be acceptable.
To investigate with the Tourism and National Parks Authority
(ORTPN)
Attribute Assessment of values or attributes assigned to features in the
Accuracy: data in relation to the reality. Attribute accuracy can be described
as percentage of correct or incorrect values of attributes. Usually
based on a sample of the data (through field checks or through
comparing to separate data source).
The project’s analysis on attribute accuracy of the data shows that
it is accurate.
Logical A statement whether data has been checked and corrected for

50124207.doc Page 1 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Consistency: topological errors, i.e. logical relationship between features of the


data. For example, duplicate lines, labelling, enclosed polygon and
boundaries. Logical consistency does not apply to raster data.
Need to be crosschecked with ORTPN
Completeness: An assessment of the completeness to identify gaps in the data.
Description may include spatial data coverage, attribute data
coverage.
The shape file is complete but the attribute table is not complete.
Currentness: Refers to the original data source, e.g. date when an aerial
photography was taken or publication date of a map or when a
field survey was conducted to capture the features.
N/A
Lineage: Information about the sources of data used to construct the data
set and steps used to process the data. For each processing step
provide (where possible) the following: source data name, source
data scale, source data date, description of processing step
performed.
N/A
User Scales, etc.
Constraints: Positional accuracy acceptable for maps of scale ≤ 1:50,000.

Data
Organisation
Information
Data Format Format in which the data reside, e.g. Personal Geodatabase,
Name: Shapefile, dBase, Excel, etc.
Shapefile.
Spatial Object Description of the types of geographic features and their
Type: representation, e.g. Raster, Vector (point, line, polygon).
The spatial data is in vector form and re-presented as a polygon
feature.

Data Reference
Information
Coordinate The scheme used for coordinates, e.g. Transverse Mercator, Lo27.
System: Transverse Mercator

Datum: The datum used in the coordinate system, e.g. Cape or Hart 94.
WGS_1984.

Distance Units: The horizontal distance units, i.e., meters.


Meters.

Language The language used in the Dataset; English, French, Kinyarwanda


or combined.
English, French.
Entity and A summary of the information contained within the data set,
Attribute reference must be made to the NLC data dictionary.
Information:

Contact
Information

50124207.doc Page 2 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Contact Person: A person who can receive inquiries regarding the contents and
distribution of the data.
In the ideal situation, it will be the same individual as stated under
“contact information” under “Metadata Reference”.
ORTPN.
Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer Format The name of the format(s) in which the distributor will make the
Name data available. The user may list as many formats as desired.
and/or Lineage: Shapefiles, geopdf, pg, xls, dbf.

50124207.doc Page 3 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Metadata
Identification
Description
Title: Title should include theme and location.
PROTECTED FORESTS; D\CENTRAL
GOVERNMENT\03_EN\01_PROTECTED NATURAL AREAS\GIS.
File name: The name of the file.
Protected_Forest
Custodian: The organisation responsible for having created the data and has
the responsibility to maintain and update.
Swedesurvey-NLC.
Abstract: A short description or summary of the contents of the data,
including the original data source. Preferably also an explanation
of why the data was created.
The shape file is a geometrical Polygon feature that shows
protected forests in the Republic of Rwanda.
Theme, Common-use word or phrase used to describe the subject of the
Keywords: data set.
Protected Forest, Protected Area, Environment.
Metadata
Reference
Contact Details about the person who has created the metadata; name of
Information: Individual and Organization, email address, the role in the
Organization.
Name: Umuraza Angeline.
Organization: Swedesurvey
E-mail address: angeloa33@yahoo.fr
Role: GIS Technician
Date: The date when the metadata was created.
October, 2010.
Data Quality
Information
Date of Insert the date when the dataset was prepared.
Capture: 2010

Positional Assessment of the expected error or range of error, of the data


Accuracy: objects location. Described as the difference (in meters) between
measured quantities and true positions (horizontal and vertical
when applicable). Method to assess depends on data type, e.g.,
RMS for image and grid data, GPS techniques. If accuracy cannot
be precisely determined, an intuitive accuracy based on
experience may be acceptable.
To investigate with the Ministry of Forestry and Mining(MINIFOM)
Attribute Assessment of values or attributes assigned to features in the
Accuracy: data in relation to the reality. Attribute accuracy can be described
as percentage of correct or incorrect values of attributes. Usually
based on a sample of the data (through field checks or through
comparing to separate data source).
To investigate with MINIFOM
Logical A statement whether data has been checked and corrected for
Consistency: topological errors, i.e. logical relationship between features of the
data. For example, duplicate lines, labelling, enclosed polygon and
boundaries. Logical consistency does not apply to raster data.
To investigate with MINIFOM

50124207.doc Page 4 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Completeness: An assessment of the completeness to identify gaps in the data.


Description may include spatial data coverage, attribute data
coverage.
To investigate with MINIFOM
Currentness: Refers to the original data source, e.g. date when an aerial
photography was taken or publication date of a map or when a
field survey was conducted to capture the features.
N/A
Lineage: Information about the sources of data used to construct the data
set and steps used to process the data. For each processing step
provide (where possible) the following: source data name, source
data scale, source data date, description of processing step
performed.
The dataset was generated from an existing basemap of
“Protected Areas”. The scale and preparation date of the basemap
is unknown.
User Scales, etc.
Constraints: Positional accuracy acceptable for maps of scale ≤ 1:50,000.

Data
Organisation
Information
Data Format Format in which the data reside, e.g. Personal Geodatabase,
Name: Shapefile, dBase, Excel, etc.
Shapefile.
Spatial Object Description of the types of geographic features and their
Type: representation, e.g. Raster, Vector (point, line, polygon).
The spatial data is in vector form and re-presented as a polygon
feature.

Data Reference
Information
Coordinate The scheme used for coordinates, e.g. Transverse Mercator, Lo27.
System: Transverse Mercator

Datum: The datum used in the coordinate system, e.g. Cape or Hart 94.
WGS_1984.

Distance Units: The horizontal distance units, i.e., meters.


Meters.

Language The language used in the Dataset; English, French, Kinyarwanda


or combined.
English.
Entity and A summary of the information contained within the data set,
Attribute reference must be made to the NLC data dictionary.
Information:

Contact
Information
Contact Person: A person who can receive inquiries regarding the contents and
distribution of the data.
In the ideal situation, it will be the same individual as stated under
“contact information” under “Metadata Reference”.
MINIFOM

50124207.doc Page 5 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer Format The name of the format(s) in which the distributor will make the
Name data available. The user may list as many formats as desired.
and/or Lineage: Shapefiles, geopdf, jpg, xls, dbf.

50124207.doc Page 6 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Metadata
Identification
Description
Title: Title should include theme and location.
PROTECTED WETLANDS; D\CENTRAL
GOVERNMENT\03_EN\01_PROTECTED NATURAL AREAS\GIS.
File name: The name of the file.
prot_wetland
Custodian: The organisation responsible for having created the data and has
the responsibility to maintain and update.
Swedesurvey-NLC/Rwanda Environment Management Authority
(REMA)
Abstract: A short description or summary of the contents of the data,
including the original data source. Preferably also an explanation
of why the data was created.
The shape file is a geometrical Polygon feature that shows
protected wetland in the Republic of Rwanda.
Theme, Common-use word or phrase used to describe the subject of the
Keywords: data set.
Protected Wetland, Protected Area, Environment.
Metadata
Reference
Contact Details about the person who has created the metadata; name of
Information: Individual and Organization, email address, the role in the
Organization.
Name: Umuraza Angeline.
Organization: Swedesurvey
E-mail address: angeloa33@yahoo.fr
Role: GIS Technician
Date: The date when the metadata was created.
October, 2010.
Data Quality
Information
Date of Insert the date when the dataset was prepared.
Capture: 2010.

Positional Assessment of the expected error or range of error, of the data


Accuracy: objects location. Described as the difference (in meters) between
measured quantities and true positions (horizontal and vertical
when applicable). Method to assess depends on data type, e.g.,
RMS for image and grid data, GPS techniques. If accuracy cannot
be precisely determined, an intuitive accuracy based on
experience may be acceptable.
This need to be crosschecked with REMA.
Attribute Assessment of values or attributes assigned to features in the
Accuracy: data in relation to the reality. Attribute accuracy can be described
as percentage of correct or incorrect values of attributes. Usually
based on a sample of the data (through field checks or through
comparing to separate data source).
This need to be crosschecked with REMA.
Logical A statement whether data has been checked and corrected for
Consistency: topological errors, i.e. logical relationship between features of the
data. For example, duplicate lines, labelling, enclosed polygon and
boundaries. Logical consistency does not apply to raster data.

50124207.doc Page 7 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

This need to be crosschecked with REMA.


Completeness: An assessment of the completeness to identify gaps in the data.
Description may include spatial data coverage, attribute data
coverage.
This need to be crosschecked with REMA.
Currentness: Refers to the original data source, e.g. date when an aerial
photography was taken or publication date of a map or when a
field survey was conducted to capture the features.
Publication date of the original data source: 2005.
Lineage: Information about the sources of data used to construct the data
set and steps used to process the data. For each processing step
provide (where possible) the following: source data name, source
data scale, source data date, description of processing step
performed.
The dataset was generated from an existing wetland basemap,
prepared by REMA in collaboration with CGIS-NUR, and published
in 2005.
User Scales, etc.
Constraints: Positional accuracy acceptable for maps of scale ≤ 1:50,000.

Data
Organisation
Information
Data Format Format in which the data reside, e.g. Personal Geodatabase,
Name: Shapefile, dBase, Excel, etc.
Shapefile.
Spatial Object Description of the types of geographic features and their
Type: representation, e.g. Raster, Vector (point, line, polygon).
The spatial data is in vector form and re-presented as a polygon
feature.

Data Reference
Information
Coordinate The scheme used for coordinates, e.g. Transverse Mercator, Lo27.
System: Transverse Mercator

Datum: The datum used in the coordinate system, e.g. Cape or Hart 94.
Arc_1960.

Distance Units: The horizontal distance units, i.e., meters.


Meters.

Language The language used in the Dataset; English, French, Kinyarwanda


or combined.
English, French.
Entity and A summary of the information contained within the data set,
Attribute reference must be made to the NLC data dictionary.
Information:

Contact
Information
Contact Person: A person who can receive inquiries regarding the contents and
distribution of the data.
In the ideal situation, it will be the same individual as stated under
“contact information” under “Metadata Reference”.
REMA.

50124207.doc Page 8 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer Format The name of the format(s) in which the distributor will make the
Name data available. The user may list as many formats as desired.
and/or Lineage: Shapefiles, geopdf, jpg, xls, dbf.

50124207.doc Page 9 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Metadata
Identification
Description
Title: Title should include theme and location.
DROUGHT RISKS; D\CENTRAL GOVERNMENT\03_EN\02_NATURAL
HAZARDS\GIS\Natural Hazards Risks.
File name: The name of the file.
Drought risk
Custodian: The organisation responsible for having created the data and has
the responsibility to maintain and update.
Swedesurvey-NLC
Abstract: A short description or summary of the contents of the data,
including the original data source. Preferably also an explanation
of why the data was created.
The shape file is a geometrical Polygon feature that shows drought
risk regions in the Republic of Rwanda.
Theme, Common-use word or phrase used to describe the subject of the
Keywords: data set.
Drought risk, Natural hazards, Environment.
Metadata
Reference
Contact Details about the person who has created the metadata; name of
Information: Individual and Organization, email address, the role in the
Organization.
Name: Umuraza Angeline.
Organization: Swedesurvey
E-mail address: angeloa33@yahoo.fr
Role: GIS Technician
Date: The date when the metadata was created.
October, 2010.
Data Quality
Information
Date of Insert the date when the dataset was prepared.
Capture: N/A

Positional Assessment of the expected error or range of error, of the data


Accuracy: objects location. Described as the difference (in meters) between
measured quantities and true positions (horizontal and vertical
when applicable). Method to assess depends on data type, e.g.,
RMS for image and grid data, GPS techniques. If accuracy cannot
be precisely determined, an intuitive accuracy based on
experience may be acceptable.
Need to be certified by MIDIMAR.
Attribute Assessment of values or attributes assigned to features in the
Accuracy: data in relation to the reality. Attribute accuracy can be described
as percentage of correct or incorrect values of attributes. Usually
based on a sample of the data (through field checks or through
comparing to separate data source).
The shape file does not have an active attribute table.
Logical A statement whether data has been checked and corrected for
Consistency: topological errors, i.e. logical relationship between features of the
data. For example, duplicate lines, labelling, enclosed polygon and
boundaries. Logical consistency does not apply to raster data.
The project’s analysis on logical consistency of the data shows

50124207.doc Page 10 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

that it is accurate.
Completeness: An assessment of the completeness to identify gaps in the data.
Description may include spatial data coverage, attribute data
coverage.
To investigate with MIDIMAR
Currentness: Refers to the original data source, e.g. date when an aerial
photography was taken or publication date of a map or when a
field survey was conducted to capture the features.
N/A
Lineage: Information about the sources of data used to construct the data
set and steps used to process the data. For each processing step
provide (where possible) the following: source data name, source
data scale, source data date, description of processing step
performed.
The dataset was digitised from an existing basemap showing
“drought risk regions”.
User Scales, etc.
Constraints: Positional accuracy acceptable for maps of scale ≤ 1:50,000.

Data
Organisation
Information
Data Format Format in which the data reside, e.g. Personal Geodatabase,
Name: Shapefile, dBase, Excel, etc.
Shapefile.
Spatial Object Description of the types of geographic features and their
Type: representation, e.g. Raster, Vector (point, line, polygon).
The spatial data is in vector form and re-presented as a polygon
feature.
Data Reference
Information
Coordinate The scheme used for coordinates, e.g. Transverse Mercator, Lo27.
System: Transverse Mercator

Datum: The datum used in the coordinate system, e.g. Cape or Hart 94.
WGS_1984.

Distance Units: The horizontal distance units, i.e., meters.


Meters.

Language The language used in the Dataset; English, French, Kinyarwanda


or combined.
English.
Entity and A summary of the information contained within the data set,
Attribute reference must be made to the NLC data dictionary.
Information:

Contact
Information
Contact Person: A person who can receive inquiries regarding the contents and
distribution of the data.
In the ideal situation, it will be the same individual as stated under
“contact information” under “Metadata Reference”.
MIDIMAR.
Office: N/A

50124207.doc Page 11 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer Format The name of the format(s) in which the distributor will make the
Name data available. The user may list as many formats as desired.
and/or Lineage: Shapefiles, geopdf, jpg, xls, dbf.

50124207.doc Page 12 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Metadata
Identification
Description
Title: Title should include theme and location.
FLOOD AND LANDSLIDE RISKS; D\CENTRAL
GOVERNMENT\03_EN\02_NATURAL HAZARDS\GIS\Natural Hazards
Risks.
File name: The name of the file.
Flood and landslide risk.
Custodian: The organisation responsible for having created the data and has
the responsibility to maintain and update.
Swedesurvey-NLC
Abstract: A short description or summary of the contents of the data,
including the original data source. Preferably also an explanation
of why the data was created.
The shape file is a geometrical Polygon feature that shows Flood
and landslide risk regions in the Republic of Rwanda.
Theme, Common-use word or phrase used to describe the subject of the
Keywords: data set.
Flood, Landslide, Natural hazards, Environment.
Metadata
Reference
Contact Details about the person who has created the metadata; name of
Information: Individual and Organization, email address, the role in the
Organization.
Name: Umuraza Angeline.
Organization: Swedesurvey
E-mail address: angeloa33@yahoo.fr
Role: GIS Technician
Date: The date when the metadata was created.
October, 2010.
Data Quality
Information
Date of Insert the date when the dataset was prepared.
Capture: 2010.

Positional Assessment of the expected error or range of error, of the data


Accuracy: objects location. Described as the difference (in meters) between
measured quantities and true positions (horizontal and vertical
when applicable). Method to assess depends on data type, e.g.,
RMS for image and grid data, GPS techniques. If accuracy cannot
be precisely determined, an intuitive accuracy based on
experience may be acceptable.
This need to be certified by MIDIMAR.
Attribute Assessment of values or attributes assigned to features in the
Accuracy: data in relation to the reality. Attribute accuracy can be described
as percentage of correct or incorrect values of attributes. Usually
based on a sample of the data (through field checks or through
comparing to separate data source).
The shape file does not have an active attribute table.
Logical A statement whether data has been checked and corrected for
Consistency: topological errors, i.e. logical relationship between features of the
data. For example, duplicate lines, labelling, enclosed polygon and
boundaries. Logical consistency does not apply to raster data.

50124207.doc Page 13 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

This has to be certified by MIDIMAR; especially since the project’s


analysis on logical consistency of the data shows that it is
accurate.
Completeness: An assessment of the completeness to identify gaps in the data.
Description may include spatial data coverage, attribute data
coverage.
To investigate with MIDIMAR.
Currentness: Refers to the original data source, e.g. date when an aerial
photography was taken or publication date of a map or when a
field survey was conducted to capture the features.
N/A
Lineage: Information about the sources of data used to construct the data
set and steps used to process the data. For each processing step
provide (where possible) the following: source data name, source
data scale, source data date, description of processing step
performed.
The dataset was digitised from an existing basemap showing
“Flood and landslide risk regions”.
User Scales, etc.
Constraints: Positional accuracy acceptable for maps of scale ≤ 1:50,000.

Data
Organisation
Information
Data Format Format in which the data reside, e.g. Personal Geodatabase,
Name: Shapefile, dBase, Excel, etc.
Shapefile.
Spatial Object Description of the types of geographic features and their
Type: representation, e.g. Raster, Vector (point, line, polygon).
The spatial data is in vector form and re-presented as a polygon
feature.
Data Reference
Information
Coordinate The scheme used for coordinates, e.g. Transverse Mercator, Lo27.
System: Transverse Mercator

Datum: The datum used in the coordinate system, e.g. Cape or Hart 94.
WGS_1984.

Distance Units: The horizontal distance units, i.e., meters.


Meters.

Language The language used in the Dataset; English, French, Kinyarwanda


or combined.
English.
Entity and A summary of the information contained within the data set,
Attribute reference must be made to the NLC data dictionary.
Information:

Contact
Information
Contact Person: A person who can receive inquiries regarding the contents and
distribution of the data.
In the ideal situation, it will be the same individual as stated under
“contact information” under “Metadata Reference”.
MIDIMAR.

50124207.doc Page 14 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer Format The name of the format(s) in which the distributor will make the
Name data available. The user may list as many formats as desired.
and/or Lineage: Shapefiles, geopdf, jpg, xls, dbf.

50124207.doc Page 15 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Metadata
Identification
Description
Title: Title should include theme and location.
LAVA RISKS; D\CENTRAL GOVERNMENT\03_EN\02_NATURAL
HAZARDS\GIS\Natural Hazards Risks.
File name: The name of the file.
Lava Risk.
Custodian: The organisation responsible for having created the data and has
the responsibility to maintain and update.
Swedesurvey-NLC
Abstract: A short description or summary of the contents of the data,
including the original data source. Preferably also an explanation
of why the data was created.
The shape file is a geometrical Polygon feature that shows Lava
Risk in Rubavu in the Republic of Rwanda.
Theme, Common-use word or phrase used to describe the subject of the
Keywords: data set.
Lava risks, Natural hazards, Environment.
Metadata
Reference
Contact Details about the person who has created the metadata; name of
Information: Individual and Organization, email address, the role in the
Organization.
Name: Umuraza Angeline.
Organization: Swedesurvey
E-mail address:angeloa33@yahoo.fr
Role: GIS Technician.
Date: The date when the metadata was created.
October, 2010.
Data Quality
Information
Date of Insert the date when the dataset was prepared.
Capture: 2010

Positional Assessment of the expected error or range of error, of the data


Accuracy: objects location. Described as the difference (in meters) between
measured quantities and true positions (horizontal and vertical
when applicable). Method to assess depends on data type, e.g.,
RMS for image and grid data, GPS techniques. If accuracy cannot
be precisely determined, an intuitive accuracy based on
experience may be acceptable.
To investigate with MIDIMAR.
Attribute Assessment of values or attributes assigned to features in the
Accuracy: data in relation to the reality. Attribute accuracy can be described
as percentage of correct or incorrect values of attributes. Usually
based on a sample of the data (through field checks or through
comparing to separate data source).
The shape file does not have an active attribute table.
Logical A statement whether data has been checked and corrected for
Consistency: topological errors, i.e. logical relationship between features of the
data. For example, duplicate lines, labelling, enclosed polygon and
boundaries. Logical consistency does not apply to raster data.
The project’s analysis on logical consistency of the data shows

50124207.doc Page 16 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

that it is accurate.
Completeness: An assessment of the completeness to identify gaps in the data.
Description may include spatial data coverage, attribute data
coverage.
N/A
Currentness: Refers to the original data source, e.g. date when an aerial
photography was taken or publication date of a map or when a
field survey was conducted to capture the features.
N/A
Lineage: Information about the sources of data used to construct the data
set and steps used to process the data. For each processing step
provide (where possible) the following: source data name, source
data scale, source data date, description of processing step
performed.
The dataset was digitised from an existing basemap showing
“probability of Lava flow invasion in Rubavu District”.
User Scales, etc.
Constraints: Positional accuracy acceptable for maps of scale ≤ 1:50,000.

Data
Organisation
Information
Data Format Format in which the data reside, e.g. Personal Geodatabase,
Name: Shapefile, dBase, Excel, etc.
Shapefile.
Spatial Object Description of the types of geographic features and their
Type: representation, e.g. Raster, Vector (point, line, polygon).
The spatial data is in vector form and re-presented as a polygon
feature.

Data Reference
Information
Coordinate The scheme used for coordinates, e.g. Transverse Mercator, Lo27.
System: Transverse Mercator

Datum: The datum used in the coordinate system, e.g. Cape or Hart 94.
WGS_1984.

Distance Units: The horizontal distance units, i.e., meters.


Meters.

Language The language used in the Dataset; English, French, Kinyarwanda


or combined.
English.
Entity and A summary of the information contained within the data set,
Attribute reference must be made to the NLC data dictionary.
Information:

Contact
Information
Contact Person: A person who can receive inquiries regarding the contents and
distribution of the data.
In the ideal situation, it will be the same individual as stated under
“contact information” under “Metadata Reference”.
MIDIMAR.

50124207.doc Page 17 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer Format The name of the format(s) in which the distributor will make the
Name data available. The user may list as many formats as desired.
and/or Lineage: Shapefiles,geopdf,jpg,xls,dbf.

50124207.doc Page 18 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Metadata
Identification
Description
Title: Title should include theme and location.
FAULT LINES; D\CENTRAL GOVERNMENT\03_EN\02_NATURAL
HAZARDS\GIS\Natural Hazards Risks.
File name: The name of the file.
Fault_Rda.
Custodian: The organisation responsible for having created the data and has
the responsibility to maintain and update.
Swedesurvey-NLC
Abstract: A short description or summary of the contents of the data,
including the original data source. Preferably also an explanation
of why the data was created.
The shape file is a geometrical Polygon feature that shows Fault
line in the Republic of Rwanda.
Theme, Common-use word or phrase used to describe the subject of the
Keywords: data set.
Fault line, Natural hazards, Environment.
Metadata
Reference
Contact Details about the person who has created the metadata; name of
Information: Individual and Organization, email address, the role in the
Organization.
Name: Umuraza Angeline.
Organization: Swedesurvey
E-mail address: angeloa33@yahoo.fr
Role: GIS Technician.
Date: The date when the metadata was created.
October, 2010.
Data Quality
Information
Date of Insert the date when the dataset was prepared.
Capture: 2010

Positional Assessment of the expected error or range of error, of the data


Accuracy: objects location. Described as the difference (in meters) between
measured quantities and true positions (horizontal and vertical
when applicable). Method to assess depends on data type, e.g.,
RMS for image and grid data, GPS techniques. If accuracy cannot
be precisely determined, an intuitive accuracy based on
experience may be acceptable.
This need to be certified by MIDIMAR.
Attribute Assessment of values or attributes assigned to features in the
Accuracy: data in relation to the reality. Attribute accuracy can be described
as percentage of correct or incorrect values of attributes. Usually
based on a sample of the data (through field checks or through
comparing to separate data source).
The shape file does not have an active attribute table.
Logical A statement whether data has been checked and corrected for
Consistency: topological errors, i.e. logical relationship between features of the
data. For example, duplicate lines, labelling, enclosed polygon and
boundaries. Logical consistency does not apply to raster data.
The project’s analysis on logical consistency of the data shows

50124207.doc Page 19 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

that it is accurate.
Completeness: An assessment of the completeness to identify gaps in the data.
Description may include spatial data coverage, attribute data
coverage.
N/A
Currentness: Refers to the original data source, e.g. date when an aerial
photography was taken or publication date of a map or when a
field survey was conducted to capture the features.
N/A
Lineage: Information about the sources of data used to construct the data
set and steps used to process the data. For each processing step
provide (where possible) the following: source data name, source
data scale, source data date, description of processing step
performed.
The dataset was digitised from an existing basemap showing
“fault line”.
User Scales, etc.
Constraints: Positional accuracy acceptable for maps of scale ≤ 1:50,000.

Data
Organisation
Information
Data Format Format in which the data reside, e.g. Personal Geodatabase,
Name: Shapefile, dBase, Excel, etc.
Shapefile.
Spatial Object Description of the types of geographic features and their
Type: representation, e.g. Raster, Vector (point, line, polygon).
The spatial data is in vector form and re-presented as a polygon
feature.

Data Reference
Information
Coordinate The scheme used for coordinates, e.g. Transverse Mercator, Lo27.
System: Transverse Mercator

Datum: The datum used in the coordinate system, e.g. Cape or Hart 94.
WGS_1984.

Distance Units: The horizontal distance units, i.e., meters.


Meters.

Language The language used in the Dataset; English, French, Kinyarwanda


or combined.
English.
Entity and A summary of the information contained within the data set,
Attribute reference must be made to the NLC data dictionary.
Information:

Contact
Information
Contact Person: A person who can receive inquiries regarding the contents and
distribution of the data.
In the ideal situation, it will be the same individual as stated under
“contact information” under “Metadata Reference”.
MIDIMAR.

50124207.doc Page 20 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer Format The name of the format(s) in which the distributor will make the
Name data available. The user may list as many formats as desired.
and/or Lineage: Shapefiles, geopdf, jpg, xls, dbf.

50124207.doc Page 21 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Metadata
Identification
Description
Title: Title should include theme and location.
EARTHQUAKE RISKS; D\CENTRAL
GOVERNMENT\03_EN\02_NATURAL HAZARDS\GIS\Natural Hazards
Risks.
File name: The name of the file.
EarthquakeRisk_Rda.
Custodian: The organisation responsible for having created the data and has
the responsibility to maintain and update.
Swedesurvey-NLC
Abstract: A short description or summary of the contents of the data,
including the original data source. Preferably also an explanation
of why the data was created.
The shape file is a geometrical Polygon feature that shows
Earthquake risk region in the Republic of Rwanda.
Theme, Common-use word or phrase used to describe the subject of the
Keywords: data set.
Earthquake Risks, Environment, Natural hazards.
Metadata
Reference
Contact Details about the person who has created the metadata; name of
Information: Individual and Organization, email address, the role in the
Organization.
Name: Umuraza Angeline.
Organization: Swedesurvey
E-mail address:angeloa33@yahoo.fr
Role: GIS Technician.
Date: The date when the metadata was created.
October, 2010.
Data Quality
Information
Date of Insert the date when the dataset was prepared.
Capture: 2010

Positional Assessment of the expected error or range of error, of the data


Accuracy: objects location. Described as the difference (in meters) between
measured quantities and true positions (horizontal and vertical
when applicable). Method to assess depends on data type, e.g.,
RMS for image and grid data, GPS techniques. If accuracy cannot
be precisely determined, an intuitive accuracy based on
experience may be acceptable.
This need to be certified by MIDIMAR.
Attribute Assessment of values or attributes assigned to features in the
Accuracy: data in relation to the reality. Attribute accuracy can be described
as percentage of correct or incorrect values of attributes. Usually
based on a sample of the data (through field checks or through
comparing to separate data source).
The shape file does not have an active attribute table.
Logical A statement whether data has been checked and corrected for
Consistency: topological errors, i.e. logical relationship between features of the
data. For example, duplicate lines, labelling, enclosed polygon and
boundaries. Logical consistency does not apply to raster data.

50124207.doc Page 22 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

The project’s analysis on logical consistency of the data shows


that it is accurate.
Completeness: An assessment of the completeness to identify gaps in the data.
Description may include spatial data coverage, attribute data
coverage.
N/A
Currentness: Refers to the original data source, e.g. date when an aerial
photography was taken or publication date of a map or when a
field survey was conducted to capture the features.
N/A
Lineage: Information about the sources of data used to construct the data
set and steps used to process the data. For each processing step
provide (where possible) the following: source data name, source
data scale, source data date, description of processing step
performed.
The dataset was digitised from an existing basemap showing
“Earthquake risk”.
User Scales, etc.
Constraints: Positional accuracy acceptable for maps of scale ≤ 1:50,000.

Data
Organisation
Information
Data Format Format in which the data reside, e.g. Personal Geodatabase,
Name: Shapefile, dBase, Excel, etc.
Shapefile.
Spatial Object Description of the types of geographic features and their
Type: representation, e.g. Raster, Vector (point, line, polygon).
The spatial data is in vector form and re-presented as a point
feature.

Data Reference
Information
Coordinate The scheme used for coordinates, e.g. Transverse Mercator, Lo27.
System: Transverse Mercator.

Datum: The datum used in the coordinate system, e.g. Cape or Hart 94.
WGS_1984.

Distance Units: The horizontal distance units, i.e., meters.


Meters.

Language The language used in the Dataset; English, French, Kinyarwanda


or combined.
English.
Entity and A summary of the information contained within the data set,
Attribute reference must be made to the NLC data dictionary.
Information:

Contact
Information
Contact Person: A person who can receive inquiries regarding the contents and
distribution of the data.
In the ideal situation, it will be the same individual as stated under
“contact information” under “Metadata Reference”.
MIDIMAR.

50124207.doc Page 23 of 24 11-01-23


SWEDESURVEY GIS STRATEGY FOR
RLUDMP

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer Format The name of the format(s) in which the distributor will make the
Name data available. The user may list as many formats as desired.
and/or Lineage: Shapefiles, geopdf, jpg, xls, dbf.

50124207.doc Page 24 of 24 11-01-23

You might also like