metadata environment

8/7/2019 Metadata Environment

1/24

SWEDESURVEY GIS STRATEGYFOR

RLUDMP

Metadata specification for Environment feature class.

MetadataIdentification DescriptionTitle: Title should include theme and location.

NATIONAL PARKS; D\CENTRALGOVERNMENT\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 hasthe 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 inthe Republic of Rwanda.

Theme,Keywords:

Common-use word or phrase used to describe the subject of thedata set.Park, Tourism, Protected Area, Environment

MetadataReference

ContactInformation:

Details about the person who has created the metadata; name ofIndividual 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.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 (horizontal and verticalwhen applicable). Method to assess depends on data type, e.g.,RMS for image and grid data, GPS techniques. If accuracy cannotbe precisely determined, an intuitive accuracy based onexperience may be acceptable.To investigate with the Tourism and National Parks Authority(ORTPN)

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can be describedas percentage of correct or incorrect values of attributes. Usuallybased on a sample of the data (through field checks or throughcomparing to separate data source).The projects 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


2/24


RLUDMP

Consistency: topological errors, i.e. logical relationship between features of thedata. For example, duplicate lines, labelling, enclosed polygon andboundaries. 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 datacoverage.The shape file is complete but the attribute table is not 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.N/A

Lineage: Information about the sources of data used to construct the dataset and steps used to process the data. For each processing stepprovide (where possible) the following: source data name, sourcedata scale, source data date, description of processing stepperformed.N/A

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 polygonfeature.

Data ReferenceInformationCoordinate

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 Hart 94.WGS_1984.

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

Meters.

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

Entity andAttribute

Information:

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

ContactInformation

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


3/24


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 stated undercontact information under Metadata Reference.ORTPN.

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 make thedata available. The user may list as many formats as desired.Shapefiles, geopdf, pg, xls, dbf.

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


4/24


RLUDMP

MetadataIdentification

Description

Title: Title should include theme and location.PROTECTED FORESTS; D\CENTRALGOVERNMENT\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 hasthe 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 explanationof why the data was created.The shape file is a geometrical Polygon feature that shows

protected forests in the Republic of Rwanda.Theme,

Keywords:

Common-use word or phrase used to describe the subject of thedata set.Protected Forest, Protected Area, Environment.

MetadataReference

ContactInformation:

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

Role: GIS TechnicianDate:



Date ofCapture:

Insert the date when the dataset was prepared.2010

PositionalAccuracy:

Assessment of the expected error or range of error, of the dataobjects location. Described as the difference (in meters) betweenmeasured quantities and true positions (horizontal and verticalwhen applicable). Method to assess depends on data type, e.g.,

RMS for image and grid data, GPS techniques. If accuracy cannotbe precisely determined, an intuitive accuracy based onexperience may be acceptable.To investigate with the Ministry of Forestry and Mining(MINIFOM)

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can be describedas percentage of correct or incorrect values of attributes. Usuallybased on a sample of the data (through field checks or throughcomparing to separate data source).To investigate with MINIFOM

LogicalConsistency:

A statement whether data has been checked and corrected fortopological errors, i.e. logical relationship between features of thedata. 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


5/24


RLUDMP

Completeness: An assessment of the completeness to identify gaps in the data.Description may include spatial data coverage, attribute datacoverage.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 afield survey was conducted to capture the features.N/A

Lineage: Information about the sources of data used to construct the dataset and steps used to process the data. For each processing stepprovide (where possible) the following: source data name, sourcedata scale, source data date, description of processing stepperformed.The dataset was generated from an existing basemap ofProtected Areas. The scale and preparation date of the basemapis unknown.

User

Constraints:



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 polygonfeature.


System:



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

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

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.MINIFOM

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


6/24


RLUDMP

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 make thedata available. The user may list as many formats as desired.Shapefiles, geopdf, jpg, xls, dbf.

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


7/24


RLUDMP


Description

Title: Title should include theme and location.PROTECTED WETLANDS; D\CENTRALGOVERNMENT\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 hasthe 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 explanationof why the data was created.

The shape file is a geometrical Polygon feature that showsprotected wetland in the Republic of Rwanda.

Theme,Keywords:

Common-use word or phrase used to describe the subject of thedata set.Protected Wetland, Protected Area, Environment.

MetadataReference

ContactInformation:

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

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

Date:



Date ofCapture:

Insert the date when the dataset was prepared.2010.

PositionalAccuracy:

Assessment of the expected error or range of error, of the dataobjects location. Described as the difference (in meters) betweenmeasured 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 cannotbe precisely determined, an intuitive accuracy based onexperience may be acceptable.This need to be crosschecked with REMA.

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can be describedas percentage of correct or incorrect values of attributes. Usuallybased on a sample of the data (through field checks or throughcomparing to separate data source).This need to be crosschecked with REMA.

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, enclosed polygon andboundaries. Logical consistency does not apply to raster data.

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


8/24


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 datacoverage.This need to be crosschecked with REMA.

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.Publication date of the original data source: 2005.

Lineage: Information about the sources of data used to construct the dataset and steps used to process the data. For each processing stepprovide (where possible) the following: source data name, sourcedata scale, source data date, description of processing stepperformed.The dataset was generated from an existing wetland basemap,prepared by REMA in collaboration with CGIS-NUR, and publishedin 2005.

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 polygon

feature.


System:


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


Language The language used in the Dataset; English, French, Kinyarwandaor combined.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 stated undercontact information under Metadata Reference.REMA.

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


9/24


RLUDMP

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:


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


10/24


11/24


RLUDMP

that it is accurate.

Completeness: An assessment of the completeness to identify gaps in the data.Description may include spatial data coverage, attribute datacoverage.To investigate with MIDIMAR


Lineage: Information about the sources of data used to construct the dataset and steps used to process the data. For each processing stepprovide (where possible) the following: source data name, sourcedata scale, source data date, description of processing stepperformed.The dataset was digitised from an existing basemap showingdrought risk regions.

User

Constraints:



Data FormatName:


Spatial ObjectType:



System:




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

or combined.English.

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 undercontact information under Metadata Reference.

MIDIMAR.Office: N/A

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


12/24


RLUDMP

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:


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


13/24


RLUDMP


Description

Title: Title should include theme and location.FLOOD AND LANDSLIDE RISKS; D\CENTRALGOVERNMENT\03_EN\02_NATURAL HAZARDS\GIS\Natural HazardsRisks.

File name: The name of the file.Flood and landslide risk.

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


The shape file is a geometrical Polygon feature that shows Floodand landslide risk regions in the Republic of Rwanda.

Theme,Keywords:

Common-use word or phrase used to describe the subject of thedata set.Flood, Landslide, Natural hazards, Environment.

MetadataReference

ContactInformation:


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

Date:



Date ofCapture:

Insert the date when the dataset was prepared.2010.

PositionalAccuracy:


when applicable). Method to assess depends on data type, e.g.,RMS for image and grid data, GPS techniques. If accuracy cannotbe precisely determined, an intuitive accuracy based onexperience may be acceptable.This need to be certified by MIDIMAR.

AttributeAccuracy:

Assessment of values or attributes assigned to features in thedata in relation to the reality. Attribute accuracy can be describedas percentage of correct or incorrect values of attributes. Usuallybased on a sample of the data (through field checks or throughcomparing to separate data source).The shape file does not have an active attribute table.

LogicalConsistency:



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


14/24


RLUDMP

This has to be certified by MIDIMAR; especially since the projectsanalysis on logical consistency of the data shows that it isaccurate.

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.


Lineage: Information about the sources of data used to construct the dataset and steps used to process the data. For each processing stepprovide (where possible) the following: source data name, sourcedata scale, source data date, description of processing stepperformed.The dataset was digitised from an existing basemap showingFlood and landslide risk regions.

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 polygonfeature.


System:





Entity andAttribute

Information:


ContactInformation


In the ideal situation, it will be the same individual as stated undercontact information under Metadata Reference.MIDIMAR.

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


15/24


RLUDMP

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:


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


16/24


RLUDMP


Description

Title: Title should include theme and location.LAVA RISKS; D\CENTRAL GOVERNMENT\03_EN\02_NATURALHAZARDS\GIS\Natural Hazards Risks.

File name: The name of the file.Lava Risk.


Abstract: A short description or summary of the contents of the data,including the original data source. Preferably also an explanationof 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,

Keywords:

Common-use word or phrase used to describe the subject of thedata set.Lava risks, Natural hazards, Environment.

MetadataReference

ContactInformation:

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

Role: GIS Technician.Date:



Date ofCapture:


PositionalAccuracy:


RMS for image and grid data, GPS techniques. If accuracy cannotbe precisely determined, an intuitive accuracy based onexperience may be acceptable.To investigate with MIDIMAR.

AttributeAccuracy:


LogicalConsistency:


boundaries. Logical consistency does not apply to raster data.The projects analysis on logical consistency of the data shows

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


17/24


RLUDMP


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


Lineage: Information about the sources of data used to construct the dataset and steps used to process the data. For each processing stepprovide (where possible) the following: source data name, sourcedata scale, source data date, description of processing stepperformed.The dataset was digitised from an existing basemap showingprobability of Lava flow invasion in Rubavu District.

User

Constraints:



Data FormatName:


Spatial ObjectType:



System:





Entity andAttribute

Information:


ContactInformation


contact information under Metadata Reference.MIDIMAR.

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


18/24


RLUDMP

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 make thedata available. The user may list as many formats as desired.Shapefiles,geopdf,jpg,xls,dbf.

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


19/24


RLUDMP


Description

Title: Title should include theme and location.FAULT LINES; D\CENTRAL GOVERNMENT\03_EN\02_NATURALHAZARDS\GIS\Natural Hazards Risks.

File name: The name of the file.Fault_Rda.


Abstract: A short description or summary of the contents of the data,including the original data source. Preferably also an explanationof why the data was created.The shape file is a geometrical Polygon feature that shows Fault

line in the Republic of Rwanda.Theme,

Keywords:

Common-use word or phrase used to describe the subject of thedata set.Fault line, Natural hazards, Environment.

MetadataReference

ContactInformation:

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

Role: GIS Technician.Date:



Date ofCapture:


PositionalAccuracy:


RMS for image and grid data, GPS techniques. If accuracy cannotbe precisely determined, an intuitive accuracy based onexperience may be acceptable.This need to be certified by MIDIMAR.

AttributeAccuracy:


LogicalConsistency:


boundaries. Logical consistency does not apply to raster data.The projects analysis on logical consistency of the data shows

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


20/24


RLUDMP


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


Lineage: Information about the sources of data used to construct the dataset and steps used to process the data. For each processing stepprovide (where possible) the following: source data name, sourcedata scale, source data date, description of processing stepperformed.The dataset was digitised from an existing basemap showingfault line.

User

Constraints:



Data FormatName:


Spatial ObjectType:



System:





Entity andAttribute

Information:


ContactInformation


contact information under Metadata Reference.MIDIMAR.

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


21/24


RLUDMP

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:


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


22/24


RLUDMP


Description

Title: Title should include theme and location.EARTHQUAKE RISKS; D\CENTRALGOVERNMENT\03_EN\02_NATURAL HAZARDS\GIS\Natural HazardsRisks.

File name: The name of the file.EarthquakeRisk_Rda.



The shape file is a geometrical Polygon feature that showsEarthquake risk region in the Republic of Rwanda.

Theme,Keywords:

Common-use word or phrase used to describe the subject of thedata set.Earthquake Risks, Environment, Natural hazards.

MetadataReference

ContactInformation:


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

Date:



Date ofCapture:


PositionalAccuracy:


when applicable). Method to assess depends on data type, e.g.,RMS for image and grid data, GPS techniques. If accuracy cannotbe precisely determined, an intuitive accuracy based onexperience may be acceptable.This need to be certified by MIDIMAR.

AttributeAccuracy:


LogicalConsistency:



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


23/24


RLUDMP

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

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

N/ACurrentness: 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 the dataset and steps used to process the data. For each processing stepprovide (where possible) the following: source data name, sourcedata scale, source data date, description of processing stepperformed.The dataset was digitised from an existing basemap showingEarthquake risk.

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.


System:

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




Entity andAttribute

Information:


ContactInformation


In the ideal situation, it will be the same individual as stated undercontact information under Metadata Reference.MIDIMAR.

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


24/24


RLUDMP

Office: N/A

Address: N/A

Phone: N/A

E-mail Address: N/A

Transfer FormatName

and/or Lineage:


metadata environment

Documents