<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article  PUBLIC "-//NLM//DTD Journal Publishing DTD v3.0 20080202//EN" "http://dtd.nlm.nih.gov/publishing/3.0/journalpublishing3.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="3.0" xml:lang="en" article-type="research article"><front><journal-meta><journal-id journal-id-type="publisher-id">GEP</journal-id><journal-title-group><journal-title>Journal of Geoscience and Environment Protection</journal-title></journal-title-group><issn pub-type="epub">2327-4336</issn><publisher><publisher-name>Scientific Research Publishing</publisher-name></publisher></journal-meta><article-meta><article-id pub-id-type="doi">10.4236/gep.2020.810018</article-id><article-id pub-id-type="publisher-id">GEP-103882</article-id><article-categories><subj-group subj-group-type="heading"><subject>Articles</subject></subj-group><subj-group subj-group-type="Discipline-v2"><subject>Earth&amp;Environmental Sciences</subject></subj-group></article-categories><title-group><article-title>
 
 
  Development of a Geographic Information Systems Baseline Spatial Geodatabase Template for Evaluating Potential and Predicted Environmental Impacts for Sustainable Environmental Impact Assessment of Mining in Sierra Leone
 
</article-title></title-group><contrib-group><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Samuel</surname><given-names>Mohamed Kamara</given-names></name><xref ref-type="aff" rid="aff1"><sub>1</sub></xref></contrib></contrib-group><aff id="aff1"><label>1</label><addr-line>Department of Geographic Information Systems, Environment Protection Agency, Freetown, Sierra Leone</addr-line></aff><pub-date pub-type="epub"><day>14</day><month>10</month><year>2020</year></pub-date><volume>08</volume><issue>10</issue><fpage>262</fpage><lpage>284</lpage><history><date date-type="received"><day>26,</day>	<month>June</month>	<year>2020</year></date><date date-type="rev-recd"><day>27,</day>	<month>October</month>	<year>2020</year>	</date><date date-type="accepted"><day>30,</day>	<month>October</month>	<year>2020</year></date></history><permissions><copyright-statement>&#169; Copyright  2014 by authors and Scientific Research Publishing Inc. </copyright-statement><copyright-year>2014</copyright-year><license><license-p>This work is licensed under the Creative Commons Attribution International License (CC BY). http://creativecommons.org/licenses/by/4.0/</license-p></license></permissions><abstract><p>
 
 
  Baseline Environmental Impact Assessment (EIA) of mining projects in Sierra Leone creates a challenging environment for data collection and impact prediction. Application of geographic information systems provides suitable spatial analysis data collection methods to reduce the challenges created by mining environments. This research develops a baseline spatial geodatabase template for evaluating potential and predicted environmental impacts assessment of mining projects in Sierra Leone. It is observed that spatial analysis of impacts of mining projects on the environmental attributes, especially air, noise, water, land, and socio-economy in mining areas is largely unexplored in Sierra Leone. The literature review revealed that no complete GIS spatial data geodatabase collection template appears to have been developed to date to provide an integrated sustainable spatial analysis and modelling tool for EIA and environmental management of mining in Sierra Leone. Therefore developing a Geographic Information Systems baseline geodatabase template for the evaluation of potential and predicted environmental impact for sustainable environmental impact assessment of mining in Sierra Leone will: 1) provide support to the data acquisition process of environmental impact assessment, 2) offer a concept for developing analysis methods for environmental management of mining, 3) minimize the undesired environmental impacts of mining, and 4) give an optimal proposal for data collection and analysis of mining industry in attaining sustainable development in Sierra Leone. Due to the limited available data, a conceptual GIS database template has been developed rather than a database case study of a mining site. No site investigation and data collection were undertaken. The geospatial database template was designed using ArcCatalog, ArcGIS 10.7.1. software, through the following steps: exploration of the general data requirement of environmental impact assessment studies of mining, the definition of the general baseline datasets requirement of environmental impact assessment in mining, structuring of the environmental impact assessment baseline spatial geodatabase, creating the geographic geodatabase dictionary, selecting, matching geographic data with geodatabase structure, designing the feature class and attributes, creating the baseline GIS geodatabase template. The GIS spatial geodatabase template has several advantages for environmental impact assessment of mining including avoiding data redundancy, integrating data into a single database, creating uniformity in data collection, easy to find and track data, integrated spatial and non-spatial data, and reducing the volume of data.
 
</p></abstract><kwd-group><kwd>GIS</kwd><kwd> Environmental Impact Assessment</kwd><kwd> Spatial Geodatabase</kwd><kwd> Sustainable Environment</kwd></kwd-group></article-meta></front><body><sec id="s1"><title>1. Introduction</title><p>Environmental Impact Assessment (EIA) was formally adopted in Sierra Leone in 2010 (EPA-SL Act, 2010) as a measure to protect the environment and to reduce environmental degradation associated with major developmental projects. Although Environmental Impact Assessments (EIAs) are dependent on geo-spatial information to make an assessment, there are no rules set on how to conduct an environmental assessment on mining activities in Sierra Leone. Since GIS is a vital tool and efficient in data collection, storage, analysis, and collation, it has become an appropriate mechanism for creating an environmental information system spatial geodatabase. This storage ability makes environmental spatial and non-spatial data easier to upgrade, update, process, and retrieve as needed. GIS is applicable in all stages of the EIA process: from the acquisition, storage, processing, manipulating and display of thematic information relative to the vulnerability of the affected natural resources. Geographic Information Systems (GIS) can improve the gathering, storage manipulation, transformation and processing of data and information. GIS contribution to environmental impact assessment studies is very important and very useful for managing environmental impact assessment and data consistently from field measurement (Kamara, 2019). Generally, an impact assessment study is an information collection and analysis process; thus, up-to-date, available, and relevant data are needed to attain useful results (Bulla et al., 2004). The section of the EIA report of mining that often describes the detailed environmental baseline conditions of a particular mining site demonstrates whether the EIA Consultant truly understands the environmental, social, health, and economic impact that the proposed mining project may create. For instance, if the EIA does not include details about the existing land cover/land use, vegetation, surface and groundwater quality, air quality, and the abundance and distribution of threatened and endangered species, then it simply is not possible for the EIA Consultant to formulate accurate information about how the project would impact land cover/land use, vegetation, surface and groundwater quality, air quality, and the abundance and distribution of threatened and endangered species. However, application of GIS in mining EIA in Sierra Leone is constrained by the availability of an appropriate digital electronic baseline geodatabase on environmental parameters and datasets, such as base maps on Land use/land cover, soil, geology, topography, population density, socio-economic levels, road accessibility, air quality, water quality, noise level, biological content, historical value, archaeological, climate change to name a few. Although very significant work has been done in environmental impact assessment and sophisticated Geological Information Systems has been developed to determine the location of mineral deposit and ore bodies, no complete GIS spatial geodatabase template for spatial data collection appears to have been developed to date to provide an integrated sustainable spatial analysis and modelling tool for EIA and environmental management of mining in Sierra Leone. This is due to 1) the absence of comprehensive understanding of interrelated environment impacts caused by the mining of different minerals, 2) the environmental uniqueness of each mine, which make it difficult to develop general tools of EIA analysis and models, 3) the availability of adequate spatial data, information and appropriate GIS technics, 4) because of the dynamic characteristics and multivariate nature of the environment, it has often been difficult to collate, analyze and interpret its datasets, 5) lack of appropriate temporal and spatial resolution of remotely sensed imageries and accurate geospatial data can be a major limitation on spatial modeling, 6) finally, the availability of GIS professionals and affordability of GIS software and related hardware is a major constraint on EIA budgeting, especially for developing countries like Sierra Leone. Most EIA studies of mining projects have focused only on one or a limited set of impacts of the project on the physical, ecological, or social environment. Thereby, such studies have not provided a holistic picture of the entire environmental impact scenario. The research aims to design a Geographic Information Systems baseline geodatabase template for the evaluation of potential and predicted environmental impact for sustainable environmental impact assessment of mining in Sierra Leone. The expected output is an application in the ArcGIS software environment where the no GIS expert and environmentalist can easily use the templates to collect and analyze the data and get a comprehensive analysis and results. This study will add a more meaningful contribution to studies already done by other researchers in the integration of GIS and GIS software to solve the problems in the EIAs of mining. Each step will be explained in detail in the subsequent sections. Therefore, it is expected that the environmental databases from mining companies have uniformity in all data collection procedures, field measurement procedures, results classification and data management, analysis method, and reporting data systems to the environmental impact assessment. The GIS spatial geodatabase template has several advantages for environmental impact assessment of mining including avoiding data redundancy, integrating, data into a single database, creating uniformity in data collection, easy to find and track data, integrated spatial and non-spatial data, and reducing the volume of data storage. This study will add a more meaningful contribution to studies already done by other researchers in the integration of GIS and GIS software to solve the environmental problems of mining. According to the trial done on the baseline GIS spatial geodatabase template, it has shown some encouraging results for evaluating potential and predicted environmental impacts assessment of mining projects in Sierra Leone. However, using the baseline spatial geodatabase template has many advantages; however, there are also several challenges to implement it as stated above.</p></sec><sec id="s2"><title>2. Materials and Methods</title><p>The process of designing the geospatial database was accomplished by using a relational personal geodatabase concept. The geodatabase consists of ten feature datasets; the geospatial database template was designed using ArcCatalog, ArcGIS 10.7.1. software, through the following steps:</p><p>1) exploration of the general data requirement of environmental impact assessment studies of mining,</p><p>2) defining the general baseline datasets requirement of environmental impact assessment in mining,</p><p>3) structuring of the environmental impact assessment baseline spatial geodatabase,</p><p>4) creating the geographic geodatabase dictionary,</p><p>5) selecting, matching geographic data with geodatabase structure,</p><p>6) designing the feature class and attributes,</p><p>7) creating the baseline GIS spatial geodatabase template.</p><p>Each step will be explained in detail in the subsequent sections.</p><sec id="s2_1"><title>2.1. Exploration of the General Data Requirement</title><p>The first step in this research was to study the specifications relative to data contained in national laws and regulations about an environmental impact analysis of mining in Sierra Leone. The relevant literature and ESHIA reports of mining companies in Sierra Leone were explored; moreover, in the course of my investigations, I examined 54 environmental impact assessments, of which 30 were completed environmental impact studies for small scale mining companies’ reports documentations and 14 were completed environmental impact studies for large scale mining companies. Most of the environmental impact assessments for investigation were selected through the impact assessment database of the Environmental Cadastral and Administrative system (ECAS) electronic system which are studies conducted by different environmental consulting firms in Sierra Leone. In the course of my investigation, I determined the general primary environmental data that the laws of Sierra Leone prescribe or recommends, or that were used by the authors of the examined environmental impact assessments for the various mining companies. On this basis, a data list was compiled containing only those data fields that occurred with at least 85% frequency in the examined impact assessment studies as a result of statistical evaluation.</p></sec><sec id="s2_2"><title>2.2. Definition of the General Datasets Requirement</title><p>In examining the phases and work stages of environmental impact assessment, it was established that the data collection and surveying phase is primarily the basic state in which databases or information systems can serve as potential data sources. Consequently, in this research, the analysis of data needed for the examination of the basic state of the environment was emphasized; hence, they are taken into consideration for impact assessment and appraisal. The following gives a more detailed discussion of the specific kinds of environmental baseline datasets that an EIA for a proposed mining project needs to contain. Those environmental data were incorporated into my master data list, which occurred in at least (85%) of the studies that were investigated. <xref ref-type="table" rid="table1">Table 1</xref> shows the primary data grouped as elements of the environment.</p><table-wrap id="table1" ><label><xref ref-type="table" rid="table1">Table 1</xref></label><caption><title> General baseline datasets of environmental impact assessments of mining</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >Soil</th><th align="center" valign="middle" >topography, geomorphology, geological structure and bedrock, parent material, the direction of slope, genetic and physical soil type, water balance, location and sensitivity of the soil layers, soil texture, pH, soil water management categories, depth of the column, soil compaction depth of the groundwater, protected geological values</th></tr></thead><tr><td align="center" valign="middle" >Air</td><td align="center" valign="middle" >average hours of sunshine, prevailing wind direction, wind speed, precipitation conditions, the spatial and temporal distribution of rainfall, average temperature data, air quality, background contamination, protected and sensitivity categories</td></tr><tr><td align="center" valign="middle" >Water</td><td align="center" valign="middle" >size and location of surface and groundwater, water flow conditions, standard flow, protected hydrological values, water facilities, water quality (pH, Total suspended residue, Fe Total, and Mn Total)</td></tr><tr><td align="center" valign="middle" >Wildlife, Biological Flora &amp; fauna</td><td align="center" valign="middle" >types of habitat, habitat patches, species composition, rare plant communities, protected plants, animal species and population of the examined area, protected animals</td></tr><tr><td align="center" valign="middle" >Socio-Economic</td><td align="center" valign="middle" >size and distance of built environment, built-up, cultural values, historical monuments, function of the examined area</td></tr><tr><td align="center" valign="middle" >Base Map</td><td align="center" valign="middle" >Administrative boundary, Concession area boundary, District boundary, Chiefdom boundary, Section boundary, Scanned parcel Maps, Digital Orth photos, imagery</td></tr><tr><td align="center" valign="middle" >Population</td><td align="center" valign="middle" >the size of the affected population, population by sex and age</td></tr><tr><td align="center" valign="middle" >Land cover/land use</td><td align="center" valign="middle" >landscape, land use, nature-function areas, protected areas, landscape values</td></tr></tbody></table></table-wrap></sec><sec id="s2_3"><title>2.3. Structuring the Geospatial Database</title><p>The structure of the spatial geodatabase includes two types of data, i.e. Spatial and non-spatial (attributes data). The structure of the spatial geodatabase contains ten features datasets namely: the basemap dataset, the air quality dataset, water quality dataset, the population dataset, the flora and fauna datasets (biological dataset), land cover/land use datasets, socio-economic datasets, waste management dataset, climate change dataset and soil quality dataset as shown in <xref ref-type="fig" rid="fig1">Figure 1</xref>.</p></sec><sec id="s2_4"><title>2.4. Creating the Geographic Geodatabase Dictionary</title><p>The data dictionary is the result of the analysis phase of existing needs in terms of geospatial data. This data is available either in analog form (maps) or digital (computer support). A data dictionary is a collection of metadata and necessary reference data for designing a geographic database and is a catalog or table containing information about the datasets stored in a database It describes data definition, data type, coordinate system, feature class field properties, relationship diagram, and reference table. It’s contained the full names of attributes, meanings of codes, the scale of the source data, accuracy of locations, and map projections used. Creating a data dictionary allows other users to view formation about the data. The data dictionary is useful for environmental practitioners, engineers, surveyors, GIS experts, and analysts for data processing and analysis, GIS users and decision-makers, environmental technicians involving in EIA studies of mining. This is the main referential of the database template. It is often represented by a table containing the name, code, data type, and comments, etc. as shown in <xref ref-type="fig" rid="fig2">Figure 2</xref>.</p></sec><sec id="s2_5"><title>2.5. Selecting, Matching Geographic Data with Geodatabase Structure</title><p>GIS database design is about identifying the thematic layers to be used and specifying the contents and representations of each thematic layer. This involves defining how the geographic features are to be represented (for example, as points, lines, polygons, raster’s, or tabular attributes); how the data is organized into feature classes, attributes, and relationships; and the spatial and database integrity rules for implementing rich GIS behavior using topologies, networks, raster catalogs, and so forth. Designing of feature classes and attributes is the most important step in the building of the template databases because this step determines what the database looks like. This step includes determination of the following feature class name, coordinate system, data type, field name and field properties, code for each environment parameters, and creating reference tables. The baseline spatial geodatabase contains a series of GIS data layers. The list above, sorted by layer category, shows the vector data layers in the database that model real-world features as points, lines, or polygons in a UTM (WGS 1984) projected geographic coordinate system. All feature classes in the geodatabase have the following common attributes as shown in <xref ref-type="table" rid="table2">Table 2</xref>.</p><p>The NAME attribute is used in ArcMap for labelling purposes, and most of the feature classes have a typical characteristic that is used for symbolizing features. The remaining attributes are primarily used for quality control and metadata purposes. The environmental impact assessment baseline spatial geodatabase model template consists of a set of core templates (sub-models) and extensions. These core templates and extensions can be linked using a common theme in the model, i.e. the concession area.</p><p>A concession area can be represented as a polygon, using a unique identifier for each concession area. Templates may interact with each other with a combination of spatial and non-spatial data with reference information to form the environmental impact assessment baseline spatial geodatabase layers, the geodatabase data model is dynamic; it will provide flexibility for end-users to manipulate the selection criteria and organizing them on a priority basis depending on the development strategies considered.</p><table-wrap id="table2" ><label><xref ref-type="table" rid="table2">Table 2</xref></label><caption><title> Common Attributes of the geodatabase</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >Attribute</th><th align="center" valign="middle" >Data Type</th><th align="center" valign="middle" >Length</th><th align="center" valign="middle" >Description</th></tr></thead><tr><td align="center" valign="middle" >NAME</td><td align="center" valign="middle" >String</td><td align="center" valign="middle" >200</td><td align="center" valign="middle" >An attribute that is typically used for labeling the feature.</td></tr><tr><td align="center" valign="middle" >SOURCEFEATUREID</td><td align="center" valign="middle" >String</td><td align="center" valign="middle" >20</td><td align="center" valign="middle" >Unique ID of the feature. This attribute should be mapped to the source dataset’s unique feature ID.</td></tr><tr><td align="center" valign="middle" >DATASOURCENAME</td><td align="center" valign="middle" >String</td><td align="center" valign="middle" >100</td><td align="center" valign="middle" >Data source name (geodatabase name, shapefile name, and so on).</td></tr><tr><td align="center" valign="middle" >LASTUPDATE</td><td align="center" valign="middle" >Date</td><td align="center" valign="middle" >8</td><td align="center" valign="middle" >Date when the feature was last loaded or updated.</td></tr><tr><td align="center" valign="middle" >ISVISIBLE</td><td align="center" valign="middle" >Small Integer</td><td align="center" valign="middle" >2</td><td align="center" valign="middle" >A flag used for turning features on and off in ArcMap through definition queries.</td></tr><tr><td align="center" valign="middle" >LASTEDITOR</td><td align="center" valign="middle" >String</td><td align="center" valign="middle" >100</td><td align="center" valign="middle" >Name of the person who migrated or edited the data.</td></tr><tr><td align="center" valign="middle" >EDITCOMMENTS</td><td align="center" valign="middle" >String</td><td align="center" valign="middle" >250</td><td align="center" valign="middle" >Description of the edit performed on the feature.</td></tr></tbody></table></table-wrap></sec></sec><sec id="s3"><title>3. Results</title><sec id="s3_1"><title>3.1. Creating the Baseline GIS Geodatabase Template</title><p>The GIS baseline geodatabase was created in the ArcCatalog of the ArcGIS Desktop 10.7.1. Software. This is a collection of feature datasets and a feature dataset is a group of feature classes. This step includes 1) creating personal geodatabase, 2) creating feature datasets, 3) creating feature class, and 4) determine the feature class properties. <xref ref-type="fig" rid="fig3">Figure 3</xref> shows the personal Environmental GIS baseline Spatial Geodatabase in the ArcCatalog, ArcGIS Software. This geodatabase contains ten (10) feature datasets.</p><p>A feature is a collection of features representing the same geographic elements such as boreholes, drill holes, parcels, or soil types, etc. All the features in a future class have the same spatial representation (for example point, line, or polygon) and share a common set of descriptive attributes. Feature datasets are organized collections of related feature classes (Maryati et al., 2012). The feature class properties (<xref ref-type="fig" rid="fig4">Figure 4</xref>) provide information regarding field properties, domain indexes, subtypes, relationship, representation, coordinate system, tolerance, and resolution. All information about the spatial data is stored in the field’s attribute. The field properties include the field name, data type, alias, allow null values, default value, and length as shown in <xref ref-type="fig" rid="fig4">Figure 4</xref>. The baseline environmental GIS spatial database template for a proposed mining project contained ten (10) datasets. The creation of each of these datasets is explained in the following sections.</p></sec><sec id="s3_2"><title>3.2. Creating the Baseline Base Map Dataset</title><p>The base map datasets are the datasets that contain the feature classes that are to be used as a base map for the creation of the thematic maps for the baseline environmental impact assessment of mining projects. This dataset includes Administrative boundary, Provincial boundary, Concession area boundary, District boundary, Chiefdom boundary, Section boundary, Village boundary Infrastructure, Public road, mined road, Railway, and River as shown in (<xref ref-type="fig" rid="fig5">Figure 5</xref>). From <xref ref-type="fig" rid="fig5">Figure 5</xref>, the GIS Base map personal geodatabase was created in the ArcCatalog of the ArcGIS Desktop 10.7.1. Software. <xref ref-type="table" rid="table3">Table 3</xref> shows the description of the baseline base map layers’ attributes.</p></sec><sec id="s3_3"><title>3.3. Creating the Baseline Land Cover/Land Use Dataset</title><p>The land cover/land use datasets are the datasets that contain the feature classes to be used as a base map for the creation of the land cover/land use thematic maps for the baseline environmental impact assessment of mining projects. It contains mainly the feature classes related to the mining operations in the project concession area which includes; land cover feature class, land use feature class, mined-out land feature class, land topography feature class, soil type feature class, geology type feature class as shown in <xref ref-type="fig" rid="fig6">Figure 6</xref>. <xref ref-type="table" rid="table4">Table 4</xref> shows the description of the baseline land cover/land use layers’ attributes.</p><table-wrap id="table3" ><label><xref ref-type="table" rid="table3">Table 3</xref></label><caption><title> Description of the baseline land cover/land use dataset</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >No</th><th align="center" valign="middle" >LAYER</th><th align="center" valign="middle" >Requirement Level</th><th align="center" valign="middle" >Geometry Type</th><th align="center" valign="middle" >Required Attributes</th></tr></thead><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >Contour</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polyline</td><td align="center" valign="middle" >Elevation, Slope, Contour ID, Shape, Contour Type, Height, Collection Date, Remarks, SHAPE_Length</td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >Administrative Boundary</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Name, Adm ID, Shape, SHAPE_Length, SHAPE_area, Collection Date, Remarks</td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Stream</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polyline</td><td align="center" valign="middle" >Stream Name, Stream ID, Shape, SHAPE_Length, Stream Type, Collection Date, Remarks</td></tr><tr><td align="center" valign="middle" >4</td><td align="center" valign="middle" >Provincial boundary</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Name, Type, Province Code, SHAPE_Length, SHAPE_area</td></tr><tr><td align="center" valign="middle" >5</td><td align="center" valign="middle" >Concession area boundary</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Name, Shape SHAPE_Length, SHAPE_area, Con ID, Application Month, Application Year, Mapping date, Mapper name, Remarks</td></tr><tr><td align="center" valign="middle" >6</td><td align="center" valign="middle" >District boundary</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Name, Type, District Code, SHAPE_Length, SHAPE_area</td></tr><tr><td align="center" valign="middle" >7</td><td align="center" valign="middle" >Chiefdom boundary</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Name, Chiefdom Code, SHAPE_Length, SHAPE_area</td></tr><tr><td align="center" valign="middle" >8</td><td align="center" valign="middle" >Railway</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polyline</td><td align="center" valign="middle" >Rail ID, Shape, SHAPE_Length, Surface Type, Rail Condition, Rail Name, Rail Type, Remarks</td></tr><tr><td align="center" valign="middle" >9</td><td align="center" valign="middle" >Village boundary</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Name, Village ID, Shape, SHAPE_Length, SHAPE_area, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >10</td><td align="center" valign="middle" >Infrastructure</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Name, Inf ID, Shape, SHAPE_Length, SHAPE_area, Collection Date, Remarks</td></tr><tr><td align="center" valign="middle" >11</td><td align="center" valign="middle" >Public Road</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polyline</td><td align="center" valign="middle" >Road ID, Shape, SHAPE_Length, Surface Type, Road Condition, Road Name, Road Type, Remarks</td></tr><tr><td align="center" valign="middle" >12</td><td align="center" valign="middle" >Mined road</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polyline</td><td align="center" valign="middle" >Road ID, Shape, SHAPE_Length, Surface Type, Road Condition, Road Name, Road Type, Remarks</td></tr><tr><td align="center" valign="middle" >13</td><td align="center" valign="middle" >River</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polyline</td><td align="center" valign="middle" >River ID, Shape, SHAPE_Length, River Type, River Name, Collection Date, Remarks</td></tr></tbody></table></table-wrap><table-wrap id="table4" ><label><xref ref-type="table" rid="table4">Table 4</xref></label><caption><title> Description of the baseline land cover/land use dataset</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >No</th><th align="center" valign="middle" >LAYER</th><th align="center" valign="middle" >Requirement Level</th><th align="center" valign="middle" >Geometry Type</th><th align="center" valign="middle" >Required Attributes</th></tr></thead><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >Land cover</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Land cover ID, Land Cover type, Shape, SHAPE_Length, SHAPE_area Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >Land Use</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Land Use ID, Land Use type, Shape, SHAPE_Length, SHAPE_area Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Mined outland</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Land Use ID, Land Use type, Shape, SHAPE_Length, SHAPE_area Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >4</td><td align="center" valign="middle" >Land Topography</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Land Use ID, Topography type, Shape, SHAPE_Length, SHAPE_area Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >5</td><td align="center" valign="middle" >Soil</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Land Use ID, Soil type, Shape, SHAPE_Length, SHAPE_area Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >6</td><td align="center" valign="middle" >Geology</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Land Use ID, Geology type, Shape, SHAPE_Length, SHAPE_area Mapping Date, Remarks</td></tr></tbody></table></table-wrap></sec><sec id="s3_4"><title>3.4. Creating the Baseline Air Quality Dataset</title><p>Baseline Air quality datasets for a mining project concession area are critical to evaluating the potential distribution of air pollutants and their effects in the area of influence. Air pollutants can travel long distances, so baseline air quality information should be considered about meteorological conditions, wind patterns, geological formations, and anything else that might influence the distribution of air pollutants. Baseline air quality datasets should include the following: location of air monitoring and/or sampling stations and measurements of these common parameters; Particulate matter (PM10 and PM2.5), Carbon monoxide (CO), Nitrogen oxides (NOx), Lead (Pb), cadmium (Cd), arsenic (As), mercury (Hg), Total Suspended Solids (TSS), and Sulfur dioxide (SO<sub>2</sub>). This dataset includes noise, air temperature, air humidity, wind speed rainfall, air quality point, ambient air quality, and air vibration, <xref ref-type="fig" rid="fig7">Figure 7</xref> illustrates the design of the geodatabase in the ArcGIS/ArcCatalog software. As can be seen in <xref ref-type="fig" rid="fig7">Figure 7</xref>, the Air quality datasets contain eight feature classes. Attributes of these future classes are further illustrated in <xref ref-type="table" rid="table5">Table 5</xref>.</p></sec><sec id="s3_5"><title>3.5. Creating the Baseline Wildlife, Flora and Fauna Datasets</title><p>The wildlife datasets comprise all living things that are undomesticated. This includes plants, animals (vertebrates, birds, fish), and other organisms (invertebrates). The baseline wildlife, flora, and fauna datasets must include a list of wildlife species within the project area and interactions between species. This should include all endemic flora and fauna in the project concession area that have a special conservation status—for example, listed by the International Union for Conservation of Nature (IUCN) or by national legislation as a threatened or endangered species, a description of the region and species distribution. The dataset contains mainly feature classes related to wildlife, flora, fauna, and biodiversity. This dataset contains six feature classes includes terrestrial species, aquatic species, habitats critical to ecological processes, biology point. <xref ref-type="fig" rid="fig8">Figure 8</xref> illustrates the design of the geodatabase in the ArcGIS/ArcCatalog software. Each feature class contains information regarding mapping point names and UTM XY position coordinates. Attributes of these future classes are further illustrated in <xref ref-type="table" rid="table6">Table 6</xref>.</p><table-wrap id="table5" ><label><xref ref-type="table" rid="table5">Table 5</xref></label><caption><title> Description of the baseline air quality dataset</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >No</th><th align="center" valign="middle" >LAYER</th><th align="center" valign="middle" >Requirement Level</th><th align="center" valign="middle" >Geometry Type</th><th align="center" valign="middle" >Required Attributes</th></tr></thead><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >Air quality point</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Air Quality ID Shape, Point Name, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >Air Humidity</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Air Quality ID, Shape, Point Name, Humidity, mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Ambient Air Quality</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Shape, Point Name, Sulphur Dioxide, Carbon Monoxide, Nitrogen Dioxide, Oxidant, Hydro Carbon, PM &lt; 10, PM &lt; 2.5, TSP, Plumbum, Dustfall, Total Florides, Fluor Index, Lead (Pb), Sulphate dioxide, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >4</td><td align="center" valign="middle" >Air Vibration</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Air Quality ID, Shape, Point Name, vibration, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >5</td><td align="center" valign="middle" >Noise Point</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Air Quality ID, Shape, Point Name, Noise, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >6</td><td align="center" valign="middle" >Air Temperature</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Air Quality ID, Shape, Point Name, Temperature, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >7</td><td align="center" valign="middle" >Wind Speed</td><td align="center" valign="middle" ></td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Air Quality ID, Shape, Point Name, Wind Speed, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >8</td><td align="center" valign="middle" >Rain Fall</td><td align="center" valign="middle" ></td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Air Quality ID, Shape, Point Name, Rain Fall, Mapping Date, Remarks</td></tr></tbody></table></table-wrap><table-wrap id="table6" ><label><xref ref-type="table" rid="table6">Table 6</xref></label><caption><title> Description of the baseline wildlife, flora and fauna dataset</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >No</th><th align="center" valign="middle" >LAYER</th><th align="center" valign="middle" >Requirement Level</th><th align="center" valign="middle" >Geometry Type</th><th align="center" valign="middle" >Required Attributes</th></tr></thead><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >Terrestrial species</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point/polygon</td><td align="center" valign="middle" >Composition, Shape, Point Name, density, distribution Status, X_Coordinate, Y_Coordinate, vegetative cover, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >Aquatic species</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point/Polygon</td><td align="center" valign="middle" >Composition, Shape, Point Name, density, distribution Status, X_Coordinate, Y_Coordinate, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Habitats</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point/Polygon</td><td align="center" valign="middle" >Biology ID, Shape, Point Name X_Coordinate, Y_Coordinate, Results, Mapping Date, remarks</td></tr><tr><td align="center" valign="middle" >4</td><td align="center" valign="middle" >Biology point</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point/Polygon</td><td align="center" valign="middle" >Biology ID, Shape, Point Name X_Coordinate, Y_Coordinate, Results Mapping Date, remarks</td></tr><tr><td align="center" valign="middle" >5</td><td align="center" valign="middle" >Flora</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point/Polygon</td><td align="center" valign="middle" >Biology ID, Shape, Point Name X_Coordinate, Y_Coordinate, Results Mapping Date, remarks</td></tr><tr><td align="center" valign="middle" >6</td><td align="center" valign="middle" >Fauna</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point/Polygon</td><td align="center" valign="middle" >Biology ID, Shape, Point Name X_Coordinate, Y_Coordinate, Results Mapping Date, remarks</td></tr></tbody></table></table-wrap></sec><sec id="s3_6"><title>3.6. Creating the Baseline Surface and Groundwater Quality Dataset</title><p>The baseline surface and groundwater quality datasets must include a list of Common water quality attributes such as Physical, chemical: pH, turbidity, suspended solids, temperature, Dissolved Oxygen (DO), Biochemical Oxygen Demand (BOD), Chemical Oxygen Demand (COD), dissolved solids, salinity, conductivity and for groundwater should include; Groundwater flow directions, Locations/flows of springs and seeps, groundwater discharge locations in streams, groundwater uses, depth to groundwater under different seasonal conditions, geology and locations of aquifers, thicknesses, and their hydraulic conductivity ranges. Describing baseline surface water quality should provide detailed information on the location, distribution, quantity, and quality of all water resources that could be affected by a project and its alternatives. The data and analysis should have a reasonable level of detail, to help understand the conditions of the environmentally important geographic locations. When baseline water quality (surface water or groundwater) samples are collected, they should be analyzed for the full suite of parameters and contaminants of concern. This baseline surface and groundwater quality datasets contain seven feature classes including Water pH, Turbidity, TSS (Total Suspended Sediment), salinity, water quality point, Fe Total, and Mn Total. <xref ref-type="fig" rid="fig9">Figure 9</xref> illustrates the design of the geodatabase in the ArcGIS/ArcCatalog software. Attributes of these future classes are further illustrated in <xref ref-type="table" rid="table7">Table 7</xref>.</p></sec><sec id="s3_7"><title>3.7. Creating the Baseline Soil Quality Dataset</title><p>The baseline soil quality datasets mainly contain feature classes related to soil based on conditions typically found in the mining concession area. Soil baseline studies are based on three major sources of information: desk study, fieldwork, and laboratory analysis. Baseline soil quality datasets should include measurements of these common parameters: soil composition, soil strength (resistance to crushing), mineral content, and pH. Some measure of water content, organic content, soil texture, particle size, and bulk density. This dataset contains six feature classes includes soil sample points, dumping soil area, soil pH, Cation exchange capacity, Soil nutrient (potassium, calcium, magnesium, nitrogen, phosphorus), and Heavy metals (lead, copper, zinc, cadmium, mercury, and chromium). <xref ref-type="fig" rid="fig1">Figure 1</xref>0 illustrates the design of the geodatabase in the ArcGIS/ArcCatalog software. Attributes of these future classes are further illustrated in <xref ref-type="table" rid="table8">Table 8</xref>.</p><table-wrap id="table7" ><label><xref ref-type="table" rid="table7">Table 7</xref></label><caption><title> Description of the baseline surface and groundwater dataset</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >No</th><th align="center" valign="middle" >LAYER</th><th align="center" valign="middle" >Requirement Level</th><th align="center" valign="middle" >Geometry Type</th><th align="center" valign="middle" >Required Attributes</th></tr></thead><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >Water quality point</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Water Quality ID, Shape, Point Name, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >TSS (Total Suspended Sediment)</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" ></td><td align="center" valign="middle" >Water Quality ID, Shape, Point Name, TSS, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Iron (Fe) Total</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Water Quality ID, Shape, Point Name, Fe Total, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >4</td><td align="center" valign="middle" >Mn Total</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Water Quality ID, Shape, Point Name, Fe Total, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >5</td><td align="center" valign="middle" >Water pH</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Water Quality ID, Shape, Point Name, pH, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >6</td><td align="center" valign="middle" >Turbidity</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Water Quality ID, Shape, Point Name, Turbidity, X_Coordinates, Y_Coordinates Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >7</td><td align="center" valign="middle" >Salinity</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Water Quality ID, Shape, Point Name, Salinity, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr></tbody></table></table-wrap><table-wrap id="table8" ><label><xref ref-type="table" rid="table8">Table 8</xref></label><caption><title> Description of the baseline soil quality datasets</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >No</th><th align="center" valign="middle" >LAYER</th><th align="center" valign="middle" >Requirement Level</th><th align="center" valign="middle" >Geometry Type</th><th align="center" valign="middle" >Required Attributes</th></tr></thead><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >Soil quality point</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Soil Quality ID, Shape, Soil type, X_Coordinates, Y_Coordinates sample depth, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >Dumping soil area</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Soil Quality ID, Shape, Soil type, Shape area, shape length, sample depth, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Soil pH</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Soil Quality ID, Shape, Point Name, Soil type, pH, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >4</td><td align="center" valign="middle" >Heavy metals</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Soil Quality ID, Shape, Point Name, Soil type, heavy metals, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >5</td><td align="center" valign="middle" >Cation exchange capacity</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Soil Quality ID, Shape, Point Name, Soil type, exchange capacity, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >6</td><td align="center" valign="middle" >Soil nutrient</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Soil Quality ID, Shape, Point Name, Soil type, nutrients, X_Coordinates, Y_Coordinates Mapping Date, Remarks</td></tr></tbody></table></table-wrap></sec><sec id="s3_8"><title>3.8. Creating the Baseline Socio-Economic Dataset</title><p>The socio-economic environment is defined as all activities, and social and economic processes, that could be influenced directly or indirectly by the mining project which includes the size and distance of built environment, built-up, cultural values, historical monuments, the function of the examined area. This dataset contains nine feature class includes, socio-economic quality point, Quality of life, Housing quality and quantity (this is particularly important if people are to be relocated), Public safety (police, fire), Education (average level, access, public and/or private), Health services, Recreation (public, private), public services sanitation, livelihood. In this dataset, the field attributes related to field measurement results are not filled in using specific code but filled with real results of field measurements. <xref ref-type="fig" rid="fig1">Figure 1</xref>1 illustrates the design of the geodatabase in the ArcGIS/ArcCatalog software. Attributes of these future classes are further illustrated in <xref ref-type="table" rid="table9">Table 9</xref>.</p></sec><sec id="s3_9"><title>3.9. Creating the Baseline Population Dataset</title><p>The baseline population datasets mainly contain location of the local population about the proposed project area, this dataset contains four feature classes which includes population size, (age composition, growth) Economic activities, employment facility and income (inventory of present economic environment without the project) usually measured with surveys and interviews. <xref ref-type="fig" rid="fig1">Figure 1</xref>2 illustrates the Composite baseline population dataset; <xref ref-type="fig" rid="fig1">Figure 1</xref>2 illustrates the design of the geodatabase in the ArcGIS/ArcCatalog software. Attributes of these future classes are further illustrated in <xref ref-type="table" rid="table1">Table 1</xref>0.</p></sec><sec id="s3_10"><title>3.10. Creating Baseline Waste Management Dataset</title><p>The baseline waste management dataset contains six feature classes related to waste generated during the mining operation. This dataset includes waste point, solid waste, chemical waste, waste treatment plant (WTP), tailings impoundment facility, and tailings disposal. <xref ref-type="fig" rid="fig1">Figure 1</xref>3 illustrates the Composite baseline waste management dataset; <xref ref-type="fig" rid="fig1">Figure 1</xref>3 illustrates the design of the geodatabase in the ArcGIS/ArcCatalog software. Attributes of these future classes are further illustrated in <xref ref-type="table" rid="table1">Table 1</xref>1. Each feature class contains information include point name, spatial position, and field check result.</p><table-wrap id="table9" ><label><xref ref-type="table" rid="table9">Table 9</xref></label><caption><title> Description of the baseline socio-economic dataset</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >No</th><th align="center" valign="middle" >LAYER</th><th align="center" valign="middle" >Requirement Level</th><th align="center" valign="middle" >Geometry Type</th><th align="center" valign="middle" >Required Attributes</th></tr></thead><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >Socio-economic</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Socio-Economic ID, SE type, Village, town X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >Quality of life</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >point</td><td align="center" valign="middle" >Socio-Economic ID, Shape, SE type, Village, Town, Quality of life, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Housing quality and quantity</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Socio-Economic ID, SE type, Village, town, housing quality, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >4</td><td align="center" valign="middle" >Public safety facility</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Socio-Economic ID, SE type, Village, town, facility type, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >5</td><td align="center" valign="middle" >Education facility</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Socio-Economic ID, SE type, Village, town, facility type, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >6</td><td align="center" valign="middle" >Health facility</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Socio-Economic ID, SE type, Village, town, facility. type, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >7</td><td align="center" valign="middle" >Recreation facility</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Socio-Economic ID, SE type, Village, town, facility. type, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >8</td><td align="center" valign="middle" >public services sanitation</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Socio-Economic ID, SE type, Village, town, facility. type, X_Coordinates, Y_Coordinates, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >9</td><td align="center" valign="middle" >Livelihood</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Socio-Economic ID, shape, shape area, shape length SE type, Village, town, livelihood type, Mapping Date, Remarks</td></tr></tbody></table></table-wrap><table-wrap id="table10" ><label><xref ref-type="table" rid="table1">Table 1</xref>0</label><caption><title> Description of the baseline population dataset</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >No</th><th align="center" valign="middle" >LAYER</th><th align="center" valign="middle" >Requirement Level</th><th align="center" valign="middle" >Geometry Type</th><th align="center" valign="middle" >Required Attributes</th></tr></thead><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >Population size</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Population ID, age composition, size, growth, X_Coordinates, Y_Coordinates Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >Economic activities</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Population ID, age composition, size, growth, activity, X_Coordinates, Y_Coordinates Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Employment facility</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Population ID, age composition, size, growth, facility, X_Coordinates, Y_Coordinates Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >4</td><td align="center" valign="middle" >Income</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Population ID, age composition, size, growth, income type, X_Coordinates, Y_Coordinates Mapping Date, Remarks</td></tr></tbody></table></table-wrap><table-wrap id="table11" ><label><xref ref-type="table" rid="table1">Table 1</xref>1</label><caption><title> Description of the baseline waste management dataset</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >No</th><th align="center" valign="middle" >LAYER</th><th align="center" valign="middle" >Requirement Level</th><th align="center" valign="middle" >Geometry Type</th><th align="center" valign="middle" >Required Attributes</th></tr></thead><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >Waste point</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Waste ID, Shape, Point Name X_Coordinates, Y_Coordinates Results, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >Solid waste</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Waste ID, Shape, Point Name X_Coordinates, Y_Coordinates Results, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Chemical waste</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Waste ID, Shape, Point Name X_Coordinates, Y_Coordinates Results, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >4</td><td align="center" valign="middle" >Waste treatment plant (WTP)</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Waste ID, Shape, Point Name X_Coordinates, Y_Coordinates Results, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >5</td><td align="center" valign="middle" >Tailings impoundment facility (TIF)</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Waste ID, Shape, Shape Name, Shape length, Shape Area, Results, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >6</td><td align="center" valign="middle" >Tailings disposal site (TDS)</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >Waste ID, Shape, Shape Name, Shape length, Shape Area, Results, Mapping Date, Remarks</td></tr></tbody></table></table-wrap></sec><sec id="s3_11"><title>3.11. Creating the Baseline Climate Change Dataset</title><p>The baseline climate change dataset contains six feature classes related to climate conditions around the surroundings of the mine site operation and concession area. This dataset includes a Concession area, Rainfall, temperature, air, protected, and sensitive areas. <xref ref-type="fig" rid="fig1">Figure 1</xref>4 illustrates the design of the geodatabase in the ArcGIS/ArcCatalog software. Attributes of these future classes are further illustrated in <xref ref-type="table" rid="table1">Table 1</xref>2. Each feature class contains information include point name, spatial position, and field check result.</p></sec><sec id="s3_12"><title>3.12. Composition of the Baseline GIS Spatial Geodatabase Template</title><p>The baseline environmental GIS spatial database template for a proposed mining project contained ten (10) datasets with seventy-one (71) feature classes as shown in <xref ref-type="fig" rid="fig1">Figure 1</xref>5. Geographic information systems (GIS) are founded upon the capability to organize information into a series of layers that can be integrated using geographic location. As a fundamental level, each GIS dataset is organized as a series of thematic layers to represent and answer questions about a particular problem set such as environmental impact assessment of mining. The basis of this step enables us to arrange the datasets required to support the baseline database of the EIA of mining and organized these data into logical feature sets. As it was discussed these blocks represent data groups or feature datasets. This provides us with a framework for understanding the design process that was presented throughout the geodatabase design. The geographic representations are organized in a series of thematic layers. A thematic layer is a collection of common geographic elements, such as road network, a collection of parcel boundaries, land use types, soil types, and elevation surface, and satellite imagery for a certain date or well locations. This concept of a thematic layer is to describe the distribution of the baseline data phenomenon and how it should be portrayed across a geographic extent. Most of the themes should be represented by a single collection of homogeneous features while other themes are represented by multiple datasets. Gridded datasets should be used to represent continuous surfaces, such as elevation, georeferenced imagery, slope, and aspect.</p><p>These data collections should be organized as feature classes and raster-based data layers. <xref ref-type="fig" rid="fig1">Figure 1</xref>5 shows the overall view of the structure of the baseline spatial geodatabase datasets of Environmental Impact Assessments of mining. There are 10 environmental datasets and 71 feature classes. Those featured classes were grouped into feature datasets. Parameters which have the same characteristic and belong to a specific theme were grouped and organized into one</p><table-wrap id="table12" ><label><xref ref-type="table" rid="table1">Table 1</xref>2</label><caption><title> Description of the baseline climate change dataset</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >No</th><th align="center" valign="middle" >LAYER</th><th align="center" valign="middle" >Requirement Level</th><th align="center" valign="middle" >Geometry Type</th><th align="center" valign="middle" >Required Attributes</th></tr></thead><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >Concession area (CA)</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >CA ID, Shape, Shape Name, Shape length, Shape Area, Results, Mapping Date Remarks</td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >Rainfall</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >CA ID, Shape, Point Name X_Coordinates, Y_Coordinates Results, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Temperature</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >CA ID, Shape, Point Name X_Coordinates, Y_Coordinates Results, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >4</td><td align="center" valign="middle" >Air</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Point</td><td align="center" valign="middle" >Waste ID, Shape, Point Name X_Coordinates, Y_Coordinates Results, Mapping Date, Remarks</td></tr><tr><td align="center" valign="middle" >5</td><td align="center" valign="middle" >Protected areas</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >CA ID, Shape, Shape Name, Shape length, Shape Area, Results, Mapping Date Remarks</td></tr><tr><td align="center" valign="middle" >6</td><td align="center" valign="middle" >Sensitive areas</td><td align="center" valign="middle" >Required</td><td align="center" valign="middle" >Polygon</td><td align="center" valign="middle" >CA ID, Shape, Shape Name, Shape length, Shape Area, Results, Mapping Date Remarks</td></tr></tbody></table></table-wrap><p>feature dataset. The grouping is not based on feature data type and attributes fields and it combines features that logically belong together. The datasets and data layers are grouped and subcategorized into blocks. As shown in <xref ref-type="fig" rid="fig1">Figure 1</xref>5. The above blocks develop the conceptual data model, model features based on the data needed for the environmental impact assessment spatial analysis functions, and determine the spatial representation (i.e. point, polygon, line, image, surface) and non-spatial representation (i.e. attributes) of each feature. These blocks also create the logical data model, which will link the conceptual model with a GIS geodatabase. The list above is sorted by layer category, shows the vector data layers in the geodatabase that model real-world features as points, lines, or polygons in a UTM (WGS 1984) projected geographic coordinate system.</p></sec></sec><sec id="s4"><title>4. Conclusion</title><p>Baseline Environmental Impact Assessment (EIA) of mining projects in Sierra Leone creates a challenging environment for data collection and impact prediction. Geographic information systems (GIS)-based EIA, using appropriate spatial analysis methods can sufficiently reduce the challenges created by mining environments. However, application of GIS in mining EIA is always constrained by availability of an appropriate baseline digital geodatabase on environmental attributes, due to 1) the absence of comprehensive understanding of interrelated environment impacts caused by the mining of different minerals, 2) the environmental uniqueness of each mine, which makes it difficult to develop general tools of EIA analysis and models, 3) the availability of adequate spatial data, information and appropriate GIS techniques, 4) because of the dynamic characteristics and multivariate nature of the environment, it has often been difficult to collate, analyze and interpret its datasets, 5) lack of appropriate temporal and spatial resolution of remotely sensed imageries and accurate geospatial data can be a major limitation on spatial modeling, 6) finally, the availability of GIS professionals and affordability of GIS software and related hardware is a major constraint on EIA budgeting, especially for developing countries like Sierra Leone, on the other hand, with the rapid fall in price of PCs, internet service, open source GIS, online GIS, GPS integrated mobiles, and freely downloadable mobile apps there is an immense scope in geovisualization of spatio-temporal impacts of such EIA studies in mining areas. Therefore developing a Geographic Information Systems baseline geodatabase template for the evaluation of potential and predicted environmental impact for sustainable environmental impact assessment of mining in Sierra Leone will provide support to the data acquisition process of environmental impact assessment and offers a concept for developing analysis methods for environmental management of mining to minimize the undesired environmental impacts of mining and give an optimal proposal for data collection and analysis of mining industry in attaining sustainable development in Sierra Leone. Due to the limited available data, a conceptual GIS database template has been developed rather than a database case study of a mining site. No site investigation and data collection were undertaken. According to the trial done on the baseline GIS spatial geodatabase template, it has shown some encouraging results for evaluating potential and predicted environmental impacts assessment of mining projects in Sierra Leone. However, using the baseline spatial geodatabase template has many advantages; however, there are also several challenges to implement it. The geospatial database template was designed using ArcCatalog, ArcGIS 10.7.1. software. This offers a tempting avenue for further studies on designing environmental spatial analysis models for environmental impact assessment and ways of integrating into GIS.</p></sec><sec id="s5"><title>Conflicts of Interest</title><p>The author declares no conflicts of interest regarding the publication of this paper.</p></sec><sec id="s6"><title>Cite this paper</title><p>Kamara, S. M. (2020). Development of a Geographic Information Systems Baseline Spatial Geodatabase Template for Evaluating Potential and Predicted Environmental Impacts for Sustainable Environmental Impact Assessment of Mining in Sierra Leone. Journal of Geoscience and Environment Protection, 8, 262-284. https://doi.org/10.4236/gep.2020.810018</p></sec></body><back><ref-list><title>References</title><ref id="scirp.103882-ref1"><label>1</label><mixed-citation publication-type="book" xlink:type="simple">Bulla, M., Keresztes, P., &amp; Kóczy, T. L. (2004). A k&amp;ouml;rnyezetben lejátszódó folyamatok elemzése Soft Computing módszerekkel. [Evaluation of Environmental Processes by/ using Soft Computing Methods.] In M. Bulla (Ed.), Komplex k&amp;ouml;rnyezetállapot-értékel&amp;#337; szakért&amp;#337;i rendszerek metodikai fejlesztése (pp. 119-129). Gy&amp;#337;r: Department of Environmental Engineering, Széchenyi István University. (In Hungarian)</mixed-citation></ref><ref id="scirp.103882-ref2"><label>2</label><mixed-citation publication-type="other" xlink:type="simple">EPA-SL Act (2010).</mixed-citation></ref><ref id="scirp.103882-ref3"><label>3</label><mixed-citation publication-type="other" xlink:type="simple">Kamara, S. M. (2019). Integration of GIS in the Development of an Environmental Cadastre Administrative System for the Environment. Protection Agency Sierra Leone. Journal of Geographic Information System, 11, 411-428. https://doi.org/10.4236/jgis.2019.114026.</mixed-citation></ref><ref id="scirp.103882-ref4"><label>4</label><mixed-citation publication-type="other" xlink:type="simple">Maryati, S., Shimada, H., Sasaoka, T., Hamanaka, A., Matsui, K., &amp; Nagawa, H. (2012). GIS Database Template for Environmental Management of Mining in Indonesia. Journal of Geographic Information System, 4, 62-70 http://dx.doi.org/10.4236/jgis.2012.41009</mixed-citation></ref></ref-list></back></article>