The information required to build the transportation maps is pulled from the Act Contact Management Database. Latitude and longitude is in the info tab.

ActDesktop

Additional information like stop name, stop type and the list of routes using that stop is in the info2 tab.

ActDesktop

A good argument could be made that stops, routes and locations should be encoded as separate tables, but doing that in Act has some challenges so we took an approach of encoding that information as a line in the SampTrans_Memo field.

Sample lines in the memo field would look like this:

on New Jersey run @ 5:20PM Th
on New Jersey run @ 9:50AM Su
on Southern PA run @ 0:30NM MTuW
on Boston Run @ 10:00PD MWF (prev day on the way out)

Three values are pulled from each line:

The route name is pulled via a regular expression pattern matching looking for text between the phrase on and the phrase run, for example:

on New Jersey run @ 5:20PM Th
on New Jersey run @ 9:50AM Su
on Southern PA run @ 0:30NM MTuW
on Boston Run @ 10:00PD MWF (prev day on the way out)

The route day is encoded after the time as a sequence of ids, valid values are Su M Tu W Th F Sa

on New Jersey run @ 5:20PM Th
on New Jersey run @ 9:50AM Su
on Southern PA run @ 0:30NM MTuW
on Boston Run @ 10:00PD MWF (prev day on the way out)

The route relative time is encoded between the word run and the day. Most of the stop times use AM and PM, but since some routes span midnight, AM and PM have been supplemented with two additional abbreviations to avoid splitting a route into pieces just because it finished 10 minutes after Midnight. on New Jersey run @ 5:20PM Th
on New Jersey run @ 9:50AM Su
on Southern PA run @ 0:30NM MTuW
on Boston Run @ 10:00PD MWF (prev day on the way out)