DISDI SDSFIE 3.0 Adaptation

Transcription

1 Defense Installation Spatial Data Infrastructure Program DISDI SDSFIE 3.0 Adaptation Requirements Analysis Prepared by: Geographic Information Services, Inc. 7/12/2012

2 Table of Contents 1. SDSFIE Overview Conceptual Framework for the DISDI Adaptation Report Format DISDI Requirements DISDI Common Installation Picture (DISDI CIP) Essential Business Processes Data Requirements I&E Community Requirements Department of Defense Explosive Safety Board (DDESB) Essential Business Processes Data Requirements Defense Critical Infrastructure Program (DCIP) Essential Business Processes Data Requirements Sustainable Ranges Initiative (SRI) Essential Business Processes Data Requirements Summary of Requirements... 18

3 1. SDSFIE Overview The Spatial Data Standards for Facilities, Installations, and Environment (SDSFIE) is a standard developed by the Defense Installation Spatial Data Infrastructure (DISDI) Group and implemented across the Department of Defense (DoD) for management of their installations and environment (I&E) geospatial data. SDSFIE has evolved over time into a well-defined collection of geospatial feature types that map the essential business processes of the I&E community. The current version of SDSFIE (3.0) is designed to provide a core standard (SDSFIE 3.0 Gold) that can be profiled or extended based on the unique needs of the implementing organization. The process of profiling and extending SDSFIE is known as adaptation. The DISDI Group established a tiered or top-down approach to adapting SDSFIE in the DoD Guidance for the Adaptation of SDSFIE 3.0 v1.0. Adaptations are first created by headquarters-level organizations that belong to the DISDI Community of Interest (COI), for example Army, Navy, Air Force, Marine Corps, and Army Corps of Engineers. Each Component in the DISDI COI then develops its own implementation strategy. The implementation strategy and subsequent policy contains the specific process for developing further Adaptations building upon the Component s approved Adaptation as a basis for modification. 2. Conceptual Framework for the DISDI Adaptation The DISDI Adaptation of SDSFIE addresses the geospatial data requirements and business processes of the DISDI Program itself (in the form of the DISDI Common Installation Picture (DISDI CIP)), the DoD Explosive Safety Board (DDESB), the Sustainable Ranges Initiative (SRI), and the Defense Critical Infrastructure Program (DCIP). Each of these organizations has unique responsibilities and geospatial data requirements that serve all DoD Components and that are not necessarily covered by any one Component s SDSFIE Adaptation. The DISDI Adaptation will capture the principal geospatial data requirements for these organizations, which will position these organizations to fully implement SDSFIE Report Format This report includes the following: 1. An overview of each community. 2. An analysis of each community s essential business processes, specifically focusing on geospatial data and associated requirements. 3. A list of geospatial data requirements specific to each community. 4. A list of the combined geospatial data requirements for all communities. 1

4 4. DISDI Requirements 4.1 DISDI Common Installation Picture (DISDI CIP) The DISDI CIP is a specified set of geospatial datasets (layers) requested by the Office of the Deputy Under Secretary of Defense for Installations and Environment (ODUSD (I&E)) from all DoD Components on an annual basis. The DISDI Program compiles all of the submitted data for the enterprise purposes of Homeland Defense, situational awareness, sharing with all authorized users inside or outside of DoD, and for display in the DISDI Portal. The primary data types included in DISDI CIP are those which provide the location of real property assets as defined in DoD Instruction These data were designated as having priority for the Installation Geospatial Information and Services (IGI&S) Programs under a guidance memorandum issued by the DUSD(I&E) in April, Essential Business Processes The DISDI CIP is designed to provide a single source for the geospatial data necessary to analyze and answer strategic questions related to DoD facilities, infrastructure, and environment. The DISDI CIP is also a mechanism to compile mission-critical SDSFIE-compliant data from the DISDI COI and make those data discoverable, understandable and accessible via the DISDI Portal. The process of compilation of this data allows DISDI to analyze and understand how common feature types and attributes are being used and populated across the I&E community, a form of "metrics" intended to inform future Departmentlevel guidance regarding data quality. The DISDI CIP is a defined subset of each Component s SDSFIE data. The 2011 DISDI CIP Request was based on SDSFIE 2.6 feature types (Table 1) because SDSFIE 3.0 had not been implemented across DoD. A list of requested layers along with a minimum level of attribution (RPSUID, RPUID, and associated locational and reference information) was sent as a formal request from DUSD(I&E). The Components then provided their best available data of the layers requested. In many cases, all layers are not maintained by the Components (Table 2) or the relative frequency of features within a layer varies among Components (Figure 1). Additionally, each Component collects a slightly different set of attributes for their data layers. Variations in the way geospatial data are collected and maintained depend on the unique missions of the DoD Components. For example, the differing number of features in the road_centerline feature type among the Components is influenced by the total length of all roads maintained, the method for dividing the lines that represent the geometry of the road, and the method used to determine which roads are mapped (Table 2). These variations were identified during the pilot phase of adapting SDSFIE 3.0, but the variations were not uniformly documented. Documenting these data metrics for the DISDI CIP feature types was a key objective of this analysis. 2

5 Table 1. DISDI CIP 2011 feature types. Feature Type Name (SDSFIE 2.6) Feature Class Geometry gate_line line gate_point point military_access_point point installation_area air_accident_zone_area road_bridge_area shed_site point and/or structure_existing_site point and/or environmental_restoratn_site point and/or oe_hazard_concern_site point and/or oe_hazard_invest_sector_area oe_hazards_rac_score_area fence_line line golf_course_area dudded_impact_site point and/or non_dudded_impact_area historic_impact_area dod_rpi_land_parcel_area military_range_area military_live_fire_range_area training_site point and/or military_parade_ground_site point and/or military_training_sub_site point and/or airfield_surface_area curb_area pedestrian_sidewalk_area road_area vehicle_driveway_area railroad_centerline line athletic_court_area athletic_field_area swimming_pool_area boating_site point and/or hunting_area miscellaneous_recreation_area picnic_site point and/or recreation_park_area road_centerline line dod_rpi_site_area* tower_site point and/or vehicle_parking_area wetland_area *dod_rpi_site_area is part of the Defense Siting Locations dataset 3

6 Table 2. DISDI CIP feature type (SDSFIE 2.6) record counts by Service. Feature types collected by all Components are in bold type. Feature Type Name (2.6) USA USAF USN USMC ARNG ANG Combined air_accident_zone_area airfield_surface_area 2,352 9,721 3,956 1,041 5,194 22,264 athletic_court_area 1,115 1,296 1, ,634 athletic_field_area ,075 boating_area 1 1 curb_area 1,997 1,997 dod_rpi_land_parcel_area dod_rpi_site_area dudded_impact_area environmental_restoratn_area 3, ,739 fence_line 156,326 74, ,599 41,848 13,368 11, ,178 gate_line 13,299 15,125 4,131 3,830 36,385 gate_point 5,862 10,643 2,145 18,650 golf_course_area 1, , ,403 historic_impact_area hunting_area 1,420 1,420 installation_area , ,423 military_access_point military_live_fire_range_area military_parade_ground_area 9 9 military_range_area 2, ,290 military_training_sub_area miscellaneous_recreation_area non_dudded_impact_area oe_hazard_concern_area oe_hazard_invest_sector_area oe_hazards_rac_score_area 0 0 pedestrian_sidewalk_area 72,920 79,840 44,554 26,074 12,952 8, ,174 picnic_area railroad_centerline 30,720 4,257 7,735 1, ,020 recreation_park_area road_area 51,879 21,745 20,832 9,357 13,269 3, ,747 road_bridge_area 1, ,764 road_centerline 409,229 87,764 91,756 19,145 39,163 18, ,685 shed_area 4,522 5,771 1,421 11,714 structure_existing_area 214, , ,433 41,851 25,275 23, ,551 swimming_pool_area tower_area tower_point 1, ,412 training_area 2, ,340 vehicle_driveway_area 48,148 57,341 35,221 18,157 17, ,498 vehicle_parking_area 34,551 33,400 24,584 8,606 9,131 9, ,951 wetland_area 678,322* 11,743 16, ,380 Total 1,744, , , , , ,305 3,172,952 * Wetlands represent a disproportionate number of records in the data submitted by the USA because of the inclusion of National Wetlands Inventory features from outside installation boundaries. 4

7 1,200,000 1,000, , , , ,000 vehicle_parking_area vehicle_driveway_area tower_point structure_existing_area shed_area road_centerline road_bridge_area road_area railroad_centerline pedestrian_sidewalk_area military_range_area installation_area golf_course_area gate_point gate_line fence_line athletic_field_area athletic_court_area airfield_surface_area 0 ANG ARNG USA USAF USMC USN Figure 1. An example subset of DISDI CIP feature type (SDSFIE 2.6) record counts by Service. Only feature types with 2,000 or more features are included. Wetlands are excluded because they represent a disproportionate number of total features in USA data. To accommodate the migration from SDSFIE 2.6 to 3.0 by all Components, a new version of the DISDI CIP will be developed using SDSFIE 3.0 (Table 3). Each existing DISDI CIP layer will be translated into the new standard using the published crosswalk where possible. In cases where existing DISDI CIP layers do not crosswalk directly to 3.0 new feature classes will be created according to the DoD Guidance for the Adaptation of SDSFIE 3.0 v1.0. 5

8 Table 3. DISDI CIP SDSFIE 2.6 to 3.0 feature type crosswalk. Feature Type Name (2.6) Feature Type Name (3.0) gate_line AccessControl gate_point AccessControl military_access_point AccessControl installation_area AdministrativeBoundary air_accident_zone_area AirAccidentZone road_bridge_area Bridge structure_existing_site Building shed_site Building oe_hazard_concern_site EnvironmentalRemediationSite environmental_restoratn_site EnvironmentalRemediationSite oe_hazard_invest_sector_area EnvironmentalRemediationSite oe_hazards_rac_score_area EnvironmentalRemediationSite fence_line Fence golf_course_area GolfCourse dudded_impact_site ImpactArea non_dudded_impact_area ImpactArea historic_impact_area ImpactArea dod_rpi_land_parcel_area LandParcel military_live_fire_range_area MilitaryRange military_range_area MilitaryRange military_training_sub_site MilitaryTrainingLocation training_site MilitaryTrainingLocation military_parade_ground_site MilitaryTrainingLocation airfield_surface_area PavementSection pedestrian_sidewalk_area PavementSection curb_area PavementSection vehicle_driveway_area PavementSection railroad_centerline RailSegment athletic_court_area RecreationArea athletic_field_area RecreationArea boating_site RecreationArea swimming_pool_area RecreationArea recreation_park_area RecreationArea hunting_area RecreationArea picnic_site RecreationArea miscellaneous_recreation_area RecreationArea road_area RoadArea road_centerline RoadCenterline dod_rpi_site_area Site tower_site Tower vehicle_parking_area VehicleParking wetland_area Wetland 6

9 Data Requirements The DISDI CIP data requirements are based on the information in the memo 2011 Update of DoD Common Installation Picture and Site Location Data, August 29, 2011, Director of Business Enterprise Integration. The specifically requested layers are listed in one of the memo s attachments, 2011 DISDI Common Installation Picture (CIP) Data Request Technical Information document. Each of the requested SDSFIE 2.6 layers in the DISDI CIP was translated to an equivalent SDSFIE 3.0 feature type based on the crosswalk in the previous section. Twenty-one feature types are included in the proposed DISDI CIP feature types (Table 4). The 2011 DISDI CIP contained 42 layers as defined per SDSFIE 2.6. The reduced number in the proposed DISDI CIP reflects changes to the design of the SDSFIE data model that included the merging of various feature types into common classes. For example, gate_point and military_access_point both belong to the SDSFIE 3.0 feature type AccessControl. The proposed DISDI CIP layers contain two new feature types, RoadCenterline and RoadArea. Although these feature types are not part of the SDSFIE 3.0 Gold data model, they have been identified as containing a significant number of features (Table 2) and are therefore important for creating a CIP. Table 4. Proposed feature types for DISDI CIP compared to other I&E communities. New feature types that are not present in SDSFIE 3.0 Gold are bold and italicized. Feature Type Name DISDI CIP DCIP DDESB SRI AccessControl AdministrativeBoundary AirAccidentZone Bridge Building EnvironmentalRemediationSite Fence GolfCourse ImpactArea LandParcel MilitaryRange MilitaryTrainingLocation PavementBranch PavementSection RailSegment RecreationArea RoadArea RoadCenterline RoadPath RoadSeg Site Tower VehicleParking Wetland 7

10 5. I&E Community Requirements 5.1. Department of Defense Explosive Safety Board (DDESB) The DDESB was established by Congress in 1928 after a fatal accident at the Naval Ammunition Depot at Lake Denmark, New Jersey. DDESB states: The DDESB mission is to provide objective advice to the Secretary of Defense and Service Secretaries on matters concerning explosives safety and to prevent hazardous conditions to life and property on and off Department of Defense installations from the explosives and environmental effects of DoD titled munitions. To fulfill their mission, DDESB develops policy guidance and has supported the creation of Explosive Safety Siting (ESS) software used to perform explosive quantity distance analysis and to generate quantity distance arcs for site planning activities. ESS is an important component of the Automated Site Planning process, the key mechanism by which DoD accomplishes the DDESB mission Essential Business Processes The ESS software is developed and maintained by the Naval Facilities Engineering Command Engineering Service Center (NAVFAC ESC) but designed to be used across DoD. ESS uses SDSFIE data as inputs for the explosive safety site planning process to determine possible impacts to personnel and structures surrounding areas where explosives are being stored or handled. Some examples of handling and storage areas are an entire building, a portion of a building, a pier, or a parking lot. Handling and storage locations may be temporary or permanent and must be approved through submission of a site plan that includes geospatial representation of explosive quantity distances. The ESS software uses a geospatial representation of these handling and storage areas to generate the required quantity distance arcs that can be mapped and submitted with site planning documents Data Requirements The current version of the ESS software is designed to use SDSFIE 2.6 data. Ongoing software development will incorporate the new SDSFIE 3.0 data. Twelve feature types have been identified as requirements for the ESS software (Table 5). Ten of the identified feature types are present in SDSFIE 3.0 Gold and two are newly identified feature types. The twelve identified feature types are related to specific input and output ESS data requirements. NAVFAC ESC also plans to build into ESS the ability to read in all Component SDSFIE Adaptations instead of requesting Components to provide their SDSFIE data in using a specified schema. The feature types identified for this Adaptation represent what is necessary for ESS. Table 5. Proposed feature types for DDESB compared to other I&E communities. New feature types that are not present in SDSFIE 3.0 Gold are bold and italicized. Feature Type Name DDESB DISDI CIP DCIP SRI AdministrativeBoundary AmmunitionStorage Building ExplosivesHandlingArea 8

11 Feature Type Name DDESB DISDI CIP DCIP SRI MilitaryQuantityDistanceArc MilQuantityDistanceCombinedArc MilQuantityDistanceArc_Planned PavementSection RailSegment Shoreline Structure VehicleParking 5.2. Defense Critical Infrastructure Program (DCIP) The DCIP is responsible for the management of risk to Defense Critical Infrastructure (DCI) according to DoD Directive DCIP coordinates with Federal, State, local, regional, territorial, and tribal entities, as well as the private sector and foreign countries where appropriate. National defense and economic vitality is dependent on the availability of DoD and non-dod critical infrastructure. For example, an installation may buy energy from a local energy company. DCIP manages risk by developing procedures and initiatives that are based on analysis and assessment of threats to defense critical infrastructure Essential Business Processes The interconnectivity of agencies, departments, the military, private industry, tribal entities, and the public business arena is crucial for DCI resiliency. DCIP uses a variety of methods for conducting analysis and assessments of the interconnected components of defense critical infrastructure, including geospatial analysis. DCIP responsibilities requiring geospatial data include analysis of vulnerabilities to critical infrastructure, alternative route planning, and population of situational awareness tools. DCIP analysis and assessment methods are adaptive according to the particular focus of a project and can require geospatial data covering a variety of disciplines. DCIP leverages several geospatial tools to accomplish its mission. Some examples include the Strategic Mission Assurance Data System (SMADS), the Homeland Defense Mission Assurance Portal (HD-MAP), the Knowledge Display Aggregate System (KDAS), and TRITON. These geospatial tools are used in all of the previously listed areas of DCIP responsibility, including DCI analysis, assessment, and situational awareness. DCIP protects against any threat to DCI, which can include natural, accidental, or deliberate causes. According to DCIP, Components are responsible for: Analyzing and assessing the potential impact to DoD operations that would result from a loss or degradation of critical infrastructure. Managing the risk of potential loss, degradation, or disruption of the infrastructure through remediation and/or mitigation efforts. Conducting outreach and education with all DCI and Mission owners. Supporting incident management when critical infrastructure is involved. 9

12 Data Requirements DCIP requirements include both DoD and non-dod owned sources for critical infrastructure data. Power, transportation, telecommunications, and water supply data are the primary SDSFIE feature types needed by DCIP. DCIP data requirements can be divided among three broad business categories: analytics, assessments, and situational awareness. Some of the required feature types are only necessary for a single category but many feature types are necessary for two or more categories (Table 6). Of the three categories, DCIP considers the analytics category to be of primary importance, therefore only those feature types that are required for analytics are included in the list of feature types identified as necessary to meet DCIP data requirements (Table 7). No new feature types are recommended. In addition to the feature types and business categories identified, DCIP utilizes a wide array of web mapping applications. An important requirement for DCIP is for SDSFIE data to be made available via web map services (WMS) that can be displayed as layers in the various web mapping applications mentioned in the previous section. The WMS layers would enhance DCIP s ability to perform analytics and assessments and would increase situational awareness. While creating WMS layers is not within the scope of this project, it would be a logical next step for use of the data described in the DISDI Adaptation. 10

13 Table 6. DCIP feature types by business categories. Feature Type Name Analytics Assessments Situational Awareness AboveGroundStorageTank AccessControl AdministrativeBoundary AmmunitionStorage ArrivalPoint BankArmoring Bridge Building ChannelLine ClosureStructure CommUtilityNode CommUtilitySegment Dam DocksAndWharfs DodFormerlyUsedDefense DredgingEvent ElectricalUtilityNode ElectricalUtilitySegment ElevationContour EmagRadiationHazard EnvironmentalDischargePoint EnvironmentalRemediationSite EnvironmentalSampleLocation Fence Fender FloodControlEncroachment FloodControlProtectedLocation FloodFight Floodwall FutureProjects GasUtilityNode GasUtilitySegment GolfCourse Hulk ImpactArea Inundation LandCover LandManagementZone LandmarkPoint LandRepair LandUse Levee LeveeFailure 11

14 12 Feature Type Name Analytics Assessments Situational Awareness LeveeInspection LeveeReliefWell LeveeStation Lock Marina MarineCable MarineCaution MilitaryDropZone MilitaryLandingZone MilitaryQuantityDistanceArc MilitaryRange MilitaryRangeEquipment MilitaryTarget MilitaryTrainingLocation MooringStructure MunitionsStorage NatResAcquisitionBoundary NaturalWaterbody NavigationLandmark PavementSection PlacementArea PollutionArea POLUtilityNode POLUtilitySegment PotentialEnvironmentalSite ProjectDimension ProjectReference PumpStation RadarEquipment RailroadFeature RailroadStation RailroadTurntable RailroadYard RailSegment RailTrack RestrictedArea RiverineFlowStructure RoadPointFeatureEvent RoadSeg Site SpotElevation StationLine StorageTankFarm Structure

15 Feature Type Name Analytics Assessments SupportStructure SurveyJob ThermalUtilityNode ThermalUtilitySegment ToeDrain Tower TransportationRoute TransportationTunnel UnderGroundStorageTank UnderwaterObstacle UtilityFeature VesselHoldingArea VesselRepairFacility WastewaterUtilityNode WastewaterUtilitySegment WatercourseLine WatercourseWithdrawal WaterUtilityNode WaterUtilitySegment Well WellField WrecksAndObstructions Situational Awareness Table 7. Proposed feature types for DCIP compared to other I&E communities. All feature types in this table are part of SDSFIE 3.0 Gold. Feature Type Name DCIP DISDI CIP DDESB SRI AboveGroundStorageTank AccessControl AdministrativeBoundary ArrivalPoint Bridge Building ChannelLine ClosureStructure CommUtilityNode CommUtilitySegment Dam DocksAndWharfs DredgingEvent ElectricalUtilityNode ElectricalUtilitySegment ElevationContour EnvironmentalDischargePoint EnvironmentalRemediationSite 13

16 Feature Type Name DCIP DISDI CIP DDESB SRI EnvironmentalSampleLocation Fender FloodControlEncroachment FloodControlProtectedLocation Floodwall GasUtilityNode GasUtilitySegment Hulk Inundation LandRepair LandUse LandmarkPoint Levee LeveeFailure Lock Marina MarineCable MarineCaution MilitaryDropZone MilitaryLandingZone MilitaryRange MilitaryRangeEquipment MooringStructure NavigationLandmark POLUtilityNode POLUtilitySegment PavementSection PollutionArea PotentialEnvironmentalSite RadarEquipment RailSegment RailTrack RailroadFeature RailroadStation RailroadTurntable RailroadYard RiverineFlowStructure RoadPointFeatureEvent RoadSeg Site SpotElevation StationLine StorageTankFarm Structure SupportStructure 14

17 Feature Type Name DCIP DISDI CIP DDESB SRI SurveyJob ThermalUtilityNode ThermalUtilitySegment Tower TransportationRoute TransportationTunnel UnderGroundStorageTank UnderwaterObstacle UtilityFeature VesselHoldingArea VesselRepairFacility WastewaterUtilityNode WastewaterUtilitySegment WaterUtilityNode WaterUtilitySegment WatercourseLine WatercourseWithdrawal Well WellField WrecksAndObstructions 5.3. Sustainable Ranges Initiative (SRI) The SRI primarily deals with the issue of encroachment on DoD installations. Encroachment is broadly defined as any external factors that inhibit the ability of DoD and the Military Services to use their ranges, airspace, and other operating areas to conduct effective training and testing. Most of the factors are related to incompatible land uses, for example urban development close to ranges or wind energy development along low-level flight paths. To sustain range function, SRI funds the purchase of buffer areas around DoD installations that promote compatible land use. The SRI obtains funding from Congress for the Readiness and Environmental Protection Initiative (REPI) that is designed to established conservation-related partnerships. SRI has also established regional partnerships through the Southeast Regional Partnership for Planning and Sustainability (SERPPAS) and the Western Regional Partnership (WRP) Essential Business Processes SERPPAS and WRP are regional partnerships that leverage both DoD and non-dod geospatial data for compatible land use planning. Both of these regional partnerships have created web map applications that facilitate planning and sharing of data across a range of partner organizations. Included in the web maps are several SDSFIE layers. The REPI program focuses on partnering with organizations interested in conservation to establish buffer areas around DoD installations. Planning and analysis for the REPI could benefit from the use of geospatial data but the exact requirements are difficult to determine. Much of the data necessary is 15

18 outside the boundaries of DoD installations, maintained by non-dod entities, and therefore currently outside the scope of SDSFIE. However, many of the existing SDSFIE feature types are relevant Data Requirements Geospatial data requirements that fall under SRI purview are related to analysis of compatible land use. An example of how compatible land uses are identified is the work that DoD and WRP conducted in the Mojave Desert. From an SRI perspective, some example areas of mutual concern for encroachment management include habitat, military mission requirements, proximity to protected areas, north-south alignment, threatened and endangered species, and wildlife corridors. These areas of mutual concern can be translated into SDSFIE feature types. Thirteen SDSFIE feature types have been identified as useful for SRI needs (Table 8). One new feature type is proposed for alternative energy sites. The remaining suggested feature types are present in SDSFIE 3.0 Gold. 16

19 Table 8. Proposed feature types for SRI compared to other I&E communities. New feature types that are not present in SDSFIE 3.0 Gold are bold and italicized. Feature Type Name SRI DISDI CIP DCIP DDESB AdministrativeBoundary AirAccidentZone AlternativeEnergy ExternalPropertyInterest FiringSite ImpactArea Installation LandCover LandManagementZone LandParcel LandUse MilitaryRange Site SpecialStatusSpecies SpeciesRange SpeciesSpecificHabitat TerrestrialEcologicalSystem Vegetation Wetland 17

20 6. Summary of Requirements The primary purpose of the DISDI Adaptation is to capture the unique geospatial data requirements of the DISDI CIP, DCIP, DDESB, and SRI and combine them into a single Adaptation of SDSFIE 3.0. While the DISDI CIP was the impetus for the DISDI Adaptation, DISDI leveraged the effort to document the requirements of DCIP, DDESB, and SRI in order to support these missions as well. Each organization s requirements were documented separately and then compiled into a single list of feature types for the DISDI Adaptation (Table 9). Feature types that belong to the DISDI Adaptation therefore represent the combined requirements of the DISDI CIP, DCIP, DDESB, and SRI. After combining the geospatial data requirements of the DISDI CIP, DCIP, DDESB, and SRI, the resulting list contains 113 feature types. Many feature types are unique to a single I&E community s requirements, with the majority of unique feature types being represented by the DCIP requirements. Five new feature types are proposed, two for the DISDI CIP, two for DDESB, and one for SRI. The remaining feature types were selected from SDSFIE 3.0 Gold in accordance with each I&E community s requirements. Table 9. All 113 feature types identified for DISDI Adaptation. Numbers in parentheses represent feature type count for each I&E community. New feature types that are not present in SDSFIE 3.0 Gold are bold and italicized. Feature Type Name DISDI CIP (24) DCIP (83) DDESB (12) SRI (19) AboveGroundStorageTank AccessControl AdministrativeBoundary AirAccidentZone AlternativeEnergy AmmunitionStorage ArrivalPoint Bridge Building ChannelLine ClosureStructure CommUtilityNode CommUtilitySegment Dam DocksAndWharfs DredgingEvent ElectricalUtilityNode ElectricalUtilitySegment ElevationContour EnvironmentalDischargePoint EnvironmentalRemediationSite EnvironmentalSampleLocation ExplosivesHandlingArea ExternalPropertyInterest Fence 18

21 Feature Type Name DISDI CIP (24) DCIP (83) DDESB (12) SRI (19) Fender FiringSite FloodControlEncroachment FloodControlProtectedLocation Floodwall GasUtilityNode GasUtilitySegment GolfCourse Hulk ImpactArea Installation Inundation LandCover LandManagementZone LandmarkPoint LandParcel LandRepair LandUse Levee LeveeFailure Lock Marina MarineCable MarineCaution MilitaryDropZone MilitaryLandingZone MilitaryQuantityDistanceArc MilitaryRange MilitaryRangeEquipment MilitaryTrainingLocation MilQuantityDistanceCombinedArc MilQuantityDistanceArc_Planned MooringStructure NavigationLandmark PavementBranch PavementSection PollutionArea POLUtilityNode POLUtilitySegment PotentialEnvironmentalSite RadarEquipment RailroadFeature RailroadStation RailroadTurntable RailroadYard 19

22 Feature Type Name DISDI CIP (24) DCIP (83) DDESB (12) SRI (19) RailSegment RailTrack RecreationArea RiverineFlowStructure RoadArea RoadCenterline RoadPath RoadPointFeatureEvent RoadSeg Shoreline Site SpecialStatusSpecies SpeciesRange SpeciesSpecificHabitat SpotElevation StationLine StorageTankFarm Structure SupportStructure SurveyJob TerrestrialEcologicalSystem ThermalUtilityNode ThermalUtilitySegment Tower TransportationRoute TransportationTunnel UnderGroundStorageTank UnderwaterObstacle UtilityFeature Vegetation VehicleParking VesselHoldingArea VesselRepairFacility WastewaterUtilityNode WastewaterUtilitySegment WatercourseLine WatercourseWithdrawal WaterUtilityNode WaterUtilitySegment Well WellField Wetland WrecksAndObstructions 20