A. Appendix A GII Requirements and Technology Matrix
This appendix contains a list of the requirements as they appeared in Version 0.21 of Volume 2 of the GII Master Plan. Commercial vendors used these requirements to complete a Technology Submission Form prepared by the Open GIS Consortium.
Following the list of requirements is a matrix containing point of contact information for the vendors who completed the forms and identifying the technology that they matched against each GII requirement. Matrix 1 contains information from all the submittals compiled by the OGC and released on 26 February 1997.
The vertical ID numbers on the left side of Matrix 1 correspond to the top horizontal numbers in Matrix 2. Matrix 2 lists the GII requirements from Version 0.21 and identifies the technology that addresses each requirement. The vendor assessment of how well the requirement is satisfied is based on the following key:
- Not Applicable/doesn't address the requirement
v - Partially addresses the requirement
u - Fully addresses the requirement
All judgments on a technology's satisfaction of a requirement were made solely by the submitter of that particular technology.
Version 0.21 GII Requirements | A-2 to A-22 |
Matrix 1: OGC/IPT Technology Submission POC Information | A-23 to A-26 |
Matrix 2: OGC/IPT Task Force Technology Matrix | A-27 to-A-72 |
The following areas specify processes which must be developed or enhanced to improve the requirements collection and management process:
-a Develop an Interactive Collection Process - A distributed, interactive process for collecting and submitting customer requirements using “web-based” technologies.
-b Decompose Requirements - Develop tools to decompose requirements and identify essential elements of information to support specific mission information needs (i.e., the mission “What” and “How”). The process should:
-c Develop Relational Database -Develop and populate a relational database of user requirements for mission specific data based on the GII data model.
-d Develop Intelligent Tools - Develop intelligent tools and user interfaces for access, data input and output, requirements analysis and report generation.
-a DTED - The ability to input Digital Terrain Elevation Data (DTED) 1 and 2 shall be provided.
-b DFAD - The ability to input Digital Feature Analysis Data (DFAD) shall be provided.
-c ADRG - The ability to input Arc-Digitized Raster Graphics (ADRG) shall be provided.
-d CADRG - The ability to input Compressed Arc-Digitized Raster Graphics (CADRG) shall be provided.
-e Raster Scanned data - The ability to input Raster Scanned data shall be provided.
-f PITD - The ability to input Planning Interim Terrain Data (PITD) shall be provided.
-g ITD - The ability to input Interim Terrain Data (ITD) shall be provided.
-h VITD - The ability to input Vector Interim Terrain Data (VITD) shall be provided.
-i VMAP - The ability to input Vector Smart Map (VMAP) 1 and 2 shall be provided.
-j UVMAP - The ability to input Urban Vector Smart Map (UVMAP) shall be provided.
-k DNC - The ability to input Digital Nautical Chart (DNC) shall be provided.
-l VPF - The ability to input Vector Product Format (VPF) shall be provided.
-m MC&G - The ability to input Mapping, Charting, and Geodesy (MC&G) shall be provided.
-n Framework Information - The ability to input Framework Information shall be provided.
-o SDRS Data - The ability to input Ships Data Recording System (SDRS) Data shall be provided.
-p MSDDB - The ability to input Master Seafloor Digital Database (MSDDB) shall be provided.
-q Soundings - The ability to input Soundings shall be provided.
-a TINT - The ability to input Target Intelligence file (TINT) shall be provided.
-b AAFIF - The ability to input Automated Air Facilities Information File (AAFIF) shall be provided.
-c DVOF - The ability to input Digital Vertical Obstruction file (DVOF) shall be provided.
-d MIDB - The ability to input Modernized Integrated Data Base (MIDB) shall be provided.
-e Intelligence Studies and Reports - The ability to input Intelligence Studies and Reports shall be provided.
-a NTM - The ability to input National Technical Means (NTM) shall be provided.
-b SPOT - The ability to input SPOT shall be provided.
-c LANDSAT - The ability to input Landsat shall be provided.
-d Multi-Spectral Imagery - The ability to input Multi-Spectral imagery shall be provided.
-e Hyper-Spectral Imagery - The ability to input Hyper-Spectral imagery shall be provided.
-f CIB - The ability to input Controlled Image Base (CIB) shall be provided.
-g DPPDB - The ability to input Digital Point Positioning Database (DPPDB) shall be provided.
-h SAR - The ability to input Synthetic Aperture Radar (SAR) shall be provided.
-i IFSAR - The ability to input Interferometric Synthetic Aperture Radar (IFSAR) shall be provided.
-j Video - The ability to input NTSC video shall be provided.
-a MMSD - The ability to input Metric Mapping Support Data (MMSD) shall be provided.
-b AMSD - The ability to input Adjusted Mapping Support data (AMSD) shall be provided.
-c IDF - The ability to input Instrument Data file (IDF) shall be provided.
-a Maps and Charts - The ability to input Maps and Charts shall be provided.
-b Notice to Mariners - The ability to input Notice to Mariners shall be provided.
-c Notice to Airmen - The ability to input Notice to Airmen shall be provided.
-d List of Lights - The ability to input List of Lights shall be provided.
-e Graphic overlays, Boundaries - The ability to input Graphic overlays, Boundaries shall be provided.
-f Graphic overlays, Names data - The ability to input Graphic overlays, Names data shall be provided.
-g Echograms - The ability to input Echograms shall be provided.
-h Sounding Log Books - The ability to input Sounding Log Books shall be provided.
-a Mono imagery - The ability to produce geodetically controlled monoscopic imagery shall be provided.
-b Stereo Imagery - The ability to produce geodetically controlled stereoscopic imagery shall be provided.
-c Elevation - The ability to produce geodetically controlled elevation data shall be provided.
-d Features - The ability to produce geodetically controlled vector feature data shall be provided.
-a CIB - The ability to produce geodetically controlled monoscopic imagery consistent with CIB (Controlled Image Base (CIB), MIL-C-89041, May 1995) shall be provided.
-b DPPDB - The ability to produce geodetically controlled stereoscopic consistent DPPDB (Digital Point Positioning Database (DPPDB) MIL-PER-89034 DRAFT) shall be provided.
-c DTED - The ability to produce geodetically controlled elevation consistent with DTED (Digital Terrain Elevation Data (DTED) MIL-PRF-89020A, Dec. 1995) shall be provided.
-d VPF - The ability to produce geodetically controlled vector feature data consistent with VPF Products (MIL-STD-2407, Interface Standard for Vector Product Format (VPF), 2nd Edition, et al) shall be provided.
-e FACC - Vector feature attribution consistent with FACC - Feature attribute coding (NATO STANAG 7074, Jan 94 DIGEST Part 4 Feature Attribute Coding Catalog) from framework information shall be provided.
-a Search - The ability to search for geospatial information shall be provided (i.e. Web Crawlers).
-b Identify - The ability to identify sources automatically as they become available shall be provided (i.e Smart agents).
-c Order - The ability to order hardcopy or softcopy source information shall be provided.
-d Retrieve - The ability to retrieve softcopy source information shall be provided.
-a Data Conversion - The ability to convert hardcopy maps and charts, echograms and imagery into a format (e.g. softcopy textual, vector, raster, gridded) for further processing shall be provided.
-b Digital Ingest - The ability to accept softcopy sources and perform adjustments for further exploitation of source data shall be provided.
-a Area of interest - The ability to determine the coverage of the area of interest by the source shall be provided.
-b Accuracy - The ability to determine the accuracy of the source shall be provided.
-c Obscuration - The ability to identify obscuration of features of interest in the source shall be provided.
-d Sufficiency- The ability to determine the sufficiency of source data density shall be provided.
-e Currency - The ability to determine the currency of the source shall be provided.
-f Change Detection - The ability to determine the difference between two or more sources of different dates or versions shall be provided
-g Maintenance - The ability to determine the requirements for routine maintenance shall be provided.
-a Generate Requirement - The ability to generate a requirement for additional source collection shall be provided.
-a Georeferencing - The ability to perform georeferencing shall be provided.
-b Geopositioning- The ability to perform geopositioning , including both triangulation and mensuration, shall be provided.
-c Datum transformations - The ability to perform datum transformations shall be provided.
-d Map projections - The ability to perform map projections shall be provided.
-e Image processing - The ability to perform image processing shall be provided.
-f Accuracy adjustments - The ability to perform accuracy adjustments shall be provided.
-g Map registration - The ability to perform map registration shall be provided.
-h Image rectification - The ability to perform image rectification shall be provided.
-i Image orthorectification - The ability to perform image orthorectification shall be provided.
-j Image mosaicing - The ability to perform image mosaicing shall be provided.
-a Select Source - The ability to select production ready source for exploitation from the available source holdings shall be provided.
-a Identify Entities - The ability to identify entities (features) through visual, statistical and other analyses and interpretation shall be provided. An example would be to identify a bridge or a road.
-a Capture Entities - The ability to capture identified entities and data/information (feature, elevation, bathymetric, aeronautical and textual data) shall be provided. An example would be an actual delineation of a road centerline or bridge location.
-b Change Detection - The ability to perform entity change detection shall be provided.
-c Edit - The ability to edit the data entities shall be provided.
-a Attribute - The ability to add appropriate attribution to the extracted data shall be provided. An example would be to attribute a road as all weather hard surface, no median and 6 meters wide.
-b Change Detection - The ability to perform attribute change detection shall be provided.
-c Edit Attribution - The ability to edit attributed data and metadata shall be provided.
-a Assemble - The ability to assemble extracted and attributed entities into coverages shall be provided.
-b Edit - The ability to edit coverages shall be provided.
-a Conflation - The ability to perform conflation, which is the identification, resolution and merging of different renditions of what is actually the same entity, shall be provided.
-b Horizontal Integration - The ability to perform horizontal integration which is the integration of a data set with datasets of adjacent geographical areas shall be provided.
-c Data fusion - The ability to perform data fusion which is the vertical integration of geographically coincident areas shall be provided.
-d Edit - The ability to identify and add, remove and modify data within a data set shall be provided.
-a Identify - The ability to identify metadata shall be provided.
-b Capture - The ability to capture metadata shall be provided.
-c Update - The ability to update metadata shall be provided.
-d Delete - The ability to delete metadata shall be provided.
-e Organize - The ability to organize metadata shall be provided.
-f Query - The ability to query metadata shall be provided.
-g Analyze - The ability to analyze metadata shall be provided.
-a Framework Data - Production of a 15 X 15 minute area of Framework data by one cartographer/analyst in one 8 hour production shift shall be achievable.
-a MSDS - Intensification of features within a 15 X 15 minute area to meet the Mission Specific Data Set requirements of our users shall be met in an 8 hour time frame.
-b Terrain Data - Generation of terrain data (DTED 3) over a 15 X 15 minute area of interest shall be supported within 8 hours.
-c Feature and Terrain Update - Populated feature and elevation information shall be easily and quickly updated using later data sources to intensify, change, and delete existing feature and elevation information as necessary to keep the information current to within 90 days.
The overarching engineering requirements that must be addressed for the implementation of the data architecture are:
-a Cataloging - Support the population of data and metadata fields through automated and interactive methods as appropriate
-b Open Databases - Support independent, evolutionary development and implementation of databases and applications accessing databases.
-c Simultaneous Access Management - Manage simultaneous access to multiple, independent and autonomous databases.
-d Maintain Data Integrity - Maintain integrity of data throughout the Enterprise.
-e Data Security - Provide for data safety which includes, but is not restricted to, the ability to recover data at the record, file, volume, database, subsystem, or center level, as well as the mechanisms required to restore an entity to operational capability.
-f Database Maintenance Operations - Support to database maintenance and overhead functions. Specifically, necessary functions and tools shall be provided to minimize database maintenance operations.
-g Standard Data Elements - Provide standard data elements to ensure interoperability among enterprise information systems.
-h Multiple Database Access - Provide discretionary access to multiple databases.
-i Independent Client-Server Connections - Sustain client-server connections independent of the client application's and database server's hosts.
-j Distributed Databases - Support distribution of databases across multiple hosts with replication and distributed updates and be extensible.
-k Security Access - Provide maintainability of users' access rights and permissions. Support a multiple security level environment (e.g., security tagging and flagging).
-l Tolerant Operations - Provide a fault-tolerant environment.
-m DBMS Independent - In addition, database services within the enterprise will not be restricted to a single vendors’ Data Base Management System (DBMS). As a result, the system databases shall have little or no dependence on any particular DBMS vendors’ product.
-n Common Browser - The development of a common browsing tool for imagery and geospatial information.
-a Commercial Database - The architecture shall be capable of storing and managing framework data in a commercially available database management system.
-b Data Management - Data Architecture shall consist of capabilities for Data Management. Data Management is the Database Management System (DBMS) functionality and the population of the database from the various certified information sources.
-c Framework Data/Metadata - The capability shall contain integrated geospatial framework data and metadata that describes that data.
Some of the capabilities envisioned for the future creation of integrated geospatial data shall include:
-d Time Relationship - Time varying relationships between database entities.
-e Edge Matching - Interactive edge matching adjustment of the locations of points and vectors to maintain the continuity of the data set.
-f Detect Errors - Detection of common integration errors including slivers and gaps.
-g Error correction - Automated and semi-automated correction or flagging of common errors.
-h Best View - Creation of single "Best" current information data view based on customer selectable parameters.
-i Maintain Foundation Data Integrity - Maintenance of foundation data integrity such that this data is separable from data generated for mission specific needs.
-j Data Model/FACC Compliant - The integrated GII 97 vector data should adhere to the NIMA feature Data Model and be FACC Compliant.
-a Distributed Data Management - Data Architecture shall support distributed data management.
-b FIPS 127-2 (SQL) - Data Architecture shall be FIPS 127-2 (SQL) compliant.
-c Portable - Data Architecture shall support hardware and software portability.
-d Non-Limiting Extensions - Data Architecture shall not implement extensions limiting portability.
-e FIPS 184 (IDEF1X) Modeling - Data Architecture shall be based on and support FIPS 184 (IDEF1X) modeling.
-f Security Granularity - Database design and implementation shall support the security and sensitivity level of all database fields at the table, row, column and cell level of granularity.
-g Precluded Responses - Database design shall preclude incorrect query response as a result of null fields and out of range fields.
-h Dynamic Extraction - Database design shall support dynamic extraction to the lowest feature attribution level.
-i Multiple Information - Data Architecture shall support an integrated architecture addressing imagery, imagery products, imagery intelligence and geospatial information.
-a GII 97 Data - Manage and store the framework information that is derived from the production systems, existing data stores, and data generated by customers (Value Added).
-b New Data Linkage - Provide the capability to define and accept new data types/products and build linkages.
-c Data Search Types - Provide the capability to do `keyword, boolean, and spatial’ searches for data.
-d Non-Blocked Access - Provide the capability to perform non-blocking (no lock-out) update, deletion and archival processes. This is especially critical for framework feature data.
-e Updating Process - Include the updating processes of the framework information .
-f Automatic Check/Update Metadata - Provide the capability to automatically check and update the metadata for both new and changed framework information during the update processes.
-g Error Conditions - Provide the capability to designate the error conditions and capture the erroneous data records during update processing.
-h Skip Erroneous Data - Provide the capability to skip erroneous records without load interruption during update processing.
-i Modify Rules - Provide administrators the capability to create and modify the rules by which data is moved.
-j Audit Trail - Capture an audit trail between backups.
-k Prioritize Resources - Provide administrators the capability to adjust resources for querying and ordering based on a customer's priority level.
-l Automatic Deletion - Provide administrators the capability to define an expiration date or event (e.g., end of special exercise, period of inactivity, etc.) after which a product or discrete file will be deleted.
-m Backup Copies - Provide administrators the capability to maintain a backup copy of databases.
-n Selective Backup - Provide administrators the capability to specify full database backup or backup of selected segments of the databases.
-o Restore Databases - Provide administrators the capability to restore the databases from the backup copy of the databases and the audit trail.
-p Access Path Monitoring - Provide administrators the capability to monitor access paths used for data retrieval (e.g., indices used).
-q Tunable - Provide the capabilities for performance tuning (e.g., creation and deletion of indices, partitioning of data, locking, parallel processing, etc.).
-a Source Data - Preserve valid, useful, and necessary information present in the source data (e.g., topological, cartographic and temporal information).
-b Topological Change Capture -Update topological relationships when changes occur.
-c Topological Consistency - Enforce topological consistency.
-d Definitions - Include definitions for data representation, data structure (format), and data schema and shall be FACC.
-e Create Associated Metadata -
-f Automatic Edge Matching - Provide the capability to perform automatic edge matching adjustments of the location of points and vectors in order to maintain the continuity of the data set.
-g Generalization - Provide generalization capabilities, (e.g., the ability to derive a lower resolution representation of the original dataset).
-a NITF - Data import and export of NITF formatted data shall be supported.
-b TFRD - Data import and export of TFRD formatted data shall be supported.
-c TIFF - Data import and export of TIFF formatted data shall be supported.
-d Sun Raster - Data import and export of Sun Raster formatted data shall be supported.
-e GIF - Data import and export of GIF formatted data shall be supported.
-f PostScript - Data import and export of PostScript formatted data shall be supported.
-g RPF - Data import and export of RPF formatted data shall be supported.
-h VPF (FACC) - Data import and export of VPF formatted data shall be supported.
-i FACS - Data import and export of FACS formatted data shall be supported.
-a 4.3 bpp DPCM - Import and export of images using 4.3 bpp DPCM compression shall be provided.
-b 2.3 bpp DCT - Import and export of images using 2.3 bpp DCT compression shall be provided.
-c 1.29 bpp DCT - Import and export of images using 1.29 bpp DCT compression shall be provided.
-d 8 bit JPEG - Import and export of images using 8 bit JPEG compression shall be provided.
-e 12 bit JPEG - Import and export of images using 12 bit JPEG compression shall be provided.
-f Color JPEG - Import and export of images using Color JPEG compression shall be provided.
-g MPEG - Import and export of images using MPEG compression shall be provided.
-h Vector Quantization - Shall be capable of performing Vector Quantization decompression on VQ compressed maps which may a company an NITF compliant imagery product.
-a SPIA/SDE - Standards Profile for Imagery Archives (SPIA) and Support Data Extensions (SDE).
-b Geospatial Feature Data Model -
-c NIMA Metadata Model -
-a Metadata/Data Access - Access and execute queries against metadata and data. The customer will have the capability to browse the metadata and retrieve items of interest.
-b Proper Coordinates - Maintain proper coordinates when spanning the 0 and 180 meridians, the equator and the poles (90N, 90S).
-c Community Archive Access - Access NIMA holdings and DODIIS compliant community archives.
-a Interface Assistance - The capability for customers to exploit graphical and textual interfaces to build queries (e.g., point, radius around a point, rectangle/drag box, customer defined polygon, and line and area surrounding the line/route).
-b Graphical/Textual Assistance - Customers graphical and textual assistance for building queries (e.g., prompts, pull-down menus, etc.).
-c Geographical Coordinates - The capability to accept geographical coordinates from graphical interaction on the map display (e.g., point, polygon, etc.).
-d Textual Input - The capability to accept geographical coordinates from textual input with degrees/minutes/seconds (DDD MM SS), degree decimal minutes (DDD MM.MMM....), decimal degrees (DDD.DDDDD....), and Universal Transverse Mercator (UTM) coordinates as initial formats presented for customer choice.
-e Administrator Assistance - The capability for administrators to maintain query building assistance.
-f Exact/Best Match - The capability for both ‘exact match’ and `best match' to textual input parameters.
-g Keyword Search - The capability for ‘keyword' searches on textual products and metadata.
-h Complex Queries - The capability to build complex queries which include combinations of query parameters and Boolean operators. The query capability shall support negative logic on all queriable fields.
-i Cross Over Queries - The capability to build a query based on individual domain parameters or any combination to allow for multiple table joins within and across themes and data libraries.
-j Resolution/Scale - The capability to build a query based on resolution/scale.
-k Save Between - The capability to save a submitted query, containing submitter's name, date of submission and query parameters between logon/logoff sessions.
-l Rework Saved Queries - The capability to retrieve, edit and delete previously saved queries.
-m Rework Standard Queries - Administrators the capability to create, edit, save and delete Standard Queries.
-n Multiple Execution - The capability for the execution of Standard Queries by multiple customers.
-o Standard Queries - The capability to create, edit, save and delete Standing Queries.
-p Customer Initiation - The capability to initiate Standing Queries based on a time or event as defined by the customer.
-q Gazetter Coordinates - The capability to query on a geographical name based on gazetter-like coordinates.
-r Keyword Index - The capability for building an index of keywords.
-s Specified Submittal - The capability to specify whether queries are submitted to a single identified library, a group of identified libraries or all available libraries.
-a Textual/Graphical - Provide textual and graphical query responses.
-b Refinement - Provide the capability to iteratively refine the query based on previous query responses.
-c Default Display - Provide administrators the capability to define the default display format for the metadata response to queries (e.g., title and date).
-d Customer Defined Default Display - Provide the customer the capability to specify a customer specific default display format for the metadata response to queries (e.g., title, date, source and size).
-e Display Format - Provide the customer the capability to specify the display format for the query specific metadata response to queries (e.g., title, date, source, quality parameters and size).
-f Customer Notification - Provide the capability for customer notification of an unviewed query response at next logon (e.g., "You have unread mail/ queries").
-g Order Creation - Support the creation of an Order.
-h Single Response - Have the ability to aggregate the query responses from distributed libraries and archives and return the aggregate as a single response to the client.
-i Search Time Termination - Provide the capability to terminate a response based on elapsed search time.
-j User Intervention Termination - Provide the capability to terminate a response based on user intervention.
-a Linkage - Maintain linkages between data and metadata.
-b Hierarchical Structure - Define hierarchically structured metadata groupings for metadata fields.
-c Specification - Specify, add, edit, and delete queriable parameters and desired formats and ranges for the parameters.
-d Query Log - Create and maintain a log of submitted queries.
-a Previews - Provide the user with the ability to view overviews of returned query results consisting of thumbnail images, sub sampled images and screen size overviews.
-b Thumbnail Metadata - Link metadata associated with the overviews to the associated thumbnail for review by the user.
-c Direct Order - Provide the user with the capability of directly ordering the full data set being browsed.
-a Interface Preferences - Provide the capability to retrieve customer profile details regarding customer interface preferences.
-b Create/Submit - Provide the ability to create and submit an order.
-c Methods - Provide the capability for a customer to choose from available order methods
-d Edit/Delete - Provide the capability to edit and delete an order before it is submitted.
-e Customer Actions - Validate all fields on an order and highlight discrepant field(s) for customer action prior to order submission (e.g., mandatory fields, range limits, dates, etc.).
-f Correction Help - Provide help in correcting discrepant fields.
-g Order Saving - Provide the capability to save an order, containing submitter's name, date of submission and order details between logon/logoff sessions.
-h Manipulate Saved Order - Provide the capability to retrieve, edit and delete a previously saved order.
-i Reuse - Provide the capability to submit a previously saved order.
-j Automatic Field Fill In - Integrate with the Query capability and automatically complete (fill in) the required Order fields based on the customer selected query response or hit.
-k Logs - Provide the capability to create and maintain logs.
-l Cancellation - Provide the capability to request a submitted order be canceled.
-m Prioritize - Allow for customer prioritization of the order.
-a Prepare Items for Delivery - Have the capability to prepare the completed ordered items for delivery to the customer.
-b Electronic Delivery - Have the capability to deliver the ordered items electronically, if within the size parameters based on the network and customer profile.
-c Acknowledge Order Submission - Provide customers with acknowledgment of order submission.
-d Processing Details - Provide the capability to collect the order processing details (e.g., time stamps, event, system routed to, etc.).
-a On-line Forms - Create and maintain on-line order forms.
-b Manipulate Parameters - Create, edit, save and delete the parameters which comprise an order.
-c Logs - Create and maintain a log of submitted orders.
-a Downgrading - Determine if Customer Orders, entering the system at a higher security level, can be downgraded to a lower security level and submitted.
-a Automatic Distribution - Various criteria to determine what information they are to receive based on an automatic distribution basis.
-b Information Profile - Various criteria to determine what information they are to receive when their profile is activated and executed.
-c Characteristics - The characteristic of the products or information of interest.
-d Notification - The method of notification of availability and dissemination means.
-a Accept Ad Hoc - The ability to accept Ad Hoc orders.
-b Accept Custom - The ability to accept Custom Orders.
-a Same Capabilities as Order - Include all the capabilities specified for Order Building.
-b Specify Parameters - Provide the ability for customers to specify parameters available for the product/data type and the available distribution media.
-c Customer Feedback - Provide the capability for a customer feedback mechanism (e.g., availability, delivery time, etc.).
-d Thresholds - Provide administrators the capability to set thresholds by customer priority (e.g., size, quantity, etc.).
-e Immediate Feedback - Provide the capability to send an immediate feedback (e.g., threshold limits, error code, etc.) message to the customer when administratively set limits are exceeded.
-f Outside Data - Provide the capability to request data not currently part of the data holdings.
-g Production Request - Provide the capability to forward a production request to the producer.
-a Transmission Time - Inform the customer of size and estimated transmission time for customer acknowledgment or cancellation prior to transmission.
-b Order Manipulation -Provide the capability for order cancellation and re submission of an order.
-b GUI - FIBS PUB 158-1 compliant Graphical User Interface (GUI).
-c CUI - Character User Interface (CUI) that supports functions not intrinsically requiring graphics capability.
-d CIIP API - USIGS Application Program Interface (API) that is Common Imagery Interoperability Profile (CIIP) compliant.
-a JWICS - Joint Worldwide Intelligence Communications System (JWICS).
-b SIPRNET - Secure Internet Protocol Router Network (SIPRNET).
-c OSIS - DoD-Intelligence Open Source Information System (OSIS).
-d NIS - National Imagery System (NIS).
-e USIGS - United States Imagery and Geospatial System (USIGS) which initially includes Image Product Library.
-f INTERNET - unclassified network connection.
-g UKMilSvy - United Kingdom Military Survey (UKMilSvy)(TBD).
-h DISN LES - Defense Information System Network Leading Edge Services
-i GBS - Global Broadcast System
-a Profile Relationships - Customer Profile shall provide administrators the capability to add, delete and modify the customer profile elements and their relationship to privileges and services.
-b CIIP Attributes - The Customer Profile shall be based on query attributes as defined in the Common Imagery Interface Profile (CIIP).
-c DoDAAC/FedACC - Additional profile information may be required based on Department of Defense Activity Address Code (DoDAAC) / Federal Activity Address Code (FedAAC) (note: this field is mandatory for customers ordering standard stocked products; not all GGI&S customers will have a DoDAAC or FedAAC)
-d New Profiles - Customer Profile shall provide new customers the capability to initiate a request for a new customer profile.
-e Customer Edit - Customer Profile shall provide customers the ability to view and edit elements of their own customer profile to which they have been granted those access privileges.
-f Administrative Edits - Customer Profile shall provide administrators the capability to create, edit, save and delete customer profiles.
-g One Profile Access - Customer Profile shall establish one profile for each customer that will give a customer access via the requested network and any lower security networks.
-h Access Control - Customer Profile shall provide administrators the capability to control customer access.
-a Information Protection - The Security Profile is used to ensure that information is restricted to customers with appropriate security access and sensitivity.
-b Capabilities - The Security Profile is a subset of Customer Profile and shall include all the capabilities specified for Customer Profile
-c Minimum Information - The Security Profile shall contain the following information at a minimum:
-d Validated Access - A customer's Security Profile information shall be validated before access to any of the data is permitted.
-e Default Levels - The default Security Profile security level/sensitivity parameters shall be at the unclassified/non-sensitive level.
-f Administrative Access - Security Profile shall provide the capability for administratively designated security officials to define, protect, and configure Security Profile elements for security access and sensitivity.
-g Customer View - Security Profile shall provide customers the capability to view their Security Profile information, except for account details (e.g., User ID, password cannot be viewed).
-h Administrator Privilege - Security Profile shall provide administrators the capability to view Security Profile information.
-a Product Data - Storage capacity for the following product data types, with the volume indicated, shall be provided:
| 1.5 GB |
| 600 GB |
| 60 GB |
| 300 GB |
| 2.5 GB |
| 7 GB |
| 300 TB (TBR) |
| 1 GB |
| 300 GB (TBR) |
-a Area Type/Color - The capability to utilize special line types and colors to indicate some attribute of an area (e.g., a restricted area, a threat area, an intersection of two areas, or an area on the map display defined by an end user) shall be provided. This capability shall include fill patterns (e.g., varieties of hachures or shading) that can be used to distinguish the type of area or the value of a feature associated with an area.
-b Boundary - Cartographic definition shall utilize boundaries to specify the region that is included in an area. The boundary shall consist of two sets of closed polylines. One set represents the regions that are included inside the polylines. That is, the “inside” of each closed polyline in this set is defined to be within the area. (No point that is outside all of these closed polylines can be in the area.) The other set represents the regions that are to be excluded. To be meaningful, each polyline in this set must bound a region that intersects some region defined in the “inclusion” set.
-c Label - The capability to label areas shall be provided.
-d Compute Area Size - The capability to compute the extent or quantity of land and/or sea covered as measured over hills or on a flat surface shall be provided. Input is an Area object; output is a value such as “5.3 square miles.” This size shall accurately reflect any exclusions.
-e Compute Average Elevation - A compute average elevation capability shall be provided to compute the average elevation within a specified area.
-f Define Area - A define area capability shall allows the user to designate a region for survey by identifying a selected closed combination of arcs and line segments as its boundary. In addition, define area capability shall allows the user to exclude a region from such a survey by identifying a selected closed combination of arcs and line segments as the boundary of an excluded region. This capability shall include the capability to create or modify an area by adding or changing any of its attributes.
-g Generate Roughness - A capability shall be provided to display a visual representation of the approximate texture or coarseness of the terrain.
-h Locate Min/Max - A locate minimum/maximum elevation capability shall be provided to compute the highest and/or lowest elevation and its corresponding geographic position within a given area.
-a Define Background - The capability to define and select the background for a display shall be provided.
-a Type of Context - The capability to distinguishes between a context map showing the area of interest within the coverage area or the area of display within the area of interest shall be provided.
-b Visibility - The capability to toggle the visibility of the overlay, context map, symbols, labels and other objects shall be provided.
-c Display Context Map - The capability to portray a map as it relates to the coverage area of spatial data or as it relates to the portion currently being displayed shall be provided.
-d Redefine Area of Display - This capability shall allow the user to move a rectangle representing the current viewing position and scale of the map in relation to the entire area of interest so that the map will automatically be redraws to reflect the new viewing position. This capability shall also resize the rectangle of the inset map by enlarging or decreasing the size in rubber-band fashion and cause a corresponding change in scale in the main map window
-a Isopleth Type - Multiple isopleth types shall be supported.
-b Unit Value - Each isopleth type shall have a unit value that defines the shape/topology of the isopleth (e.g., 3000 foot elevation contour).
-c Define Isopleth - The capability to specify the isopleth type (e.g., equal elevation, equal threat, etc.) and to specify the unit value for which the isopleth is to be identified (e.g., 100 meters, threat level 1) shall be provided.
-a Area of Interest - A map shall be capable of supporting multiple areas of interest (AOI) which are used to specify a particular region under investigation.
-b Datum - Maps shall be supported by a variety of datum. Datum is defined as any numerical or geometrical quantity or set of such quantities which may serve as a reference or base for other quantities.
-c Projection - The capability for different map projections shall be provided. Examples include, but are not limited to, Mercator, Equidistant Conic, Orthographic, and Polar Sterographic.
-d Scale - Multiple map scales shall be supported.
-e Define Area of Interest - The capability to define area of interest shall be provided. This capability allows a narrowing of focus from a global to a regional area of interest within a coverage area. Its parameters are: area of interest (AOI), data type, and destination (overlay or background).
-f Register/Align - The elements in overlays and the background shall be automatically moved, resized, or otherwise adjusted based on the selected Map attributes.
-g Select/Set Scale - Select/set scale shall expand or restrict the inclusion of map features based on map scale. The smaller scale maps (those with the larger denominator, e.g., 1:1,000,000) will not include the detail that could be included in larger scale maps (those with smaller denominators, e.g., 1:12,500).
-h Transform Projection - Transform projection shall alter the map so that all features conform to the spatial relationships of the specified Projection attribute. Transformations involve changes in equations, ellipsoids, scale factors, cone constants, standard lines, standard parallels, origins, central meridians, etc. Grids shall be included to allow display in latitude/longitude, UTM, UPS or MGRS coordinates. Grid control shall include on/off, line type, line width, line color, scale increments, hatch increments, and labeling.
-i Transform/Shift Datum - The capability to alter the position of a point or feature in the map based on its datum attributes, different datum recorded with a spatial data set, or datum given by a user, shall be provided. The result shall be an equivalent set of coordinates for one or more coordinates in an alternate datum. Transform/shift datum can be performed on one coordinate pair, area of interest, or entire data store.
-a Area of Display - The capability to specify the display area within a map shall be provided.
-b Center Point - A center point capability which automatically auto-pans to the middle of the map display shall be provided.
-c Orientation - Map orientation shall be selectable.
-d Convert Unit of Measure - The capability to change from one unit of measurement to another (e.g., nautical miles to statute miles, height in feet to height in meters, etc.) shall be provided.
-e Display - The capability to create a map display and output its image to a computer screen shall be provided.
-f Fade/Unfade - The degree of brightness (map intensity) of a map shall be selectable.
-g Pan - The capability to pan (i.e. scroll or roam) the display shall be provided.
-h Print/Plot Map - The capability to create a map image that is output to a printer, plotter, or other device shall be provided.
-i Recenter - Recenter shall position the map image so that a selected or default point is in the middle of the display window.
-j Rotate - The user shall have the capability to rotate displayed data.
-k Zoom - The capability to allow the user to zoom in and out of a map display by a specified factor shall be provided.
-a Define Marginalia - The capability to create, define, and modify the contents of map marginalia shall be provided.
-a Visibility (on/off) - The visibility of an overlay shall be on/off selectable.
-b Annotate - The capability to create and modify annotations shall be provided.
-c Declutter Features - A declutter capability shall be provided to remove, offset, or restore symbols in the overlay. This service shall operate based on criteria supplied by the end user.
-d Define Overlay - The capability to create, delete, select and/or modify the coverage and content of an overlay shall be provided.
-e Determine Union/Intersection - The capability to determine the union/intersection of two or more constituent areas or polylines of an overlay shall be provided.
-f Hide/Show/Reorder - This capability shall the capability to specify the order in which overlays are presented (e.g., an overlay containing city outlines and rivers would be presented “first prior” to an overlay containing building outlines and bridges or the city outline overlay would obscure the building outline overlay). This service shall also provide the capability to either hide (i.e., make the overlay invisible) or show (i.e., make the overlay visible).
-g Register/Align - Register/Align shall provide the following capability:
-a Date and Time - The user shall be able to specify the date and time of day (Zulu) so that solar illumination is properly provided to a visual prediction.
-b Field of View - The user shall be able to specify the field of view.
-c Illumination - The user shall be able to specify illumination. This attribute represents the lighting effect of sun or moon based on date, time, or weather information.
-d Observer Orientation - The user shall be able to specify the observer orientation.
-e Observer Position - The user shall be able to specify observer position (vertical and horizontal location of the observer to be used as the basis for intervisibility calculations). This may include the height and/or altitude of the observer or sensor.
-f Terrain Exaggeration - Perspective view shall include a capability that enhances differences in displayed elevation to highlight subtle terrain undulations.
-g Define Perspective View - The user shall be able to define perspective view shall by creating or modifying the three-dimensional representation of the map based on horizontal and vertical viewing position and azimuth.
-h Depict Illumination - Adjust perspective view display to reflect light/shadow effects of the sun or moon as defined by the Illumination attribute.
-a Coordinate - Coordinates shall be available for each point as defined above.
-b Elevation/Depth - Elevation and depth of points shall be supported.
-c Label - Descriptive labels for points shall be supported.
-d Point Type/Color - The use of colors to indicate special points or features shall be supported.
-e Convert Coordinate - The capability to translate the value of a point in one coordinate system to its equal in a different coordinate system shall be provided.
-f Define Point - The capability to create, select, and/or modify a point shall be provided.
-a Label - Labeling of polylines shall be supported.
-b Polyline Type/Color - The capability to use different colors and/or types (also known as visual line formats [e.g., dashes]) to distinguish the associated values or meanings of a polylines shall be supported.
-c Compute Distance - A compute distance capability shall be provided that can determine the spatial separation of two points, measured by the length of a line joining them. This capability shall include support for great circles, rhumb lines, true distance and convergence.
-d Define Polyline - The capability to create, select, and/or modify a Polyline shall be provided.
-a Label - Labeling of symbols shall be supported.
-b Symbol Type/Color - Different colors and types of symbols shall be supported.
-c Define Symbology - The capability to create, edit, or delete predefined templates for symbols and define the criteria or rules for applying a template to a unique symbol shall be provided.
-d Group/Ungroup - A group/ungroup capability which can manipulate an assemblage of symbols as one or, conversely, to segregate and manipulate each of the various symbols independently of the group shall be provided.
-a Ending Point - The capability to define a terrain profile end point shall be provided.
-b Starting Point - The capability to define a terrain profile start point shall be provided.
-c Define Terrain Profile - The capability to define a terrain profile or modify the cross-section representation of the Earth’s terrain from the starting point to the ending point shall be provided.
-a Text Type/Color - Different types and colors of text shall be supported.
-b Define Text - A define text capability shall allow the user to insert additional information within the map as an annotation or as free text.
-a Ending Point - The capability to define an end point shall be provided.
-b Starting Point - The capability to define a start point shall be provided.
-c Compute Azimuth/Bearing - The capability to calculate true distance and azimuth between two geographical positions shall be provided.
-d Compute Slope - The capability to determine the rate of rise or fall of a quantity against horizontal distance expressed as a ratio, decimal, fraction, percentage, or the tangent of the angle of inclination shall be provided.
-a Store/Play - Video Disc Software (VDS) that supports store, display, zoom, pan and scroll of image frames from a video disc shall be provided.
-a Chart Notices - Chart notices (e.g. CHUM, ECHUM, Notice to Mariners, DAFIF) shall be supported.
-a Gazetter - A gazetteer capability shall be provided. A gazetteer is an alphabetical list of place names giving feature identification and geographic and/or grid coordinates.
-b Interpret Place Attributes - The gazetteer shall provide a list of named locations. Upon selection of a name, the map shall be centered at the corresponding latitude/longitude at an appropriate magnification. The user shall be able to add and remove named locations using a gazetteer list.
-a Gridded Data Set - Support for gridded data sets shall be provided. A gridded data set of MC&G data is characterized by a matrix of evenly spaced rows and columns of data points (e.g., DTED, DEM, World Mean Elevation Data - WMED, Digital Bathymetric Data Base - DBDB).
-a Imagery - Display of imagery data shall be supported. Imagery data includes photographic, satellite, radar, infrared, and multi-spectral.
-b Filter Type - Image filters shall be provided. Filter categories provided shall include contrast enhancement, high-pass, noise reduction, smoothing, edge detection, point detection, and thresholding.
-c Apply Filter - The capability for the user to select the filter type and specify an area of the image display to enhance shall be provided.
-a Raster Data Set - Raster data set shall be supported. Raster data sets typically record scanned maps and charts, image data, or gridded data.
-a Scanned Data Set - Scanned data sets (e.g., successive parallel strips or capture data from a sensor or scanner, such as a row of a raster grid) shall be supported.
-a Coverage Area - Geospatial data sets shall be defined by coverage area.
-b Format - Different Geospatial formats shall be supported. The format is varied as well as the level of resolution and the type of information content. Data sets may include topographic, hydrographic, and aeronautical information.
-c Metadata - Metadata for Geospatial data sets shall be supported.
-d Convert Unit of Measure - The capability for the user to change from one unit of measurement to another (e.g., nautical miles to statute miles, height in feet to height in meters, etc.) shall be provided.
-e Import/Export - The capability to retrieve and load (import) Geospatial data from external sources and to transfer (export) data from a local Geospatial data set to external systems shall be provided.
-f Raster Data - The capability to import and export raster data and metadata based on selected coverage area shall be provided. Representative raster formats and data types include:
-g Vector/Feature Data - The capability to import and export vector/feature data and metadata based on selected coverage area shall be provided. Representative vector/feature formats and data types include:
-h Text Data - The capability to import and export text (character) data and metadata based on selected coverage area shall be provided. Representative text formats and data types include:
-i Format Conversion - The capability to convert data from one format to another shall be provided. This capability shall include the ability to convert an image to an appropriate interchange format (e.g. Computer Graphics Metafile (CGM)) and place it within a National Imagery Transmission Format (NITF) file.
-j Maintain Metadata - The capability for the user to maintain metadata shall be provided.
-k Select/Search - The capability for the user to specify the type, extent, format of Geospatial data set, or sub-set, to be used for a particular task shall be provided.
-l Show Coverage Area - The capability for the user review and identify the extent of Geospatial data set coverages shall be provided.
-m Show Differences - The capability to compare and show the difference of two similar data sets shall be provided.
-n Service Store/Update/Retrieve - The capability to update, save, and retrieve “new” or “changed” Geospatial data or mission folders data shall be provided.
-o Thin/Interpolate - A thin/interpolate capability to reduce or infer the values of a collection of Geospatial data based on proximate elements shall be provided.
-a Text Data Set - Geospatial data sets shall include text data sets. Text data is narrative information relating to Geospatial data. An example is the DMA Notice to Mariners System and Chart Updating Manual (CHUM).
-a Add Feature Height - The capability to add the vertical length of an object to the elevation value at which it is located shall be provided.
-b Interpret Feature Attributes - The capability for the user to get more detailed information on a specific feature or set of features or a type of spatial data set shall be provided.
-a Mobility Corridor - Cross country movement shall include the ability to specify the off-road passageway (mobility corridor) to be taken by the vehicles between a starting point and an ending point.
-b Determine Path of Least Resistance - Cross country movement shall include the ability to determine path of least resistance. This path is the route requiring the least amount of time, fuel, and risk between a starting point and an ending point.
-a Observer Position - The capability to specify the vertical and horizontal location of the observer used for intervisibility calculations shall be provided.
-b Range - The capability for the user to define the viewing area of interest shall be provided. This capability shall include, but not necessarily limited to, definition of:
-c Assess Visibility - An assess visibility capability shall be provided that compares the total visibility of each area, based on different observer positions, and rank the best to worst positions.
-d Determine Masked/Visible Area - The capability to identify and display areas that are not visible or detectable from those that are visible or detectable shall be provided
-e Determine Visible Profile - The capability to compute the visibility of portions of a vertical cross-section of visible terrain and display this information on a terrain profile background shall be provided.
-a Target Position - LOS shall include a target position capability that specifies the horizontal and vertical position of a (potential) target or other object within a viewing azimuth/range.
-b Determine Visibility - LOS shall include the capability to search for terrain obstructions or other hindrances to seeing or detecting an object at the target position from the observer position. This capability shall also compute the degree to which visibility may be degraded, based on smoke, dust, fog, or similar obscurants identified by the user.
-c Indicate Obstruction - LOS shall include the capability to identifies the reasons for lack of visibility.
-a Area of Operations - Mission analysis shall utilize an area of operations.
-b Target - A capability to define or estimate enemy characteristics such as identifier, type, strength, strategic or tactical significance, position, range, and bearing shall be provided. This capability also applies to geographical areas, complexes, and installations planned for capture or destruction by military forces.
-c Define Area of Operations - Mission analysis shall include the capability to select, create, and/or modify the area of operations.
-d Define Special Area - The capability to select, create, and/or modify areas that have significant meaning for the specific context at hand shall be provided. For example, the selection of cover and concealment to identify areas that are suitable for hiding, based on terrain contour and vegetation (type, average height, density, etc.), along with factors such as the physical attributes of weapon and sensor systems, vehicles, etc.
-e Define Supply/Refuel Point - Mission analysis shall include the capability to define supply and refuel points.
-f Define Target - Mission analysis shall include the capability to identify the position of enemy forces and facilities to be destroyed.
-g Define Unit Position - Mission analysis shall include the capability to identify the location of the position of friendly forces and identify areas where units are not (but need to be) assigned. This capability uses information about military units and spatial data and includes estimate friendly-force characteristics such as echelon, type, strength, position, heading, and areas of responsibility.
-h Determine Weapon Fan/Ballistics - Mission analysis shall include the capability to identify areas that can (or cannot) be hit by artillery, missiles, and other ammunition. This capability shall compute weapon and ballistics characteristics such as type, firing rate, munitions class, position, maximum range, and bearing..
-a Mission Folder - The user shall be provided an on-line capability to accumulate materials associated with a mission analysis effort.
-b Print Mission Folder - The capability to preview and print the materials contained within a mission folder shall be provided.
-c Store/Update/Retrieve - The capability to save, update, and retrieve “new” or “changed” mission folder data shall be provided.
-a Determine Alternate Routes - Road mobility shall include the capability to determine alternate routes. The analysis shall consider road conditions and threat areas.
-a Average Speed/March Rate - The route function shall provide the capability to specify the velocity of a vehicle, unit or other entity expressed in terms of units of distance per units of time along a route.
-b Ending Point - The route function shall provide the capability to specify the end point of a route.
-c Starting Point - The route function shall provide the capability to specify the start point of a route.
-d Waypoints - The route function shall provide the capability to specify waypoints that designate important features of a Route such as turn points (start/end of a leg), rendezvous points, supply/refueling points, etc.
-e Assess Route - The route function shall provide the capability to evaluates a particular route against user-specified criteria such as observability, threat detection/engagement, terrain clearance, and conflicts with other routes. In the special case of ground routes, this service is traditionally called trafficability analysis. Factors for assess route include average speed, surface traversing, travel duration (e.g., how much time does it take from point of departure to a destination?). Assess route can also indicate travel constraints (e.g., damaged bridge) as well as depicting points of intersection or alternate routes.
-f Compute Duration - The route function shall provide the capability to compute an estimate for the elapsed time to go from a given Starting Point at a given Average Speed/March Rate to a given Ending Point.
-g Deconflict Route - The route function shall provide the capability to deconflict a route including ability for rerouting and diverting due to physical conflicts (e.g., traffic disruptions) and/or time conflicts.
-h Define Route - The route function shall provide the capability to allows the user or mission software to create and update a route by choosing a starting point, an ending point, and a series of intermediate (zero or more) waypoints. This service also allows for the update of a route by adding, deleting, or modifying legs/segments in an existing route.
-i Determine Optimal Route - The route function shall provide the capability to identify the route segments between a starting point and an ending point that are most effective/desirable given travel constraints.
-j Estimate Distance - The route function shall provide the capability to estimate the length from a point of departure to a destination and/or for a travel duration.
-a Threat Range/Probability - Threat analysis shall include the capability to display threat rings (isopleths) that represent threat probabilities for detection and engagement.
-b Threat Type - Threat analysis shall support multiple threat types.
-c Create Composite Range - Threat analysis shall include threat evaluation tools to assist the user in determining risk of Detection, Engagement, Kill, or of being seen (Terrain Masking).
-d Determine Detection - Threat analysis shall include the capability to assess likelihood of detection by one or more threats.
-e Determine Engagement - Threat analysis shall include the capability to assess likelihood of a hostile encounter.
-f Determine Threat Fans - Threat analysis shall include the capability to display detection or engagement fans for selected threats.
-g Select/Define Threat - Threat analysis shall include the capability for the user to select from the map displayed on the screen, define new threats to be used, and remove (filter) threats from a selected threat list.
-a Deconflict/Fuse - The capability to merge (fuse) data from different sources shall be provided.
-b Perform Data Quality Control - The capability to verify that the MC&G data has been produced according to certain guidelines and/or product specifications shall be provided. Data Quality Control shall include content, format, and context checking, as well as provide a means of assisting human interpretation of a data set.
-c Perform Mensuration - The capability to perform mensuration shall be provided.
-d Rectify Image - The capability to rectify an image shall be provided. Rectification shall include Rubber sheeting which is a process that resamples data to transform (stretch or compress) it from one statistical model to fit another model.
-e Request External Data - The capability to request a specific type of data (coverage and format) from appropriate external sources shall be provided.
-f Remote Replication - The capability to display and print framework information shall be provided. This capability shall include the use of “color separates”.
-g Construction Information - The capability to record and maintain product (e.g. map) generation and modification information shall be provided.
-h Browse - The browse capabilities, specified for Information Management and Dissemination, shall be provided.