|
The diagram below illustrates the basic software components
used in the City's GIS. These components control data flows
from the AutoCAD Map down into the SQL Server database for
central storage. As the information passes through the SPATIALnet
Client and the SDM Server, strict quality control and quality
assurance rules are enforced, e.g., end points of linear features
must connect to the center of nodes in order for these features
to participate in link-node topologies, attribute values must
comply with valid value lists, etc.
From the SQL Server
database, other software components move spatial information
(geometries and attributes) out to support other user specific
software such as ArcGIS, DHI Mouse and MapGuide.
|
|
Furthermore, this
software allows the City to process "jobs" (change
orders). For example, the processing of an electronic as-built
constitutes a job, as such all of the features associated
with that as-built combine into a group with a specific job
number. As it can take some time to process each job, the
software tracks the group of components, controls the status
of these components, and then once the job is complete posts
the features for others to use. Prior to posting the group
of system components are only available to those responsible
for processing the job. Once a job is posted for production,
the software then synchronizes the group of system components
with the Hansen IMS, and publishes them for general use.
These jobs are
processed within the transactional components of the City's
enterprise GIS. From the transactional DBMS, infrastructure
components are warehoused out to a variety of specialized
users.
|
