 |
|
 |
Live Demo |
|
|
 |
Brochure |
|
|
 |
Screen Shot |
|
|
 |
PS.NET/CAD - Geo Integration | |||
| Geographic Integration |
|
|||
| The PS.NET Computer Aided Dispatch system was designed with the understanding that saving a life and ensuring officer safety may depend upon the accuracy and timeliness of information. The first step if knowing where to send help! Address Verification Screen Shot PS.NET/CAD automatially attempts to validate any location entered, and provides our exclusive “Any” location address verification sub-system. Input locations are automatically submitted for verification and results instantly returned to the operator. If the geofile gets a "hit" it will return police beats, fire response zones, and other data to assist in dispatching police units or fire apparatus. If it does not get a hit, it will return a list of "possible" locations for operator selection. Callers do not always know where they are when they need help. To alleviate this problem the PS.NET/ Advanced Mapping application can use any reported location for address verification. With the appropriate verification layers constructed, discreet addresses, common place names, intersections, mileposts, location aliases and Lat/Long location identifiers can be used to accurately locate an event location. Geo-Coder The Advanced Mapping System using a new geo-coder that runs directly against the map attribute data on the Map Application Server. The geo-coder supports point and segment polygon layers and a broad range of map attribute data definitions. The specific attribute fields used by the geo-coder are configurable without programming. The advanced geo-coder is odd/even and left/right aware and can place events on the correct side of the street. This handles, for example, situations where the streets centerline divides two response areas. The geo-coder has been optimized for the communications center. In all cases, it attempts to look for situations where ambiguity may exist in the response location, such as North/South and multiple streets with the same or similar name. These are optimizations that typically don’t exist in general purpose geo-coders intended for mass mailing address verifications and zip-code look-ups. |
||||
|
|
|
|
|
| Premise Information File Associated with the geofile is a premise information file. This file contains user defined information about a specific address or location. The premise records can be grouped into user defined categories and designated for a particular agency (police, fire or EMS). This file normally contains information on hazardous materials, medical conditions, registrants, etc. The premise file is searched automatically and information returned to the operator on each incident. The system also fuly supports the inclusion of other system objects linked t the premise records & associated with specific locations; i.e. photos, floor plans, and other image data that may be important to responders. Total Geo-Coding Integration Screen Shot The complete system geoCode is built and maintained in the system map. The Advanced Mapping System includes a geo-coder that runs directly against the map attribute data. The geo-coder supports point and segment polygon layers and a broad range of map attribute data definitions. The specific attribute fields used by the geo-coder are configurable without programming. GIS and Map Processing Screen Shot All GIS data in the Advanced Mapping System reside in the map files and is not duplicated in tabular database tables. This includes all definitions of segments (streets), points (buildings, public buildings, and structures), polygons (response areas, grids, zones, etc.) The single point of maintenance of the geo-files is the map data. ESRI or other standard products are used to maintain this data in batch, off-line mode. The CAD system can be updated with new map data files at any time. This is accomplished by simply copying the new map files to the CAD server and CAD workstations that have mapping enabled. The attribute data provided with the map files, related to any of the layers, is used as the basis for address verification. Address verification is done against addresses (point or polygon layers), common names, mileposts, or intersections; depending on the attribute data contained within the map files. The attribute fields used for verification in various layers are configurable in the system. If more than one layer or source is used for verification and multiple possible hits qualify for operator input, all possibles are returned to the operator for selection. One or more polygon layers are used for determination of response areas (run card areas, beats). The layer to be used for each agency type (law, fire, EMS, other) is configurable. The same layer can be used for all agencies. For more information please contact us at info@goeis.net or fill out our online form or give us a call toll free at 877.EISWARE (347-9273). |
||||
|
|
|
|
|
back to top 
