Before collecting track measurement data for a new territory, a database must be prepared. If your organization collects data using the Rangecam Field System, two copies of the database are required: one for the computer on the data collection vehicle, and one for the office computer where the data will be post-processed and edited. These databases must be consistent in key respects. Try to be sure that the information in a new database is accurate before it is replicated for field and office. If field and office databases get out of sync, the inconsistencies must be corrected. It is important to establish company database management procedures to ensure that field and office databases are consistent and accurate, and to ensure that any updates are done in parallel.
To start a new MS Access database, copy the files permrail.mdb and measrail.mdb, found in EXE\NEWDB under the folder in which Rangecam is installed, to a new folder, which you have created for your database. Do not alter the originals of these files! You will need to copy them in order to start each new database.
However, if you need to set up many databases you can eliminate repetitive work by creating one or more database templates. A template is a database that contains general information needed in many, or all, of the databases you will create. Examples of such general information include railroad name, rail classification information, track point types, and the picture icons used to represent track points in charts. Having created a template, you would use it rather than the database in EXE\NEWDB as the starting point for new production databases.
Before the first data collection run in a new territory, the database must be set up with all required divisions and subdivisions. The direction of increasing mileage for each subdivision must be entered correctly. This is required in order to correctly identify the left and right sides of the track, and accurately determine profile location. See Subdivision in the Reference chapter for details.
It is also important to determine the distance units used in the territory. Track locations are normally marked by mileposts, or Kilometer posts, or engineering stations. If in doubt, you should ascertain which system of distance units is used, and set the Distance Units option accordingly. Default setting is miles. It can be done from Rangecam menu of Profile Display Window selecting Options/CurveDistance Units/....
Next step is to determine Curve Cord Length. Default setting is 100 ft that works for users in USA, Canada, Brazil. Mexico users has to set it 20 m. It can be changed it from the menu of Profile Display Window selecting Options/Curve/Degree Chord Length/....
The rail types, or weights, which are thought to be in the territory, should also be imported. However, it is not a serious problem if some are missed before the first data collection run. If the field system encounters an unexpected type of rail, it will be unable to identify the rail and derive measurements from it. However, the profile data will still be collected and can be post-processed in the office after enabling the correct rail type.
If you plan to record curve locations and obstacles (crossings, switches, lubricators, etc.) you must also enter track segment and point types into the database. Like subdivisions, segment and point types must be entered into the database before it is replicated for field and office use.
After point types are set it is necessary to import pictures associated with bridges, lubricators, crossings and so on. Rangecam provides default set of this pictures.
Rangecam can classify rail profiles on the basis of wear limits. The simplest classification scheme distinguishes between rail that is worn beyond condemning limits and rail that is not. However, most railroads find it useful to employ several classifications reflecting degrees of wear. If rail classification criteria are known, it is a good idea to enter them in the database when it is first set up. Classification limits can easily be changed later.