Attachment 18 -- GEOFidelis Data Model Version 3.0.0.2 (9 October 2017).pdf

PDF 12 MB Posted

Attached to
U. S. Marine Corps Training & Education Command (TECOM) Range and Training Area Management Branch (RTAM) Military Operations Data Support Federal contract opportunity
Solicitation number
M67854-21-R-7901
Issued by
United States Marine Corps

View the file

Other files for this federal contract opportunity

Other files attached to U. S. Marine Corps Training & Education Command (TECOM) Range and Training Area Management Branch (RTAM) Military Operations Data Support, newest first.
File Type Posted
Attachment 26 -- Past Performance Questionnaire (Revised).docx DOCX document
Solicitation Amendment -- M67854-21-R-7901 U00001.docx DOCX document
Solicitation Questions -- M67854-21-R-7901 RTAM MILOPS GIS Data Svcs (Final).xlsx XLSX spreadsheet
Attachment 03 -- DoDI 8130 Installation Geospatial Information and Services (IGI-S) (9 April 2020).pdf PDF
Attachment 04 -- NAVFAC P-78 Real Property Inventory (RPI) Procedures Manual (July 2008).pdf PDF
Attachment 06 -- Real Property Inventory Requirements (RPIR) (January 2005).pdf PDF
Attachment 11 -- IGI-S Authoritative Data Store (ADS) Implementation Guidance (13 March 2019).pdf PDF
Attachment 05 -- Real Property Acceptance Requirements Document (RPAR) Version 2.0 (15 May 2014).pdf PDF
Attachment 07 -- Unified Facilities Criteria (UFC) Small Arms Ranges (5 March 2020).pdf PDF
Attachment 08 -- UFC Ammunition and Explosives Storage Magazines (1 May 2015).pdf PDF
Attachment 09 -- MIMICS Standard Operating Procedure (March 2019).pdf PDF
Attachment 14 -- U.S. Army SRP Military Installation Map (MIM) Production (May 2019).pdf PDF
Attachment 19 -- Current Military Operations Related Feature Class List.docx DOCX document
Attachment 25 -- Latest version of MIM and MIMICS produced for each of the required Bases and Stati.pdf PDF
Solicitation (RFP) -- M67854-21-R-7901.pdf PDF
Attachment 01 -- Section C -- PWS -- RTAM MILOPS GIS Data Svcs.docx DOCX document
Attachment 10 -- GIS Data to iNFADS and RMFSS Comparison Excel Template Document.xlsx XLSX spreadsheet
Attachment 14a -- Appendix H - MIM Finishing Review Checklist.xlsx XLSX spreadsheet
Attachment 15 -- RTAM Range Inventory Real Property Form.docx DOCX document
Attachment 21 -- Example GPS Collection Summary.pdf PDF
Attachment 23 -- Example SDZ Map.pdf PDF
Attachment 26 -- Past Performance Questionnaire.docx DOCX document
Attachment 27 -- Task Order Service Needs Form.xlsx XLSX spreadsheet
Attachment 20 -- Example Miramar SDZ Map.pdf PDF
Attachment 02 -- Data Layer Specification for Military Operations Feature Classes (15 December 2015).pdf PDF
Attachment 12 -- IGI-S ADS Implementation Guidance Annex A - Reference Architecture (13 March 2019).pdf PDF
Attachment 13 -- SDSFIE Quality (SDSFIE-Q) (12 September 2018).pdf PDF
Attachment 16 -- GEOFidelis Data Management Guide Version 2.0.1 (23 September 2011).pdf PDF
Attachment 17 -- GEOFidelis Operations Guide Version 1.0 (March 2011).pdf PDF
Attachment 22 -- Military Operations Data Status Stoplight Diagram (September 2020).pdf PDF
Attachment 24 -- Example Deviations Map.pdf PDF
Show all 31

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

GEOFidelis Data Model

Version: 3.0.0.2

Prepared for:

HQMC Installation Geospatial Information and Services Program (GEOFidelis)

October 9, 2017

TABLE OF CONTENTS

TABLE OF CONTENTS

1.0 INTRODUCTION

2.0 APPROACH

2.1 GEOFidelis Data Model Change Requests

3.0 MODEL ELEMENTS

4.0 STANDARDIZED FEATURE TYPES

4.1 COMMON

ElevationContour

4.2 EMERGENCY_SERVICES

AddressPoint

AdmiBoun_EmergencyService AdmiBoun_PSAP RoadCenterline

4.3 ENVIRONMENTAL

AboveGroundStorageTankArea AboveGroundStorageTankPoint EnvironmentalDischargePoint EnvDischargePoint_Air

EnvDischargePoint_HazWaste EnvDischargePoint_SolidWaste EnvDischargePoint_Stormwater EnvDischargePoint_Wastewater EnviRemeSiteArea EnviRemeSitePoint EnvironmentalSampleLocation UnderGroundStorageTankArea UnderGroundStorageTankPoint

4.4 ENVIRONMENTAL_REVA

EnvSampleLocation_REVA MunitionConstituentLoadingArea

4.5 HOUSING

PPVUnit

4.6 MILITARY_OPERATIONS

AmmunitionStorage FiringSiteArea FiringSiteLine FiringSitePoint

ImpactArea MilitaryDropZone MilitaryLandingZoneArea MilitaryLandingZonePoint MilitaryRange

MilitaryTargetArea MilitaryTargetLine MilitaryTargetPoint MilitaryTrainingLocation MilObservationPositionArea MilObservationPositionPoint NoFireArea

4.7 MILITARY_OPERATIONS_RESTRICTED

USMCSpecialUseAirspace

4.8 NATURAL_RESOURCES

ForestCompartment Vegetation Wetland

4.9 PLANNING_MILCON_FSRM

FutureProjectsArea FutureProjectsPoint MilitaryQuantityDistanceArc

4.10 REAL_ESTATE

AdmiBoun_MilitaryReservation

AirAccidentZone CantonmentArea Disposal Disposal_RealEstate LandParcel Outgrant Site

4.11 REAL_PROPERTY

AccessControlLine AccessControlPoint Bridge Building Campground Disposal_RealProperty DocksAndWharfs

Fence GolfCourse PavementSection PavementSectionAirfield PavementSectionParkingArea

PavementSectionRoadway PavementSectionSidewalk RailTrack RecreationArea StructureArea StructureLine StructurePoint Tower

4.12 REAL_PROPERTY_RESTRICTED

Well

4.13 UTILITIES_ELECTRICAL

ElecUtilNode ElecUtilNode_eCapacitorBank ElecUtilNode_eDynaProtectDevic ElecUtilNode_eExteriorLight ElecUtilNode_eFuse

ElecUtilNode_eGenerator ElecUtilNode_eGroundingPoint ElecUtilNode_eMeterPoint ElecUtilNode_eMiscNetworkFeatu ElecUtilNode_eOpenPoint ElecUtilNode_eSwitch ElecUtilNode_eTransformer ElecUtilNode_eVoltageRegulator ElecUtilSegment

4.14 UTILITIES_GAS

GasUtilNode GasUtilNode_gControlFitting GasUtilNode_gDrip GasUtilNode_gGasLamp GasUtilNode_gMeterPoint GasUtilNode_gNonContrFitting GasUtilNode_gOdorizer GasUtilNode_gPressMonitorDevic GasUtilNode_gRegulator

GasUtilNode_gRegulatorStation GasUtilNode_gReliefValve GasUtilNode_gRuralTap GasUtilNode_gTownBorderStation GasUtilNode_gValve

GasUtilSegment

4.15 UTILITIES_POL

POLUtilNode POLUtilNode_oDispenser POLUtilNode_oFillStand POLUtilNode_oFilterSeparator POLUtilNode_oHydrantOutlet POLUtilNode_oInjector

POLUtilNode_oLoadingArm POLUtilNode_oMeter POLUtilNode_oPump POLUtilNode_oRelaxationTank POLUtilNode_oStrainer POLUtilNode_oTank POLUtilNode_oValve POLUtilSegment

4.16 UTILITIES_THERMAL

TherUtilNode TherUtilNode_tAquastat TherUtilNode_tCondensateCollec TherUtilNode_tControlValve TherUtilNode_tExpansionJoint TherUtilNode_tExpansionLoop TherUtilNode_tExpansionTank TherUtilNode_tFitting TherUtilNode_tMeterPoint TherUtilNode_tProdStruc TherUtilNode_tPump TherUtilNode_tReliefValve

TherUtilNode_tStrainer TherUtilNode_tSystemValve TherUtilNode_tTrap TherUtilSegment

4.17 UTILITIES_WASTEWATER

WastUtilNode

WastUtilNode_sCleanOut WastUtilNode_sFitting WastUtilNode_sManhole WastUtilNode_sMeterPoint WastUtilNode_sPump

WastUtilNode_sPumpStation WastUtilNode_sReleaseValve WastUtilNode_sSystemValve WastUtilNode_sTreatmentPlant WastUtilSegment

4.18 UTILITIES_WATER

WateUtilNode WateUtilNode_wBackflwPrvDevice

WateUtilNode_wControlValve WateUtilNode_wFitting WateUtilNode_wHydrant WateUtilNode_wMeterPoint WateUtilNode_wPressReduStation WateUtilNode_wProdStructure WateUtilNode_wPump WateUtilNode_wReliefValve WateUtilNode_wStorageStructure WateUtilNode_wSystemValve WateUtilSegment

5.0 NON-STANDARDIZED FEATURE TYPES

5.1 COMMON

ControlMonumentPoint

5.2 COMMUNICATIONS

CommUtilityNode CommUtilitySegment

5.3 CULTURAL_RESOURCES

ArchaeologicalSite CemeteryOrBurialSite CulturalResourcePotentialArea CulturalRestrictedAccess CulturalSurveyArea HistoricDistrict HistoricLandscape HistoricObject

NativeAffiliation SacredSite TraditionalCulturalResource

5.5 ENVIRONMENTAL

PollutionArea

5.6 HOUSING

LandManagementZone_Housing

5.7 MILITARY_OPERATIONS

ExplosiveDangerZone ExplosiveSite MilitaryLaserSurfaceDangerZone MilitaryMoutStructure MilitaryRangeEquipment MilitaryRangeLighting MilitarySurfaceDangerZone MilitaryWeaponDangerZone

RangeControllerPosition UnexplodedOrdnanceClearance WeaponTargetLine

5.8 NATURAL_RESOURCES

AgriculturalTract ForestProductHarvest NaturalResourceResRecProject NaturalResourceSurvey

SpecialStatusSpecies SpeciesSpecificHabitat TerrestrialEcologicalSystem WildlandFire

5.9 PLANNING_MILCON_FSRM

Landuse MilQuantityDistanceCombinedArc ProjectReference

5.10 PLANNING_MILCON_FSRM_RESTRICTED

FutureProjects_HostNation

5.11 REAL_ESTATE

ExternalPropertyInterest

NoiseZone

5.12 REAL_PROPERTY

AlternativeEnergy

BoatRamp Impoundment Levee Marina MooringStructure

NavigationalAid Relocatable TrafficControlLight TransportationTunnel VesselRepairFacility Wall WaveAttenuator

5.13 UTILITIES

UtilityFeature

6.0 DATABASE VIEWS

Class 2 Real Property Ingrants Outgrants

7.0 DOMAINS

AccessControlTransSystType AccessControlTypeCode ActivityStatusType AddressParityType AddressStatus AirfieldPavementUse AgricultureTractType AirfieldTargetType AllowedSpeciesType AlternativeEnergyType AmmunitionStorageType

ApronType ArchaeologicalSiteType AssetOwner BanksideCode BarrierTopType BogType Boolean BranchRailwayType BridgeOpeningType

BridgeOperationalStatus BridgeTransSystType BridgeType BuildingFunctionType BuildingStatus

BulbType CableMaterialType CableSheathingType CampgroundClassificationType CatCode_eExteriorLight CatCode_eMiscNetworkFeatu CatCode_eSwitch CatCode_eTransformer CatCode_oTank CatCode_ProdStruc CatCode_PumpStation CatCode_TreatmentPlant

CatCode_wPump CatCode_wStorageStructure CatCodeAccessControl CatCodeAmmunitionStorage CatCodeBridge CatCodeBuilding CatCodeCampground CatCodeDocksAndWharfs CatCodeElecUtilSeg CatCodeFence CatCodeGasUtilSegment CatCodeGolfCourse CatCodeImpactArea

CatCodeLandParcel CatCodeMilitaryDropZone CatCodeMilitaryRange CatCodeMilTrainingLocation CatCodeParking CatCodePavementAirfield CatCodePOLUtilSegm CatCodeRailTrack CatCodeRecreationArea CatCodeRoad

CatCodeSidewalk CatCodeStorageTank CatCodeStructure CatCodeThermalUtilitySegment CatCodeTower

CatCodeWastUtilSeg CatCodeWateUtilSeg CatCodeWell CategoryOfCraftFacility CemeteryExhumedStatus CemeteryMarkerStatus ClearanceStatus CommNodeType CommSegmentType ConfigurationType ConstructionMaterialType ContaminantType

ControllingAuthority ControlMonumentPointType CoordinateCaptureMethod CountryCode CowardinType CutoffType d_states DemandZoneType DirectionalIndicator DischargeType DisposalType DockAccessType DockPurposeType

ElectricalNodeType ElectricalSegmentType ElectricalSwitchInstallation ElectricalSwitchPosition ElectricalSwitchType ElevationContourType EnergySource EnvHazardCategory EnvRestorationCategory ExplosivesActivity

ExteriorLightType ExternalInterestType FacCode_eExteriorLight FacCode_eMiscNetworkFeatu FacCode_eSwitch

FacCode_eTransformer FacCode_oTank FacCode_ProdStruc FacCode_sPumpStation FacCode_TreatmentPlant FacCode_wPump FacCode_wStorageStructure FacCodeAccessControl FacCodeAmmunitionStorage FacCodeBridge FacCodeBuilding FacCodeCampground

FacCodeDocksAndWharfs FacCodeElecUtilSeg FacCodeFence FacCodeGasUtilSegment FacCodeGolfCourse FacCodeImpactArea FacCodeLandParcel FacCodeMilitaryDropZone FacCodeMilitaryRange FacCodeMilTrainingLocation FacCodeParking FacCodePavementAirfield FacCodePOLUtilSegm

FacCodeRailTrack FacCodeRecreationArea FacCodeRoad FacCodeSidewalk FacCodeStorageTank FacCodeStructure FacCodeThermalUtilitySegment FacCodeTower FacCodeWastUtilSeg FacCodeWateUtilSeg

FacCodeWell FeatureFunction FeatureFunctionTrainingSite FenceType FenceUseType

FGDCFormationClassType FGDCFormationSubclassType FGDCFormationType FireRestrictionType FiringSiteType FiringSurfaceType FittingType FoliageType FoliageTypeForest FuelType FundingSourceCode FutureProjectStatus

GasNodeType GasSegmentType GateType GateUse GeneratorType GroundStorageStatus GSIP_AreaUOM GSIP_LengthUOM GSIP_VolumeUOM HabitatType HelipadAssociatedFac HistoricalStatusCode HorizontalDatumType

HydrantConnectionType HydrantType HydroGeomorphologyType HydrologicPersistence ImpactAreaType ImpoundmentType ITESCClassificationType JurisdictionalFeatureType JurisdictionType KingdomType

LandClass LandingZoneUseType LandUse LandUsePlanLength LandUseStatus

LeveeType LightType LinearFeatureArrangement LocationType MarinaType MaterialType MatrixType MeterType MeterUse MilitaryAirspaceType MilitaryRangeUseType MooringCategory

MountType MoveAreaSurfaceCat MoveAreaSurfaceComp MoveAreaSurfacePrep NavigationAidType NetworkSubType NetworkType NoiseSourceType NoiseZoneMetricType NumberOfPhases ObservationPointType OneWayClassification OtherSpecialStatusType

Owner Ownership PavementSectionType PhysicalCondition PipeDiameterValues PipeMaterial PipeType PlanningFeatureType POLNetworkSubType POLNodeType

POLSegmentType PortrayalCode_eMiscNetworkFeat PortrayalCode_POLUtilSegm PortrayalCodeAccessControl PortrayalCodeAdmiBoun

PortrayalCodeAmmoStorage PortrayalCodeBridge PortrayalCodeBuilding PortrayalCodeCampground PortrayalCodeFence PortrayalCodeForCompartment PortrayalCodeGolfCourse PortrayalCodeImpactArea PortrayalCodeMilitaryRange PortrayalCodeMilTrainingLoc PortrayalCodeObsPos PortrayalCodePaveSectAirf

PortrayalCodePaveSectPark PortrayalCodePOLUtilNode_oTank PortrayalCodePumpStation PortrayalCodeRailTrack PortrayalCodeRecreationArea PortrayalCodeRoad PortrayalCodeStorageTank PortrayalCodeStructure PortrayalCodeTower PortrayalCodeTreatPlant PortrayalCodeVegetation PortrayalCodeWatStorStruc PortrayalCodeWell

PortrayalCodeWetland PotentialLevel Product_POLUtilitySegment PumpingStationProduct PumpType PylonConfiguration QdExposureType QuantityDistanceArcType RailConstructionType RailNetworkSubType

RailwayClass RailwayGaugeClassification RailwayPowerMethod RailwayUse RangeCapacityUOM

RangeEquipmentType RangeOperationalStatus RealEstateAction RecreationAreaType RecResProjectType RelativeLevel Restriction RevaSurveyType RoadClassification RoadSuffixType RoadwayType RoofShape

RouteDesignation RouteSurfaceComposition RPClassType RunwayClass SafetyZone SiteUsage SpecialStatusCategoryType StorageTankProductType StructuralCondition StructuralMaterial StructureMaterial StructureShape StructureShapeTower

TankType TaxiwayType ThermalNetworkSubType ThermalNodeType ThermalSegmentType ThermalValveType TowerType TowerUseType TrainingSiteType TransformerType

TransTunnelType TypeOfDock UtilityFeatureType UtilityOperationalStatus ValveType

VegetationCharacteristic VegetationSpecies VegetationType VehicleType VerticalConstMatBridge VerticalConstMatBuilding VerticalConstructionMaterial VerticalDatumType VerticalRelativeLocation VesselRepairFacilityType Voltage WallType

WastewaterNetworkSubType WastewaterNodeType WastewaterSegmentType WaterElevationCode WaterNetworkSubType WaterNodeType WaterSegmentType WaterType WeaponLineType WeaponsRangeType WeatherRestriction WellPurpose WellResource

WellType WildlandFireCauseType WildlandFireType WireGaugeSize WirelessTelecomType

8.0 NON-SPATIAL TABLES

ETRT_info FeatureMetadata LRMT_Scenarios_Table REVA_Sampling_Results sdz_parameters_input WDZ_parameters_input

9.0 DOCUMENT HISTORY

1.0 INTRODUCTION

The GEOFidelis Data Model is the standard for all USMC Installation Geospatial Information and Services (IGI&S) geospatial data. The data model will provide data standard consistency that incorporates enough breadth for mission execution and the ability to record data in a consistent manner across the Marine Corps.

Based on the Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE), the GEOFidelis Data Model maintains a common USMC IGI&S data standard that provides all USMC installations with a common structure for data layers and attributes. All USMC commands, installations and reserve sites, with installation management responsibilities, will implement the GEOFidelis Data Model to enhance interoperability and enterprise integration.

The GEOFidelis Data Model is consistent with USMC and DoD policy for IGI&S.

• Meets the policy and goals set forth in Marine Corps Order (MCO) 11000.25, Installation Geospatial Information and Services.

• Meets the policy set forth by IGI&S and DODI 8130.01.

• Compliance with the goals and DoD enterprise objectives set forth in the Office of the Under Secretary of Defense (OUSD) memorandum dated April 14, 2009 – Installation Geospatial Information and Services Guidance.

• Follows DoD interoperability strategy set forth in the OUSD guidance dated May 11, 2011 – Guidance for the Adaptation of SDSFIE 3.0.

The GEOFidelis Data Model improves geospatial information accessibility and usability to support USMC business processes. This geospatial data requirement will improve discovery and utilization by end-users to meet the GEOFidelis strategic goal of supporting Marine Corps Installation Management by “GEO-ENABLING

THE MISSION”.

2.0 APPROACH

The GEOFidelis Program has worked for several years to produce a common USMC IGI&S data model. This effort allowed for early successes with the integration of USMC geospatial data with USMC installation business systems. Building upon these early initiatives, the GEOFidelis Program was well positioned to meet DoD goals focused on DoD interoperability of geospatial data and development of the SDSFIE Version 3.0 Gold.

The GEOFidelis Program coordinated with Functional Data Set Leads and Subject Matter Experts (SMEs) at Headquarters Marine Corps (HQMC) to ensure USMC enterprise-wide business requirements and the geospatial features (also refered to as feature types) that support those requirements are included in the GEOFidelis Data Model. This ensured that the resulting model will:

• Integrate with business systems and provide visualization and analysis of USMC installation business data.

• Focus USMC geospatial data management to collect geospatial features best suited for Functional Data Set Leads and SME use.

• Eliminate redundant business data collection by linking to authoritative business systems.

The GEOFidelis Data Model 3.0.0.2 is the primary USMC SDSFIE adaptation and defines the minimum required geospatial data elements that must be standardized across the Marine Corps enterprise in support of common installation management business practices and requirements. Feature types in the GEOFidelis Data Model

3.0.0.2 are recognized as either “STANDARDIZED FEATURE TYPES” or “NON-STANDARDIZED FEATURE TYPES” contingent on the features’ designation as a Common Installation Picture (CIP) or Critical Infrastructure layer.

For feature types identified as non-standardized, GEOFidelis Data Model 3.0.0.2 maintains the flexibility allotted in GEOFidelis Data Model 3.0.0.1, allowing installations to create their own adaptations to meet local installation requirements that are not met in the standard GEOFidelis Data Model. Standardized feature types must be incorporated by local installations according to the standard schema provided in this data dictionary.

Such feature types must either 1) be added to installation geospatial databases or 2) existing database feature types must be altered to match the standardized GEOFidelis Data Model 3.0.0.2 structure.

2.1 GEOFidelis Data Model Change Requests

Users of the GEOFidelis Data Model should report issues and/or suggest enhancements. Changes to GDM

3.0.0.2 will occur through Change Requests (CRs) (hereafter referred to as “CRs”). All GDM 3.0.0.2 CRs require the submittal of at a minimum a Formal CR Document and, if applicable, a Formal Schema Proposal.

These required forms are available on the GEOFidelis IGI&S SharePoint site or can be acquired from the Program Support Team.

All standardized feature type CRs will need to go through the GEOFidelis Configuration Control Board (CCB) for approval. Prior to GEOFidelis CCB review, these CRs and Schema Proposals will need to be submitted through Regional processes/CABs and subsequently brought up during the GEOFidelis Monthly Meeting for discussion. Regionally approved CRs will then proceed through the CCB adjudication/voting process during the semi-annual GEOFidelis CCB meetings.

Non-standardized feature types, will still be governed by the change request process for installation adaptations. When a need for a change has been identified, it should be documented and submitted to the Program Support Team for adjudication (this step in the process may come after internal Regional Command approval processes). Submittals of this type will be accepted throughout the months of October and April and will be adjudicated within two weeks of receipt. Non-standardized approved CRs require Installations to resubmit an updated data dictionary document to the Program Support Team before changes will be implemented. If a non-standardized CR has potential benefit or impact to the GEOFidelis Program, it can be escalated to the CCB adjudication/voting process. USMC Change Management Workflow is depicted in Figure 1.

GDM 3.0.0.2 Change Management Workflow

N on

-S ta nd ar di ze d Fe at ur e Ty pe s

GEOFidelis Configuration Control Board (CCB)

Vote

St an da rd iz ed

F ea tu re

T yp es

Approved Denied

Regional CR Approval

GEOFidelis Monthly Meeting

Installation CR Documentation

Submitted to Program Support

MCICOM/Program Support

Adjudication

Approved

Denied

Changes Made in February/July

Maintenance Window

Changes Made in December/June

Maintenance Window

Figure 1 – Change Request Workflow

Approved standardized feature type CRs will be implemented semi-annually during the enterprise database maintenance window for the month following their corresponding CCB vote (February and July). All approved non-standardized feature type CRs will be implemented during the enterprise database maintenance window for the month following MCICOM/Program Support adjudication and approval (December and June). USMC Change Management Timeline is depicted in Figure 2.

Figure 2 – Change Management Timeline

3.0 MODEL ELEMENTS

A data dictionary is a part of the metadata that is used to understand the data and the databases that contain

it. The data dictionary identifies data elements and their attributes including names, definitions and other information. The development and use of a consistent set of data elements and formats for documenting database content and structures make information in the GEOFidelis Data Model more accessible. Model elements will be populated differently based on the source of the feature or attribute. If the feature or attribute is a part of the SDSFIE 3.0 Logical Data Model (LDM) then the information that will populate the model elements will be taken from the SDSFIE website (www.sdsfieonline.org). For features and attributes which are not a part of SDSFIE 3.0 LDM, the model elements will be identified by the HQMC proponent who requested its inclusion.

There are many times when a model element is designated as Not Applicable (“N/A”). This is used to show that the model element does not apply to that feature or attribute. For example, the model element “Justification” will always be “N/A” when the data structure source is SDSFIE 3.0. The use of “N/A” is allowed for the following model elements only: GEO

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .