Naming Conventions
- Thread starter reddog_ut
- Start date
100000+ items on DLS and absolutely no meaningful way to locate any particular item. The lack of a consistant taxonomy results in a virtually useless search capability. Apparently content creators much prefer individualized naming schemes and skipping meta data that is optional over having a database that can facilitate search and retrieval. So, there ain't no rules. Feel free to call your content anything you like.
For what it's worth, I name junctions as to where they go - say, Hyde Pulp Mill Entry/Exit, Hereford Siding 1, that sort of thing. One word of caution, if you use the Replace Assets function on named objects the names aren't preserved, so only name things that won't be changed.
I know of no standard nomenclature used across prototype railroads to identify their turnouts. When you create a turnout, the program automatically assigns it a number based on a system I have been unable to decipher, much like DLS nomenclature.
I leave this number and add the frog number or a speed limit if the switch is freehand to indicate an appropriate speed through the diverging route. For example, "1105 #10" would indicate a switch assigned #1105 by the program, and that it has a #10 frog, suggesting a maximum speed through the diverging route of about 20mph. You might also give the switch a name if it leads into a major industry or a branch line. If this switch were leading onto the Spreckels Branch it might read "1105 #10 Spkl."
Remember the KISS principle. On my first few routes I tried to establish an elaborate coding system and quickly found it was cumbersome to use and contained information I really didn't need.
Bernie
I leave this number and add the frog number or a speed limit if the switch is freehand to indicate an appropriate speed through the diverging route. For example, "1105 #10" would indicate a switch assigned #1105 by the program, and that it has a #10 frog, suggesting a maximum speed through the diverging route of about 20mph. You might also give the switch a name if it leads into a major industry or a branch line. If this switch were leading onto the Spreckels Branch it might read "1105 #10 Spkl."Remember the KISS principle. On my first few routes I tried to establish an elaborate coding system and quickly found it was cumbersome to use and contained information I really didn't need.
Bernie
switch identification
I have two comments on switch identification, first my prototype experience and secondly my practice in Trainz.
When I worked as a fireman/brakeman for a small tourist railroad here in Maine, I found there was no standard for naming switches in a everyday manner. If a switch was specifically identified, in general a switch would be called by the track it served, or for the location it served. For example the switch for the "industry" track would be called the "industry" switch. The exception being passing sidings which would be identified by location and/or function, the switch for the "location" passing siding would be called by direction (North, East, South, West) followed by "location", for example "North location" or "South location run around". However this is for a small line with a small number of employees.
In Trainz, I use the keep it simple process, and only name switches that are tightly packed together such as in a yard. If I name a switch I name it according to its function or location. Here are some examples; "Wye North" for the north end of a wye on a North/South line, 'Wye Tail" for the tail track of the wye, "Yard 3N" for the north end of the third track in a yard, "EH" for an engine house lead, "Bay 2" for a second bay in an engine house, "Service" for the servicing area, and "Coal" or "Ash" for the sidings specific to coal supply and ash removal.
I hope some of this helps with your project.
I have two comments on switch identification, first my prototype experience and secondly my practice in Trainz.
When I worked as a fireman/brakeman for a small tourist railroad here in Maine, I found there was no standard for naming switches in a everyday manner. If a switch was specifically identified, in general a switch would be called by the track it served, or for the location it served. For example the switch for the "industry" track would be called the "industry" switch. The exception being passing sidings which would be identified by location and/or function, the switch for the "location" passing siding would be called by direction (North, East, South, West) followed by "location", for example "North location" or "South location run around". However this is for a small line with a small number of employees.
In Trainz, I use the keep it simple process, and only name switches that are tightly packed together such as in a yard. If I name a switch I name it according to its function or location. Here are some examples; "Wye North" for the north end of a wye on a North/South line, 'Wye Tail" for the tail track of the wye, "Yard 3N" for the north end of the third track in a yard, "EH" for an engine house lead, "Bay 2" for a second bay in an engine house, "Service" for the servicing area, and "Coal" or "Ash" for the sidings specific to coal supply and ash removal.
I hope some of this helps with your project.
I use about the same system, but with frequent abbreviations. Eastwood Wye switches become E-Wd Wye N and E-Wd Wye S, to give a random example. Basically, just use whatever names help you remember what the turnout is for as you approach it.
Apparently my "system" isn't too far off at least one prototype.
Claude
Apparently my "system" isn't too far off at least one prototype.
Claudefor me i worked out a system:
normaly(sidings, turnouts, etc...):
Location name, switch type, and #(I number switches from left to right)
Yard switches:
yard name, yard end(north, east, west, south etc..), and #
when making larger routes it helps to name switchs in a standard system to make it easyier to program automatic drivers, but it is just what i use
normaly(sidings, turnouts, etc...):
Location name, switch type, and #(I number switches from left to right)
Yard switches:
yard name, yard end(north, east, west, south etc..), and #
when making larger routes it helps to name switchs in a standard system to make it easyier to program automatic drivers, but it is just what i use
I try to give mine a location-specific name followed by an alpha-numeric tag because too many unique names gets confusing.... NewYard1A etc I wiil sometimes add a NorthSouthEastWest as well.
Signals I name numerically. Lately I have started using a milepost tag for signals - S102.35 is a signal at milepost 102.35 etc.
Whatever system you use one thing is important - NO SPACES!! Spaces in names will drive anybody trying to write a scenario nuts. If you simply must have a gap between words, use an underscore. It will appear as a 'space', but isn't!
No%20%spaces....
Andy
Signals I name numerically. Lately I have started using a milepost tag for signals - S102.35 is a signal at milepost 102.35 etc.
Whatever system you use one thing is important - NO SPACES!! Spaces in names will drive anybody trying to write a scenario nuts. If you simply must have a gap between words, use an underscore. It will appear as a 'space', but isn't!
No%20%spaces....
Andy