Map Update System --> MAP GIS Operator:
map operator updates

Definitions

map operator updates (Information Flow): Interactive display of base map and information layers and associated information that supports map development, management, and dissemination.

Map Update System (Source Physical Object): The 'Map Update System' represents a provider of map databases used to support ITS services. It supports the provision of the map data that are used directly by vehicles (e.g., roadway and intersection geometry data sets), travelers (e.g., navigable maps used for route guidance and display maps used at traveler information points), system operators (e.g., map data used by Traffic Operators to monitor and manage the road network, and map data used by Fleet Managers to manage a vehicle fleet). It may represent a third-party provider or an internal organization that produces map data for agency use. In the latter case, the 'Map Update System' is typically included as part of the center (e.g., a Traffic Management Center) of the infrastructure owner/operator that manages map data. Products may include simple display maps, map data sets that define detailed road network topology and geometry, or full geographic information system databases that are used to support planning and operations.

MAP GIS Operator (Destination Physical Object): The 'Map GIS Operator' represents the person or people that manage GIS updates, supporting import and translation of source data, preparing the base map and information layers, and providing oversight and management for incremental releases of updated map data.

Included In

This Triple is in the following Service Packages:

This Triple is described by the following Functional View Functional Objects:

This Triple is described by the following Functional View Data Flows:

This Triple has the following triple relationships:

Communication Solutions

No communications solutions identified.

Characteristics

None defined


Interoperability Description
Not Applicable Interoperability ratings don't apply per se to some types of interfaces like human interfaces. These interfaces may still benefit from associated standards (e.g., ergonomic and human factors standards for human interfaces), but the primary motive for these standards is not interoperability.

Security

Information Flow Security
  Confidentiality Integrity Availability
Rating Not Applicable Moderate Moderate
Basis System core flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over core equipment Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation. The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take.


None defined