|
Present:
Peggi Knight
John Nervig
Joyce Emery
Bill Lutz
Richard Rothart
Dorothea Trotter
Dan Gieseman
Jack Laterell
Tim Strauss
Brad Estochen
Michael Pawlovich
Reg Souleyrette
Meeting Minutes:
Developed an agenda. The following topics were to be discussed:
- Iowa DOT Transportation Data Desktop Location Tool
- Population of the Database (including coding conventions)
from base records
- Data-flow diagram and understanding how and where the data
is going to be transferred
- Working with AMS
- User review of product
Transportation Data Location Tool
Developed using MDL (Microstation Development Language) by
Transportation Data to develop a prototype application for locating
points.
This tool will work if all three things are known:
- An X, Y location
- Case Number
- Route ID.
This allows linkage to each database that contains the information
for all objects of interest (base records and crash files).
Has features that are not in the scope of CTRE location project
(e.g., Location of the intersection of two streets and a link
to an Oracle database)
- This will facilitate use by the crash locators without
good knowledge of an area of a crash
This tool is not feasible for the laptops or local police department
offices. It requires expensive software and hardware and is
not useful for locating a small number of crashes.
CTRE Location Tool
To be used by all three types of users
- Mobile Units
- Police Offices
- Driver Services (at first)
- It may be decided that the MDL tool is better for the
Driver Service situation, this will be decided later this
year.
Will be developed for the field vehicles as well as the office.
Will be evaluated at a latter date.
Basic program will not have a lot of bells and whistles. Will
produce a route and an X, Y location of the crash.
Local users and State users may want different tools based
upon local knowledge about geographic areas. (Local users know
geographical area and need little assistance in locating area
vs. person in Des Moines trying to locate a crash)
Same application will be used in the field as well as in the
police department office. Extra features will be added based
upon time remaining in the contract.
Data Flow
Gain insight from the officers that will be using the system.
This will provide answers to what data they would like to see
assist them in locating the crash on the laptop electronic map.
Motor Vehicle Department will determine who these people are:
some possibilities include, but are not limited to, the ISU
Department of Public Safety, Charlie McClintock, and other selected
officers.
What data is needed for the Location tool?
- Reference Layers
- Roads
- linework
- ID fields
- street name
- others ??? (to be determined)
Possible crash report items to be added later
Surface Type
Type of Trafficway
Roadway Geometrics
Locality
Traffic Flow
Type of Trafficway
Options for handling such items
- Officer enters (as before)
- Include in the roadway file – brought up on screen
- To verify location
- Check data (with option to change data??? probably not)
- Deleted from crash form and entered during post-processing.
Additional Data elements
- as needed for research, analysis, and other statistical
determinations
- Possibly ADT, pavement width, etc…
Population of Database from base records
Not in scope of CTRE contract
May be useful to people within the DOT
There is a need to determine which items in crash report that
could potentially be attached to the linework used for the maps
in the officers vehicle (Save officers time and encourage use)
Driver Services, Transportation Data, and Safety to determine
which, if any, items in base records could be used to populate
the crash records through post-processing (To report at next
meeting)
Future Plan
AMS is planning to send a visual basic (VB) programmer to work
with Dan Gieseman in mid/late October
Next Meeting: During or After AMS VB programmer visits.
|