This post continues a series describing our approach to using a platform-independent approach to managing data models and standards. In any situation where a geospatial data model is agreed upon and adopted by multiple participants, management of the model itself becomes a significant issue. Over time, modifications to the model are required. Such modification can have significant impacts on the implementations of each participant. As a result, configuration management is needed to ensure smooth transition and traceability between data model versions.
Posts tagged SDSFIE
Previous posts have touched the problems that traditionally face those wanting some geospatial consistency in data collection, data presentation, and data understanding. These issues drive much of the continual interest and push for increased Metadata and many of the “Use Liability” clauses that are attached to current datasets. After all, if you don’t really know what the feature is, or what many of the attributes really mean, geospatial data is of considerably reduced value.
Background: While many organizations see the clear advantages of establishing and using geospatial data standards, obtaining compliance from constituents continues to be a frustrating, and costly, problem. Users are frequently reluctant to adopt a new standard given the potential cost of modifying applications that use an existing, custom schema or simply having a ‘not invented here’ mentality. This was true within the Department of Defense (DoD) Installation Geospatial Information and Services (IGI&S) community, even though a standard had existed from more than 10 years. As a part of 2006 Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE) initiative, Zekiah developed a data standardization concept intended to provide flexibility in schema naming conventions and organization without compromising ease of data sharing, conversion, and information understanding.
One of the more critical, and somewhat confusing, concepts in the SDSFIE 3.0 is the notion of what constitutes a ‘compliant’ data set. SDSFIE 3.0 offers considerably more flexibility in schema options than earlier releases. This capability was created to permit individual DoD users some naming options to accommodate existing legacy applications that use geospatial data. But the capability comes with a risk… namely compromising the very nature of a standard.
Many new DoD contracts are being awarded with a clause stating that the data deliverables are to be submitted compliant with SDSFIE. Given the flexibility in schema naming and content, what does that really mean and how is that consistent with an absolute standard.
Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE): Five Fundamental Tools
The Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE) is the single Department of Defense spatial data standard that supports common implementation and interoperability for installations, environment, and civil works missions.
SDSFIE is being managed by the Defense Installations Spatial Data Infrastructure (DISDI) Group. The DISDI Group is a formal governance group reporting to the Department of Defense’s Installations & Environment Investment Review Board.