<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" version="2.0"><channel><title><![CDATA[Transitland — Interline Technologies]]></title><description><![CDATA[Occasional updates on Interline's Transitland data platform]]></description><link>https://www.interline.io/</link><image><url>https://www.interline.io/favicon.ico</url><title>Transitland — Interline Technologies</title><link>https://www.interline.io/</link></image><lastBuildDate>Thu, 23 Apr 2026 17:12:35 GMT</lastBuildDate><atom:link href="https://www.interline.io/blog/tag/transitland/rss.xml" rel="self" type="application/rss+xml"/><ttl>60</ttl><item><title><![CDATA[Riding transit to California's beaches]]></title><description><![CDATA[California Coastal Commission maps car parking at 1,600+ public access points. A spatial join with Transitland Datasets reveals which trailheads, surf spots, and overlooks can be reached by bus or rail.]]></description><link>https://www.interline.io/blog/riding-transit-to-californias-beaches/</link><guid isPermaLink="false">69e06b419f78c50001adb479</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Thu, 23 Apr 2026 17:12:35 GMT</pubDate><media:content url="https://www.interline.io/content/images/unsplash/photo-1746859782086-eafe092caa85.jpg" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/unsplash/photo-1746859782086-eafe092caa85.jpg" alt="Riding transit to California's beaches"><p>The California Coastal Commission recently updated <a href="https://www.coastal.ca.gov/YourCoast/#/map">YourCoast</a>, an interactive web map of over 1,600 public access points along the California coast. It's a genuinely useful tool: you can filter by restrooms, surfing, camping, dog-friendliness, stroller access, and more.</p><p>You can also filter by car parking.</p><figure><img src="https://www.interline.io/content/images/2026/04/yourmap-car-parking-amenity.png" alt="Screenshot of the YourCoast web map with &quot;Parking&quot; toggled on, showing clusters of access points up and down the California coast." width="2000" height="1269"></figure><p>What you <em>can't</em> filter by is public transit. The filter panel lists ten amenity types, but getting to the beach without a car isn't one of them. This is an unfortunate gap for an agency whose founding mandate under the landmark California Coastal Act is to &quot;maximize public access&quot; to the coast.</p><h2 id="californias-coastal-access-data-has-just-a-bit-of-transit">California's coastal access data has just a bit of transit</h2><p>The Commission publishes its access point data as an <a href="https://california-coastal-commission-open-data-1-3-coastalcomm.hub.arcgis.com/datasets/e45f130ce101423ea1de943a69445ece_0/explore">open dataset</a>, which is great. Digging into the raw CSV, there <em>is</em> a <code>PUBTRANSP</code> column, but out of 1,631 access points, only 39 have a value of &quot;Yes&quot; and 10 have &quot;No.&quot; The remaining 1,582 are blank.</p><p>That field is currently too sparse to be useful. So, let's enrich the Coastal Commission's public access points using Transitland Datasets.</p><h2 id="spatial-join-transitland-datasets-coastal-commission-open-data">Spatial join: Transitland Datasets + Coastal Commission open data</h2><p>Rather than calling an API for each of the 1,600+ access points, we'll use <a href="https://www.transit.land/documentation/datasets/data-dictionary">Transitland Datasets</a>, bulk exports of transit stop and route data that you can download and work with locally.</p><p>What makes Transitland Datasets especially useful here is the <strong>schedule summary data</strong>: for every stop, the dataset includes departure counts broken down by day of week. This isn't just a list of stop locations. Rather, it tells you <em>how much service actually runs</em> at each stop, every day of the week.</p><p>The plan:</p><ol><li><strong>Load the Transitland stops dataset</strong> and filter to California using the <code>adm1_iso</code> column</li><li><strong>Load the Coastal Commission's access points CSV</strong></li><li><strong>Search at two radii</strong>: a half mile (~805 m) for stops within walking distance, and three miles (~4.8 km) for stops that are in the approximate area but might require a hike or a bike.</li><li><strong>Aggregate the results</strong>, including which routes serve nearby stops and how often they run on weekdays and weekends</li></ol><h2 id="getting-the-data">Getting the data</h2><p>You'll need two files:</p><ul><li><strong>Transitland stops dataset (US)</strong>: Available through <a href="https://www.transit.land/datasets/">Transitland Datasets</a> (which are free for non-commercial use). The stop-oriented CSV includes stop locations, route names, agency names, vehicle types, and scheduled departure counts for each day of the week. See the <a href="https://www.transit.land/documentation/datasets/data-dictionary">data dictionary</a> for full column definitions.</li><li><strong>California Coastal Commission access points</strong>: Download from their <a href="https://california-coastal-commission-open-data-1-3-coastalcomm.hub.arcgis.com/datasets/e45f130ce101423ea1de943a69445ece_0/explore">ArcGIS Hub open data site</a> in CSV format.</li></ul><h2 id="python-script-using-geopandas-and-uv">Python script using GeoPandas and uv</h2><p>Here's a Python script that performs the analysis using <a href="https://geopandas.org/">GeoPandas</a> for the spatial join. It defines its dependencies inline, so if you have <a href="https://docs.astral.sh/uv/">uv</a> installed, you can run it directly (with no need to set up a virtualenv or perform a pip install):</p><pre><code><span><span>#!/usr/bin/env -S uv run --script
</span></span><span><span>#</span><span> /// script
</span></span><span><span># requires-python = &quot;&gt;=3.10&quot;
</span></span><span><span># dependencies = [&quot;geopandas&quot;, &quot;pandas&quot;]
</span></span><span><span>#</span><span> ///
</span></span><span><span>&quot;&quot;&quot;
</span></span><span><span>Find California coastal access points with nearby public transit
</span></span><span><span>by spatially joining Coastal Commission open data with a Transitland Dataset.
</span></span><span><span>
</span></span><span><span>Searches at two radii:
</span></span><span><span>  🚌  ½ mile:  walking distance to a transit stop
</span></span><span><span>  🔍  3 miles: transit in the area, worth planning a trip
</span></span><span><span>
</span></span><span><span>Usage:
</span></span><span><span>    uv run coastal_transit.py &lt;transitland-stops.csv&gt; &lt;AccessPoints.csv&gt;
</span></span><span><span>&quot;&quot;&quot;
</span></span><span><span>
</span></span><span><span>import sys
</span></span><span><span>import pandas as pd
</span></span><span><span>import geopandas as gpd
</span></span><span><span>
</span></span><span><span>WALK_M = 805   # ~0.5 miles
</span></span><span><span>NEAR_M = 4828  # ~3.0 miles
</span></span><span><span>
</span></span><span><span>def _clean(val):
</span></span><span><span>    &quot;&quot;&quot;Return empty string for NaN-ish values.&quot;&quot;&quot;
</span></span><span><span>    s = str(val or &quot;&quot;).strip()
</span></span><span><span>    return &quot;&quot; if s in (&quot;&quot;, &quot;nan&quot;, &quot;None&quot;) else s
</span></span><span><span>
</span></span><span><span>def load_stops(path):
</span></span><span><span>    &quot;&quot;&quot;Load Transitland stops CSV, filter to California, build route labels.&quot;&quot;&quot;
</span></span><span><span>    print(&quot;Loading Transitland stops...&quot;, file=sys.stderr)
</span></span><span><span>    df = pd.read_csv(path, dtype=str)
</span></span><span><span>    ca = df[df[&quot;adm1_iso&quot;] == &quot;US-CA&quot;].copy()
</span></span><span><span>    ca[&quot;stop_lat&quot;] = ca[&quot;stop_lat&quot;].astype(float)
</span></span><span><span>    ca[&quot;stop_lon&quot;] = ca[&quot;stop_lon&quot;].astype(float)
</span></span><span><span>    ca[&quot;tue&quot;] = pd.to_numeric(ca[&quot;departure_count_dow2&quot;], errors=&quot;coerce&quot;).fillna(0).astype(int)
</span></span><span><span>    ca[&quot;sat&quot;] = pd.to_numeric(ca[&quot;departure_count_dow6&quot;], errors=&quot;coerce&quot;).fillna(0).astype(int)
</span></span><span><span>    ca[&quot;sun&quot;] = pd.to_numeric(ca[&quot;departure_count_dow7&quot;], errors=&quot;coerce&quot;).fillna(0).astype(int)
</span></span><span><span>
</span></span><span><span>    def route_labels(row):
</span></span><span><span>        labels = []
</span></span><span><span>        for i in range(1, 6):
</span></span><span><span>            name = _clean(row.get(f&quot;route_short_name_{i}&quot;))
</span></span><span><span>            name = name or _clean(row.get(f&quot;route_long_name_{i}&quot;))
</span></span><span><span>            agency = _clean(row.get(f&quot;agency_name_{i}&quot;))
</span></span><span><span>            if name and agency:
</span></span><span><span>                labels.append(f&quot;{name} ({agency})&quot;)
</span></span><span><span>        return labels
</span></span><span><span>
</span></span><span><span>    ca[&quot;routes&quot;] = ca.apply(route_labels, axis=1)
</span></span><span><span>    print(f&quot;  {len(ca):,} California stops&quot;, file=sys.stderr)
</span></span><span><span>    return gpd.GeoDataFrame(
</span></span><span><span>        ca, geometry=gpd.points_from_xy(ca.stop_lon, ca.stop_lat), crs=&quot;EPSG:4326&quot;
</span></span><span><span>    )
</span></span><span><span>
</span></span><span><span>def load_access_points(path):
</span></span><span><span>    df = pd.read_csv(path, encoding=&quot;utf-8-sig&quot;)
</span></span><span><span>    df = df.dropna(subset=[&quot;LATITUDE&quot;, &quot;LONGITUDE&quot;])
</span></span><span><span>    print(f&quot;  {len(df):,} coastal access points&quot;, file=sys.stderr)
</span></span><span><span>    return gpd.GeoDataFrame(
</span></span><span><span>        df, geometry=gpd.points_from_xy(df.LONGITUDE, df.LATITUDE), crs=&quot;EPSG:4326&quot;
</span></span><span><span>    )
</span></span><span><span>
</span></span><span><span>def spatial_join(stops, pts, radius_m):
</span></span><span><span>    &quot;&quot;&quot;Buffer access points by radius_m and find all stops within.&quot;&quot;&quot;
</span></span><span><span>    buf = pts.copy()
</span></span><span><span>    buf[&quot;geometry&quot;] = buf.geometry.buffer(radius_m)
</span></span><span><span>    joined = gpd.sjoin(stops, buf, predicate=&quot;within&quot;)
</span></span><span><span>    return joined.groupby(&quot;index_right&quot;).apply(
</span></span><span><span>        lambda g: pd.Series({
</span></span><span><span>            &quot;stops&quot;: len(g),
</span></span><span><span>            &quot;tue&quot;: int(g[&quot;tue&quot;].sum()),
</span></span><span><span>            &quot;sat&quot;: int(g[&quot;sat&quot;].sum()),
</span></span><span><span>            &quot;sun&quot;: int(g[&quot;sun&quot;].sum()),
</span></span><span><span>            &quot;routes&quot;: list(dict.fromkeys(r for rs in g[&quot;routes&quot;] for r in rs)),
</span></span><span><span>        }),
</span></span><span><span>        include_groups=False,
</span></span><span><span>    )
</span></span><span><span>
</span></span><span><span>def main():
</span></span><span><span>    if len(sys.argv) &lt; 3:
</span></span><span><span>        print(&quot;Usage: uv run coastal_transit.py &lt;transitland-stops.csv&gt; &lt;AccessPoints.csv&gt;&quot;)
</span></span><span><span>        sys.exit(1)
</span></span><span><span>
</span></span><span><span>    stops = load_stops(sys.argv[1]).to_crs(&quot;EPSG:3310&quot;)
</span></span><span><span>    pts = load_access_points(sys.argv[2]).to_crs(&quot;EPSG:3310&quot;)
</span></span><span><span>
</span></span><span><span>    walk = spatial_join(stops, pts, WALK_M)
</span></span><span><span>    near = spatial_join(stops, pts, NEAR_M)
</span></span><span><span>
</span></span><span><span>    # Build result: prefer ½-mile data; fall back to 3-mile
</span></span><span><span>    rows = []
</span></span><span><span>    for idx, pt in pts.iterrows():
</span></span><span><span>        w = walk.loc[idx] if idx in walk.index else None
</span></span><span><span>        n = near.loc[idx] if idx in near.index else None
</span></span><span><span>
</span></span><span><span>        if w is not None and w[&quot;stops&quot;] &gt; 0:
</span></span><span><span>            tier, data = &quot;walk&quot;, w
</span></span><span><span>        elif n is not None and n[&quot;stops&quot;] &gt; 0:
</span></span><span><span>            tier, data = &quot;near&quot;, n
</span></span><span><span>        else:
</span></span><span><span>            tier, data = &quot;none&quot;, None
</span></span><span><span>
</span></span><span><span>        rows.append({
</span></span><span><span>            &quot;name&quot;: str(pt[&quot;Name&quot;])[:49],
</span></span><span><span>            &quot;county&quot;: pt[&quot;COUNTY&quot;],
</span></span><span><span>            &quot;tier&quot;: tier,
</span></span><span><span>            &quot;stops&quot;: int(data[&quot;stops&quot;]) if data is not None else 0,
</span></span><span><span>            &quot;tue&quot;: int(data[&quot;tue&quot;]) if data is not None else 0,
</span></span><span><span>            &quot;sat&quot;: int(data[&quot;sat&quot;]) if data is not None else 0,
</span></span><span><span>            &quot;sun&quot;: int(data[&quot;sun&quot;]) if data is not None else 0,
</span></span><span><span>            &quot;routes&quot;: data[&quot;routes&quot;] if data is not None else [],
</span></span><span><span>        })
</span></span><span><span>
</span></span><span><span>    result = pd.DataFrame(rows)
</span></span><span><span>
</span></span><span><span>    # Print table
</span></span><span><span>    print(f&quot;\n{'Name':50s} {'County':15s} {'':4s} {'Stops':&gt;5s} {'Tue':&gt;5s} {'Sat':&gt;5s} {'Sun':&gt;5s}  Routes&quot;)
</span></span><span><span>    print(&quot;=&quot; * 120)
</span></span><span><span>    for _, r in result.iterrows():
</span></span><span><span>        icon = {&quot;walk&quot;: &quot;🚌&quot;, &quot;near&quot;: &quot;🔍&quot;, &quot;none&quot;: &quot;  &quot;}[r[&quot;tier&quot;]]
</span></span><span><span>        route_str = &quot;, &quot;.join(r[&quot;routes&quot;][:4])
</span></span><span><span>        if len(r[&quot;routes&quot;]) &gt; 4:
</span></span><span><span>            route_str += f&quot;  (+{len(r['routes']) - 4} more)&quot;
</span></span><span><span>        print(
</span></span><span><span>            f&quot;{r['name']:50s} {r['county']:15s} {icon:4s} &quot;
</span></span><span><span>            f&quot;{r['stops']:&gt;5} {r['tue']:&gt;5} {r['sat']:&gt;5} {r['sun']:&gt;5}  &quot;
</span></span><span><span>            f&quot;{route_str or '-'}&quot;
</span></span><span><span>        )
</span></span><span><span>
</span></span><span><span>    walk_n = (result[&quot;tier&quot;] == &quot;walk&quot;).sum()
</span></span><span><span>    near_n = (result[&quot;tier&quot;] == &quot;near&quot;).sum()
</span></span><span><span>    none_n = (result[&quot;tier&quot;] == &quot;none&quot;).sum()
</span></span><span><span>    print(f&quot;\n{'='*60}&quot;)
</span></span><span><span>    print(f&quot;🚌 Within ½ mile (walkable):       {walk_n:&gt;5,}&quot;)
</span></span><span><span>    print(f&quot;🔍 Within 3 miles (hikeable):       {near_n:&gt;5,}&quot;)
</span></span><span><span>    print(f&quot;   No transit within 3 miles:      {none_n:&gt;5,}&quot;)
</span></span><span><span>    print(f&quot;   Total:                          {len(result):&gt;5,}&quot;)
</span></span><span><span>
</span></span><span><span>if __name__ == &quot;__main__&quot;:
</span></span><span><span>    main()
</span></span></code></pre><p>Run it:</p><pre><code><span><span>uv</span><span> run</span><span> coastal_transit.py</span><span> tl-dataset-US-stops.csv</span><span> AccessPoints.csv
</span></span></code></pre><p><code>uv</code> reads the inline dependency metadata, installs <code>geopandas</code> and <code>pandas</code> into an isolated environment, and runs the script. The spatial joins use <a href="https://epsg.io/3310">California Albers</a> (EPSG:3310) for accurate meter-based distance calculations.</p><h2 id="results-transit-frequency-to-reach-the-california-coast">Results: transit frequency to reach the California coast</h2><p>We ran that script against an April 2026 Transitland Dataset covering all US transit operators. Out of 1,625 coastal access points with coordinates:</p><ul><li>🚌 <strong>913</strong> have a transit stop within a half mile (more than half of all coastal access points in the state)</li><li>🔍 <strong>427</strong> more have transit within three miles (likely hikeable, assuming there are appropriate pedestrian shoulders or trails)</li><li>The remaining <strong>285</strong> have no transit within three miles</li></ul><p>Here's a sample of results across all three tiers:</p><table><thead><tr><th>Name</th><th>County</th><th>Tier</th><th>Stops</th><th>Tue</th><th>Sat</th><th>Sun</th><th>Routes</th></tr></thead><tbody><tr><td>Santa Monica State Beach</td><td>Los Angeles</td><td>🚌</td><td>10</td><td>732</td><td>497</td><td>497</td><td>2, 9, 43, 3 (Big Blue Bus)</td></tr><tr><td>Santa Cruz Beach Boardwalk</td><td>Santa Cruz</td><td>🚌</td><td>7</td><td>426</td><td>342</td><td>344</td><td>19B, 20, 19 (Santa Cruz METRO) +1 more</td></tr><tr><td>Monterey Bay Aquarium</td><td>Monterey</td><td>🚌</td><td>17</td><td>547</td><td>419</td><td>419</td><td>2, 1, A (Monterey-Salinas Transit) +2 more</td></tr><tr><td>Half Moon Bay State Beach</td><td>San Mateo</td><td>🔍</td><td>60</td><td>1,054</td><td>885</td><td>885</td><td>294, 15, 117, 18 (SamTrans)</td></tr><tr><td>Huntington City Beach</td><td>Orange</td><td>🚌</td><td>13</td><td>506</td><td>551</td><td>549</td><td>29, 29A, 25 (OCTA) +1 more</td></tr><tr><td>Coronado City Beach</td><td>San Diego</td><td>🚌</td><td>9</td><td>451</td><td>365</td><td>243</td><td>901, 904 (MTS)</td></tr><tr><td>Beach Front Park (Crescent City)</td><td>Del Norte</td><td>🚌</td><td>22</td><td>267</td><td>156</td><td>2</td><td>199, 1, 20, 2 (Redwood Coast Transit) +5 more</td></tr><tr><td>Fort Bragg Coastal Parkland</td><td>Mendocino</td><td>🚌</td><td>5</td><td>73</td><td>10</td><td>4</td><td>5, 65 (Mendocino Transit Authority)</td></tr><tr><td>Point Reyes Hostel</td><td>Marin</td><td>🔍</td><td>2</td><td>17</td><td>14</td><td>14</td><td>68 (Marin Transit)</td></tr><tr><td>Peter Strauss Ranch</td><td>Los Angeles</td><td>🔍</td><td>54</td><td>879</td><td>476</td><td>476</td><td>161 (Metro - Los Angeles), 423, 422 (LADOT), KS (Kanan Shuttle)</td></tr><tr><td>Pelican State Beach</td><td>Del Norte</td><td>🔍</td><td>4</td><td>12</td><td>8</td><td>0</td><td>20 (Redwood Coast Transit), Coastal Express (Curry Public Transit)</td></tr><tr><td>Pfeiffer Big Sur State Park</td><td>Monterey</td><td></td><td>0</td><td>0</td><td>0</td><td>0</td><td></td></tr></tbody></table><p>A few patterns to point out:</p><ul><li><strong>Departure counts tell a story that proximity alone can't.</strong> The table uses Tuesday as a representative weekday (as that day avoids most holidays). Santa Monica has 732 weekday and nearly 500 Sunday departures across 10 nearby stops, so you can show up any day without needing to closely follow a schedule. Fort Bragg has stops nearby, but 73 weekday departures drop to 10 on Saturday and 4 on Sunday. Crescent City's Beach Front Park has 267 weekday departures that drop to 156 on Saturday and just 2 on Sunday. Instead of asking <em>is there a bus stop nearby?</em> using Transitland Datasets, we can ask <em>is there a bus stop with service nearby?</em> (Note that these are raw departure counts summed across all nearby stops and both directions, so they represent <em>service intensity</em> in the area.)</li><li><strong>Some access points show zero transit even at three miles.</strong> This is genuinely the case for remote stretches like the Lost Coast and Big Sur. (In fairness, Highway 1 can be washed out by weather, so you may not be traveling to some of those coastal access points by private auto either!)</li><li><strong>The three-mile radius catches real transit corridors where the stop isn't right at the beach.</strong> Point Reyes Hostel, for example, has no stops within a half mile but 17 weekday and 14 Sunday departures within three miles. That's Marin Transit route 68 running along Sir Francis Drake Boulevard to Point Reyes Station village. In Southern California, Peter Strauss Ranch is another example: 879 weekday and 476 Sunday departures within three miles, from LA Metro 161 plus LADOT and Calabasas shuttles threading through the Santa Monica Mountains, but none of them drop you at the trailhead. The 🔍 tier flags these cases: transit exists in the corridor, and it's worth checking the <a href="https://www.transit.land/map">Transitland map</a> or using the Transitland Routing API to see if the full journey is actually feasible. (Note that some of these sites aren't literally right on the water. They may be on bluffs or in ocean-fronting preserves, so a hike is part of the point.)</li><li><strong>Half Moon Bay State Beach is a good case for the &quot;hikeable&quot; tier.</strong> It shows 60 stops and over 1,000 weekday departures within three miles (SamTrans routes 294, 15, 117, and 18) but the closest stops are on Highway 1, not at the beach entrance. A short walk or bike ride will take you from the bus to the beach. (That's a favorite spot of our Bay Area-based staff!)</li></ul><p>This is exactly the kind of analysis that the schedule summary columns in Transitland Datasets are designed for. Each stop row includes departure counts for every day of the week (<code>departure_count_dow1</code> through <code>departure_count_dow7</code>). Departure counts are also broken apart by direction, for finer-grained analysis, but that's beyond the scope of this blog post.</p><blockquote><p><strong>How does this compare to other open transit data?</strong> The <a href="https://www.interline.io/transitland/compare/us-national-transit-map/">USDOT National Transit Map</a> provides stop locations and route associations, and is a great resource for <em>visually</em> mapping where transit exists. Transitland Datasets are unique in summarizing and embedding temporal schedule data as well.</p></blockquote><h2 id="going-further-full-trip-planning-with-transitlands-routing-api">Going further: full trip planning with Transitland's routing API</h2><p>Finding nearby stops and counting departures tells you whether transit <em>exists</em> near a beach. It doesn't tell you whether you can actually <em>get there</em> from home in a reasonable amount of time.</p><p>For that, you need a transit routing engine. The <a href="https://www.interline.io/routing-platform/">Interline Routing Platform</a> provides transit routing powered by the same GTFS feeds behind Transitland, combined with OpenStreetMap's pedestrian network via the Valhalla engine. You could use it to compute actual travel times from residential areas to coastal access points, accounting for real schedules, transfers, and the final walking leg from the last stop to the sand.</p><p>Imagine a version of YourCoast where the filter panel included: <em>&quot;Reachable by transit from my location in under 60 minutes.&quot;</em> Or imagine an equivalent for your own state or country with a rich dataset of destinations, ready to reach via public transit. The data and APIs to build that exist today.</p><h2 id="resources">Resources</h2><ul><li><strong>Transitland Datasets</strong>, bulk CSV/GeoJSON exports of stops, routes, and schedules: <a href="https://www.transit.land/documentation/datasets/data-dictionary">transit.land/documentation/datasets/data-dictionary</a></li><li><strong>Transitland map</strong>, explore transit stops and routes visually: <a href="https://www.transit.land/map">transit.land/map</a></li><li><strong>Transitland REST API (stops endpoint)</strong>, query individual stops by location: <a href="https://www.transit.land/documentation/rest-api/stops">transit.land/documentation/rest-api/stops</a></li><li><strong>Transitland API key signup</strong>: <a href="https://www.transit.land/documentation/index#signing-up-for-an-api-key">transit.land/documentation#signing-up-for-an-api-key</a></li><li><strong>California Coastal Commission open data</strong>: <a href="https://california-coastal-commission-open-data-1-3-coastalcomm.hub.arcgis.com/datasets/e45f130ce101423ea1de943a69445ece_0/explore">ArcGIS Hub dataset</a></li><li><strong>YourCoast web map</strong>: <a href="https://www.coastal.ca.gov/YourCoast/#/map">coastal.ca.gov/YourCoast</a></li></ul><style>html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}</style>]]></content:encoded></item><item><title><![CDATA[Explore GTFS-Pathways station layouts using Transitland]]></title><description><![CDATA[Visualize subway station topologies. Inspect wheelchair-accessible navigation. Transitland's free GTFS-Pathways viewer is powered by Interline Station Editor.]]></description><link>https://www.interline.io/blog/explore-gtfs-pathways-station-layouts-using-transitland/</link><guid isPermaLink="false">69a8b8bb24682d0001f25803</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Thu, 05 Mar 2026 04:48:03 GMT</pubDate><media:content url="https://www.interline.io/content/images/unsplash/photo-1617727553230-35c143f84010.jpg" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/unsplash/photo-1617727553230-35c143f84010.jpg" alt="Explore GTFS-Pathways station layouts using Transitland"><p><a href="https://www.interline.io/saas-tools/station-editor/">Interline Station Editor</a> has helped transit agencies and consultants build GTFS-Pathways data for major transit hubs across North America. Now we're also bringing the core of that functionality to Transitland, so anyone can explore and inspect pathways data, wherever it exists and however it was originally created.</p><blockquote><p>GTFS-Pathways data is useful to provide wheelchair-accessible navigation and to enrich wayfinding instructions for riders using smartphone apps.</p><p>The GTFS-Pathways extension adds <code>pathways.txt</code> and <code>levels.txt</code> files, as well as stops with <code>location_type={3,4}</code> so GTFS can represent the physical layout of a transit station.</p><p>In contrast with other indoor mapping data formats, GTFS-Pathways represents a topological &quot;skeleton&quot; of how riders can travel through a multi-level subway, train, or bus station.</p></blockquote><p>Find a pathways-enabled station in Transitland and open the Transitland Pathways Explorer to use the interactive Map View tab to view the structure of multi-level stations. For example, <a href="https://www.transit.land/stops/s-dqcjr1jyg8-metrocenterredlinetrack1platform/pathways">WMATA's Metro Center</a> underground subway station:</p><figure><img src="https://www.interline.io/content/images/2026/03/CleanShot-2026-03-04-at-15.04.22.jpg" alt="" width="1200" height="1089"></figure><p>Use the Network Diagram tab to understand the topological organization of a station's levels and nodes. For example, the San Francisco Bay Area's <a href="https://www.transit.land/stops/s-9q8vzhbs2k-millbraebart/pathways">Millbrae Intermodal Station</a>, which is served by BART and Caltrain and bus agencies:</p><figure><img src="https://www.interline.io/content/images/2026/03/CleanShot-2026-03-04-at-20.23.16@2x.png" alt="" width="2000" height="1439"></figure><p>Use the Route Finder tab to test a journey through a station. For example, <a href="https://www.transit.land/stops/s-drt2yyxdb8-downtowncrossing/pathways">MBTA's Downtown Crossing</a> underground subway station:</p><figure><img src="https://www.interline.io/content/images/2026/03/image-2.png" alt="using Transitland to find a route through MBTA's Downtown Crossing subway station in Boston" width="1490" height="1814"></figure><p>The Validation tab provides a high-level summary of potential issues to debug and improve within a station's GTFS-Pathways data.</p><blockquote><p>The Transitland Pathways Explorer is great for understanding what's publicly available. When you need to build it, fix it, or validate it to detailed production standards, that's what <a href="https://www.interline.io/saas-tools/station-editor/">Interline Station Editor</a> is for.</p></blockquote><p>To find pathways-enabled stations, use the Transitland global transit map and look for the notice that &quot;<em>Station pathway points are in view</em>&quot;</p><figure><img src="https://www.interline.io/content/images/2026/03/CleanShot-2026-03-04-at-15.12.40@2x.png" alt="" width="2000" height="1463"></figure><p>Click on (or near) a relevant stop point to view the stop details, and to then open the Transitland Pathways Explorer:</p><figure><img src="https://www.interline.io/content/images/2026/03/CleanShot-2026-03-04-at-16.00.08@2x.png" alt="" width="1828" height="1084"></figure><p>Transitland Pathways Explorer is available to all registered Transitland users, including those on the free plan.</p><p>As more transit operators publish GTFS-Pathways data in their feeds, we look forward to this functionality being even more widely useful.</p>]]></content:encoded></item><item><title><![CDATA[Same data, different zip: How to identify unique GTFS feed versions]]></title><description><![CDATA[Standard zip hashes are unreliable for GTFS versioning due to variable metadata. Learn to use content-aware checksums to accurately identify unique transit datasets.]]></description><link>https://www.interline.io/blog/gtfs-checksum-versioning/</link><guid isPermaLink="false">698cc3c44b4f20000160b769</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Wed, 11 Feb 2026 22:45:59 GMT</pubDate><media:content url="https://www.interline.io/content/images/unsplash/photo-1531376653594-e9bcf0f0c65b.jpg" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/unsplash/photo-1531376653594-e9bcf0f0c65b.jpg" alt="photograph of overlapping zippers (as a metaphor for different zip archives)"><p>If you've ever downloaded a GTFS feed twice from the same URL and gotten two different zip files, you've encountered a surprisingly common problem in the transit data ecosystem. The data inside hasn't changed (the same stops, routes, and schedules) but the zip archive itself is different. Maybe the server regenerated it dynamically. Maybe the compression level changed. Maybe the file timestamps inside the archive shifted by a second.</p><p>For Transitland, which archives and imports <a href="https://www.transit.land/feeds">thousands of GTFS feeds</a> from around the world, this matters. We need to know: <em>has this feed actually changed, or is it just the same data in a new wrapper?</em></p><p>The answer lies in how we calculate checksums — and you can use the same tools we do.</p><h2 id="the-problem-with-hashing-zip-files">The problem with hashing zip files</h2><p>The naive approach to detecting changes is straightforward: compute a <a href="https://en.wikipedia.org/wiki/SHA-1">SHA1 hash</a> of the zip file and compare it to what you had before. If the hashes differ, something changed.</p><p>But zip archives are containers, and containers have metadata. A zip file's checksum can change for reasons that have nothing to do with the transit data inside:</p><ul><li><strong>Dynamic generation</strong>: Some transit agencies serve GTFS through vendor platforms that create the zip on the fly for each download. Same data, different zip bytes every time.</li><li><strong>Compression differences</strong>: Repackaging a zip with a different compression level produces a different file.</li><li><strong>Timestamps and ordering</strong>: The internal file modification times and the order of entries within the archive can vary between builds.</li></ul><p>If Transitland treated every new zip checksum as a new feed version, we'd be archiving and importing duplicate data constantly, wasting storage, processing time, and cluttering the archive with phantom &quot;updates.&quot;</p><h2 id="two-checksums-two-purposes">Two checksums, two purposes</h2><p>Transitland calculates two SHA1 checksums for every <a href="https://www.transit.land/documentation/concepts/static-gtfs-feed-versions">feed version</a>:</p><p><strong>Zip SHA1</strong>: a conventional hash of the entire zip archive file. This is fragile by nature (it changes whenever the packaging changes), but it's useful as a unique identifier for the exact file you downloaded. Transitland uses this as the primary key for feed versions in its <a href="https://www.transit.land/documentation/rest-api/feed_versions">REST API</a> and website URLs.</p><p><strong>Directory SHA1</strong>: a content-aware hash that looks <em>inside</em> the zip, directly at the GTFS CSV files. This is the one that solves the deduplication problem. Two zip files with completely different Zip SHA1 values will share the same Directory SHA1 if the actual transit data is identical.</p><p>When Transitland's <a href="https://www.transit.land/documentation/concepts/source-feeds">feed fetching service</a> downloads a new copy of a feed, it checks both hashes against its archive. If either one matches an existing feed version, it knows the data isn't new and skips the import.</p><h2 id="inside-the-directory-sha1">Inside the Directory SHA1</h2><p>The Directory SHA1 algorithm in <a href="https://www.transit.land/documentation/transitland-lib">transitland-lib</a> is deliberately simple, but each design choice is intentional:</p><ol><li><strong>Open the zip and enumerate its entries.</strong> We look at what's inside the archive, not the archive itself.</li><li><strong>Filter to GTFS content files.</strong> Only lowercase <code>.txt</code> files in the root directory of the archive are included — <code>stops.txt</code>, <code>routes.txt</code>, <code>trips.txt</code>, and so on. Directories, hidden files (starting with <code>.</code>), files in subdirectories, and non-<code>.txt</code> files are all excluded.</li><li><strong>Sort the files alphabetically by name.</strong> This neutralizes any variation in the order files appear within the zip.</li><li><strong>Stream each file's bytes sequentially into a single SHA1 hash.</strong> The contents of <code>agency.txt</code>, then <code>calendar.txt</code>, then <code>calendar_dates.txt</code>, and so on, all fed into one running hash computation.</li></ol><p>The result is a 40-character hex string that represents the actual transit data, independent of how it was packaged. Re-zip the same GTFS files with different compression? Same Directory SHA1. Download the feed again tomorrow from a server that regenerates the zip? Same Directory SHA1, as long as the CSV contents haven't changed.</p><p>Notably, the algorithm does <em>not</em> reorder rows within files or normalize field ordering within CSVs. It operates on the raw byte contents of each file. This is a pragmatic choice: it avoids the complexity and potential bugs of CSV parsing at the checksum stage, while still achieving the goal of being packaging-independent.</p><blockquote><p>The transitland-lib CLI does also include a <code>diff</code> command that can do deeper, row-level comparisons between two feed versions, but that's a topic for another blog post.</p></blockquote><h2 id="try-it-yourself">Try it yourself</h2><p>The <code>transitland</code> command-line interface includes a <code>checksum</code> command that computes both hashes for any GTFS feed on your local machine.</p><p>Here's a real example using <a href="https://www.transit.land/feeds/f-drt-mbta/">MBTA's static feed</a>:</p><pre><code>$ wget https://cdn.mbta.com/MBTA_GTFS.zip
$ transitland checksum MBTA_GTFS.zip

Zip SHA1 (archive file): 6d768217c1e441cc13f313595856669d4c24c013
Directory SHA1 (feed contents): 34e21ac222935b7acdd395e5f6b36dc996da0d60
Find via Transitland website: https://www.transit.land/feed-versions/6d768217c1e441cc13f313595856669d4c24c013
Find via Transitland REST API: https://transit.land/api/v2/rest/feed_versions/6d768217c1e441cc13f313595856669d4c24c013?apikey=YOUR_API_KEY
</code></pre><p>The CLI gives you everything you need to cross-reference the local file against Transitland's global archive. Click the website link and you'll land directly on <a href="https://www.transit.land/feed-versions/6d768217c1e441cc13f313595856669d4c24c013">that feed version's page</a>, where you can see when it was fetched, what date range it covers, and explore its stops, routes, and agencies. The CLI's output can also be compared against another zip file you have locally.</p><p>This is useful in a few scenarios:</p><ul><li><strong>Agency staff</strong> can verify that Transitland has successfully fetched and archived their latest feed. Publish an update, wait for the next fetch cycle, then run <code>transitland checksum</code> on the same file and check if the Zip SHA1 appears in the archive.</li><li><strong>Developers</strong> responsible for legacy systems can ensure their pipelines are only emitting new GTFS feeds when the Directory SHA1 changes from its previously cached value.</li><li><strong>Analysts</strong> who download GTFS feeds directly from agencies can confirm they're working with the same version that Transitland has processed, which is helpful when comparing your analysis against Transitland's API results.</li><li><strong>Researchers</strong> working with historical GTFS data can use the checksum to determine exactly which feed version in Transitland corresponds to a file they've been handed. They can then use Transitland's additional metadata to inform their research.</li></ul><h2 id="installing-the-cli">Installing the CLI</h2><p>The <code>transitland</code> CLI is a single binary. You can:</p><ul><li>download it prebuilt for Linux and macOS from the <a href="https://github.com/interline-io/transitland-lib/releases">transitland-lib releases page</a> on GitHub</li><li>install it <a href="https://github.com/interline-io/homebrew-transitland-lib">using the Homebrew package manager</a></li><li>build it from Golang source if you prefer</li></ul><h2 id="a-small-detail-that-makes-a-big-difference">A small detail that makes a big difference</h2><p>Checksumming transit feeds might sound like plumbing. It's the kind of plumbing that makes a global transit data platform reliable. Without content-aware hashing, Transitland would either miss real updates (by relying on unreliable zip hashes) or drown in false positives (by treating every re-downloaded zip as new data).</p><p>The <code>transitland checksum</code> command also puts this capability in your hands. Whether you're an agency verifying that your feed updates are being picked up, or an analyst reconciling local data against the Transitland archive, you can generate the same fingerprints that Transitland uses internally.</p><p>If you have questions or want to explore further, check out the <a href="https://www.transit.land/documentation/">Transitland documentation</a> or browse the <a href="https://github.com/interline-io/transitland-lib">transitland-lib source code</a> on GitHub.</p>]]></content:encoded></item><item><title><![CDATA[Easily inspect GTFS Realtime using Transitland's website or API]]></title><description><![CDATA[Web browsers and text editors can't open GTFS Realtime. But with Transitland, you now can.]]></description><link>https://www.interline.io/blog/easily-inspect-gtfs-realtime-using-transitlands-website-or-api/</link><guid isPermaLink="false">687e9eed48c47c000167b980</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Tue, 22 Jul 2025 03:45:24 GMT</pubDate><media:content url="https://www.interline.io/content/images/2025/07/image-2.png" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/2025/07/image-2.png" alt="Viewing a GTFS Realtime feed as human-readable JSON using the Transitland website"><p>GTFS Realtime feeds provide live updates about vehicle positions, trip updates, and service alerts, but they can be challenging to inspect due to their Protocol Buffer format. This binary <a href="https://protobuf.dev/">format</a> is highly efficient for data transmission but requires special tools to decode. You can't just open it up in a text editor or a web browser.</p><p>Transitland now offers two convenient ways to parse and view GTFS Realtime feeds: through our web interface and via our REST API.</p><h2 id="inspecting-gtfs-realtime-on-the-transitland-website">Inspecting GTFS Realtime on the Transitland Website</h2><p>The Transitland website now provides an intuitive interface for viewing GTFS Realtime data directly in your browser. Let's walk through how to use this feature using Portland TriMet's GTFS Realtime feed as an example.</p><h3 id="finding-a-gtfs-realtime-feed">Finding a GTFS Realtime Feed</h3><ol><li>Navigate to <a href="https://www.transit.land/">www.transit.land</a> and go to the &quot;Source Feeds&quot; section</li><li>Look for feeds with the GTFS Realtime format designation</li><li>Click on any GTFS Realtime feed to view its details</li></ol><figure><img src="https://www.interline.io/content/images/2025/07/image-1.png" alt="browsing Transitland website for GTFS Realtime feeds" width="2000" height="1361"></figure><p>For this example, we'll use the TriMet GTFS Realtime feed at <a href="https://www.transit.land/feeds/f-trimet~rt">https://www.transit.land/feeds/f-trimet~rt</a></p><h3 id="viewing-real-time-data">Viewing Real-time Data</h3><p>On the feed page, you'll see comprehensive information about the feed including:</p><ul><li><strong>Feed identification</strong>: Onestop ID and source URLs</li><li><strong>Last fetch time</strong>: When the data was most recently updated (Transitland typically refreshes GTFS Realtime feeds once per minute)</li><li><strong>Authorization details</strong>: Any required API keys or parameters (Transitland keeps its own credentials private; to access the source feed directly, you'll have to sign up for your own credentials)</li></ul><blockquote><p><a href="https://www.transit.land/documentation/concepts/source-feeds/#gtfs-realtime-feed-fetching-and-caching">Learn more</a> about how Transitland caches GTFS Realtime feeds.</p></blockquote><p>The most exciting feature is the &quot;GTFS Realtime Feed Messages&quot; section, which provides three ways to inspect each type of real-time data:</p><figure><img src="https://www.interline.io/content/images/2025/07/CleanShot-2025-07-21-at-13.25.59.png" alt="screenshot of https://www.transit.land/feeds/f-trimet~rt" width="2000" height="2743"></figure><h3 id="interactive-json-viewer">Interactive JSON Viewer</h3><p>When you click &quot;View as JSON&quot; for any real-time endpoint, a modal window opens showing:</p><ul><li><strong>Last fetched timestamp</strong>: When the data was fetched from the source feed</li><li><strong>Formatted JSON data</strong>: Human-readable data structure. Click the caret arrows to open or close nested sections.</li><li><strong>Download options</strong>: Buttons to download the entire JSON document or copy it to clipboard</li></ul><figure><img src="https://www.interline.io/content/images/2025/07/image.png" alt="Interactive JSON viewer for TriMet GTFS Realtime vehicle positions feed" width="2000" height="1799"></figure><p>The JSON viewer displays the data in a structured format that's easy to read and understand, showing all the fields defined in the <a href="https://gtfs.org/documentation/realtime/reference/">GTFS Realtime specification</a>.</p><h2 id="accessing-gtfs-realtime-via-the-transitland-api">Accessing GTFS Realtime via the Transitland API</h2><p>For programmatic access or integration into your applications, the Transitland REST API provides direct access to Transitland's cached GTFS Realtime data.</p><h3 id="api-endpoint-structure">API Endpoint Structure</h3><p>The API uses the following endpoint pattern:</p><pre><code>GET https://transit.land/api/v2/rest/feeds/{feed_key}/download_latest_rt/{rt_type}.{format}
</code></pre><p>Where:</p><ul><li><code>{feed_key}</code> is the feed's Onestop ID (e.g., <code>f-trimet~rt</code>)</li><li><code>{rt_type}</code> is one of:
<ul><li><code>vehicle_positions</code> for vehicle location data</li><li><code>trip_updates</code> for arrival/departure time changes</li><li><code>alerts</code> for service disruptions</li></ul></li><li><code>{format}</code> is either <code>json</code> or <code>pb</code> (raw Protocol Buffers)</li></ul><h3 id="example-api-call">Example API Call</h3><p>To access TriMet's cached GTFS Realtime service alerts through the Transitland REST API in JSON format:</p><pre><code><span><span>curl</span><span> https://transit.land/api/v2/rest/feeds/f-trimet~rt/download_latest_rt/alerts.json?apikey=YOUR_API_KEY
</span></span></code></pre><h3 id="api-response-format">API Response Format</h3><p>When requesting JSON format, the API returns data in the standard GTFS Realtime JSON structure. For example:</p><pre><code><span><span>{
</span></span><span><span>  &quot;header&quot;</span><span>: {
</span></span><span><span>    &quot;gtfsRealtimeVersion&quot;</span><span>: </span><span>&quot;2.0&quot;</span><span>,
</span></span><span><span>    &quot;incrementality&quot;</span><span>: </span><span>&quot;FULL_DATASET&quot;</span><span>,
</span></span><span><span>    &quot;timestamp&quot;</span><span>: </span><span>&quot;1753153829&quot;
</span></span><span><span>  },
</span></span><span><span>  &quot;entity&quot;</span><span>: [
</span></span><span><span>    {
</span></span><span><span>      &quot;alert&quot;</span><span>: {
</span></span><span><span>        &quot;activePeriod&quot;</span><span>: [
</span></span><span><span>          {
</span></span><span><span>            &quot;start&quot;</span><span>: </span><span>&quot;1675370449&quot;
</span></span><span><span>          }
</span></span><span><span>        ],
</span></span><span><span>        &quot;descriptionText&quot;</span><span>: {
</span></span><span><span>          &quot;translation&quot;</span><span>: [
</span></span><span><span>            {
</span></span><span><span>              &quot;text&quot;</span><span>: </span><span>&quot;No service to the eastbound stop at SW Tualatin-Sherwood Rd &amp; Langer Farms (Stop ID 13837) due to Tualatin-Sherwood Rd project.&quot;
</span></span><span><span>            }
</span></span><span><span>          ]
</span></span><span><span>        },
</span></span><span><span>        &quot;headerText&quot;</span><span>: {
</span></span><span><span>          &quot;translation&quot;</span><span>: [
</span></span><span><span>            {
</span></span><span><span>              &quot;text&quot;</span><span>: </span><span>&quot;&quot;
</span></span><span><span>            }
</span></span><span><span>          ]
</span></span><span><span>        },
</span></span><span><span>        &quot;informedEntity&quot;</span><span>: [
</span></span><span><span>          {
</span></span><span><span>            &quot;routeId&quot;</span><span>: </span><span>&quot;97&quot;
</span></span><span><span>          },
</span></span><span><span>          {
</span></span><span><span>            &quot;stopId&quot;</span><span>: </span><span>&quot;13837&quot;
</span></span><span><span>          }
</span></span><span><span>        ],
</span></span><span><span>        &quot;url&quot;</span><span>: {
</span></span><span><span>          &quot;translation&quot;</span><span>: [
</span></span><span><span>            {
</span></span><span><span>              &quot;text&quot;</span><span>: </span><span>&quot;https://trimet.org/alerts/&quot;
</span></span><span><span>            }
</span></span><span><span>          ]
</span></span><span><span>        }
</span></span><span><span>      },
</span></span><span><span>      &quot;id&quot;</span><span>: </span><span>&quot;164849&quot;
</span></span><span><span>    }
</span></span></code></pre><h3 id="finding-available-gtfs-realtime-feeds">Finding Available GTFS Realtime Feeds</h3><p>To discover available GTFS Realtime feeds, use the <a href="https://www.transit.land/documentation/rest-api/feeds">feeds REST endpoint</a> with the <code>spec=gtfs-rt</code> parameter:</p><pre><code><span><span>curl</span><span> https://transit.land/api/v2/rest/feeds?spec=gtfs-rt</span><span>&amp;apikey</span><span>=</span><span>YOUR_API_KEY
</span></span></code></pre><p>You can also <a href="https://www.transit.land/documentation/rest-api/feeds">filter by other criteria</a> to find feeds relevant to your needs.</p><h2 id="benefits-of-using-transitland-for-gtfs-realtime">Benefits of Using Transitland for GTFS Realtime</h2><p>Transitland's website and API provide simplified access:</p><ul><li><strong>No Protocol Buffer tools required</strong>: View data directly in JSON format</li><li><strong>Real-time updates</strong>: Access the latest data as it becomes available</li><li><strong>Standardized interface</strong>: Consistent API across all feeds</li></ul><p>Transitland also offers comprehensive coverage:</p><ul><li><strong>Multiple feed types</strong>: Vehicle positions, trip updates, and service alerts (when available)</li><li><strong>Global coverage</strong>: Access feeds from transit agencies worldwide</li></ul><blockquote><p>Don't see a GTFS Realtime feed available through Transitland? Help <a href="https://www.transit.land/documentation/atlas">add it the Transitland Atlas feed registry</a>.</p><p>Alternatively, transit agency staff are welcome to email us GTFS Realtime feed URLs at <a href="mailto:hello@transit.land">hello@transit.land</a>. You may also share auth credentials, which we will keep private.</p></blockquote><blockquote><p>Finally, please note that some agencies do not allow Transitland to redistribute their feeds in full. In these cases, GTFS Realtime feed export is not allowed through either the Transitland API or website.</p></blockquote><h2 id="getting-started">Getting Started</h2><ul><li><strong>Sign up</strong>: Inspecting GTFS Realtime feeds requires a <a href="https://app.interline.io/">free Interline account</a> (which helps us to limit concurrent requests and ensure prompt responses).</li><li><strong>For web browsing</strong>: Visit <a href="https://www.transit.land/">www.transit.land</a> and explore the Source Feeds section.</li><li><strong>For API access</strong>: Get an API key by following the <a href="https://www.transit.land/documentation/index#signing-up-for-an-api-key">sign-up instructions</a>.</li></ul><p>Whether you're an analyst learning your way around GTFS data or an agency staffer trying to quickly debug your own systems, Transitland provides the tools you need to automatically parse and read GTFS Realtime feeds. The combination of our web interface and REST API makes it simple to explore real-time transit data without the complexity of Protocol Buffer conversion tools.</p><style>html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}</style>]]></content:encoded></item><item><title><![CDATA[Announcing transitland-lib v1.0.0]]></title><description><![CDATA[We're pleased to announce the release of transitland-lib version 1.0.0. This software library, written in the Go programming language, is the foundation of the Transitland platform and integral to a growing range of purpose-built applications.]]></description><link>https://www.interline.io/blog/announcing-transitland-lib-v1-0-0/</link><guid isPermaLink="false">67d3036abc10db0001cc01b7</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Fri, 28 Mar 2025 19:56:25 GMT</pubDate><media:content url="https://www.interline.io/content/images/2025/03/CleanShot-2025-03-26-at-13.52.03-1.jpg" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/2025/03/CleanShot-2025-03-26-at-13.52.03-1.jpg" alt="Announcing transitland-lib v1.0.0"><p>We're pleased to announce the release of transitland-lib version 1.0.0. This software library, written in the <a href="https://go.dev/">Go programming language</a>, is the foundation of the Transitland platform and integral to a growing range of purpose-built applications.</p><h2 id="from-experiment-to-production">From experiment to production</h2><p>In 2019, the Interline team began exploring how Go's performance characteristics could serve as a new foundation for <a href="https://www.interline.io/blog/tlv2/">Transitland's v2 platform</a>. The goal was simple: process the largest and most complex GTFS feeds faster and more efficiently.</p><p>After years of iteration and real-world testing, with hundreds of thousands of GTFS feeds processed, we've finally tagged a v1.0.0. This release represents a stable production-ready library that powers critical transit data systems.</p><h2 id="real-world-uses">Real-world uses</h2><p>transitland-lib can be found within many transit data platforms operated by Interline:</p><ul><li>The canonical Transitland deployment at <a href="https://www.transit.land/">www.transit.land</a></li><li><a href="https://www.interline.io/blog/tag/511-sf-bay-regional-feed/">MTC's 511 Regional Feed for the San Francisco Bay Area</a></li><li>A new transit analysis tool for public agencies across the states of Washington, Oregon, and California</li><li>A routing engine deployment for a business client that covers an entire country</li><li>The new <a href="https://www.transit.land/documentation/routing-platform/transit-otp/">Transitland Routing API</a> beta that currently provides journey planning across the entire United States</li></ul><p>This component is also in use by other organizations. For example, Portland TriMet uses transitland-lib to efficiently clip <a href="https://www.transit.land/feeds/f-9-amtrak~amtrakcalifornia~amtrakcharteredvehicle">Amtrak's country-wide feed</a> to create a focused feed to ingest into their own <a href="https://trimet.org/home/planner/">OpenTripPlanner routing engine for the greater Portland, Oregon, region</a>.</p><h2 id="built-for-handling-many-feeds">Built for handling many feeds</h2><p>transitland-lib provides:</p><ul><li>Fast feed processing for both static GTFS and GTFS Realtime</li><li>Memory-efficient operations</li><li>Concurrent data handling</li><li>Robust error handling</li><li>Defining multiple input feeds using the <a href="https://github.com/transitland/distributed-mobility-feed-registry">Distributed Mobility Feed Registry (DMFR) format</a></li></ul><h2 id="performance-in-action">Performance in action</h2><p>Let's look at one example of transitland-lib's capabilities to process and validate massive GTFS feeds. This demonstration covers Switzerland's entire transit network, one of the largest GTFS feeds in the world (<a href="https://www.transit.land/feeds/f-u0-switzerland">view on transit.land</a>):</p><pre><code><span><span>✗ transitland validate https://data.opentransportdata.swiss/en/dataset/timetable-2025-gtfs2020/permalink
</span></span></code></pre><figure><img src="https://www.interline.io/content/images/2025/03/CleanShot-2025-03-26-at-13.52.03.jpg" alt="" width="1200" height="884"></figure><p>In about one and a half minutes on a laptop, transitland-lib downloads and processes a GTFS feed including 460 separate agencies, over 90,000 stops, over 4,000 routes, over 1.2 million trips, and a complicated set of calendar and calendar date records.</p><p>The library's ability to handle such large datasets reliably makes it an ideal choice for processing national-scale transit feeds or creating regional subsets of larger networks.</p><h2 id="extensible-architecture">Extensible architecture</h2><p>transitland-lib's extension framework enables support for both standard GTFS and <a href="https://gtfs.org/community/extensions/overview/">experimental extensions</a>. This flexibility has been crucial for:</p><ul><li>Processing <a href="https://www.transitwiki.org/TransitWiki/images/e/e7/GTFS%2B_Additional_Files_Format_Ver_1.7.pdf">MTC GTFS+ files</a> for the SF Bay Regional Feed</li><li>Supporting <a href="https://www.interline.io/blog/mtc-regional-gtfs-feed-fares-updates/">GTFS Fares-v2</a> as it has iteratively evolved from proposal to adopted specification</li><li>Supporting the addition of <a href="https://www.interline.io/blog/mtc-regional-gtfs-feed-additions/#station-pathways-and-levels">GTFS Pathways</a> using <a href="https://www.interline.io/saas-tools/station-editor/">Interline's Station Editor</a></li></ul><p>We update transitland-lib to track the latest static GTFS and GTFS Realtime specifications. To check which version of the specifications you are using, simply run the <code>transitland version</code> command:</p><pre><code><span><span>✗ transitland version
</span></span><span><span>transitland-lib version: v1.0.0
</span></span><span><span>transitland-lib commit: https://github.com/interline-io/transitland-lib/commit/bae91cd7f32c67ffe89965cab3636e22ddbce817 (time: 2025-03-11T18:47:50Z)
</span></span><span><span>GTFS specification version: https://github.com/google/transit/blob/11a49075c1f50d0130b934833b7eeb3fe518961c/gtfs/spec/en/reference.md
</span></span><span><span>GTFS Realtime specification version: https://github.com/google/transit/blob/7b9f229dfa0b539c3fcf461986638890024feb06/gtfs-realtime/proto/gtfs-realtime.proto
</span></span></code></pre><h2 id="validation-and-best-practices">Validation and best practices</h2><p>GTFS feeds can be messy. Therefore, transitland-lib:</p><ul><li>Validates required fields and data types</li><li>Ensures referential integrity between files</li><li>Checks that feeds meet many of the <a href="https://gtfs.org/documentation/schedule/schedule-best-practices/">best practices</a></li><li>Also supports validating GTFS Realtime feeds</li></ul><p>With both static GTFS and GTFS Realtime processed using the same library, we're now able to put into ongoing production-scale use <a href="https://www.interline.io/blog/trb-transit-idea-gtfs-realtime-report/">Interline's previous research with University of South Florida into GTFS Realtime validation</a>.</p><blockquote><p>While transitland-lib implements many of the same validation and best practice rules as <a href="https://github.com/MobilityData/gtfs-validator">MobilityData's static GTFS validator</a>, the purposes and advantages of each library are distinct.</p><p>The MobilityData validator lends itself well to interactive use when people and organizations creating GTFS feeds want to check to ensure their static feed is ready for submission to a third-party consumer. The MobilityData validator outputs a report that is useful for reference and sharing.</p><p>In contrast, transitland-lib is designed to efficiently process many feeds, to serve as a component within production-scale processing pipelines, and to optionally validate GTFS Realtime endpoints with the context of a static GTFS feed with associated schedules.</p></blockquote><p>transitland-lib also gives developers options for how to handle invalid data:</p><ul><li>For the canonical Transitland deployment, we've configured transitland-lib to fail <em>soft</em>. When errors are limited to certain rows in a GTFS feed, those entities are filtered out. The rest of the feed's data is imported and made available to users.</li><li>For some client deployments, we've configured transitland-lib to fail <em>hard</em>. Any error in a source feed will halt the entire workflow and instantly notify staff to review the issue.</li></ul><p>Each application may have different goals and different tradeoffs for how to handle invalid data, and transitland-lib provides options to customize and control this behavior.</p><h2 id="powerful-filtering-system">Powerful filtering system</h2><p>transitland-lib's filtering system enables modifying and transforming GTFS feeds for specific project contexts, such as:</p><ul><li>Producing date-specific GTFS feeds</li><li>Building regional routing engines with optimized data</li><li>Merging together many source feeds to create regional, state, or national scale feeds</li><li>Standardizing data across multiple agencies, with customized rules for namespacing entities</li></ul><p>Interline uses transitland-lib to <a href="https://app.interline.io/contact_forms/curated_gtfs">curate full-service data deliveries for our clients needing consistent GTFS data across states and countries</a>.</p><h2 id="using-transitland-lib">Using transitland-lib</h2><p>If you use the Transitland website or the Transitland APIs, you're already using transitland-lib.</p><p>Developers can visit <a href="https://github.com/interline-io/transitland-lib">github.com/interline-io/transitland-lib</a> to learn more about transitland-lib as a command-line interface (CLI) or a library for programmatic usage.</p><p>transitland-lib is available under a <a href="https://github.com/interline-io/transitland-lib/blob/main/LICENSE">dual license model</a> enabling open-source use under the permissive GPLv3 license and also providing flexibility to Interline's clients under a customizable business license.</p><p>We look forward to continuing to maintain transitland-lib for another six years as the GTFS and GTFS Realtime specifications continue to evolve and as the number and size of source feeds continues to grow.</p><style>html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}</style>]]></content:encoded></item><item><title><![CDATA[Transitland for nighttime]]></title><description><![CDATA[Our engineering team has recently been refactoring some of the internals of the Transitland website. The main goal has been to update various components and dependencies, to better support Interline's consulting clients who also use these components. As a side effect: the canonical Transitland website now has an optional dark mode.]]></description><link>https://www.interline.io/blog/transitland-for-nighttime/</link><guid isPermaLink="false">67be419bc6a81900012997a7</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Tue, 25 Feb 2025 22:23:06 GMT</pubDate><media:content url="https://www.interline.io/content/images/2025/02/CleanShot-2025-02-25-at-13.37.14.jpg" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/2025/02/CleanShot-2025-02-25-at-13.37.14.jpg" alt="Transitland for nighttime"><p>Our engineering team has recently been refactoring some of the internals of the Transitland website. The main goal has been to update various components and dependencies, to better support Interline's consulting clients who also use these components. As a side effect: the canonical Transitland website now has an optional dark mode.</p><p>Go to <a href="https://www.transit.land/">www.transit.land</a> and the website's styling will now respect your device's settings. So if your smartphone or laptop automatically switches to dark mode in the evening, when you access Transitland, you'll see a similarly dark background.</p><p>Or tap the little sun or moon icon in the top bar to manually switch the appearance.</p><p>We hope you enjoy Transitland — whatever time of day you're using it.</p>]]></content:encoded></item><item><title><![CDATA[Built with Transitland: Digital departures screen]]></title><description><![CDATA[Want to build your own display to show when a bus, train, or ferry next departs? Here's a fun Instructables how-to guide.]]></description><link>https://www.interline.io/blog/built-with-transitland-instructables/</link><guid isPermaLink="false">678158c911e94800010cde43</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Fri, 10 Jan 2025 17:40:06 GMT</pubDate><media:content url="https://www.interline.io/content/images/2025/01/Screenshot-2025-01-10-at-09-28-24-NYC-Ferry-Schedule-Ticker-Clock-6-Steps--with-Pictures----Instructables.png" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/2025/01/Screenshot-2025-01-10-at-09-28-24-NYC-Ferry-Schedule-Ticker-Clock-6-Steps--with-Pictures----Instructables.png" alt="screenshot of webpage titled &quot;NYC Ferry Schedule Ticker Clock&quot;"><p>Want to build your own digital display to show when a bus, train, or ferry next departs?</p><p>Here's a fun how-to guide from Instructables user @mpreston21:</p><blockquote><p>In this project, I iterated on the concept of <u>a subway clock</u> and created a version that displays the current schedule of the NYC ferry— for those who ride in style!</p><p>This product was created for my boyfriend who takes the ferry from the same stop every day to get to work. The design incorporates a perpetual scroll display that shares the next 3 departure times from his stop (North Williamsburg). He can glance over at the ferry times in the morning and determine which ferry to catch, and whether to walk, bike, or skateboard to catch his ferry. Using this clock reduces the likelihood that he will be distracted when looking up the schedule on the NYC Ferry's mobile app. It's a great way to start the day for anyone who relies on the ferry schedule with regularity :)</p></blockquote><p>Their instructions guide you through the process of creating all the relevant electronics:</p><figure><img src="https://www.interline.io/content/images/2025/01/CleanShot-2025-01-10-at-09.36.59@2x.png" alt="picture and list of supplies needed for the project, including an Arduino board, an LED RGB matrix, and wires" width="2000" height="1493"></figure><p>When it's time to program, the instructions describe how to query the <a href="https://www.transit.land/documentation/rest-api/departures">Transitland v2 REST API stop departures endpoint</a>:</p><blockquote><p>In order to work with GTFS directly, you need to spin up a server to manage the rate/volume of data when you make your query.</p><p>[...]</p><p>after digging around on the internet, I found <strong><u>Transit.Land</u></strong>-- an open data platform that collects GTFS and other open data feeds from transit providers around the world. Transitland makes all of this data queryable via <strong>REST APIs</strong>. There are feeds from <a href="https://www.transit.land/operators">over 2,500 operators in over 55 countries</a>, including the NYC ferry!</p><p>I read through the <u>Transit.Land documentation</u>, and started to decode the the key/value pair data for <a href="https://www.transit.land/operators/o-dr5r-nycferry#stops"><u>ferry stops</u></a> and <a href="https://www.transit.land/operators/o-dr5r-nycferry#routes"><u>ferry routes</u></a> from the source feeds. I created an account on <u>Interline.co</u> to get a <strong>secure API key</strong>. Armed with my API key, I started to get to work on the program for my ESP32.</p></blockquote><p>Thanks to @mpreston21 for sharing their creation.</p><p>See the <a href="https://www.instructables.com/NYC-Ferry-Schedule-Ticker-Clock/">full set of instructions, code, and illustrations on the Instructables website</a>.</p><blockquote><p><strong>Want to share your own project you've created using Transitland APIs or datasets?</strong> Please post to the <a href="https://github.com/transitland/transitland/discussions/categories/show-and-tell">&quot;show and tell&quot; section</a> of the Transitland discussion board on GitHub.</p></blockquote>]]></content:encoded></item><item><title><![CDATA[How current is that schedule?]]></title><description><![CDATA[The GTFS Best Practices guide recommends publishing data for the current data plus at least 7 days in the future. We've used the Transitland archives to assess how many feeds meet this goal.]]></description><link>https://www.interline.io/blog/how-current-is-that-schedule/</link><guid isPermaLink="false">6740e5ec598b590001b04997</guid><dc:creator><![CDATA[Ian Rees]]></dc:creator><pubDate>Mon, 25 Nov 2024 19:36:52 GMT</pubDate><media:content url="https://www.interline.io/content/images/2024/11/unnamed--1--1-1.png" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/2024/11/unnamed--1--1-1.png" alt="How current is that schedule?"><blockquote><p>This blog post is based on a presentation by Ian Rees and a panel discussion along with representatives from Google, Transit app, and MobilityData regarding &quot;<em>How to Make Sure Transit Riders Get New Schedules from GTFS Static Datasets on Time?</em>&quot; at the <a href="https://mobilitydata.org/the-2024-international-mobility-data-summit-new/">2024 International Mobility Data Summit</a>.</p></blockquote><p><a href="https://www.interline.io/transitland/">Transitland</a> monitors schedule data for thousands of public transit operators. This data is collected and archived — currently at a pace of tens of thousands of updates per year:</p><figure><img src="https://www.interline.io/content/images/2024/11/unnamed.png" alt="" width="1640" height="1012"><figcaption><p>The number of <a href="https://www.transit.land/documentation/concepts/static-gtfs-feed-versions/">feed versions</a> in the Transitland archive continues to grow year by year.</p></figcaption></figure><p>We rely on operators to set their own policies for updates to their schedule data, and the time period covered by that schedule data. Operators may publish data that contains scheduled service for the next week, the next month, or even the next year. In some instances, operators publish data that only contains service that begins at a future date. This is a critical, and often hidden, factor in how useful the data is to riders and other data consumers.</p><h2 id="the-7-day-rule">The &quot;7-day rule&quot;</h2><p>Data that changes frequently or data that only contains schedules for the next few days struggles against an important constraint: Data consumers might require many hours or days before data updates can be processed and available. (For example, to rebuild a routing graph used in trip-planning software.) These constraints mean service changes may be in effect, on the ground, before these changes can be communicated back to riders, via apps and websites.</p><p>Schedules that contain less than a week of future scheduled service can also force consumers to make (often faulty) assumptions about trips on future dates.</p><p>Currently, the <a href="https://gtfs.org/documentation/schedule/schedule-best-practices/">GTFS Best Practices</a> guide recommends publishing data for the current data plus at least 7 days in the future; we'll call this the &quot;7-day rule.&quot;</p><figure><img src="https://www.interline.io/content/images/2024/11/unnamed--1--1.png" alt="" width="1640" height="1012"><figcaption><p>The percentage of feed versions in Transitland's archive by year (on the x-asis) that have 7 days, 30 days, or 90 days of forward-looking schedule coverage as of when they were fetched by Transitland.</p></figcaption></figure><p>Fortunately, this is a mostly &quot;good news&quot; situation.</p><h2 id="using-transitlands-feed-archive-to-assess-update-frequency">Using Transitland's feed archive to assess update frequency</h2><p>Averaged across all transit operators in Transitland, about 95% of static schedule updates follow the 7-day rule. This number remains about 90% even when expanding the future service window to 30 days.</p><p>It's also a good picture when disaggregating and looking at the individual operator level: The vast majority of operators have 100% of schedule updates following the 7-day rule.</p><p>The most common exceptions are:</p><ol><li>operators that have a tendency to publish data that begins in the future, with no scheduled service on the date of publication</li><li>operators that fail to update the values in <code>feed_info.txt</code> which explicitly set the range of valid service dates and remove guesswork and ambiguity for the data consumer.</li></ol><p>Even if these exceptions apply to comparatively few feeds, it's still unfortunate if they occur in feeds that are important to a data consumer's use-case (e.g., to provide up-to-date trip-planning for travelers on an important transit operator).</p><h2 id="even-more-carefully-characterizing-updates">Even more carefully characterizing updates</h2><p>This provides an optimistic baseline for the current state of GTFS updates. For an even more holistic picture, we also need to incorporate a few additional metrics:</p><ul><li>Percentage of days for each operator where the data is &quot;stale&quot;, that is, outside the scheduled service window for the last published data.</li><li>The number of operators that publish data on a very frequent basis that assumes consumers have a fast turn-around process, and the characteristics of these updates.</li></ul><p>These questions will be explored in a future blog post.</p><blockquote><p><strong>The take-away from this blog post for transit data producers</strong>: Please check to ensure that your GTFS feed always includes service for the current point-in-time when it is published, and include at least 7 days of forward-looking schedule coverage (if not 30 or 90 days).</p></blockquote>]]></content:encoded></item><item><title><![CDATA[Giving equal prominence to buses and trains on the map]]></title><description><![CDATA[We've refined Transitland's global map to emphasize where riders can access the most frequent transit service. Thanks to leaders at San Francisco's transit agency for informing this improvement.]]></description><link>https://www.interline.io/blog/giving-equal-prominence-to-buses-and-trains-on-the-map/</link><guid isPermaLink="false">67364bd462576d000158a4d4</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Thu, 14 Nov 2024 19:42:08 GMT</pubDate><media:content url="https://www.interline.io/content/images/2024/11/Refinements-to-rail-line-width-1.png" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/2024/11/Refinements-to-rail-line-width-1.png" alt="screenshots of Transitland global transit map before and after changes to rail styling"><p>Transitland’s global map of transit has an ambitious goal: to map buses, trains, subways, cable cars, ferries, and other modes of public transit across all urban and rural regions where we can source <a href="https://www.transit.land/documentation/concepts/source-feeds/">standardized open-data feeds</a>. While the data feeds may be standardized, every route/trip/stop record also represents the manifestation of local history, politics, and economics — factors that can vary widely from country to country, or metro region to metro region. When we design our map of transit to be consistently usable and understandable across the world, we also touch on questions unique to each place.</p><p>Earlier this year, <strong>Jeffrey Tumlin,</strong> <a href="https://www.sfmta.com/people/jeffrey-tumlin">director of the San Francisco Municipal Transportation Agency</a>, took the time to discuss with our team some of the complicated questions raised by Transitland’s global map (and by similar transit navigation apps):</p><ul><li><em>Why are intercity trains, which only serve their riders a few times a day, often displayed more prominently than bus routes that actually provide much more frequent service?</em></li><li><em>When transit agencies offer a network of high-frequency bus service, how can riders identify this backbone to reach the nearest “entry point” and to plan transfers to most efficiently reach their ultimate destination?</em></li><li><em>Are colors a meaningful way to brand rail lines or high-frequency bus lines in a regional context, particularly if multiple overlapping agencies end up selecting the same colors for different lines?</em></li></ul><p>The discussion was spirited: Tumlin shared how his current experience leading a major US transit agency and his previous experience consulting internationally highlights how much of an outlier the US is in terms of privileging rail transit over bus transit. Legacies of racism continue to shape the transit networks of today. Whether transit service is provided to riders by a bus with rubber wheels or a train on steel tracks still resonates in an almost cultural manner, aside from the practicalities of whether the route will help riders reach their destinations.</p><p>The discussion was also optimistic: SFMTA is strengthening its network of bus routes with service of at least every 10 minutes. As frequencies increase further, riders are finding it even more convenient to quickly transfer from one high-frequency route to another. As a square of roughly 7 miles by 7 miles, San Francisco is now covered by a grid of high-frequency bus routes, enabling riders to travel “diagonally” with a single transfer with minimal wait time. SFMTA may stand out in the Bay Area in this respect, but it’s using patterns long common to other parts of the world and increasingly adopted in the dense cores of more American cities.</p><blockquote><p>Interline is currently engaged by the SF Bay Area's Metropolitan Transportation Commission to build a regional mapping data services platform to support transit cartography throughout the entire Bay Area. This platform will help to support MTC's <a href="https://mtc.ca.gov/operations/transit-regional-network-management/regional-mapping-wayfinding">Regional Mapping and Wayfinding project</a>, of which SFMTA is also a key stakeholder. All transit riders and residents of the greater Bay Area stand to gain from this initiative to design consistent maps and signage, as well as <a href="https://mtc.ca.gov/operations/transit-regional-network-management/transit-fare-coordination-integration">related initiatives to better integrate transit service</a>.</p></blockquote><p>Based on input from Tumlin, as well as from <strong>SFMTA transit planner</strong> <a href="http://calurbanist.com/"><strong>Steve Boland</strong></a>, we’ve tuned the Transitland global map.</p><h2 id="rail-routes-are-now-zoom-level-dependent">Rail routes are now zoom-level dependent</h2><p>Rail lines continue to be more prominent at national or region-wide views. As you zoom into a city or neighborhood scale, rail lines now shrink to be equally sized with bus lines:</p><figure><img src="https://www.interline.io/content/images/2024/11/Refinements-to-rail-line-width.png" alt="screenshots of Transitland global transit map before and after changes to rail styling" width="2000" height="1275"></figure><p>This change reflects how rail lines are helpful for riders orienting across broader viewers and relevant for traveling longer distances, but for intra-urban travel, a bus may often be competitive if not better than a rail-based transit service.</p><h2 id="bus-routes-are-grouped-by-styling">Bus routes are grouped by styling</h2><p>Previously, our map classified buses routes into two groups by their frequency: less frequent routes were styled with a lighter blue color, more frequent routes were styled with a darker and more prominent blue.</p><p>Now our map groups buses into three different groups by their <em>headway</em> (the term that transit planners use to refer to how frequently a transit service operates):</p><figure><img src="https://www.interline.io/content/images/2024/11/Bus-frequency.png" alt="screenshots of Transitland global transit map before and after changes to bus frequency styling" width="2000" height="1851"></figure><p>In cities and metros with a network of high-frequency service, this change will help to emphasize that subset of fast and dependable service, while still also showing connections with less frequent bus services that provide coverage.</p><h2 id="onward">Onward</h2><p>We’re working on some longer term improvements to the way bus and rail route shapes are handled within the Transitland software stack, and we look forward to sharing more in the future.</p><p>It’s also always a pleasure to place the work we do with data and software within the broader context of public transit in the US. Thanks to SFMTA staff for a lively conversation and useful feedback!</p>]]></content:encoded></item><item><title><![CDATA[Turning off the Transitland v1 Datastore API]]></title><description><![CDATA[We announced the multi-step deprecation of the Transitland v1 API in a blog post in 2019. The time has now come the Interline team to finally turn off the v1 Datastore API.]]></description><link>https://www.interline.io/blog/turning-off-the-transitland-v1-datastore-api/</link><guid isPermaLink="false">67255cafb62841000136ee97</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Thu, 14 Sep 2023 07:00:00 GMT</pubDate><content:encoded><![CDATA[<blockquote><p><strong>October, 31, 2023</strong>: We've now fully shut down the servers that respond to queries at <code>https://transit.land/api/v1</code>. Thank you to the many users who have migrated to using v2 APIs. For the handful who have yet to make the transition, we hope you'll read the following to learn more about the benefits of Transitland v2 APIs.</p></blockquote><p>We announced the <a href="https://www.interline.io/blog/tlv2/#gradual-deprecation-of-tlv1">multi-step deprecation of the Transitland v1 API in a blog post in 2019</a>. In the intervening years, we've been greatly expanding the functionality, speed, and data coverage of the new v2 APIs. We've been pointing existing and new Transitland developers to the v2 APIs — particularly the v2 REST API — for a few years.</p><p>The time has now come the Interline team to finally turn off the v1 Datastore API. On <strong>October 31, 2023</strong> we are planning to shut down the systems that handle queries to URLs to all endpoints that begin in <code>https://transit.land/api/v1</code></p><p>If you're in the subset of Transitland developers who continue to use the v1 APIs, please switch as soon as possible. We've emailed everyone with an API key that has queried the v1 APIs in the last 30 days to share this information. Most applications that used the v1 APIs should find the v2 REST API to be similar or better. The v2 REST API mixes together information from both static GTFS and GTFS Realtime feeds; it's highly performant; and we're about to announce some exciting new functionality that will only be available through the v2 endpoints. The same Transitland v1 API key will work with the v2 REST API.</p><p>For more information on how to migrate an application or script to the v2 REST API:</p><ul><li>See the <a href="https://www.transit.land/documentation/rest-api/">Transitland v2 REST API documentation</a>.</li><li>Post questions to the <a href="https://github.com/transitland/transitland/discussions">Transitland discussions forum on GitHub</a> to be answered by Interline staff and fellow developers as time permits.</li><li>Sign up for a paid <a href="https://www.transit.land/plans-pricing/">Transitland Professional or Enterprise subscription</a> to receive support via email by Interline staff. These plans also include the Transitland v2 GraphQL API, with even more functionality and flexibility.</li></ul><p>We appreciate having so many developers who've used the v1 APIs since 2015 to power such a wide range of applications and use-cases, and we look forward to fully focusing our efforts on further expanding v2 functionality and continuing its solid record of uptime and performance. Thanks to the developer-users been part of the Transitland platform over many years!</p>]]></content:encoded></item><item><title><![CDATA[Downloading archived GTFS feed versions from Transitland]]></title><description><![CDATA[We are adjusting access to Transitland's GTFS feed version archive to better balance concerns.]]></description><link>https://www.interline.io/blog/downloading-archived-gtfs-feed-versions-from-transitland/</link><guid isPermaLink="false">67255c32b62841000136ee84</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Thu, 16 Jun 2022 07:00:00 GMT</pubDate><content:encoded><![CDATA[<blockquote><p><strong>July 19, 2022</strong>: We appreciate questions and feedback we've received from a wide range of Transitland users about this change. Based on feedback, we are adding a Hobbyist/Academic plan with no cost. Users developing non-commercial applications may use this plan to access historical feed versions through the v2 REST API.</p><p>Commercial users who need access to historical feed versions, as well as academic users who require support and/or access to the v2 GraphQL API, are directed to the Professional plan.</p><p>See a comparison of functionality on the <a href="https://www.transit.land/plans-pricing/">Transitland plans and pricing</a> page.</p><p>(And one more update to this blog post: the count of feed version in the Transitland archive is out of date. Now there are 105,763 :)</p></blockquote><p>For roughly seven years, Transitland has been fetching and archiving static GTFS feeds from transit operators. We've also imported a selection of feed versions from other public archives, such as <a href="https://www.transit.land/news/2016/05/16/gtfs-data-exchange">GTFS Data Exchange</a>. Today Transitland contains 102,191 processed and archived feed versions.</p><p>To date, we have allowed the public to freely download archived feed versions through the Transitland website. The <a href="https://www.transit.land/plans-pricing/">free tier for Transitland API access</a> has also provided a generous allotment of queries, which can be used to download archived feed versions, in addition to querying into data contents imported from those feed versions.</p><p>Some users are taking advantage of this openness by scraping the entire contents of Transitland's feed version archive. These mass downloads put load on Transitland servers and bandwidth, increasing our operating expenses. It also blurs distinctions between the API free tier (intended to be generous enough for hobbyist projects and pilot projects by companies) and the professional tier (intended to support production projects).</p><p>We are adjusting access to Transitland's GTFS feed version archive to better balance these concerns.</p><h2 id="downloading-feed-versions-through-the-website">Downloading feed versions through the website</h2><p>This website now allows users to download the latest version of any feed (with the exception of those marked as having licenses that prevent redistribution). Click through to a feed page and you'll see a download icon in the top frow of the table of archived feed versions. For example, the <a href="https://www.transit.land/feeds/f-9q9-caltrain">Caltrain feed</a>:</p><h2 id="downloading-feed-versions-through-the-v2-rest-api">Downloading feed versions through the v2 REST API</h2><p>Developers can use the v2 REST API to download feed versions by two means:</p><ol><li>Use <a href="https://www.transit.land/documentation/rest-api/feeds#downloading-source-gtfs">feed endpoint</a> to download the latest feed version of a given feed. For example: <code>GET /api/v2/rest/feeds/f-9q9-caltrain/download_latest_feed_version</code></li><li>Use the <a href="https://www.transit.land/documentation/rest-api/feed_versions#downloading-source-gtfs">feed versions endpoint</a> to specify a feed version by its unique SHA1 hash and download it. For example: <code>GET /api/v2/rest/feed_versions/8f99f69503edfa52e06ec5673e582d3a684c05ca/download</code></li></ol><p>Starting in seven days (on Thursday, June 23, 2022), Transitland will only allow users on the <a href="https://www.transit.land/plans-pricing/">Professional or Enterprise plan</a> to download feeds using the second of those options. (As of July 19, 2022, non-commercial users on the <a href="https://www.transit.land/plans-pricing/">Hobbyist/Academic plan</a> are also being given this capability.) All registered developers, including those on the Free plan, will still be able to use the first of those options.</p><h2 id="continuing-to-tune-and-improve">Continuing to tune and improve</h2><p>We founded Transitland in 2014 to serve as &quot;a community-edited data service aggregating transit networks across metropolitan and rural areas around the world.&quot; We've added, adjusted, and removed functionality over time. We've also supported Transitland's expenses and upkeep through a changing mixture of organizational sponsorship, charitable sponsorship, and customer revenue. We expect to continue to adjust Transitland's functionality and access policies over time to maintain and expand this platform as the best possible set of open transit and mobility APIs. Thanks to our users — both old and new, and on both free and paid plans — for making such good use of Transitland.</p>]]></content:encoded></item><item><title><![CDATA[Transitland Vector Tile Improvements]]></title><description><![CDATA[Since releasing the global transit map and v2 Vector Tiles API last year, we've added a variety of improvements in functionality and in rendering.]]></description><link>https://www.interline.io/blog/vector-map-tiles/</link><guid isPermaLink="false">67255bacb62841000136ee73</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Fri, 10 Jun 2022 07:00:00 GMT</pubDate><media:content url="https://www.interline.io/content/images/2024/11/global-transit-map-europe.png" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/2024/11/global-transit-map-europe.png" alt="Transitland Vector Tile Improvements"><p>Transitland's <a href="https://www.transit.land/map">global transit map</a> provides a worldwide view of public bus, train, subway, ferry, and gondola route lines and stop points around the world. Using the <a href="https://www.transit.land/documentation/vector-tiles">v2 Vector Tiles API</a> developers can integrate Transitland routes and stops tiles into their own web maps.</p><p>Since <a href="https://www.interline.io/blog/transitland-v2-vector-map-tiles/">releasing</a> the global transit map and v2 Vector Tiles API last year, we've added a variety of improvements in functionality and in rendering.</p><h2 id="performance-improvements">Performance Improvements</h2><p>The Transitland global transit map and v2 Vector Tiles API are based on tiles in the <a href="https://docs.mapbox.com/data/tilesets/guides/vector-tiles-standards/">MVT (Mapbox Vector Tile) format</a>. We've made a number of changes to the data that's encoded into each MVT tile for route geometries. The changes are small but add up to a meaningful decrease in the size of the tiles and an increase in rendering performance. These improvements are especially useful at zoomed out (small scale) views:</p><h2 id="representative-route-geometries">Representative Route Geometries</h2><p>While some transit routes are simple, with all trips following the same line, other transit routes can be very complicated. Routes may have trips along certain lines at peak hours and along other lines at off-hours. Routes may branch and go in multiple directions depending upon the trip. Many different combinations are possible all under the same branding of a single route name.</p><p>Transitland creates &quot;representative&quot; route geometries for every route. This geometry must balance competing goals:</p><ul><li>show all of the different variants of the route (all of the possible trip geometries)</li><li>provide a single geometry that can be understood on its or on a map with many other routes</li><li>not be too large in file size</li></ul><p>When a source feed does not provide <code>shapes.txt</code> for a given trip, Transitland generates &quot;stop-to-stop geometries&quot; by drawing straight lines between stop locations.</p><p>The representative geometry for each route is created using the following rules:</p><ol><li>for each route direction:
<ul><li>select the longest shape</li><li>select any shape used for at least 20% of trips</li></ul></li><li>from this collection, drop shapes with totally broken geometry, e.g. a point at (0,0)</li><li>drop shapes contained entirely within another selected shape</li><li>include generated stop-to-stop geometries only if no <code>shapes.txt</code> shapes are available</li><li>combine the selected shapes into a representative <code>MultiLineString</code></li><li>the single most frequently used shape becomes the representative <code>LineString</code></li></ol><h2 id="problematic-route-geometries">Problematic Route Geometries</h2><p>Creating high quality <code>shapes.txt</code> records in GTFS feeds can be a challenge. Occasionally agencies do make mistakes. For example:</p><ul><li>routes shapes that travel to <a href="https://blogs.loc.gov/maps/2016/04/the-geographical-oddity-of-null-island/">Null Island</a> (include a 0,0 point)</li><li>routes shapes that zigzag between stop locations out of order</li><li>route shapes that have not been updated to reflect current stop locations and sequence</li></ul><p>Transitland's goal when importing from <code>shapes.txt</code> is the same as our overall goal with GTFS source feeds: We aim to import as many records as possible, while ignoring records that are invalid or that are of such low quality that they will not be usable. Transitland continues to import the overall feed, even if it must leave out some records.</p><p>(Transitland's import strategy is in contrast with validators and tooling that are used by agencies when generating GTFS — for those types of use-cases, the user may wish to have the process fail an entire feed when one of its entities causes a problem. The operator will then fix the feed before repeating the validation process.)</p><p>Transitland tags as problematic route geometries that fit the following criteria:</p><ul><li>Shape length greater than 5,000km</li><li>Any individual line segment above 50km for <code>shapes.txt</code> geometries</li><li>Any individual line segment above 5km for generated stop-to-stop geometries</li><li>&quot;Zigzag&quot; shapes where points are in obviously incorrect order</li></ul><p>Problematic geometries are still included in the MVT vector tile data, but the global transit map hides these geometries by default. To see them, open <em>Options</em> and select <em>Show problematic route geometries</em>:</p><h2 id="two-tiers-of-feature-detail">Two tiers of feature detail</h2><p>A typical tile set contains over 150,000 routes! This can be expensive to load and render at low zoom levels, so some compromises are baked into the tiles. Vector tile zoom levels 8 and higher include the full <code>MultiLineString</code> representative geometries and all route features. Tile zoom levels between 0 and 7 include a single <code>LineString</code> geometry for each route, and on particularly dense tiles, a percentage of route features are dropped to help manage the file size of each tile (routes with high levels of service are weighted towards inclusion). Zoom levels 0 to 13 include line simplification appropriate for displaying at that zoom level; zoom level 14 includes the full, unsimplified geometry.</p><table><thead><tr><th>Zoom level</th><th>Feature(s)</th><th>Level of detail</th></tr></thead><tbody><tr><td>0</td><td>single <code>LineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>1</td><td>single <code>LineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>2</td><td>single <code>LineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>3</td><td>single <code>LineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>4</td><td>single <code>LineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>5</td><td>single <code>LineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>6</td><td>single <code>LineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>7</td><td>single <code>LineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>8</td><td>full <code>MultiLineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>9</td><td>full <code>MultiLineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>10</td><td>full <code>MultiLineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>11</td><td>full <code>MultiLineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>12</td><td>full <code>MultiLineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>13</td><td>full <code>MultiLineString</code></td><td>geometry simplified for display at given zoom level</td></tr><tr><td>14</td><td>full <code>MultiLineString</code></td><td>full unsimplified geometry</td></tr></tbody></table><h2 id="use-transitland-v2-vector-tiles-api-in-qgis">Use Transitland v2 Vector Tiles API in QGIS</h2><p>Can you use Transitland vector tiles in desktop GIS software? Thanks to a curious user for <a href="https://github.com/transitland/transitland/discussions/355">asking this question</a>. Turns out the answer is yes.</p><p>If you want to use Transitland route lines and stop locations as layers in your own GIS map, along with your other data sources, here are instructions for how to do so in QGIS:</p><ol><li>If you have not already, download and install the <a href="https://qgis.org/">QGIS desktop GIS software package</a>.</li><li>If you have not already, <a href="https://www.transit.land/documentation#signing-up-for-an-api-key">sign up for a Transitland API key</a>.</li><li>From the menu, select <em>Layer &gt; Add Layer &gt; Add Vector Tile Layer...</em></li><li>Press the <em>New</em> button and select <em>New Generic Connection...</em></li><li>Enter &quot;Transitland stops&quot; or &quot;Transitland routes&quot; at the name (or whatever you wish)</li><li>For URL, enter <code>https://transit.land/api/v2/tiles/routes/tiles/{z}/{x}/{y}.pbf?apikey=xxx</code> or <code>https://transit.land/api/v2/tiles/stops/tiles/{z}/{x}/{y}.pbf?apikey=xxx</code> You will need to replace <code>xxx</code> with your own API key</li><li>Press the <em>OK</em> button</li><li>In the _Browser_side menu, you will now see the new source listed under <em>Vector Tiles</em>. Right click on it and select <em>Add Layer to Project</em></li><li>You should now see the layer visualized. Repeat the steps to add the other layer, if you wish to have both stop points and route lines.</li><li>Customize the styling for one or both of the layers.</li></ol><figure><img src="https://www.interline.io/content/transit-land/vector-map-tiles/transitland-tiles-in-qgis.png" alt="screenshot of QGIS desktop GIS software displaying Transitland vector tiles" width="2912" height="1920"></figure><p>Please note that the <a href="https://www.transit.land/terms">Transitland terms</a> require that you provide attribution on maps and other creations using output from the Transitland APIs.</p><p>We look forward to seeing what GIS users, software developers, and data analysts create using these enhanced transit map tiles. We welcome all to post their creations on <a href="https://github.com/transitland/transitland/discussions/categories/show-and-tell">Transitland's &quot;show and tell&quot; discussion board</a>.</p>]]></content:encoded></item><item><title><![CDATA[Use Transitland v2 to Search Across Operators, Feeds, and Routes]]></title><description><![CDATA[Here's one of our favorite new additions to Transitland v2: search across all of the operators, feed records, and routes in Transitland.]]></description><link>https://www.interline.io/blog/transitland-v2-search/</link><guid isPermaLink="false">67255b45b62841000136ee62</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Thu, 04 Mar 2021 08:00:00 GMT</pubDate><content:encoded><![CDATA[<p>Over the last year (or two?) <a href="https://www.interline.io/blog/tlv2/">we've been creating Transitland v2</a>, a major rewrite of the platform's internals. Transitland v2 brings performance improvements, the option to deploy any number of customized Transitland installations (in addition to the &quot;canonical&quot; Transitland that lives here at <a href="https://www.transit.land/">transit.land</a>), and useful new feature additions. Here's one of our favorite new additions: search across all of the operators, feed records, and routes in Transitland.</p><figure><img src="https://www.interline.io/content/transit-land/tlv2-feature-announcements/tlv2-search-animation.jpg" alt="" width="2722" height="2132"></figure><p>The new search functionality currently indexes millions of records and returns results quickly — very quickly! Try it yourself. Type into the search box in the upper right corner of this page and watch as the results are returned.</p><p>Search can also be scoped. For example, open up the Chicago Transit Authority operator page and you can search within that operator's stops and routes:</p><p>Developers, we welcome you to start thinking of ways you might want to integrate Transitland's search functionality into your own apps, websites, and creations. Search will be included in the <a href="https://www.transit.land/documentation">upcoming Transitland v2 APIs</a>.</p><p>Search is always complicated. There are questions of what to index, how to weight different parameters, and so on. For example, we are not yet including stops/stations in the global search at this point. We welcome feedback and bug reports.</p><p>Are you searching Transitland only to find that we do not have data for your favorite transit operator? Help expand Transitland's coverage by contributing to the <a href="https://github.com/transitland/transitland-atlas">Transitland Atlas</a>, the open directory of feeds that powers Transitland's services.</p>]]></content:encoded></item><item><title><![CDATA[Transitland v2 Adds a Global Map and Vector Tiles]]></title><description><![CDATA[Here's one of our favorite new additions to Transitland v2: a "slippy map" of transit routes and stops around the world.]]></description><link>https://www.interline.io/blog/transitland-v2-vector-map-tiles/</link><guid isPermaLink="false">67255a85b62841000136ee4e</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Thu, 25 Feb 2021 08:00:00 GMT</pubDate><media:content url="https://www.interline.io/content/images/2024/11/tlv2-map-animation.jpg" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/2024/11/tlv2-map-animation.jpg" alt="Transitland v2 Adds a Global Map and Vector Tiles"><blockquote><p><strong>June 10, 2022</strong>: Here's a more recent blog post <a href="https://www.interline.io/blog/vector-map-tiles/">describing further improvements and refinements to Transitland's global transit map and vector tile API</a>.</p></blockquote><p>Over the last year (or two?) <a href="https://www.interline.io/blog/tlv2/">we've been creating Transitland v2</a>, a major rewrite of the platform's internals. Transitland v2 brings performance improvements, the option to deploy any number of customized Transitland installations (in addition to the &quot;canonical&quot; Transitland that lives here at <a href="https://www.transit.land/">transit.land</a>), and useful new feature additions. Here's one of our favorite new additions: a &quot;slippy map&quot; of transit routes and stops around the world.</p><figure><img src="https://www.interline.io/content/transit-land/tlv2-feature-announcements/tlv2-map-animation.jpg" alt="" width="1197" height="990"></figure><p>Try the Transitland global transit map yourself at <a href="https://www.transit.land/map">https://www.transit.land/map</a> Pan, zoom, and place your mouse cursor over features to learn more. Click to see more details about particular routes and stops.</p><p>The Transitland global transit map powered by vector tiles in the <a href="https://docs.mapbox.com/vector-tiles/specification/">Mapbox Vector Tile format</a>. Any user of the <a href="https://www.transit.land/documentation/vector-tiles">Transitland v2 Vector Tile API</a> can build these route line and stop location layers into their own &quot;slippy maps&quot; on the web, with their own styling and customizations. The tiles are always fresh — Transitland updates them with the latest data each day.</p><p>Note that Transitland continues to provide GeoJSON through the <a href="https://www.transit.land/documentation">Datastore v1 API and the upcoming v2 APIs</a>. When creating smaller maps or static maps, it may be simpler to use GeoJSON. The power of MVT is when you need both wide coverage and precise detail.</p><p>Not seeing public transit routes and stops where you expect to find them on the map? Help expand Transitland's coverage by contributing to the <a href="https://github.com/transitland/transitland-atlas">Transitland Atlas</a>, the open directory of feeds that powers Transitland's services.</p>]]></content:encoded></item><item><title><![CDATA[Transportation Research Board funds an open platform for transit agencies to improve the quality of their real-time data]]></title><description><![CDATA[We’re excited to share that the Transportation Research Board has awarded a Transit IDEA Program grant to Interline. We’re using this unique opportunity to expand Transitland to support GTFS Realtime feeds.]]></description><link>https://www.interline.io/blog/transportation-research-board-funds-gtfs-realtime/</link><guid isPermaLink="false">67255705b62841000136eddc</guid><dc:creator><![CDATA[Drew Dara-Abrams]]></dc:creator><pubDate>Wed, 23 Jan 2019 08:00:00 GMT</pubDate><content:encoded><![CDATA[<blockquote><p><strong>January 19, 2021</strong>: Interline and CUTR@USF have now published a Transportation Research Board report on this project. See <a href="https://www.interline.io/blog/trb-transit-idea-gtfs-realtime-report/">this more recent blog post</a>.</p></blockquote><p>We’re excited to share that the <a href="http://www.trb.org/">Transportation Research Board</a> has awarded a <a href="http://apps.trb.org/cmsfeed/TRBNetProjectDisplay.asp?ProjectID=4695">Transit IDEA Program grant</a> to Interline. We’re using this unique opportunity to expand <a href="https://www.transit.land/">Transitland</a> to support <a href="https://developers.google.com/transit/gtfs-realtime/">GTFS Realtime</a> feeds. Our goal is for Transitland to provide a suite of validation tools for public-transit agency staff to validate the contents and quality of their real-time data feeds.</p><h2 id="high-quality-real-time-data-is-hard-but-worthwhile">High-quality real-time data is hard but worthwhile</h2><figure><img src="https://www.interline.io/content/images/2024/11/trb-idea-the-problem.png" alt="the problem statement" width="960" height="720"></figure><p>Real-time transit information has many benefits to transit riders and agencies, including shorter perceived and actual wait times, a more welcoming experience for new riders, and an increased feeling of safety, and increased ridership. Real-time transit data is, in comparison with many other potential operational or capital improvements to bus or rail service, an affordable means of increasing ridership. In the last few years, a real-time complement to the General Transit Feed Specification (GTFS) format, GTFS Realtime, has emerged.</p><p>Despite its promise, adoption of GTFS Realtime by transit agencies has been hampered by a lack of clear documentation and readily available validation tools. Hardware and software vendors for automatic vehicle location (AVL) systems also vary in the depth and quality of their support for the GTFS Realtime specification. As a result, transit agencies must invest significant time and effort to create and maintain high quality GTFS Realtime feeds. Furthermore, bad data has been shown to have a negative effect on ridership, the rider’s opinion of the agency, and the rider’s satisfaction with multimodal trip-planning apps. Thus, transit agencies must put even more effort toward ensuring that the GTFS Realtime data produced by their systems is of sufficient quality.</p><h2 id="our-solution-gtfs-validation-in-transitland">Our Solution: GTFS Validation in Transitland</h2><p>In this project, Interline and the <a href="https://www.cutr.usf.edu/">Center for Urban Transportation Research</a> are creating a prototype platform that makes GTFS Realtime validation tools readily available to, potentially, all transit agencies in North America. We will build upon two open-source projects: the <a href="https://github.com/CUTR-at-USF/gtfs-realtime-validator">GTFS Realtime validator prototype</a> and Transitland, an open transit data platform. This project will apply the open-source and open-data community models to the challenges of creating and improving GTFS Realtime data.</p><p>By combining the open-source components of a GTFS Realtime validator with a catalog of GTFS Realtime feeds, hosted on Transitland’s cloud servers, this project will make the process of validating real-time data simple and accessible to agency staff from any computer with a web browser. As a result, GTFS Realtime data will improve in quality and availability. Transit riders will have a better experience (which has been linked to higher ridership), agency staff will provide better service with less effort and cost, and system vendors will provide higher quality product.</p><h2 id="our-partner-center-for-urban-transportation-research">Our Partner: Center for Urban Transportation Research</h2><p>We’re glad to have on our project team an expert on GTFS Realtime: Sean Barbeau. Sean and his colleagues at the University of South Florida’s Center for Urban Transportation Research have been involved in GTFS, GTFS Realtime, and related transit data specifications and systems for many years. Most recently, they have created a GTFS Realtime validator prototype. We’ll be working together to test and deploy this validator tooling within the Transitland platform.</p><p>For more about their preliminary findings about the quality of GTFS Realtime feeds, see <a href="https://medium.com/@sjbarbeau/introducing-the-gtfs-realtime-validator-e1aae3185439">this recent summary of their TRB paper</a>. Here are the most common errors and warnings their prototype validator found in a sample of GTFS Realtime feeds:</p><figure><img src="https://www.interline.io/content/images/2024/11/validator-test-errors.png" alt="most common errors found in a sample of GTFS Realtime feeds" width="624" height="431"><figcaption><p>Image Credit: Sean Barbeau, Transportation Research Board 2018 paper <a href="https://trid.trb.org/view/1496848">18–05585 &quot;Quality Control — Lessons Learned from the Deployment and Evaluation of GTFS-realtime Feeds&quot;</a>.</p></figcaption></figure><h2 id="about-the-transit-idea-program">About the Transit IDEA program</h2><p>Here’s an overview of the <a href="http://www.trb.org/IDEAProgram/IDEATransit.aspx">Transit IDEA Program</a>:</p><blockquote><p>The Transit IDEA Program is part of the Transit Cooperative Research Program, a cooperative effort of the Federal Transit Administration (FTA), the Transportation Research Board (TRB), and the Transit Development Corporation (a nonprofit educational and research organization of the American Public Transportation Association). The program is funded by the FTA and is managed by TRB.</p><p>The Transit IDEA Panel has established four high-priority focus areas to encourage proposals in the following areas:Increasing transit ridershipImproving transit safety, security, and emergency preparednessImproving transit capital and operating efficienciesProtecting the environment and promoting energy independence.</p></blockquote><p>IDEA stands for “Innovations Deserving Exploratory Analysis” — which we think is an apt description for the Transitland platform providing GTFS Realtime feed validation to agency staff!</p><h2 id="an-open-call-to-transit-agency-staff">An open call to transit agency staff</h2><p>If your agency provides a GTFS Realtime feed, we welcome you to participate in the user-testing phase of this project. Please write us at <a href="mailto:info@interline.io">info@interline.io</a> for more information.</p>]]></content:encoded></item><item><title><![CDATA[Metropolitan Transportation Commission and Interline to tackle regional transit data challenges]]></title><description><![CDATA[We're excited to share that the Metropolitan Transportation Commission has selected Interline through a competitive process to participate in its 2019 Startup in Residence (STIR) program. Interline and MTC will collaborate on the problem of regional transit data.]]></description><link>https://www.interline.io/blog/metropolitan-transportation-commission-selects-interline/</link><guid isPermaLink="false">67254697b62841000136ece8</guid><dc:creator><![CDATA[Interline Technologies]]></dc:creator><pubDate>Thu, 10 Jan 2019 08:00:00 GMT</pubDate><media:content url="https://www.interline.io/content/images/2024/11/stir-banner.png" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/2024/11/stir-banner.png" alt="Metropolitan Transportation Commission and Interline to tackle regional transit data challenges"><blockquote><p><strong>January 8, 2020</strong>: MTC and Interline have released the Regional GTFS Feed. See <a href="https://www.interline.io/blog/mtc-regional-gtfs-feed-release/">this more recent blog post</a>.</p></blockquote><blockquote><p><strong>August 10, 2020</strong>: MTC and Interline have released additional functionality in the Regional GTFS Feed. See <a href="https://www.interline.io/blog/mtc-regional-gtfs-feed-additions/">this more recent blog post</a>.</p></blockquote><p>We’re excited to share that the <a href="https://mtc.ca.gov/whats-happening/news/mtc-work-startups-tackle-transportation-challenges">Metropolitan Transportation Commission has selected Interline</a> through a competitive process to participate in its 2019 Startup in Residence (STIR) program.</p><h2 id="regional-transit-data-for-the-bay-area">Regional Transit Data for the Bay Area</h2><p>Interline and MTC will collaborate on the problem of regional transit data. The Bay Area has over 30 public-transit operators. Most agencies provide open-data in the <a href="http://gtfs.org/">GTFS format</a>, which is in turn used by many companies and developers to power navigation and transportation apps. However, to use all of these GTFS feeds together presents many technical challenges to both public agencies and private consumers. During the STIR residency, Interline will use the <a href="https://www.transit.land/">Transitland</a> platform to help the MTC improve regional transit data distribution.</p><p>Transitland currently aggregates GTFS feeds from approximately 2,500 transit operators around the world. Transitland users — including startups, large corporations, advocacy groups, and government agencies — currently query Transitland’s open APIs five million times per month. Transitland is powered by open-source software, and can be customized by Interline for particular agency needs.</p><p>Transitland currently aggregates transit data for the San Francisco Bay Area from 36 operators:</p><figure><img src="https://www.interline.io/content/images/2024/11/feed-registry-bay-area.png" alt="Transitland Feed Registry listing 36 operators in the San Francisco Bay Area" width="1197" height="3857"></figure><p>For a current list of Bay Area transit agencies that provide open GTFS data, see the <a href="https://www.transit.land/feed-registry/?metro=San+Francisco+Bay+Area">Transitland Feed Registry</a>.</p><h2 id="startup-in-residence-program">Startup in Residence Program</h2><figure><img src="https://www.interline.io/content/images/2024/11/stir-banner-2.png" alt="Start up in Residence program logo" width="231" height="128"></figure><p>The national STIR program is supported by the <a href="https://www.cityinnovate.com/">City Innovate Foundation</a>.</p><p>“The Startup in Residence program is a model for civic innovation and national collaboration,” says Jay Nath, former Chief Innovation Officer for San Francisco and Executive Director for City Innovate. “This program is a unique opportunity for government agencies and startups to think creatively about how we can all work together to modernize government to benefit residents.”</p><p>For more on STIR, see <a href="https://medium.com/@CityInnovate/700-startups-compete-to-work-on-urban-challenges-through-startup-in-residence-55052fd781ea">City Innovate’s announcement of the 2019 program</a>.</p><h2 id="metropolitan-transportation-commission">Metropolitan Transportation Commission</h2><figure><img src="https://www.interline.io/content/images/2024/11/mtc-logo-1.png" alt="Metropolitan Transportation Commission (MTC) logo" width="516" height="128"></figure><p>The <a href="https://mtc.ca.gov/">Metropolitan Transportation Commission</a> (MTC) is the transportation planning, financing, and coordinating agency for the nine-county San Francisco Bay Area. MTC is based out of downtown San Francisco.</p><p>MTC provides <a href="https://511.org/">511.org</a> with transportation information for travelers around the Bay Area and <a href="https://511.org/developers/list/resources/">511 Developer Resources</a> to power third-party apps and websites.</p><h2 id="transitland-and-interline">Transitland and Interline</h2><figure><img src="https://www.interline.io/content/images/2024/11/transitland_logo-1.png" alt="Transitland logo" width="620" height="290"></figure><p>Transitland is powered by open-source software and open data. Started in 2014 by Mapzen, <a href="https://www.transit.land/news/2019/01/08/transitland-continues.html">Transitland is now supported by Interline and a growing list of partners</a>.</p><p>To follow Interline’s progress on this project, follow this blog or <a href="http://eepurl.com/dmWHln">subscribe to our newsletter</a>.</p><p>Interline’s team of principals and specialists all live in the Bay Area and ride public transit regularly. We’re pleased to have this opportunity to collaborate with the MTC on improvements to our region and its transportation systems!</p>]]></content:encoded></item><item><title><![CDATA[Transitland Version 2]]></title><description><![CDATA[What first started as two simple, separate, little experiments has grown into the seeds of a major revision of the entire Transitland platform: Transitland Version 2.]]></description><link>https://www.interline.io/blog/tlv2/</link><guid isPermaLink="false">67255876b62841000136ee13</guid><dc:creator><![CDATA[Drew Dara-Abrams]]></dc:creator><pubDate>Tue, 08 Jan 2019 08:00:00 GMT</pubDate><media:content url="https://www.interline.io/content/images/2024/11/tlv2-architecture-diagram.png" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/2024/11/tlv2-architecture-diagram.png" alt="Transitland Version 2"><blockquote><p><strong>March 4, 2021</strong>: Here's a more recent blog post <a href="https://www.interline.io/blog/transitland-v2-search/">demonstrating Transitland v2's new ability to search across transit operators, feeds, and routes</a>.</p></blockquote><blockquote><p><strong>February 25, 2021</strong>: Here's a more recent blog post <a href="https://www.interline.io/blog/transitland-v2-vector-map-tiles/">demonstrating Transitland v2's new global transit map and vector tiles</a>.</p></blockquote><p>It's been a quiet year on this blog, and we're overdue to share all the work that's been going on behind the scenes since the <a href="https://www.interline.io/blog/transitland-continues/">last post</a>. What first started as two simple, separate, little experiments has grown into the seeds of a major revision of the entire Transitland platform: Transitland Version 2.</p><h2 id="tlv2-functionality-and-goals">Tlv2 Functionality and Goals</h2><p><em>Tlv2</em> (as we've come to call this new version) provides continuity on the most used parts of the Transitland platform. Tlv2 will still provide a canonical service at transit.land that includes a Feed Registry of open GTFS data feeds from around the world, a queryable API, and a range of user interfaces. Tlv2, like Tlv1, will be powered by open-source components. Tlv2's API will continue to be accessible without charge, and most of the Tlv1 API will continue to be available during the transition. (As before, we will enforce rate limits to ensure no one user hogs too many server resources; more on how rate limits will change below.)</p><p>What we are changing in Tlv2 is in support of three goals:</p><ul><li>Higher Performance</li><li>More Modular Architecture</li><li>Distributed Deployments</li></ul><h2 id="goal-1-higher-performance">Goal #1: Higher Performance</h2><p>Tlv1 successfully parses and imports GTFS feeds from thousands of transit agencies. However its &quot;FeedEater&quot; component slows down or halts on a handful of the very larger GTFS feeds — typically single feeds that cover entire countries. This has always been a constraint on Tlv1.</p><p>Interline's new <code>transitland-lib</code> (tlib) library solves this problem. Transitland-lib is a new transit data library written in the <a href="https://golang.org/">Go programming language</a>, which provides finer-grained control of memory usage, as well as much easier patterns for concurrency and parallelization of complex tasks. Transitland-lib replaces replaces FeedEater, and will be used for feed validation, pre-processing, and importing data into the Tlv2 database. Transitland-lib is efficient enough to handle the largest feeds in a small memory footprint, and is fast enough to encourage interactive use; imports that took hours with FeedEater are completed in minutes.</p><p>Transitland-lib began as an experiment by Ian Rees over the last winter holidays, and it now complete enough to power multiple Interline projects, from the San Francisco Bay Area Regional GTFS Feed (which merges ~30 feeds into one) to a transit-to-routing-engine pipeline that Interline built for another client (which covers transit service for an entire country!). We look forward to releasing transitland-lib under an open-source license shortly.</p><p>Transitland's most demanding API users have also hit performance limitations over the years. As part of Tlv2, we'll be providing bulk data dumps that give users another option. Use the Tlv2 API to explore data or power a small web app; use Tlv2 data extracts to power a large analysis, a giant web app, or a country-wide routing engine.</p><h2 id="goal-2-more-modular-architecture">Goal #2: More Modular Architecture</h2><p>Tlv1 has succeeded in part due to its &quot;monolith&quot; architecture. FeedEater, the API, and administrative operations all live within the same <a href="https://www.transit.land/documentation/datastore/">Transitland Datastore</a> codebase. This has allowed for efficient reuse of data models, helpers, and test code. The single Datastore codebase is also straightforward to deploy and configure for the canonical transit.land site. The Datastore codebase can be reused — some have in fact redeployed it for their own regional or internal GTFS management needs—but customizing and redeploying the Datastore is not straightforward.</p><p>For Tlv2, we're breaking the Transitland Datastore into modular components. Some components will be in Go (data processing), some will remain in Ruby (general back-end) and JavaScript (user interfaces). The canonical transit.land deployment will continue to use all. Other deployments by Interline, our partners, or open-source users may only use a subset. This more modular architecture will also allow deployments that connect Tlv2 components to internal data pipelines, routing engines, and other tools that may not be relevant to the canonical transit.land deployment.</p><p>While the software components of Tlv2 will be more modular, they will still be glued together using the data schemes developed for Transitland, including <a href="https://www.transit.land/documentation/concepts/onestop-id-scheme">Onestop IDs</a> and a common feed format spec (described below). Additionally, we will be sharing our database schema in versions appropriate for PostgreSQL and SQLite to help simplify additional application development, including outside of the canonical transit.land.</p><h2 id="goal-3-distributed-deployments">Goal #3: Distributed Deployments</h2><p>The Feed Registry at transit.land will continue to be our canonical list of GTFS feeds. However, some deployments of Tlv2 components may want to use just a subset of the Feed Registry or a private list of feeds. We also want to open up the canonical Feed Registry for more collaborative tending, beyond just staff from Interline and Trillium Transit.</p><p>The second of the two experiments that has led to Tlv2 is called the <a href="https://github.com/transitland/distributed-mobility-feed-registry">Distributed Mobility Feed Registry</a>. DMFR (for short) is a standard way of representing a list of GTFS feeds as one or more JSON files. It also currently supports GTFS-RT, and we expect it to extend to GBFS (bike rental) and MDS (e-scooter rental) in the future.</p><p>(Some history: This experiment actually started way back in the early tests of Transitland, before the fully built out Tlv1 monolith. It's still <a href="https://github.com/transitland/transitland-datastore">archived</a> on GitHub. Now we've come full circle to revisit and build out this approach.)</p><p>Soon the <code>transitland/distributed-mobility-feed-registry</code> repository on GitHub will become the source of truth for the Transitland Feed Registry of public open data feeds. We'll accept pull requests against the JSON files to add or edit feeds. This should substantially lower the burden for outside contributors to contribute new feeds and help manage existing records. However, this will be just be one repository of DMFR files. In effect we're blowing up the single Transitland Feed Registry and inviting the creation of many.</p><p>Transitland-lib can manage a datastore using one or more DMFR files, meaning that the canonical transit.land, distributed instances of Tlv2, and temporary interactive sessions with transitland-lib on the command line can all share the same representation for mobility data feeds. At Interline, we've gone one step further and also use DMFR files to configure some of our routing engines and any other workflow that takes two or more mobility data feeds as input. We welcome other consumers or transformers of GTFS, GTFS-RT, and related data to try a DMFR file for their own needs.</p><h2 id="tlv2-architecture-diagram">Tlv2 Architecture Diagram</h2><p>Now that we've introduced and discussed the new components of Tlv2, here's a diagram of how they connect:</p><figure><img src="https://www.interline.io/content/transit-land/tlv2/tlv2-architecture-diagram.png" alt="Tlv2 architecture diagram" width="768" height="942"></figure><h2 id="gradual-deprecation-of-tlv1">Gradual Deprecation of Tlv1</h2><p>Tlv1 requires a fair amount of attention and resources to maintain. While developing Tlv2, we've already had to split our attention. As we shift our focus to deploying and supporting Tlv2, we'll be gradually deprecating Tlv1. Don't worry — it won't be too quickly.</p><p><strong>Step 1: Tlv2 API Preview</strong> The initial release of Tlv2 will include a preview of a new <a href="https://graphql.org/">GraphQL</a> API that provides flexible, structured access to transit data. All new data will be available through this API from the start. API access will require a key. Sign-up will be free. We will institute tight rate limits at first and increase them over time, as we better understand the type and complexity of queries that users run.</p><p><strong>Step 2: Deprecate Tlv1 Schedule API</strong> Immediately upon Tlv2 release, we will stop importing new <a href="https://www.transit.land/documentation/datastore/schedules.html">schedule data</a> into Tlv1. The <code>ScheduleStopPair</code> data model is the most expensive part of Tlv1 to run and maintain. We'll first stop imports, keeping the API available against the last imported version. We'll share tutorials on how to switch to the Tlv2 GraphQL API to access schedules. Then, after sufficient notice, we'll empty old Tlv1 schedule data and remove that API endpoint.</p><p><strong>Step 3: Other Tlv1 Entity API Endpoints</strong> While the Tlv2 GraphQL API will make a number of complex queries much simpler than with the current Tlv1 API, it may take a while for us to make all Tlv1 query options available in the Tlv2 API. During this time, we'll try to continue to power the Tlv1 APIs (with the exception of the schedules endpoint). We'll recommend that you build any new applications on the Tlv2 API, in case we do have to announce any specific incompatibilities during the Tlv1-to-Tlv2 API transition.</p><p>We'll post updates to this site. Or watch <a href="https://twitter.com/transitland">@transitland</a> and <a href="https://twitter.com/interline_io">@interline_io</a> for updates on Twitter.</p><h2 id="how-you-can-help">How You Can Help</h2><p>Here are ways you can help with the rollout of Tlv2:</p><ul><li>Provide your input on Tlv2 by taking our <a href="https://docs.google.com/forms/d/e/1FAIpQLSdmhW28zcP1kBMBkmelAt7OQGqKjRcoILjsbZvGXLsGfmFNGw/viewform">survey and signing up for the beta tester list</a>.</li><li>Comment on the <a href="https://funding.communitybridge.org/projects/transitland">DMFR GitHub repository</a>. Contribute edits once we migrate over the Feed Registry to DMFR files.</li><li>If you work for a GTFS producing transit operator or mobility provider, <a href="mailto:info@interline.io">contact Interline</a> to learn more about &quot;Tlv2 on premise&quot; and regional GTFS feeds. It's consulting projects like this that help us serve both mobility providers and further the development of transitland-lib.</li><li>Contribute financially to the upkeep and growth of Tlv2 through the Linux Foundation's <a href="https://funding.communitybridge.org/projects/transitland">CommunityBridge donation page for Transitland</a>. These contributions go directly toward upkeep of the canonical transit.land.</li></ul>]]></content:encoded></item><item><title><![CDATA[Transitland Continues in 2019]]></title><description><![CDATA[Just like a garden, open-source and open-data projects require continual tending. With 2019 beginning, we're glad to share more widely these plans for Transitland's ongoing tending and growth as an open platform.]]></description><link>https://www.interline.io/blog/transitland-continues/</link><guid isPermaLink="false">672559d3b62841000136ee31</guid><dc:creator><![CDATA[Drew Dara-Abrams]]></dc:creator><pubDate>Tue, 08 Jan 2019 08:00:00 GMT</pubDate><media:content url="https://www.interline.io/content/images/2024/11/transitland_logo.png" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/2024/11/transitland_logo.png" alt="Transitland Continues in 2019"><p>Just like a garden, open-source and open-data projects require continual tending. During 2018, we quietly maintained the core of Transitland's code and data. We also worked to put in place new partnerships and structures to support Transitland after the <a href="https://mapzen.com/blog/shutdown/">shuttering of Mapzen</a>. With 2019 beginning, we're glad to share more widely these plans for Transitland's ongoing tending and growth as an open platform.</p><h2 id="core-support-and-maintenance">Core Support and Maintenance</h2><p>We have a combination of organizations that are together supporting Transitland:</p><ul><li>Transitland's open-source code is moving to the <a href="https://www.linuxfoundation.org/">Linux Foundation</a>, allowing code use and contributions by any and all.</li><li>Amazon Web Services continues to provide servers and access for Transitland's API users, thanks to awards from the <a href="https://aws.amazon.com/earth/research-credits/">Earth on AWS Cloud Credits for Research Program</a>.</li><li><a href="https://www.interline.io/">Interline Technologies</a> (the firm that I am now a part of) has been donating resources to maintain code and is now also offering professional services and support to the companies that depend on Transitland APIs.</li><li><a href="https://trilliumtransit.com/">Trillium Solutions</a>, a team of experts at GTFS production, is helping to curate submissions to the Transitland Feed Registry and maintain existing records.</li></ul><p>Previously Mapzen was a single &quot;keystone&quot; supporter for Transitland. Now we have a growing list of &quot;tentpole&quot; supporters for Transitland's code, servers, and data. Together in 2018, we quietly shifted Transitland on to a new generation of infrastructure, fixed pressing bugs, and gradually increased feed coverage. Transitland now aggregates data for 2,466 transit operators across 53 countries! Each month, the API handles 5 million queries!</p><figure><img src="https://www.interline.io/content/transit-land/transitland-continues/transitland-operators-by-country-2019.png" alt="bar chart of Transitland operators by country" width="257" height="1158"></figure><p><em>Operators records in Transitland, by</em> <a href="https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2"><em>two-letter country code</em></a><em>.</em></p><p>Now that Transitland again has a stable foundation of support, post Mapzen, we can return to feature development, major data additions, and community outreach.</p><h2 id="growth-and-development-in-2019">Growth and Development in 2019</h2><p>We're working together with a series of partners and sponsors on new Transitland platform features and data additions in 2019. The list of topics tentatively includes:</p><ul><li><a href="https://www.interline.io/blog/transportation-research-board-funds-gtfs-realtime/">GTFS-realtime support</a></li><li>feed validation and best-practices report cards</li><li><a href="https://www.interline.io/blog/metropolitan-transportation-commission-selects-interline/">feed merging</a></li><li>&quot;Transitland Tiles&quot; for bulk download and analysis</li><li>website and documentation updates</li><li>an experimental, distributed replacement to the Transitland Feed Registry</li></ul><p><strong>Technical folks</strong>: As you've likely guessed, many of these new experiments require a level of performance that Transitland's current mix of scripting languages cannot always provide. My colleague <a href="https://www.interline.io/about/">Ian Rees</a>, who is Interline's principal engineer, is leading an effort to re-architect key Transitland components in the high-performance Go programming language. Transitland's technical architecture has always had the goal of accessibility — now we're pursuing both accessibility <em>and</em> performance.</p><p><strong>Professional users of Transitland APIs</strong>: We've heard from many of you in 2018 that new functionality is nice, but that dependable service is even more important. Interline is now preparing professional services and support around the Transitland APIs. <a href="http://eepurl.com/dmWHln">Sign up for the Interline newsletter</a> for related announcements or contact <a href="mailto:info@interline.io">info@interline.io</a> with questions. Note that these commercial services supplement and do not change existing free access to the Transitland APIs.</p><p><strong>All Transitland Community Members</strong>: Thanks for sticking with us over the past year. Despite all the work happening behind the scenes, we weren't able to share full news of Transitland's progress publicly. We're excited to return to our previous cadance of public announcements and conversations. Watch this website for updates. We also welcome questions and participation from potential partners in the above topics and others — please write to <a href="mailto:hello@transit.land">hello@transit.land</a>.</p><p>Here's to a new year of open transit data!</p>]]></content:encoded></item><item><title><![CDATA[Bringing Back the Spirit of Map Mashups: Combine Open Geodata APIs using HERE XYZ]]></title><description><![CDATA[Interline and HERE are collaborating to make Interline's open data services like OSM Extracts and the Transitland API easy to combine, mix, filter, analyze, and visualize using the new HERE XYZ platform. ]]></description><link>https://www.interline.io/blog/here-xyz-open-geo-data/</link><guid isPermaLink="false">6725453eb62841000136ecbc</guid><dc:creator><![CDATA[Drew Dara-Abrams]]></dc:creator><pubDate>Mon, 01 Oct 2018 07:00:00 GMT</pubDate><media:content url="https://www.interline.io/content/images/2024/11/xyz-tutorial-1-animation.jpg" medium="image"/><content:encoded><![CDATA[<img src="https://www.interline.io/content/images/2024/11/xyz-tutorial-1-animation.jpg" alt="Bringing Back the Spirit of Map Mashups: Combine Open Geodata APIs using HERE XYZ"><p>At Interline, we spend much of our time with open geodata APIs. We create our own open geodata APIs (like <a href="https://www.transit.land/">Transitland</a>) and we use others (for example, whenever we need to throw a bunch of GeoJSON on a base map). At their best, open geodata APIs are fun — you get to combine pieces together to create something new. Then again, public APIs can have many limitations — combine together a few and you can end up with the worst of all worlds: duplicate data, misregistered overlays, a slow user experience, incompatible data formats… With all these mixed experiences in our minds, we’ve been playing with the initial beta of <a href="http://explore.xyz.here.com/">HERE XYZ</a>. It’s a brand new developer service from one of the oldest names in geodata.</p><p>HERE XYZ provides the full set of components that “modern” geo developers have come to expect: GeoJSON input and output, “slippy map” libraries, a RESTful API, a JavaScript SDK, a cross-platform CLI, base maps and styles. As we’ve been experimenting with the HERE XYZ beta, we’ve found it provides some unique combinations that make it especially well suited to combining open geodata APIs — especially in large quantities.</p><p>Combining geodata is nothing new. <a href="http://ladprofile.weebly.com/ian-mcharg-1920-2001.html">Ian McHarg</a>, a prominent environmental designer, printed maps on transparent plastic sheets and overlaid them atop each other, inspiring the idea of layers in GIS (<a href="https://en.wikipedia.org/wiki/Geographic_information_system">geographic information systems</a>):</p><figure><img src="https://www.interline.io/content/images/2024/11/ian-mcharg.jpg" alt="photo of Ian McHarg" width="1100" height="742"></figure><p><em>Image credit: University of Pennsylvania</em></p><p>More recently, Google Maps brought us <em>mashups</em>. At first, it involved hacking the Google Maps JavaScript code in order to overlay <a href="https://www.nytimes.com/2005/12/11/magazine/doityourself-cartography.html">crimes in Chicago</a> and <a href="http://www.housingmaps.com/">Craigslist house listings</a>:</p><figure><img src="https://www.interline.io/content/images/2024/11/housingmaps2.png" alt="screenshot of old housingmaps.com" width="1088" height="684"></figure><p><em>Image credit: housingmaps.com</em></p><p>Neither hacking nor reverse-engineering are required any more to combine multiple sources of geodata in a web browser. Companies like Google, Esri, Mapbox, Carto — also a now defunct start-up where we previously worked, called Mapzen — all offer accessible APIs for creating web maps. We’ve also been freed of many of the constraints on dataset size in 2005 mashups. Original mashups involved drawing points and other geographic features on top of base-map images, with a low limit on the number of these vector features that could be drawn at once. More recent techniques send both the base map and overlays as vector tiles. Instead of an image, a vector tile is effectively a square of data, which can be pre-generated by a server. Many vector tiles are then loaded and drawn by your web browser simultaneously.</p><p>We’ve left behind the constraints of mashups — and it also feels like we’ve forgotten the fun of mashups. Vector tiles help greatly with performance, but often add complexity to the overall set of steps required to combine together existing and new data sources on a web map or another type of visualization.</p><p>Our experiments with the HERE CLI and the XYZ API are bringing back that creative spirit of 2005 mashups. The XYZ platform generates vector tiles near instantly for any new imported data sources. The HERE CLI and XYZ API provide a range of ways to import GeoJSON files, connect to APIs, or stream in from other CLI tools. It’s the best of 2005 and 2018. If you use the SDKs to style your web maps to look like the transparency overlays in Ian McHarg’s book <em>Design With Nature</em>, it’s the best of 1969 proto-GIS, too.</p><p>We’re collaborating with the HERE XYZ team to turn our experiments into tutorials that demonstrate how Interline’s open geodata services can be combined, mixed, filtered, analyzed, and visualized. In the first tutorial, you’ll fetch and filter data from <a href="https://app.interline.io/osm_extracts/interactive_view">Interline OSM Extracts</a>:</p><figure><img src="https://www.interline.io/content/images/2024/11/xyz-tutorial-1-animation-2.jpg" alt="" width="918" height="756"></figure><p>In the second tutorial, you’ll query the <a href="https://www.transit.land/">Transitland</a> API repeatedly to build up an analysis and a web map of just not subway locations but also the frequency of how often each subway line operates. (Especially when working with geodata for transportation applications, both space and time matter.) We’ll show you how to do this for the entire planet:</p><figure><img src="https://www.interline.io/content/images/2024/11/xyz-tutorial-2-animation-3.jpg" alt="" width="800" height="526"></figure><p>The sample projects and tutorials take intermediate and advanced users on a tour through some of the unique features of XYZ and the HERE CLI:</p><ul><li>filtering Interline OSM Extracts using OpenStreetMap tags</li><li>writing scripts that stream geodata from external APIs into an XYZ space using the HERE CLI</li><li>using multiple API queries to aggregate together properties about the same features (identified by unique IDs, such as <a href="https://www.transit.land/documentation/concepts/onestop-id-scheme/">Transitland Onestop IDs</a>)</li><li>quickly building global tile sets</li></ul><p>We’re experimenting with additional features, for creating a new generation of mashups, and we look forward to sharing more soon.</p><p>Now, get started with our <a href="https://www.interline.io/docs/here-xyz/">first two tutorials on combining HERE XYZ, Interline OSM Extracts, and Transitland</a>.</p>]]></content:encoded></item></channel></rss>