There is a growing need for information exchanges to include geospatial elements and capabilities—NIEM provides this functionality.
Using GML with NIEM
The role and utility of geospatial technology continues to increase along with the amount of information containing geotags (address, latitude/longitude, location). To meet this growing demand, NIEM developed geospatial exchange capabilities that leverage Geography Markup Language (GML) standards established by the Open Geospatial Consortium (OGC). By combining NIEM with GML, mission partners benefit from shared access to the common operating data and services used within these geospatial systems. NIEM is working with members of the community who have leveraged GML in NIEM exchange development. Please contact us if you have examples of how you’re using NIEM and GML.
The Geospatial Enhancement for NIEM (Geo4NIEM) initiative enhances NIEM’s geospatial exchange capabilities by demonstrating and providing enterprise NIEM-conformant content in a map visualization context that:
- Provided the appropriate security markings and access controls to ensure the right people have access to the right information at the right time in the right context.
- Can be reused across the public and private sector.
- Promoted cost-savings (through use of NIEM and OGC community open standards).
There have been two major Geo4NIEM efforts:
Geo4NIEM Part 1 (2013)
Geo4NIEM Part 1 (2013) was a collaborative, hands-on rapid prototype development and testing initiative in accordance with the Open Geospatial Consortium (OGC)'s Interoperability Program. The partnership included NGA, Department of Defense (DoD), Defense Information Systems Agency (DISA), U.S. Geological Survey (USGS), the Army Geospatial Center and numerous participants and supporters from the public and private sector.
Geo4NIEM Part 2 (2015)
Geo4NIEM Part 2 (2015) was one of four threads in OGC’s Testbed 11—a scenario-based test and demonstration of Geo4NIEM work. It focused on enhancing NIEM’s geospatial exchange capabilities to include Intelligence Community (IC) data encoding specifications, along with OASIS standards to enable granular data object level access authorization and/or denial aligned to OCG web services.