metadata infrastructure

8/7/2019 Metadata Infrastructure

1/35

SWEDESURVEY GIS STRATEGYFOR

RLUDMP

Metadata specification for Infrastructure feature class

I. AIRPORTS

MetadataIdentification

Description

Title: Title should include theme and location.AIRPORTS;D\CENTRALGOVERNMENT\02_IS\01_TRANSPORTATION\GIS\Airports

File name: The name of the file.Airports.

Custodian: The organisation responsible for having created the data andhas the responsibility to maintain and update.

Swedesurvey-NLCAbstract: A short description or summary of the contents of the data,including the original data source. Preferably also anexplanation of why the data was created.The shape file is a geometrical point feature that showsairports in the Republic of Rwanda.

Theme,Keywords:

Common-use word or phrase used to describe the subject ofthe data set.Airport.

MetadataReference

Contact

Information:

Details about the person who has created the metadata; name

of Individual and Organization, email address, the role in theOrganization.Name: Umuraza Angeline,Organization: SwedesurveyE-mail address: [email protected]: GIS Technician.

Date:

The date when the metadata was created.October, 2010.

Data QualityInformation

Date ofCapture:

Insert the date when the dataset was prepared.March, 2010.

PositionalAccuracy:

Assessment of the expected error or range of error, of the dataobjects location. Described as the difference (in meters)between measured quantities and true positions (horizontaland vertical when applicable). Method to assess depends ondata type, e.g., RMS for image and grid data, GPS techniques.If accuracy cannot be precisely determined, an intuitiveaccuracy based on experience may be acceptable.The projects analysis on positional accuracy of the data showsthat it is accurate.

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can be

described as percentage of correct or incorrect values ofattributes. Usually based on a sample of the data (through field

50124211.doc Page 1 of 35 11-01-23


2/35


RLUDMP

checks or through comparing to separate data source).100% accurate; the attribute file contains place names, runwaytype and length, town of location and type of airport.

LogicalConsistency:

A statement whether data has been checked and corrected fortopological errors, i.e. logical relationship between features of

the data. For example, duplicate lines, labelling, enclosedpolygon and boundaries. Logical consistency does not apply toraster data.The point features are unique and independently placed.

Completeness: An assessment of the completeness to identify gaps in thedata. Description may include spatial data coverage, attributedata coverage.The dataset is complete.

Currentness: Refers to the original data source, e.g. date when an aerialphotography was taken or publication date of a map or when afield survey was conducted to capture the features.The shapefile was digitized from orthophotos taken in 2008-2009.

Lineage: Information about the sources of data used to construct thedata set and steps used to process the data. For eachprocessing step provide (where possible) the following: sourcedata name, source data scale, source data date, description ofprocessing step performed.The shapefile was digitized from orthophotos taken in 2008-2009.

UserConstraints:

Scales, etc.Positional accuracy acceptable for maps of scale 1:50,000.

DataOrganisationInformation

Data FormatName:

Format in which the data reside, e.g. Personal Geodatabase,Shapefile, dBase, Excel, etc.Shapefile.

Spatial ObjectType:

Description of the types of geographic features and theirrepresentation, e.g. Raster, Vector (point, line, polygon).The spatial data is in vector form and re-presented as a pointfeature.

Data Reference

InformationCoordinate

System:

The scheme used for coordinates, e.g. Transverse Mercator,Lo27.Transverse Mercator

Datum: The datum used in the coordinate system, e.g. Cape or Hart94.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 andAttribute

A summary of the information contained within the data set,reference must be made to the NLC data dictionary.

50124211.doc Page 2 of 35 11-01-23


3/35


RLUDMP

Information:

ContactInformation

Contact Person: A person who can receive inquiries regarding the contents anddistribution of the data.In the ideal situation, it will be the same individual as statedunder contact information under Metadata Reference.N/A

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:

The name of the format(s) in which the distributor will makethe data available. The user may list as many formats asdesired.Shapefiles, geopdf, jpg, xls, dbf.


Description

Title: Title should include theme and location.PROPOSED NEW BUGESERA INTERNATIONAL AIRPORT;D\CENTRALGOVERNMENT\02_IS\01_TRANSPORTATION\GIS\Airports\Bugesera Airport_RTDA.

File name: The name of the file.New Bugs_Airport_RTDA

Custodian: The organisation responsible for having created the data andhas the responsibility to maintain and update.Ministry of Infrastructure/Swedesurvey-NLC

Abstract: A short description or summary of the contents of the data,including the original data source. Preferably also anexplanation of why the data was created.The shapefile is a geometrical polygon feature that shows theplanned new Bugesera airport in the Republic of Rwanda. The

original data set was collected from the Rwanda TransportDevelopment Agency (RTDA).

Theme,Keywords:

Common-use word or phrase used to describe the subject ofthe data set.Airport, Bugesera new airport.

MetadataReference

ContactInformation:

Details about the person who has created the metadata; nameof Individual and Organization, email address, the role in theOrganization.Name: Umuraza Angeline,Organization: Swedesurvey

E-mail address: [email protected]: GIS Technician.

Date: The date when the metadata was created.

50124211.doc Page 3 of 35 11-01-23


4/35


RLUDMP

October, 2010.


Date of

Capture:

Insert the date when the dataset was prepared.July, 2010.

PositionalAccuracy:

Assessment of the expected error or range of error, of the dataobjects location. Described as the difference (in meters)between measured quantities and true positions (horizontaland vertical when applicable). Method to assess depends ondata type, e.g., RMS for image and grid data, GPS techniques.If accuracy cannot be precisely determined, an intuitiveaccuracy based on experience may be acceptable.It is not yet known especially since the airport is still in aproposal format.

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can be

described as percentage of correct or incorrect values ofattributes. Usually based on a sample of the data (through fieldchecks or through comparing to separate data source).This is a planned project, it does not exist yet.

LogicalConsistency:

A statement whether data has been checked and corrected fortopological errors, i.e. logical relationship between features ofthe data. For example, duplicate lines, labelling, enclosedpolygon and boundaries. Logical consistency does not apply toraster data.This has to be certified by the Ministry of Infrastructure.

Completeness: An assessment of the completeness to identify gaps in thedata. Description may include spatial data coverage, attributedata coverage.The data will require to be updated when the finalimplementation is complete.

50124211.doc Page 4 of 35 11-01-23


5/35


RLUDMP

Currentness: Refers to the original data source, e.g. date when an aerialphotography was taken or publication date of a map or when afield survey was conducted to capture the features.The shapefile was digitized from an existing base map

prepared in 2006.Lineage: Information about the sources of data used to construct the

data set and steps used to process the data. For eachprocessing step provide (where possible) the following: sourcedata name, source data scale, source data date, description ofprocessing step performed.The shapefile was digitized from an existing basemap named:Surficial Geology of the proposed Kigali International Airport,provided by RTDA, and prepared in 2006.

UserConstraints:



Data FormatName:


Spatial ObjectType:

Description of the types of geographic features and theirrepresentation, e.g. Raster, Vector (point, line, polygon).The spatial data is in vector form and re-presented as apolygon feature.

Data Reference


System:





Entity andAttribute

Information:


ContactInformation


Office: N/A

Address: N/A

50124211.doc Page 5 of 35 11-01-23


6/35


RLUDMP

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:

The name of the format(s) in which the distributor will makethe data available.The user may list as many formats asdesired.Shapefiles, geopdf, jpg, xls, dbf.

50124211.doc Page 6 of 35 11-01-23


7/35


RLUDMP


Description

Title: Title should include theme and location.NEW BUGESERA INTERNATIONAL AIRPORT RUNWAY;D\CENTRALGOVERNMENT\02_IS\01_TRANSPORTATION\GIS\Airports\Bugesera Airport_RTDA.

File name: The name of the file.New Bugs_Airport_Runway_RTDA

Custodian: The organisation responsible for having created the data andhas the responsibility to maintain and update.Ministry of Infrastructure/Swedesurvey-NLC

Abstract: A short description or summary of the contents of the data,including the original data source. Preferably also anexplanation of why the data was created.

The shapefile is a geometrical polyline feature that shows theRunway of the planned new Bugesera international airport inthe Republic of Rwanda. The original data set was collectedfrom the Rwanda Transport Development Agency (RTDA).

Theme,Keywords:

Common-use word or phrase used to describe the subject ofthe data set.Runway, airport, new airport.

MetadataReference

ContactInformation:

Details about the person who has created the metadata; nameof Individual and Organization, email address, the role in theOrganization.

Name: Umuraza Angeline,Organization: SwedesurveyE-mail address:[email protected]: GIS Technician.

Date:



Date ofCapture:

Insert the date when the dataset was prepared.July, 2010.

PositionalAccuracy:

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

objects location. Described as the difference (in meters)between measured quantities and true positions (horizontaland vertical when applicable). Method to assess depends ondata type, e.g., RMS for image and grid data, GPS techniques.If accuracy cannot be precisely determined, an intuitiveaccuracy based on experience may be acceptable.It is not yet known especially since the airport is still in aproposal format.

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can bedescribed as percentage of correct or incorrect values ofattributes. Usually based on a sample of the data (through fieldchecks or through comparing to separate data source).This is a planned project, it does not exist yet.

Logical A statement whether data has been checked and corrected for

50124211.doc Page 7 of 35 11-01-23


8/35


RLUDMP

Consistency: topological errors, i.e. logical relationship between features ofthe data. For example, duplicate lines, labelling, enclosedpolygon and boundaries. Logical consistency does not apply toraster data.This has to be certified by the Ministry of Infrastructure.

Completeness: An assessment of the completeness to identify gaps in thedata. Description may include spatial data coverage, attributedata coverage.The data will require to be updated when the finalimplementation is complete.

Currentness: Refers to the original data source, e.g. date when an aerialphotography was taken or publication date of a map or when afield survey was conducted to capture the features.The shapefile was digitized from an existing base mapprepared in 2006.

Lineage: Information about the sources of data used to construct thedata set and steps used to process the data. For eachprocessing step provide (where possible) the following: sourcedata name, source data scale, source data date, description ofprocessing step performed.The shapefile was digitized from an existing basemap named:Surficial Geology of the proposed Kigali International Airport,provided by RTDA, and prepared in 2006.

UserConstraints:



Data FormatName:


Spatial ObjectType:

Description of the types of geographic features and theirrepresentation, e.g. Raster, Vector (point, line, polygon).The spatial data is in vector form and re-presented as apolyline feature.

Data ReferenceInformationCoordinate

System:

The scheme used for coordinates, e.g. Transverse Mercator,Lo27.Transverse Mercator.


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


Entity andAttribute

Information:


ContactInformation

50124211.doc Page 8 of 35 11-01-23


9/35


RLUDMP


Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:


50124211.doc Page 9 of 35 11-01-23


10/35


RLUDMP

II. RAILWAYMetadata

Identification DescriptionTitle: Title should include theme and location.

PROPOSED RAILWAY; D\CENTRALGOVERNMENT\02_IS\01_TRANSPORTATION\GIS\Railway

File name: The name of the file.Railway_WGS84_TM_RW

Custodian: The organisation responsible for having created the data andhas the responsibility to maintain and update.Ministry of Infrastructure

Abstract: A short description or summary of the contents of the data,including the original data source. Preferably also anexplanation of why the data was created.The shape file is a geometrical polyline feature that shows theproposed Railway in the Republic of Rwanda.

Theme,Keywords:

Common-use word or phrase used to describe the subject ofthe data set.Railway.

MetadataReference

ContactInformation:

Details about the person who has created the metadata; nameof Individual and Organization, email address, the role in theOrganization.Name: Umuraza Angeline,Organization: SwedesurveyE-mail address: [email protected]: GIS Technician.

Date:



Date ofCapture:

Insert the date when the dataset was prepared.N/A.

Positional

Accuracy:

Assessment of the expected error or range of error, of the dataobjects location. Described as the difference (in meters)between measured quantities and true positions (horizontaland vertical when applicable). Method to assess depends ondata type, e.g., RMS for image and grid data, GPS techniques.If accuracy cannot be precisely determined, an intuitiveaccuracy based on experience may be acceptable.It is not yet known especially since the railway line is still in aproposal format.

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can bedescribed as percentage of correct or incorrect values ofattributes. Usually based on a sample of the data (through fieldchecks or through comparing to separate data source).

This is a proposed line, it does not exist yet.Logical A statement whether data has been checked and corrected for

topological errors, i.e. logical relationship between features of

50124211.doc Page 10 of 35 11-01-23


11/35


RLUDMP

Consistency: the data. For example, duplicate lines, labelling, enclosedpolygon and boundaries. Logical consistency does not apply toraster data.This has to be certified by the Ministry of Infrastructure.

50124211.doc Page 11 of 35 11-01-23


12/35


RLUDMP

Completeness: An assessment of the completeness to identify gaps in thedata. Description may include spatial data coverage, attributedata coverage.The data will require to be updated when the final

implementation is 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 afield survey was conducted to capture the features.N/A

Lineage: Information about the sources of data used to construct thedata set and steps used to process the data. For eachprocessing step provide (where possible) the following: sourcedata name, source data scale, source data date, description ofprocessing step performed.This needs to be crosschecked with the Ministry ofInfrastructure.

UserConstraints: Scales, etc.Positional accuracy acceptable for maps of scale 1:50,000.Scale of data capture is not known.


Data FormatName:


Spatial ObjectType:

Description of the types of geographic features and theirrepresentation, e.g. Raster, Vector (point, line, polygon).The spatial data is in vector form and re-presented as a

polyline feature.


System:





Entity andAttribute

Information:


ContactInformation

Contact Person: A person who can receive inquiries regarding the contents anddistribution of the data.In the ideal situation, it will be the same individual as stated

under contact information under Metadata Reference.Ministry of Infrastructure.

50124211.doc Page 12 of 35 11-01-23


13/35


RLUDMP

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:


50124211.doc Page 13 of 35 11-01-23


14/35


RLUDMP

I II. ROADS.Metadata

Identification DescriptionTitle: Title should include theme and location.

ROAD NETWORK;D\CENTRALGOVERNMENT\02_IS\01_TRANSPORTATION\GIS\Roads_Merged.

File name: The name of the file.Road_Merge

Custodian: The organisation responsible for having created the data andhas the responsibility to maintain and update.Ministry of Infrastructure/NLC-Swedesurvey.

Abstract: A short description or summary of the contents of the data,including the original data source. Preferably also anexplanation of why the data was created.The shapefile is a geometrical polyline feature that shows theroad network of the Republic of Rwanda.

Theme,Keywords:

Common-use word or phrase used to describe the subject ofthe data set.Roads.

MetadataReference

ContactInformation:

Details about the person who has created the metadata; nameof Individual and Organization, email address, the role in theOrganization.Name: Umuraza Angeline,Organization: SwedesurveyE-mail address:[email protected]: GIS Technician.

Date:



Date ofCapture:

Insert the date when the dataset was prepared.2010.

PositionalAccuracy:


AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can bedescribed as percentage of correct or incorrect values ofattributes. Usually based on a sample of the data (through fieldchecks or through comparing to separate data source).The attribute data include classifications for the different

categories and nature of roads. However, some roadconditions may have changed and this will require to beupdated.

50124211.doc Page 14 of 35 11-01-23


15/35


RLUDMP

LogicalConsistency:

A statement whether data has been checked and corrected fortopological errors, i.e. logical relationship between features ofthe data. For example, duplicate lines, labelling, enclosedpolygon and boundaries. Logical consistency does not apply toraster data.

The projects analysis on logical consistency of the data showsthat it is accurate.

Completeness: An assessment of the completeness to identify gaps in thedata. Description may include spatial data coverage, attributedata coverage.The dataset will require to be updated.

Currentness: Refers to the original data source, e.g. date when an aerialphotography was taken or publication date of a map or when afield survey was conducted to capture the features.The file was originally digitized from the existing base mapswhich were derived from an aerial photo campaign in 1992.Recent roads added through NLC were digitized fromorthophotos taken in 2008-2009.

Lineage: Information about the sources of data used to construct thedata set and steps used to process the data. For eachprocessing step provide (where possible) the following: sourcedata name, source data scale, source data date, description ofprocessing step performed.The file was originally digitized from the existing base maps atthe scale of 1:50000, which were derived from an aerial photocampaign in 1992. The dataset has been updated by digitizingnew roads, from orthophotos taken in 2008-2009.

User

Constraints:

Scales, etc.

Positional accuracy acceptable for maps of scale 1:50,000.Scale of data capture is 1:50,000.


Data FormatName:


Spatial ObjectType:



System:




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

Kinyarwanda or combined.English.

50124211.doc Page 15 of 35 11-01-23


16/35


RLUDMP

Entity andAttribute

Information:

A summary of the information contained within the data set,reference must be made to the NLC data dictionary.Unique ID for road, Road classification: National; district;sector.

ContactInformationContact 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 statedunder contact information under Metadata Reference.Ministry of Infrastructure/NLC-Swedesurvey.

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:



Description

Title: Title should include theme and location.PROPOSED NEW OR IMPROVEMENT OF NATIONAL ANDDISTRICT ROAD,D\CENTRALGOVERNMENT\02_IS\01_TRANSPORTATION\GIS\Proposed roadsimprovement.

File name: The name of the file.Road_Imprv_Merge.

Custodian: The organisation responsible for having created the data andhas the responsibility to maintain and update.NLC-Swedesurvey.

Abstract: A short description or summary of the contents of the data,including the original data source. Preferably also anexplanation of why the data was created.

The shape file is a geometrical polyline feature that showsproposed new or improvement of national and district road inthe Republic of Rwanda.

Theme,Keywords:

Common-use word or phrase used to describe the subject ofthe data set.Roads.

MetadataReference

ContactInformation:

Details about the person who has created the metadata; nameof Individual and Organization, email address, the role in theOrganization.Name: Umuraza Angeline,

Organization: SwedesurveyE-mail address: [email protected]: GIS Technician.

50124211.doc Page 16 of 35 11-01-23


17/35


RLUDMP

Date:



Date ofCapture: Insert the date when the dataset was prepared.N/A.

PositionalAccuracy:


AttributeAccuracy:

Assessment of values or attributes assigned to features in the

data in relation to the reality. Attribute accuracy can bedescribed as percentage of correct or incorrect values ofattributes. Usually based on a sample of the data (through fieldchecks or through comparing to separate data source).The projects analysis on attribute accuracy of the data showsthat it is accurate.

LogicalConsistency:

A statement whether data has been checked and corrected fortopological errors, i.e. logical relationship between features ofthe data. For example, duplicate lines, labelling, enclosedpolygon and boundaries. Logical consistency does not apply toraster data.The projects analysis on logical consistency of the data showsthat it is accurate.

Completeness: An assessment of the completeness to identify gaps in thedata. Description may include spatial data coverage, attributedata coverage.The data will require to be updated.

Currentness: Refers to the original data source, e.g. date when an aerialphotography was taken or publication date of a map or when afield survey was conducted to capture the features.The shapefile was prepared from an existing base maps at thescale of 1:50000, which were derived from an aerial photocampaign in 1992. Recent roads added through NLC wasdigitized from orthophotos taken in 2008-2009.

Lineage: Information about the sources of data used to construct the

data set and steps used to process the data. For eachprocessing step provide (where possible) the following: sourcedata name, source data scale, source data date, description ofprocessing step performed.The shapefile was prepared from an existing base maps at thescale of 1:50000, which were derived from an aerial photocampaign in 1992. Recent roads added through NLC wasdigitized from orthophotos taken in 2008-2009.

UserConstraints:

Scales, etc.Positional accuracy acceptable for maps of scale 1:50,000.Scale of data capture is 1:50,000.

Data

OrganisationInformation

50124211.doc Page 17 of 35 11-01-23


18/35


RLUDMP

Data FormatName:


Spatial Object

Type:



System:


Datum: The datum used in the coordinate system, e.g. Cape or Hart94.ITRF_2000.



Entity andAttribute

Information:

A summary of the information contained within the data set,reference must be made to the NLC data dictionary.Unique ID for road, Road classification: National; district;sector.

ContactInformation

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 statedunder contact information under Metadata Reference.Ministry of Infrastructure.

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:


50124211.doc Page 18 of 35 11-01-23


19/35


RLUDMP

VI. POWER SUPPLY.

MetadataIdentification Description

Title: Title should include theme and location.POWER PLANTS; D\CENTRAL GOVERNMENT\02_IS\04_POWER(SUPPLY & NETWORK)\GIS\Power plants.

File name: The name of the file.Power Plant.

Custodian: The organisation responsible for having created the data andhas 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 anexplanation of why the data was created.The shapefile is a geometric point feature that shows powerPlants in the Republic of Rwanda.

Theme,Keywords:

Common-use word or phrase used to describe the subject ofthe data set.Electricity, Power Plants.

MetadataReference

ContactInformation:

Details about the person who has created the metadata; nameof Individual and Organization, email address, the role in theOrganization.Name: Umuraza Angeline,Organization: SwedesurveyE-mail address: [email protected]: GIS Technician.

Date:



Date ofCapture:

Insert the date when the dataset was prepared.March,2010

PositionalAccuracy:

Assessment of the expected error or range of error, of the dataobjects location. Described as the difference (in meters)between measured quantities and true positions (horizontaland vertical when applicable). Method to assess depends ondata type, e.g., RMS for image and grid data, GPS techniques.If accuracy cannot be precisely determined, an intuitiveaccuracy based on experience may be acceptable.This has to be certified by RECO; especially since the projectsanalysis on positional accuracy of the data shows that it isaccurate.

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can bedescribed as percentage of correct or incorrect values ofattributes. Usually based on a sample of the data (through field

checks or through comparing to separate data source).This has to be certified by RECO; especially since the projectsanalysis on attribute accurracy of the data shows that it is

50124211.doc Page 19 of 35 11-01-23


20/35


RLUDMP

accurate.

LogicalConsistency:

A statement whether data has been checked and corrected fortopological errors, i.e. logical relationship between features ofthe data. For example, duplicate lines, labelling, enclosed

polygon and boundaries. Logical consistency does not apply toraster data.The point features are unique and independently placed.

Completeness: An assessment of the completeness to identify gaps in thedata. Description may include spatial data coverage, attributedata coverage.The dataset is not complete. Some power plants are missing.

Currentness: Refers to the original data source, e.g. date when an aerialphotography was taken or publication date of a map or when afield survey was conducted to capture the features.2009.

Lineage: Information about the sources of data used to construct thedata set and steps used to process the data. For eachprocessing step provide (where possible) the following: sourcedata name, source data scale, source data date, description ofprocessing step performed.The Shapefile was digitised from orthophotos taken in 2008-2009.

UserConstraints:



Data FormatName:


Spatial ObjectType:

Description of the types of geographic features and theirrepresentation, e.g. Raster, Vector (point, line, polygon).The spatial data is in vector form and re-presented as a pointfeature.


System:





Entity andAttribute

Information:


ContactInformation

50124211.doc Page 20 of 35 11-01-23


21/35


RLUDMP

Contact Person: A person who can receive inquiries regarding the contents anddistribution of the data.In the ideal situation, it will be the same individual as statedunder contact information under Metadata Reference.RECO.

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:

The name of the format(s) in which the distributor will makethe data available.The user may list as many formats asdesired.Shapefiles, geopdf, jpg,xls, dbf.


Description

Title: Title should include theme and location.POWER LINES; D\CENTRAL GOVERNMENT\02_IS\04_POWER(SUPPLY & NETWORK)\GIS\Powerlines & Transfomers.

File name: The name of the file.Power Line Merged.

Custodian: The organisation responsible for having created the data andhas the responsibility to maintain and update.

Rwanda Electricity Corporation (RECO).Abstract: A short description or summary of the contents of the data,

including the original data source. Preferably also anexplanation of why the data was created.The shapefile is a geometric polyline feature that shows powerlines in the Republic of Rwanda. Only the medium and highvoltage lines are shown. The shapefile was prepared bymerging shapefile prepared in 1988 with another prepared in2008.

Theme,Keywords:

Common-use word or phrase used to describe the subject ofthe data set.Power lines, Electricity.

MetadataReferenceContact

Information:

Details about the person who has created the metadata; nameof Individual and Organization, email address, the role in theOrganization.Name: Umuraza Angeline,Organization: SwedesurveyE-mail address:[email protected]: GIS Technician.

Date:


Data Quality

InformationDate of Insert the date when the dataset was prepared.1988; 2008.

50124211.doc Page 21 of 35 11-01-23


22/35


RLUDMP

Capture:

PositionalAccuracy:

Assessment of the expected error or range of error, of the dataobjects location. Described as the difference (in meters)between measured quantities and true positions (horizontaland vertical when applicable). Method to assess depends ondata type, e.g., RMS for image and grid data, GPS techniques.If accuracy cannot be precisely determined, an intuitiveaccuracy based on experience may be acceptable.Need to be crosschecked with RECO.

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can bedescribed as percentage of correct or incorrect values ofattributes. Usually based on a sample of the data (through fieldchecks or through comparing to separate data source).Need to be crosschecked with RECO.

Logical

Consistency:

A statement whether data has been checked and corrected for

topological errors, i.e. logical relationship between features ofthe data. For example, duplicate lines, labelling, enclosedpolygon and boundaries. Logical consistency does not apply toraster data.Need to be crosschecked with RECO.

Completeness: An assessment of the completeness to identify gaps in thedata. Description may include spatial data coverage, attributedata coverage.Need to be updated.

Currentness: Refers to the original data source, e.g. date when an aerialphotography was taken or publication date of a map or when afield survey was conducted to capture the features.1988,2008.

Lineage: Information about the sources of data used to construct thedata set and steps used to process the data. For eachprocessing step provide (where possible) the following: sourcedata name, source data scale, source data date, description ofprocessing step performed.Some power lines were digitized from the georeferenced1:50'000 topo maps (tif) from 1988 at a scale of1:15'000.Others were collected by RECO staff using GarminGPSmap60 handhelds (with +/-10m of accuracy).

UserConstraints:



Data FormatName:


Spatial ObjectType:


Data ReferenceInformation

CoordinateSystem:

The scheme used for coordinates, e.g. Transverse Mercator,Lo27.

50124211.doc Page 22 of 35 11-01-23


23/35


RLUDMP

Transverse Mercator.




Entity andAttribute

Information:


ContactInformation


Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:


50124211.doc Page 23 of 35 11-01-23


24/35


RLUDMP


Description

Title: Title should include theme and location.PLANNED POWER LINES; D\CENTRALGOVERNMENT\02_IS\04_POWER (SUPPLY &NETWORK)\GIS\Powerlines & Transfomers.

File name: The name of the file.Electrogaz_planned_powerlines1.

Custodian: The organisation responsible for having created the data andhas the responsibility to maintain and update.Rwanda Electricity Corporation (RECO).

Abstract: A short description or summary of the contents of the data,including the original data source. Preferably also anexplanation of why the data was created.The shape file is a geometric polyline feature that shows

planned power lines in the Republic of Rwanda.Theme,

Keywords:

Common-use word or phrase used to describe the subject ofthe data set.Planned Power lines, Electricity.

MetadataReference

ContactInformation:

Details about the person who has created the metadata; nameof Individual and Organization, email address, the role in theOrganization.Name: Umuraza Angeline,Organization: SwedesurveyE-mail address: [email protected]

Role: GIS Technician.Date:



Date ofCapture:

Insert the date when the dataset was prepared.N/A.

PositionalAccuracy:

Assessment of the expected error or range of error, of the dataobjects location. Described as the difference (in meters)between measured quantities and true positions (horizontaland 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 intuitiveaccuracy based on experience may be acceptable.Need to be crosschecked with RECO.

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can bedescribed as percentage of correct or incorrect values ofattributes. Usually based on a sample of the data (through fieldchecks or through comparing to separate data source).Need to be crosschecked with RECO.

LogicalConsistency:


the data. For example, duplicate lines, labelling, enclosedpolygon and boundaries. Logical consistency does not apply toraster data.

50124211.doc Page 24 of 35 11-01-23


25/35


RLUDMP

Need to be crosschecked with RECO.

Completeness: An assessment of the completeness to identify gaps in thedata. Description may include spatial data coverage, attributedata coverage.Need to be updated.

Currentness: Refers to the original data source, e.g. date when an aerialphotography was taken or publication date of a map or when afield survey was conducted to capture the features.N/A.

Lineage: Information about the sources of data used to construct thedata set and steps used to process the data. For eachprocessing step provide (where possible) the following: sourcedata name, source data scale, source data date, description ofprocessing step performed.N/A

UserConstraints:



Data FormatName:


Spatial ObjectType:


Data Reference


System:





Entity andAttribute

Information:


ContactInformation


Office: N/A

Address: N/A

50124211.doc Page 25 of 35 11-01-23


26/35


RLUDMP

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:

The name of the format(s) in which the distributor will makethe data available.The user may list as many formats asdesired.Shapefiles,geopdf,jpg,xls,dbf.

50124211.doc Page 26 of 35 11-01-23


27/35


RLUDMP


Description

Title: Title should include theme and location.GEOTHERMAL POTENTIALS; D\CENTRALGOVERNMENT\02_IS\04_POWER (SUPPLY &NETWORK)\GIS\Sites for potential development of energy.

File name: The name of the file.Geothermal Resources.

Custodian: The organisation responsible for having created the data andhas 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 anexplanation of why the data was created.The shapefile shows Geothermal potential site for development

of energy in the Republic of Rwanda.Theme,

Keywords:

Common-use word or phrase used to describe the subject ofthe data set.Geothermal resources, Energy potential.

MetadataReference

ContactInformation:





Date ofCapture:


PositionalAccuracy:


data type, e.g., RMS for image and grid data, GPS techniques.If accuracy cannot be precisely determined, an intuitiveaccuracy based on experience may be acceptable.Need to be crosschecked with RECO

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can bedescribed as percentage of correct or incorrect values ofattributes. Usually based on a sample of the data (through fieldchecks or through comparing to separate data source).To investigate with RECO

LogicalConsistency:



50124211.doc Page 27 of 35 11-01-23


28/35


RLUDMP

The point features are unique and independently placed.

Completeness: An assessment of the completeness to identify gaps in thedata. Description may include spatial data coverage, attributedata coverage.To investigate with RECO


Lineage: Information about the sources of data used to construct thedata set and steps used to process the data. For eachprocessing step provide (where possible) the following: sourcedata name, source data scale, source data date, description ofprocessing step performed.The Dataset was digitised from an existing base of principalsources for potential development of energy. Its preparationdate is unknown.

UserConstraints:



Data FormatName:


Spatial ObjectType:

Description of the types of geographic features and theirrepresentation, e.g. Raster, Vector (point, line, polygon).The spatial data is in vector form and re-presented as a point

feature.Data Reference


System:






Entity andAttribute

Information:


ContactInformation

Contact Person: A person who can receive inquiries regarding the contents anddistribution of the data.In the ideal situation, it will be the same individual as statedunder contact information under Metadata Reference.

RECO.Office: N/A

50124211.doc Page 28 of 35 11-01-23


29/35


RLUDMP

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:


50124211.doc Page 29 of 35 11-01-23


30/35


RLUDMP


Description

Title: Title should include theme and location.HYDROPOWER POTENTIALS; D\CENTRALGOVERNMENT\02_IS\04_POWER (SUPPLY &NETWORK)\GIS\Sites for potential development of energy.

File name: The name of the file.Hydropower.

Custodian: The organisation responsible for having created the data andhas 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 anexplanation of why the data was created.The Dataset shows Hydropower potential sites for development

of energy in the Republic of Rwanda.

Theme,Keywords:

Common-use word or phrase used to describe the subject ofthe data set.Hydropower, Energy potential.

MetadataReference

ContactInformation:

Details about the person who has created the metadata; nameof Individual and Organization, email address, the role in theOrganization.Name: Umuraza Angeline,

Organization: SwedesurveyE-mail address:[email protected]: GIS Technician.

Date:



Date ofCapture:


PositionalAccuracy:

Assessment of the expected error or range of error, of the dataobjects location. Described as the difference (in meters)

between measured quantities and true positions (horizontaland vertical when applicable). Method to assess depends ondata type, e.g., RMS for image and grid data, GPS techniques.If accuracy cannot be precisely determined, an intuitiveaccuracy based on experience may be acceptable.Need to be crosschecked with RECO

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can bedescribed as percentage of correct or incorrect values ofattributes. Usually based on a sample of the data (through fieldchecks or through comparing to separate data source).Need to be crosschecked with RECO

LogicalConsistency:

A statement whether data has been checked and corrected for

topological errors, i.e. logical relationship between features ofthe data. For example, duplicate lines, labelling, enclosed

50124211.doc Page 30 of 35 11-01-23


31/35


RLUDMP

polygon and boundaries. Logical consistency does not apply toraster data.The point features are unique and independently placed.

Completeness: An assessment of the completeness to identify gaps in thedata. Description may include spatial data coverage, attribute

data coverage.To investigate with RECO



UserConstraints:



Data FormatName:


Spatial Object

Type:

Description of the types of geographic features and their

representation, e.g. Raster, Vector (point, line, polygon).The spatial data is in vector form and re-presented as a pointfeature.


System:



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

Meters.Language The language used in the Dataset; English, French,


Entity andAttribute

Information:


ContactInformation

Contact Person: A person who can receive inquiries regarding the contents anddistribution of the data.

In the ideal situation, it will be the same individual as statedunder contact information under Metadata Reference.

50124211.doc Page 31 of 35 11-01-23


32/35


RLUDMP

RECO.

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:


50124211.doc Page 32 of 35 11-01-23


33/35


RLUDMP


Description

Title: Title should include theme and location.METHANE GAS POTENTIALS IN LAKE KIVU; D\CENTRALGOVERNMENT\02_IS\04_POWER (SUPPLY &NETWORK)\GIS\Sites for potential development of energy.

File name: The name of the file.Methane Kivu Lake.

Custodian: The organisation responsible for having created the data andhas 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 anexplanation of why the data was created.The Dataset shows methane gas potential sites for

development of energy in the Republic of Rwanda.Theme,

Keywords:

Common-use word or phrase used to describe the subject ofthe data set.Methane Gas, Energy potential.

MetadataReference

ContactInformation:





Date ofCapture:


PositionalAccuracy:


data type, e.g., RMS for image and grid data, GPS techniques.If accuracy cannot be precisely determined, an intuitiveaccuracy based on experience may be acceptable.Need to be crosschecked with RECO

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can bedescribed as percentage of correct or incorrect values ofattributes. Usually based on a sample of the data (through fieldchecks or through comparing to separate data source).To investigate with RECO

LogicalConsistency:



50124211.doc Page 33 of 35 11-01-23


34/35


RLUDMP

The point features are unique and independently placed.

Completeness: An assessment of the completeness to identify gaps in thedata. Description may include spatial data coverage, attributedata coverage.Need to be crosschecked with RECO



UserConstraints:



Data FormatName:


Spatial ObjectType:

Description of the types of geographic features and theirrepresentation, e.g. Raster, Vector (point, line, polygon).The spatial data is in vector form and re-presented as a point

feature.Data Reference


System:






Entity andAttribute

Information:


ContactInformation

Contact Person: A person who can receive inquiries regarding the contents anddistribution of the data.In the ideal situation, it will be the same individual as statedunder contact information under Metadata Reference.

RECO.Office: N/A

50124211.doc Page 34 of 35 11-01-23


35/35


RLUDMP

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:


metadata infrastructure

Documents