UtahRails.net

(This page printed from UtahRails.net, Copyright 2000-2016 Don Strack)

UtahRails.net Roster Page

Index For This Page

This page was last updated on June 13, 2015.

Utah Railroads

U.S. Steel in Utah -- Rosters of U.S. Steel's Geneva Works, and Ironton Works, including the later independent Geneva Steel.

Utah Copper -- A roster of all steam locomotives used by Utah Copper Co. in its Bingham Canyon Utah mine, including the company's common carrier, Bingham and Garfield.

Utah Railway Diesels - A roster of Utah Railway's diesel locomotives, including the Alcos, the SD45s, and the SD40s.

Utah Railway Steam -- A roster of Utah Railway's steam locomotives.

Kennecott Utah Copper -- A roster of Utah Copper and Kennecott Copper electric and diesel-electric locomotives used in the Bingham Canyon mine.

Utah Copper/Bingham & Garfield Railway -- A roster listing of the steam locomotives used in the Bingham Canyon mine.

UtahRails Locomotive Rosters -- Locomotive rosters (steam and diesel) for railroads that operate (operated) solely within Utah, including Bamberger Railroad and more recent railroads.

UtahRails Industrial Locomotive Rosters -- Locomotive rosters and information about rail-served industries in Utah that have their own locomotives, including U. S. Steel's Geneva plant.

D&RGW

Rio Grande Diesels -- A roster of all of D&RGW's diesel locomotives, 1941 to 2002. (no updates after 2002)

Union Pacific

Union Pacific Cabooses -- Roster listings and narrative histories of UP's wooden and steel cabooses.

Union Pacific Diesels -- A full and complete roster of Union Pacific's diesel locomotive fleet, from 1934 to 2009, including all merger partners. (no updates after May 2009)

Union Pacific Motor Cars -- A roster of UP's motor cars, including the McKeen motor cars, the EMC motor cars, the Brill motor cars, and the motor cars that UP itself built.

Union Pacific Passenger Cars -- A roster of UP's steel and Streamliner passenger cars, from the earliest Harriman-style arch-roofed cars delivered in 1909, to the newsest lightweight cars of 1964, to today's Heritage Fleet cars, including UP's Heritage fleet water cars.

Union Pacific Roadway Equipment -- Roster listings of former passenger cars assigned to UP's 900000 series Roadway (maintenance of way) numbers.

Union Pacific Steam Locomotives -- A full and complete roster of Union Pacific's steam locomotives from 1864-1962.

Other Rosters

Chicago and North Western Railway -- A roster of C&NW diesel locomotives from 1926 to 1995, when C&NW was merged with UP.

Roster Style and Format

A question about roster style and format:

I recently upgraded some software to Microsoft Office which includes Access and Excel. It is time to move my MRL roster from the old Radio Shack TRS-80 4p to the real world of Windows XP.

The question is about any 'standard' roster formats for Access or Excel. Does anyone know of a boilerplate template commonly used for rosters to allow greater interchangability? Lacking a set format, what common column headers are used to make the data easier to integrate with other personal formats?

I also have Lotus Smart Suite available to me and could use the database in that program instead of the Office option.

Mr. Ardinger, Mr. Strack what works best in your experience? How well does Access work with dBase based rosters? Is there an easy way to attach photo thumbnails to a roster entry? Can the finished roster be posted to a web page with links to photos?

I did my first locomotive roster in January 1973. It covered the diesel and electric locomotives of Kennecott's Utah Copper Division. It was done on a regular typewriter. My first computer arrived in late 1986, but was characters on an amber screen. The software was Wordstar. Within a couple years I was using a Windows computer with WordPerfect. In late 1988 I met John Signor and he suggested that I start compiling my Utah railroads research into computer files, including the locomotive rosters.

From then on, all my rosters were formatted as tab-delimited columns in Wordperfect files. The first ones were what was used in Cockle's UP 1990 book. Next came the UP 1992 book from Hyrail, with the same file structure. By the time of the C&NW book in 1995, I had switched to Word and soon discovered that tables worked better than columns. For the files that were used for publication, I converted the tables to tab-delimited columns, but the actual roster files remained as tables.

When I did my first web rosters, it was by direct conversion of the tabled Word files, into tabled HTML files, although Word back then (and still to some degree today) tended to produce really bloated HTML files. I have since gained quite a bit of experience in manipulating HTML tables, especially using styles for the actual on-line presentation. Today, the actual roster data is in simple HTML rows and cells, with CSS styles governing how the data looks.

I have tried using formal databases on several occasions (including Access and FileMaker), starting way back in the late 1980s with DBASE II. But getting the reports to generate in a format usable in publishing was always the limiting factor. I always ended up exporting the report to a delimited text file and fixing it in either Wordperfect or Word. I have used Excel spreadsheets with some success, but always ended up exporting them into Word tables to be able to format the rosters into a usable format.

For anyone looking to start compiling rosters, I would recommend using tables in Word (or any other word processor). Using a database to too complex for the simple data we use in rail equipment rosters.

All my rosters today are done in HTML using Dreamweaver as the editor of choice. Editing a roster is very easy in Dreamweaver because it displays the HTML code as What-You-See-Is-What-You-Get (WYSIWYG) tables, and I simply edit the data in the tables. Take a look at the source code for any of the rosters at UtahRails.net and you will see "the man behind the curtain".

Using this combination of software makes immediate publishing very easy, and I don't have to hassle with page-count as a limiting factor. Publishing to the web removes all of the limitations that publishing to paper brings with it, such as lack of promotion, lack of distribution, and limited press runs. Of course, I have never seen my railroad interests as a potential revenue stream, which is good since there really isn't any money in it, except for about five guys nationwide. And for those guys, money is always their number one concern; money coming in and money going out.

(First published to the UtahRails.net blog on September 22, 2007, in answer to an email in January 2006.)

###