Question: InRoads seems case-sensitive in some places and not in others. Is it really this way?

Answer: Yes, it is. InRoads is case-sensitive in some areas and non-case-sensitive in others. Yet we are not aware of any place that documents where it is case-sensitive and where it is not. Some areas where InRoads is case-sensitive are: with regards to template layer naming, template names themselves, surfaces, geometry projects, horizontal alignments, vertical alignments and roadway definitions. This means that a typical section layer called “CL II AC” is not the same as “Cl II ac.” This is why it’s a good idea to create a template (or choose one that has already been developed); copy that template to another name; and then proceed to edit that template. This method helps maintain some consistent layer naming between templates during transitioning.

On the other hand, InRoads is not case-sensitive when it comes to creating TCs (transition control points used in template construction). Named symbologies created in the Symbology Manager, feature styles in the Feature Style Manager and preferences are also non-case-sensitive. For example, if a named symbology exists called “aaa” and another is created called “AAA,” the “aaa” will be overwritten resulting in “AAA.” If a style “AAA” exists and a new style called “aaa” is created, “AAA” is modified to reflect the “aaa” style (InRoads preferences react the same way as the feature styles).