The Mapping Services Component Area provides the capability to present and manipulate
information in a geographical context.
| Criteria Number |
Criteria Description |
| 1.0 |
Architectural Characteristics |
| 1.1 |
The Mapping Services processes should be self-contained to allow a potential user to
easily evolve their environment to meet changing requirements (modular). |
| 1.2 |
The Mapping Services should distribute its processes among servers or workstations
allowing users to configure their particular application to meet different domain
requirements and architectures. |
| 1.3 |
The Mapping Services should provide modular, add-on capabilities which can selectively
be integrated into specific applications, allowing developers/users to select only that
portion of the total functionality they require. |
| 1.4 |
The Mapping Services should run on a variety of platforms. |
| 1.5 |
The Mapping Services should accommodate a variety of operating systems that include
but are not limited to POSIX or POSIT compliant. |
| 2.0 |
Implementation Constraints |
| 2.1 |
The Mapping Services should support X11 Release 4 or higher. |
| 2.2 |
The Mapping Services should support Open Systems Foundation/Motif graphical user
interface style guide. |
| 2.3 |
The Mapping Services should be POSIX and/or Windows (3.1, 3.11, NT, 95) compliant. |
| 2.4 |
The Mapping Services should NOT assume a stand-alone environment, e.g., does not
capture system interrupts. |
| 3.0 |
Security Features |
| 4.0 |
Mapping Services Requirements |
| 4.1 |
The Mapping Services should support standard Defense Mapping Agency (DMA products
(ADRG, DCW, WVS, WDBII, DTED), plus the ability to import/register imagery. |
| 4.2 |
The Mapping Services should support map projections: |
| 4.2.1 |
Mercator |
| 4.2.2 |
Oblique Mercator (Hotline) |
| 4.2.3 |
Transverse Mercator |
| 4.2.4 |
Orthographic |
| 4.2.5 |
Azimuthal Equal Area |
| 4.2.6 |
Universal Transverse Mercator (UTM) |
| 4.2.7 |
Stereographic |
| 4.2.8 |
Polar Stereographic |
| 4.2.9 |
Gnomonic |
| 4.2.10 |
Azimuthal Equidistant |
| 4.2.11 |
Three-Dimensional |
| 4.3 |
The Mapping Services should support coordinate transformations between UTM,
latitude/longitude, radians, and pixels. |
| 4.4 |
The Mapping Services should support calculations: |
| 4.4.1 |
The Mapping Services should compute and display range rings from a given point. |
| 4.4.2 |
The Mapping Services should support Range: |
| 4.4.2.1 |
Distances can be generated based on Great Circle |
| 4.4.2.2 |
Distances can be generated based on Rhumb Line |
| 4.4.2.3 |
Distances can be generated based on Rectangular Lat/Long algorithms. |
| 4.4.3 |
The Mapping Services should support Bearing: |
| 4.4.3.1 |
True North |
| 4.4.3.2 |
Magnetic North. |
| 4.4.4 |
The Mapping Services should support Line of Sight. |
| 4.4.5 |
The Mapping Services should support Radar Coverage/Fire Fan (sensor output simulation,
threat envelopes): |
| 4.4.6 |
The Mapping Services should support trial Intercept Calculations. |
| 4.4.7 |
The Mapping Services should support Azimuth. |
| 4.4.8 |
The Mapping Services should support spatial queries (e.g., closest approach). |
| 4.4.9 |
The Mapping Services should support Point-to-point slope. |
| 4.4.10 |
The Mapping Services should support Terrain shading. |
| 4.4.11 |
The Mapping Services should support Area calculation. |
| 4.4.12 |
The Mapping Services should support Volume calculation. |
| 4.4.13 |
The Mapping Services should support MIN/MAX elevation readout. |
| 4.4.14 |
NOT USED |
| 4.4.15 |
The Mapping Services should support Terrain masking (by area). |
| 4.4.16 |
The Mapping Services should support Shortest path along network. |
| 4.4.17 |
The Mapping Services should support Spatial adjacency search. |
| 4.4.18 |
The Mapping Services should support Nearest neighbor search. |
| 4.4.19 |
The Mapping Services should support Optimal path. |
| 4.5 |
The Mapping Services should support contours: |
| 4.5.1 |
Spacing |
| 4.5.2 |
Labeling |
| 4.5.3 |
Colors. |
| 4.5.4 |
The Mapping Services should support displaying land contours in 3D |
| 4.5.4.1 |
Allow specification of vertical exaggeration. |
| 4.5.4.2 |
Allow specification of position of illumination/light source. |
| 4.5.4.3 |
Allow surface rendering (as a cartographic display operation). |
| 4.6 |
The Mapping Services should support latitude/longitude grids: |
| 4.6.1 |
Spacing |
| 4.6.2 |
Labeling |
| 4.6.3 |
The Mapping Services should allow setting grid line attributes: |
| 4.6.3.1 |
Weight and style |
| 4.6.3.2 |
Colors |
| 4.6.4 |
The Mapping Services should allow turning off and on of map features. |
| 4.6.5 |
The Mapping Services should display with annotation at a specified scale and
coordinate system: |
| 4.6.5.1 |
Neat lines |
| 4.6.5.2 |
grid lines |
| 4.6.5.3 |
tick marks |
| 4.6.5.4 |
cross hairs. |
| 4.7 |
The Mapping Services should support processing of overlays: |
| 4.7.1 |
Saving |
| 4.7.2 |
Loading/Activating |
| 4.7.3 |
Creating |
| 4.7.4 |
Editing |
| 4.7.5 |
Deleting |
| 4.7.6 |
Linking to Map |
| 4.7.7 |
The Mapping Services should allow selective display of overlay from Vector Data: |
| 4.7.7.1 |
Text |
| 4.7.7.2 |
Symbols |
| 4.7.7.3 |
Rivers |
| 4.7.7.4 |
Roads |
| 4.7.7.5 |
Rails |
| 4.7.7.6 |
Boundaries |
| 4.7.7.7 |
Urban |
| 4.7.7.8 |
Vegetation. |
| 4.7.8 |
The Mapping Services should support selection of Vector Data Only. |
| 4.7.9 |
The Mapping Services should support selection of Raster Data Only. |
| 4.7.10 |
The Mapping Services should support selection of both Vector and Rater Data. |
| 4.7.11 |
The Mapping Services should support boolean AND, OR, XOR, NOT overlay operators for
vector data: |
| 4.7.11.1 |
polygon in polygon |
| 4.7.11.2 |
point in polygon |
| 4.7.11.3 |
point in line |
| 4.7.11.4 |
line in polygon. |
| 4.7.12 |
The Mapping Services should support boolean AND, OR, XOR, NOT overlay operators for
raster data: |
| 4.7.12.1 |
polygon in polygon |
| 4.7.12.2 |
point in polygon |
| 4.7.12.3 |
point in line |
| 4.7.12.4 |
line in polygon. |
| 4.7.13 |
The Mapping Services should support the ability to weigh features within a data
category or data categories during the overlay process. |
| 4.7.14 |
The Mapping Services should support the ability to superimpose one data category on
another with replacement. |
| 4.8 |
The Mapping Services should support symbology: |
| 4.8.1 |
The Mapping Services should support User Creation of symbology: |
| 4.8.1.1 |
The Mapping Services should define icons via icon editor and/or bitmaps. |
| 4.8.1.2 |
The Mapping Services should provide icon hook capability of symbology. |
| 4.8.2 |
The Mapping Services symbology should support multiple colors. |
| 4.8.3 |
The Mapping Services symbology should be scalable. |
| 4.8.4 |
The Mapping Services symbology should be rotatable. |
| 4.8.5 |
The Mapping Services symbology should support associated text: |
| 4.8.6 |
The Mapping Services should support map lines. |
| 4.8.7 |
The Mapping Services should support legends. |
| 4.8.8 |
The Mapping Services should support bar and text scales. |
| 4.8.9 |
The Mapping Services should support north/south arrows. |
| 4.8.10 |
The Mapping Services should support the ability to select point symbols and icons,
line types, area fill patterns, and character fonts from existing tables. |
| 4.8.11 |
The Mapping Services should support naming, storing, and retrieving (user created
symbols). |
| 4.8.12 |
The Mapping Services should support interactively positioning (user created symbols). |
| 4.8.13 |
The Mapping Services should ensure that annotations and icons attach to a location and
remain in place during panning and zooming. |
| 4.8.14 |
The Mapping Services should support movement of icons on the screen (for tracking
purposes): |
| 4.8.14.1 |
Allow automatic updating of tracking information for a target. |
| 4.8.14.2 |
Allow displaying all or a subset of ancillary data on demand and/or constantly,
following position changes of icons or points. |
| 4.8.14.3 |
Allow displaying satellite footprint/ground track with position based on current time
or user specified time. |
| 4.8.14.4 |
Allow a breadcrumb (track history) trail capability. |
| 4.8.14.5 |
Allow cross country movement. |
| 4.8.15 |
The Mapping Services should display catalog information (coverage, scale, contents) of
disparate data sources (ADRG, VPF, Arc, etc.) |
| 4.9 |
The Mapping Services should support screen navigation: |
| 4.9.1 |
Panning |
| 4.9.2 |
The Mapping Services should support Zooming In/out: |
| 4.9.2.1 |
Zoom to top Zoom to the highest (default) level (in the QDR, the full world view). |
| 4.9.2.2 |
Zoom in center (i.e., causes the currently displayed map to be redrawn, using the same
center point, at one magnitude of resolution greater). |
| 4.9.2.3 |
Zoom via a bounding box (i.e., map is zoomed to selected area and resized to fill the
entire drawing widget). |
| 4.9.3 |
Save Map Views |
| 4.9.4 |
Load Saved Map View |
| 4.9.5 |
Dynamic Map Resizing |
| 4.9.6 |
The Mapping Services should generate maps that are larger than the physical dimensions
of the output display device that can be composed in a mosaic of the larger area. |
| 4.9.7 |
The Mapping Services should support coordinate key-in. |
| 4.9.8 |
NOT USED |
| 4.9.9 |
The Mapping Services should be able to access the current scale (magnitude). |
| 4.10 |
The Mapping Services should support various types of drawing capabilities: |
| 4.10.1 |
Lines |
| 4.10.2 |
Polygons |
| 4.10.3 |
Ellipses |
| 4.10.4 |
Rectangles. |
| 4.10.5 |
The Mapping Services should support filled objects: |
| 4.10.5.1 |
Allow for creating, naming, storing, and selecting default fill patterns. |
| 4.10.5.2 |
Allow for interactively assigning a fill pattern. |
| 4.10.5.3 |
Allow for crosshatch fill areas by specifying hatch color, line type, rotation angle,
and distance interval. |
| 4.10.6 |
The Mapping Services should support points: |
| 4.10.6.1 |
Allow for creating, naming, storing, and selecting default point symbols |
| 4.10.6.2 |
Allow for interactively assigning a point symbol to a point. |
| 4.10.7 |
The Mapping Services should support text: |
| 4.10.7.1 |
Allow to specify font type, case, character size, color and string orientation for
text entries |
| 4.10.7.2 |
Allow capability to automatically position text entries at pre-specified point
locations (e.g., polygon centroids), supplemented with the capability to interactively
move or rubberband respective entries |
| 4.10.8 |
The Mapping Services should support arcs. |
| 4.10.9 |
The Mapping Services should support creating, naming, storing, and selecting default
line patterns for line-based graphic objects (e.g., lines, boxes, circles, etc.): |
| 4.10.9.1 |
Allow the width drawing attribute. |
| 4.10.9.2 |
Allow the style drawing attribute. |
| 4.10.9.3 |
Allow the color drawing attribute. |
| 4.10.9.4 |
The Mapping Services should support various drawing attributes including: XOR,
transparent, opaque, filled, open, and closed. |
| 4.10.10 |
The Mapping Services should support interactive assignment of line type or line width
or other definable line attribute to a line or line-based graphics object. |
| 4.10.11 |
The Mapping Services should support interactive assignment of color to a graphics
object. |
| 4.11 |
The Mapping Services should support unit data type representations as specified by the
operator: |
| 4.11.1 |
Range (distance) data |
| 4.11.1.1 |
Nautical miles |
| 4.11.1.2 |
Miles |
| 4.11.1.3 |
Statute miles |
| 4.11.1.4 |
Kilometers |
| 4.11.1.5 |
meters |
| 4.11.1.6 |
feet |
| 4.11.2 |
Allow various units of angle data |
| 4.11.2.1 |
degrees |
| 4.11.2.2 |
mils |
| 4.11.2.3 |
radians |
| 4.11.3 |
Allow various precision of displayed UTM data |
| 4.11.3.1 |
1000 meters |
| 4.11.3.2 |
100 meters |
| 4.11.3.3 |
10 meters |
| 4.11.3.4 |
1 meter |
| 4.11.4 |
Allow various units for position data |
| 4.11.4.1 |
Lat/Long Degrees, Minutes and Seconds |
| 4.11.4.2 |
Lat/Long in Decimal Degrees |
| 4.11.4.3 |
Lat/Long Packed |
| 4.11.4.4 |
UTM with sheet numbers |
| 4.11.5 |
Allow various precision of displayed lat/long data |
| 4.11.5.1 |
0 decimals |
| 4.11.5.2 |
1 decimal |
| 4.11.5.3 |
2 decimals |
| 4.11.5.4 |
4 decimals |
| 4.11.6 |
Allow various units of speed data |
| 4.11.6.1 |
Knots |
| 4.11.6.2 |
miles per hour |
| 4.11.6.3 |
kilometers per hour |
| 4.11.6.4 |
mach |
| 4.11.6.5 |
meters per second |
| 4.11.7 |
Allow various units of altitude data |
| 4.11.7.1 |
Feet in thousands |
| 4.11.7.2 |
Feet in hundreds |
| 4.11.7.3 |
feet |
| 4.11.7.4 |
meters. |
| 4.12 |
The Mapping Services should support location functions: |
| 4.12.1 |
Go to a specified point: |
| 4.12.1.1 |
Accept point specification in latitude/longitude. |
| 4.12.1.2 |
Accept point specification in UTM. |
| 4.12.1.3 |
Accept point specification in cartesian (radians) coordinates. |
| 4.12.2 |
Identify location of a point: |
| 4.12.2.1 |
Accept point specification in latitude/longitude. |
| 4.12.2.2 |
Accept point specification in UTM. |
| 4.12.2.3 |
Accept point specification in cartesian (radians) coordinates. |
| 4.13 |
The Mapping Services should support selection of spatial or attribute data: |
| 4.13.1 |
Within a specified rectangular area. |
| 4.13.2 |
Within a specified circular area. |
| 4.13.3 |
Within a specified polygonal area. |
| 4.13.4 |
By feature name or groups of names. |
| 4.13.5 |
By boolean retrievals on attributes. |
| 4.13.6 |
By graphic hooks (e.g., digitized point). |
| 4.14 |
The Mapping Services should support capabilities to restructure information for
display enhancement: |
| 4.14.1 |
Allow interactive or automatic joining of geometrically adjacent data resolving gaps
and overlaps within default or user-specified tolerances. |
| 4.14.2 |
Allow modification of raster cell size through re-sampling. |
| 4.14.3 |
Allow reduction of unnecessary coordinate detail (weeding) while retaining corner
points, general sinuosity, and shape. |
| 4.14.4 |
Allow smoothing of line data to recover general sinuosity and shape. |
| 4.14.5 |
Allow generation of contours from either random or gridded Z value data points, and
conversely generate gridded Z value data points from contour data. |
| 4.14.6 |
Allow generation of a triangulated irregular network from random or gridded Z value
data points or from contour data. |
| 4.14.7 |
Allow generation of gridded data or contour data from a triangulated irregular
network. |
| 4.14.8 |
Allow constraining of contour generation by specifying barriers (e.g, fault lines) or
constraints (e.g., ridge and stream lines). |
| 4.14.9 |
Allow image registration. |
| 4.14.10 |
Allow image warping. |
| 4.15 |
The Mapping Services should support raster cell operations: |
| 4.15.1 |
Allow capability to assign binary (0/1), discrete (0-32768) or real continuous data
values to cells in a raster data set. |
| 4.15.2 |
Allow capability to perform mathematical operations on two or more raster data
categories: |
| 4.15.2.1 |
add |
| 4.15.2.2 |
subtract |
| 4.15.2.3 |
multiply |
| 4.15.2.4 |
divide |
| 4.15.2.5 |
minimum |
| 4.15.2.6 |
maximum. |
| 4.15.3 |
The Mapping Services should support capability to perform mathematical operations on a
single raster data category: |
| 4.15.3.1 |
exponentiate |
| 4.15.3.2 |
logarithm |
| 4.15.3.3 |
natural logarithm |
| 4.15.3.4 |
absolute value |
| 4.15.3.5 |
sine/arcsine |
| 4.15.3.6 |
cosine/arccosine |
| 4.15.3.7 |
tangent/arctangent. |
| 4.15.4 |
The Mapping Services should support capability to replace cell values with a new value
reflecting some mathematical combination of neighborhood cell values: |
| 4.15.4.1 |
average |
| 4.15.4.2 |
maximum |
| 4.15.4.3 |
minimum |
| 4.15.4.4 |
total |
| 4.15.4.5 |
most frequent |
| 4.15.4.6 |
least frequent |
| 4.15.4.7 |
mean deviation |
| 4.15.4.8 |
standard deviation |
| 4.15.4.9 |
user defined. |
| 4.16 |
The Mapping Services should support supervised and unsupervised clustering capability.
|
| 4.17 |
The Mapping Services should support generation of slope, aspect, and sun intensity
data categories. |
| 4.18 |
The Mapping Services should support generation of 3D orthographic and two-point
perspective view plots of gridded surfaces or other Z value data categories. |
| 4.19 |
The Mapping Services should support composition of displays interactively or use
default map composition layouts. |
| 4.20 |
The Mapping Services should support the capability to specify the location, size,
scale, and orientation of multiple view ports on a single display. |
| 4.21 |
The Mapping Services should support access to control cursor type and position: |
| 4.21.1 |
Coordinate readouts |
| 4.22 |
The Mapping Services should support access to position of cursor. |
| 5.0 |
Interfaces to External Devices |
| 5.1 |
The Mapping Services should support hardcopy output to standard laser printer. |
| 5.2 |
The Mapping Services should support hardcopy output to a plotter. |
| 5.3 |
The Mapping Services should support importing of standard DoD imagery products as
scanned/electronic map data. |
| 5.4 |
The Mapping Services should support importing of standard DoD imagery products as
scanned/electronic photographic data. |
| 5.5 |
The Mapping Services should support reading/displaying data formats directly from
source media. |
| 5.6 |
The Mapping Services should support manual digitizing. |
| 5.7 |
The Mapping Services should support scanner interface. |
| 6.0 |
User Language |
| 6.1 |
The Mapping Services should support languages: |
| 6.1.1 |
C |
| 6.1.2 |
C++ |
| 6.1.3 |
The Mapping Services should support Ada: |
| 6.1.3.1 |
Allow Ada bindings to POSIX (IEEE 1003.5). |
| 6.1.3.2 |
Allow Ada bindings to embedded SQL (ANSI X 3.168). |
| 6.1.4 |
Proprietary/closed |
| 6.1.5 |
User command macro. |
| 6.2 |
The Mapping Services should have a development environment integrated to the
toolkit/runtime. |
| 6.3 |
The Mapping Services must support toolkit implementation: |
| 6.3.1 |
Allow for building of macros, shell scripts, and/or batch files to automatically
execute complex functions from an aggregate of simpler individual functions. |
| 6.3.2 |
Allow error handling that can be redefined and controlled by the developer via API. |
| 6.3.3 |
Allow ability to develop custom mapping applications. |
| 6.3.4 |
Allow existence of an API for customizing applications. |
| 6.3.5 |
Allow tools for developing custom applications. |
| 6.3.6 |
Allow macro commands for creating working procedures. |
| 6.3.7 |
Allow linking to external function libraries. |
| 6.4 |
The Mapping Services vendor should provide technical support: Dedicated technical
support staff |
| 6.4.1 |
The Mapping Services vendor should provide material support (other than documentation)
e.g., code templates. |
| 6.4.2 |
The Mapping Services vendor should provide users manual and tutorials. |
| 6.4.3 |
The Mapping Services vendor should provide hardcopy documentation. |
| 6.4.4 |
The Mapping Services vendor should provide training/end-user learning support. |
| 6.4.5 |
The Mapping Services vendor should provide help screens. |
| 6.4.6 |
The Mapping Services vendor should establish third-party development programs. |
| 6.4.7 |
The Mapping Services vendor should provide system integration support. |
| 6.4.8 |
Hotline support. |
| 7.0 |
Performance |
| 7.1 |
NOT USED |
| 7.2 |
The Mapping Services should include vector redraw in less than 1second. |
| 7.3 |
The Mapping Services should include raster redraw in less than 5 seconds. |
| 7.4 |
The Mapping Services should support 3D mapping functions should execute in less than
30 seconds (average). |
| 7.5 |
The Mapping Services should accommodate real-time mapping display of 2,000 objects
without degradation. |
