A: Our system provides a flexible structure where data administrators can define and maintain standards for classifying features and feature types. In the United States, our users have adopted the Spatial Data Standards for Facilities, Infrastructure and Environment (SDS/FIE) developed by US Army Corps of Engineers as the underlying standards. Data administrators can adopt any existing spatial data standards, and activate only the feature types and attributes which are needed.
A: Our spatial database design stores data in one location, where both CAD and GIS platforms can retrieve and use the data with guaranteed lossless conversion. While spatial and attribute data can be viewed and edited in both environment, our users prefer to use the CAD for spatial data creation and use the GIS platform for spatial analysis.
A: Our solution is built on an Oracle Spatial database, using Oracle spatial (MDSYS) open architecture format to allow future migration of the spatial data. Oracle's scalability, load balancing, and fail-safe features provide the necessary foundation for creating a single centralized database.
The database can be physically distributed across different sites to achieve ideal performance and reliability. Oracle's security features provides the ability to secure features classes based user's security assigned privileges.
In addition to Oracle database our solution also allows for file-based storage of data. The following formats are supported:
A: x-Spatial's database design (including data access middle tier) allows spatial data to be created and viewed on either CAD or GIS platform without any translation or conversion. Therefore, any data entered through AutoCAD is immediately available to ArcGIS users (via ArcSDE connection) for spatial analysis and/or presentation.
A: Features on the map can be located by browsing the map and selecting one or more features. Alternatively, users can search for features using any attribute value(s). Two levels are search are available:
Data on the features you have selected or found are shown in a tabular form, where "zoom to" button locates and displays the features on the map. Quick Search panel can be used for Google-like searches of any feature type.
A: Redlines (markups) can be created and shared in separate layers by all users, and are stored in a separate table. The redline management tool shows the owner and the date of last change as well as an explanation. All redlines can be loaded into AutoCAD directly, without any conversion; if required, they can also be classified using the UMS CAD module and saved as classified features.
A: When a user is editing a feature or its attributes a lock is placed on that feature preventing any other user from editing the same feature. If a user attempts to edit a feature which is being edited by another user, a "Record Locked" message is displayed showing who locked the record and when.
A: Our solution has built-in functionalities for data maintenance which allows saving of spatial data before performing any changes (this is an optional step). The spatial data is saved in a historical spatial data table which can be used to construct a time series showing the spatial changes in any given area and feature class.
A: Our solution's spatial data standard functionality makes it possible to classify all base map feature (roadways, building, curb lines, etc.). Typically the base map is classified using planimetric data from aerial photography, which can be displayed in a separate layer; other common image formats such as MrSID, ECW, TIFF are also supported.
A: Our Shutdown Notice extension lets users identify the valves that should be closed to shut down a segment of the system, to view disconnected segments of the network, and to trace flows through the network. This makes it easy to deal with leaks or breakage in the system that must be shut down quickly, and to prepare for planned maintenance.