Skip to content
English
  • There are no suggestions because the search field is empty.

RailState New Features Highlight - June 11, 2025

Release notes June 11, 2025

We are excited to introduce several powerful new features in the RailState User Interface that we think you will find valuable.

Some of these enhancements are quite advanced, so we have included training videos to help you get up to speed - just follow the links below.

‼️BIG ENHANCEMENTS

  • Train ID Updates: Track trains with greater clarity and continuity. Our new 'Train Set' and 'Active Trip' functionality gives you deeper insight into train movements across multiple cycles - making it easier to follow and analyze operations over time.
  • Custom Regions: You can now define your own custom regions to simplify train monitoring. Group sensors into logical areas or measure traffic moving between regions for more tailored insights.    
  • New 'Traversal' Matching Sites on Charts: You can now quickly identify train counts moving between sensors (or new regions) with fewer clicks. The new 'Matching Sites' dropdown helps you get to unique RailState train counts faster and more intuitively. 
  • New 'Initial Train Trip Site' and 'Last Train Trip Site' Fields: You can now gain instant insight into train movement patterns with the new Initial and Last Train Site fields, which show you, at-a-glance, where RailState first and most recently detected that Train Trip ID.

❗SMALLER (BUT MIGHTY!) ENHANCEMENTS

  • More Container ID links: We have added additional hyperlinks throughout the UI to streamline navigation and make it easier for you to access intermodal container insights.
  • Chart Presentation Improvements: To make charts easier to understand and more intuitive, we have: set Direction at standard compass order (N, E, S, W); Train Route displays in logical site sequence; Chart titles and download names are now more descriptive; Group By options now build dynamically based on the order in which you select them.
  • Smarter Labels and Downloads: We have added some more informative labelling throughout the UI. Of particular note, we have now given report attachments and downloads descriptive and unique names including date/time run, and browser tabs notify you to what the search results are showing.
  • Calendar selection improvements: We have refined calendar date selection behavior - with some options now defaulting to include the current date, making it easier to get the data you need without the extra clicks.
  • New Resource: We added a new Data Dictionary to the Knowledge Base to help you better understand the fields and metrics used throught the RailState UI. Access it here 👉 RailState Data Dictionary

These updates are designed to give you deeper insights and faster access as you navigate the RailState platform. We are not done yet - more exciting features are on the way, and we will be sure to highlight them as they are released!

For more details and usage tips keep scrolling below.

As always, if you have feedback or would like a personalized feature review, don't hesitate to reach out to us at support+UI@RailState.com or Schedule an Overview.

 

RailState Product Team

Tip: For past release notes and answers to some frequently asked questions visit our searchable knowledge base: RailState Knowledge Base

Train ID Enhancements: 

To provide more context and continuity in tracking train movements, we hav introduced several important updates:

  • UPDATE Train ID → Train Trip ID: The field formerly known as Train ID is now labeled 'Train Trip ID' within the UI. It still represents the same concept - a unique identifier assigned by RailState to a train set that has been detected at one or more sightings - but now with a more descriptive name.
  • NEW Train Set ID: This new field is initialized with the original Train Trip ID, when the train is first detected. It remains consistent across multiple trips, allowing you to track a train across cycles - as long as its composition remains materially unchanged. 
  • NEW Active Train Trip: This field indicates whether a train (as identified by the Train Set ID) is on an active trip vs prior cycle. A train is no longer active if it has started a new trip or timed out due to inactivity.

❓Step through a refresher on adding/removing fields via the link: Customize your Results table

 

Introducing Custom Regions:

This is a feature we have been working on for a while - and are excited to now be able to share it with you!
 
With Custom Regions, you can define regions however you like. Whether it is a few sensors grouped together or an entire set of states or provinces, you are in control. 
 
Where this helps is you then get a count of activity in that region, without having to do complex comparisons between a number of separate queries. 
 
Once a region partition is created, you can then measure traffic moving between those regions.
 
❓Step through the training via this link: Creating a custom Region within RailState
 
You can access Regions via the new menu item as indicated below:
 
 
 
 Note: While any user can create regions, geographical restrictions tied to your subscription will apply. You will not be able to match traffic to regions outside your access permissions (where applicable). (In this case, further below we will highlight additional tools to help you segment traffic within your allowed geographical areas).  
 
 

'Traversal' Matching Sites:

We have made it easier to analyze train movements between sensors or regions - with fewer clicks and more precision.

When using Traversal Matching Sites, you can now choose if you want a data point for each time a train was detected, or more importantly, to get a unique count of trains that meet your criteria.

After defining your Route (or route segment) RailState will match for trains that meet all specified criteria, within your selected timeframe. The new Matching Sites dropdown streamlines this further by allowing you to select what point to plot on, helping you quickly identify unique train counts.

To access, while defining a route, click Set Train Route Details. Spend some time within help for a full explanation of the various matching methods. 

 
 

❓Step through the training via this link: Using Traversal Matching Sites within a Route Definition

Note: To be counted on a train route or region route match, RailState needs to have seen the same train in both specified points, and kept the same Train Trip ID.

New Summary Fields: Initial & Last Train Trip Site

We have added two new fields to the Trains tab to help you quickly understand train movement - without having to drill into Train Trip History.

By adding Initial Train Trip Site and Last Train Trip Site fields to your display, you can see in summary form where RailState first detected and last detected that Train Trip ID.

❓Step through a refresher on adding/removing fields via the link: Customize your Results table

Remember, these fields do not represent the train's true origin or final destination - only where RailState first and last observed it.

Accessing these new fields will allow you to segment traffic more easily, to know what came from or went to certain areas.

 
 
 Note: If your subscription includes geographical restrictions, you may see 'Restricted' populated in these fields when the detection event occurred outside your permitted geographic area. Even so, this still provides valuable insight when interpreted as follows:
  • Initial Train Trip Site = Restricted → Train originated outside your area
  • Last Train Trip Site = Restricted → Train exited your area
  • Both = Restricted → Train passed through your area
  • Neither = Restricted → Train remained within your area

We have additional functionality in this area currently in development - stay tuned for future updates!

 
 
 We look forward to your feedback and suggestions in general, or as it relates to these newly released and in-development features.