This is a new dialog box that centralizes a lot of old features and adds a few new ones. Select Utilities / Database / Streets manager to open this dialog.
This dialog box is used to create and maintain a streets layout table. Use it to define all the streets in your jurisdiction, where they cross, and what direction they travel.
From this dialog, you can also add, remove and change streets.
Streets
| • | Add one: adds a single street as prompted for in a dialog box. |
| • | Add list: prompts for an ascii file containing a list of street names, one per line. |
| • | Cng one changes a single street name to another as prompted for in two dialog boxes. |
| • | Cng list: prompts for a street changes file. (described elsewhere in the manual) This new change streets function includes a "dry run" mode that displays the changes that will occur when the process runs for real. |
| • | Del one: prompts for a single street name to delete. If the name is not already in use in the database, it removes it. If it is in use, it suggests that you use change streets to change it to another name. |
| • | Del unused: removes all streets in the database that do not have an accident record that refers to them. Do not run this if you have a complete list of street for your jurisdiction in your database. It will empty many of the from the database! |
Street aliases
| • | Add one: prompts for a street and an alias,both names must already be in the database. From this point on, all intersection references to this street or its alias will include crashes that occurred on either street name. The street name on the actual records remain untouched. This feature should be used to identify that HWY 93 is the same as BROADWAY, for example. |
| • | Add list: prompts for the name of an ascii file that contains a list of aliases to add. Each line in the file should contain a list of street names seperated by commas. All the street names on each line will be considered aliases to each other. The primary street will be the first one on the line. The primary street is currently not treated differently except internally by the system. However, if you have a name that you consider to be the primary name, it is suggested that you make it the first name on the line. Future versions of the program may treat this street in a special way. |
| • | Del one: Prompts for a street name and makes it into a primary or "root" street. It will no longer be considered an alias to another street name. |
| • | Del all: Deletes all alias references in the database. Note that this does not delete any street names from the database, just the reference to their "root" street names. |
| • | Export streets. Produces a series of reports, or data files, that show the current street names and aliases in the system. This is the same function as Reports / Listings / Streets in database, and has been enhanced to support aliases. |
GIS aliases
| • | Add list: Adds a list of "search and replace" strings to the GIS processing engine. Each time a location is sent to ArcView from the high accident locations dialog box, the location is first passed through a sequence of change requests. The list contains a "from" and "to" string. This process does not change any data in any database. What it does is make sure that when ArcView is geocoding Central and HWY 93, that it knows to geocode Central and Broadway instead, because that's what's on the map. This is done by making a GIS alias of: |
HWY 93, BROADWAY.
| • | Del all: Deletes all GIS aliases in the system |
| • | Export GIS Aliases: Produces an ascii file of all current aliases in the system. This list can be re-imported at a later date, or used as a reference of what is in the system. |
