Who writes the notes
The notes are written and published by Tan Solutions, the independent software studio that builds Rail Crossing Atlas. Each note carries the byline “By Tan Solutions”, the date it was published and the date it was last updated.
No note is paid for or sponsored. The notes describe what the federal records say. They never rank crossings or places, and they do not rate any crossing.
Where the figures come from
Every figure in a note names its source and the date it was read.
- Rail Crossing Atlas. Most counts come from Rail Crossing Atlas, which is built from the Federal Railroad Administration’s crossing inventory. The current figures are from the FRA inventory of 3 November 2026. The atlas explains its method on its about the data page.
- The FRA dataset. Some figures are read directly from the FRA’s Crossing Inventory Data, Current on data.transportation.gov. The note says when the dataset was read.
- The regulations. Reporting rules are summarized from the current text of the Code of Federal Regulations, read in the Cornell Legal Information Institute’s copy, such as 49 CFR Part 234, Subpart F. Each note gives the date it read each section.
- One file for the figures. The figures the notes use are kept in one data file with the date they were read, so a figure reads the same on every page where it appears.
How each note is checked
The site is built and checked by a script before every release. A release does not go out while any check fails.
- Every source a note lists is linked in its Sources section, with the date it was read.
- Each note has at least 1,000 words before its sources.
- Each note keeps to the studio’s wording rules: it describes records and does not judge or rank crossings.
- Each note shows its byline, its Published and Updated dates, and a link to this page.
- Every link inside the site must lead to a page that exists, and every link to another site must be on a reviewed list.
Corrections
If a note gets a fact, a figure or a rule wrong, email support@tansolutions.org with the note’s address and what you found. The privacy notice says what we keep when you write.
When the error is confirmed against the source, the note is corrected, its Updated date changes, and the correction is listed below with its date and what changed. A change that fixes only a typing slip changes the Updated date but is not listed.
Corrections log
- , Reading a U.S. railroad crossing record, field by field: the note said that train counts have no date of their own and are only as old as the record's revision date. That was wrong: Box II.2 of the form, Year of Train Count Data, records the year of the train count, and it is filled in on 186,889 of the 203,162 records for open crossings at track level (FRA dataset, data updated 12 November 2026, queried 13 November 2026). The note now says so and asks readers to check that year rather than the revision date.
Other changes to the notes
- : Four new notes were published: how train counts are reported, and why they can be old; what a DOT crossing number is, and how to find one; U.S. railroad crossings by railroad class; and Section 130 and the Railroad Crossing Elimination Program. Their figures come from the FRA dataset, data updated 12 November 2026, queried 13 November 2026.
- : Every note now shows the date it was published and the date it was last updated, and links to this page. The notes also have an Atom feed. No note text changed.
- : The first seven notes were published, each with its sources and the date its figures were read.
How often notes change
Notes are not refreshed on a schedule. Each one keeps the figures of the date it states, so a count can differ from the atlas on a later day. When a note’s text or figures change, its Updated date changes, and new figures carry the date they were read.