Florida tolls: how to maintain

Files: /srv/toll/draft/FL, last built 2026-10-10 02:05 ET · the FL toll page · map test · facts below are read from the files each time this page is built (python3 /home/geo1/system/handbuilt/maintain_pages.py FL)

Procedure for this state

Florida is the most hand-made state: some operators' amounts are typed into code (below). The printed tables of Florida's Turnpike and CFX are rebuilt from the archived PDFs by one script.

When to check

• Before July 1: Florida's Turnpike (FTE, toll rate indexing: rule 14-15.0081 "New toll rates will be in effect July 1"), CFX ("adjust annually 1.5 percent or to the annual Consumer Price Index"), THEA.
• Around October 1: county facilities (Card Sound, Osceola: "Effective 10/01/2026").
• Whenever FTE posts a new regional PDF. The URLs in urls.txt carry dated file names: edit them by hand.

Sources

• FTE regional PDFs (FL-T01..T22): fte_south_florida, fte_south_central, fte_central, fte_west_central, fte_north_east, fte_panhandle; CFX: cfx_toll_rates_2026 (FL-T23..29, T46); other operators THEA, Mid-Bay, Lee, Miami-Dade causeways, Card Sound, Escambia, Osceola, GIBA, GMX, Dunes; express-lane rule pages. All via python3 fetch_list.py FL [names].
• Positions: FTE TurnpikeBaseData (fte_toll_plazas_gantries layer 10, fte_interchanges layer 3, fte_mile_posts) and FDOT RCI layers (fdot_rci_*); fetch_layer.py FL <name> <url> pages through ArcGIS layers. FTE layer positions win over RCI.
• Fetched by hand (no script): fte_toll_calculator/…/facility_elements.json from https://ftcv3-prd.techworks.dev/api/Map/facility-elements (express lanes FL-T47..T55, Broad Causeway, Orchard Pond); cfx_calculator_register/…/mapdata.json (the var mapData on cfxway.com/for-travelers). gmx_expressway_map is not in urls.txt.

Rebuild

1. Printed rates: /home/geo1/maps/toll/FL/printed_rates.csv (2028 rows). /home/geo1/system/handbuilt/fl_printed.sh rebuilds it from the newest archived PDFs: fl_rows.py dumps the six Turnpike regional PDFs' rows, the CFX schedule's rows are taken by amount count, and fl_build.py writes the table. It prints unchanged or the differences; fl_printed.sh --write takes a changed result (the old file is kept with the date). Rebuilt on 2026-10-09: identical to the file in use. A new regional PDF with a new table or a changed title also needs FTE_TABLES in fl_build.py updated (title, county line, effective date as printed, in PDF order).
2. Typed in code: THEA, Mid-Bay, Lee, Miami-Dade, Card Sound in fl_build.py hand(); Escambia, Osceola, GIBA, GMX (5), Dunes in fl_state.py HAND; Mercy Drive META_ROW; FTE effective dates in FTE_TABLES.
3. Express lanes: python3 express_booths.py (reads facility_elements.json, writes osm/fl_express_booths.json, osm/fl_lane_ways.json). Amounts are the calculator's minimums (time_band=dynamic), charged as the floor with a note.
4. Full chain with tollnode_ways.py FL before toll_ways.py FL. Ramp fixes: register_ramps.py and calc_ramps.py (needs /tmp/fte_elements.json, /tmp/moves.jsonl and Valhalla on 127.0.0.1:8002 — the /tmp inputs are not kept), then toll_ways.py FL again. OSM box -87.7,24.3,-79.8,31.1.

Verify

• python3 fl_verify.py compares transcribed amounts with the archived PDFs' text (2026-10-09: 206 of 206 rows verified, 0 mismatched).
• fl_pricecheck.py compares the printed 2-axle amount with OSM price tags within 150 m (last: 328 checked, 35 differ, 2026-10-07).
• No record on disk of a trip-by-trip check against FDOT's calculator.

Watch out

• FETCHED and SRC_FETCHED dates are hard-coded in fl_state.py; cfx_calculator_register is missing from SRC_FETCHED.
• PTS uses glob(...)[0]: the oldest RCI fetch, not the newest.
• 66 hand positions (HAND_POS) are tied to OSM node ids: re-check after an OSM refresh. Wekiva "53 - ORANGE PLAZA" is geometry only; Hammock Dunes eastbound comes from an OSM note.
• Osceola's "Effective 10/01/2026" is not parsed: its rows carry _observed.
• fl_cross.py, fl_gapcand.py, fl_osmline.py read ~/system/scratch/fl_toll.osm; fl_rateblocks.py needs /tmp/llm_exp/s1f_exp.py; fl_xcheck.py and fl_gapcand.py read a calc/ folder that does not exist.

The chain every state shares

Hosts: geo1 (192.168.50.220) holds the sources, builders, drafts, map and API; b100 (192.168.50.14) is the test client. All times are Eastern.

1. Refresh a source

1. Fetch into a new dated folder: python3 /home/geo1/system/handbuilt/fetch_list.py FL [name ...] (no names = every line of urls.txt). A new source: add a line to urls.txt first, then fetch it by name.
2. A site that refuses geo1 (HTTP 403) or scripts: fetch it on b100 in headless Chrome with node ~/apitest/fetch_b100.mjs <out> <name>=<url> ..., then rsync -a <out>/ geo1@192.168.50.220:/home/geo1/maps/toll/FL/sources/. Its meta.json records that it came from b100.
3. Compare the new file with the previous dated one (diff, pdftotext -layout for PDFs). Same content: nothing to do. Changed amounts or a new effective date: rebuild (step 2) and update the expected amounts of the affected regression trips from the operator's own figures.

1b. The corpus (NJ, PA, VA start from it; DE is published from it)

python3 /home/geo1/maps/toll/bin/tollup.py FL update fetches the adapter's sources (bin/adapters/fl.py), stores a document only when its content changes, writes one rate file per version under /home/geo1/maps/toll/FL/rates/ and appends every price change to history.csv (every run to runs.log). TOLL_WEB=/home/geo1/maps/toll/corpus python3 /home/geo1/maps/toll/bin/publish.py FL writes the corpus /home/geo1/maps/toll/corpus/FL from it (DE: plain publish.py DE writes /srv/toll/DE). Never hand-edit either. Then rebuild the draft (step 2) so it picks up the new rates.

2. Rebuild

• Amounts or schedules changed, toll points unchanged: cd /home/geo1/system/handbuilt && python3 fl_state.py
• The full chain in one command: bash /home/geo1/system/handbuilt/chain.sh FL (logs in /tmp/fl1.log ... fl6.log; it prints the points, any point on no road and the untied count). The builders written since October 2026 share state_kit.py (sources, booths, terms, rows, write) and own_state.py (keeps a state's untied list to toll nodes inside the state, by the local geocoder; cache osm/node_state.json).
• Toll points added, moved or renamed, or a new OSM extract: the full chain (about 2-4 minutes):
  cd /home/geo1/system/handbuilt; H=$(ls osm/fl_highways_*.geojsonseq); J=$(ls osm/fl_junctions_*.geojsonseq)
python3 fl_state.py && python3 osm_streets.py FL $H $J && python3 fl_state.py && python3 osm_snap.py FL && python3 toll_ways.py FL && python3 fl_state.py
• Read the end of toll_ways.py's output: nodes claimed by two points: {} and points on no road: [] must both be empty.
• A point whose booth is an OSM way (OSM way <id>) needs that way in osm/fl_lane_ways.json (the builder writes it). A point on a road priced entry to exit needs gantry in its location name, or toll_ways.py treats it as a position-only exit marker.
• Rebuilding NY changes osm/ny_not_toll_nodes.json (congestion-zone gantries that are not tolls); every state's untied list leaves those out, so rebuild NJ and PA after NY.

3. Load it into the API and test from b100

1. The API reads the toll pages and tolls.js when it starts. Restart it: cd /home/geo1/maps/api && kill $(cat logs/test.pid); (nohup /home/geo1/maps/node/bin/node server.mjs > logs/server.log 2>&1 & echo $! > logs/test.pid) (it is started by hand, not a service).
2. From b100 only: python3 ~/apitest/run.py ~/apitest/site/cases.json. Every trip must be OK. Add a trip for every rate or rule you change, with the amount taken from the operator's own source.
3. Engine change (tolls.js): edit /home/geo1/maps/web/tolls.js, check with /home/geo1/maps/node/bin/node --check, copy to /srv/maps/tolls.js with sudo install -o www-data -g www-data -m 644, restart the API, run the trips.

4. OpenStreetMap refresh (all states at once)

The builders match toll points to the OSM way ids the router drives, so the extracts here must come from the same us-latest.osm.pbf the router (Valhalla, /home/geo1/maps/valhalla_data) was built from (now 2026-09-27). New OSM data means: rebuild the router tiles, then for each state cut the box, rebuild its OSM inputs and run the full chain, then compare untied_toll_nodes.csv and the estimated positions below. The box for FL and the cutting commands are in the state's procedure above; the toll-node and way index comes from python3 tollnode_ways.py FL.

5. Publish

A rebuild writes the draft (/srv/toll/draft/FL); the published page (/srv/toll/FL) does not change. python3 /home/geo1/maps/toll/bin/promote.py review FL lists the draft for review: the map and the API then read it instead of the published page. Run the regression trips from b100. After approval, python3 /home/geo1/maps/toll/bin/promote.py publish FL copies the draft to /srv/toll/FL (the previous page is kept under /home/geo1/maps/toll/FL/published/<time>/) and takes it off the review list. After a change, update the coverage line for FL in the API page (/api.html, generator /home/geo1/maps/api/doc/api_page.py) and rebuild this page: python3 /home/geo1/system/handbuilt/maintain_pages.py FL.

Sources (39)

Each fetch is kept in its own dated folder under /home/geo1/maps/toll/FL/sources/<name>/; the builder always reads the newest one, so a new fetch takes effect at the next rebuild and the old one stays for comparison.

Facilities (56)

Positions placed by estimate (0): re-check when OpenStreetMap or the operator changes

None: every position comes from an official layer or a mapped toll node.

Decisions by rule

R0: 9, R1: 38, R2a: 44, R2b: 72, R2c: 1, R2d: 22, R2e: 10, R2f: 56, R3: 7, direction: 221, mile: 1, positions: 5, source: 1, statewide: 44 (all in decisions.csv).

Open gaps (0)

None.

Untied OSM toll nodes: 225

Toll booths / gantries mapped in OpenStreetMap on or near this state's roads that no toll point claims; a route through one lists it under unpriced. After an OSM refresh, look at new ones here (untied_toll_nodes.csv): a new gantry on a priced road means a point is missing.

Regression trips for FL (2)

Run from b100 (never on geo1): python3 ~/apitest/run.py ~/apitest/site/cases.json. Every trip must come back OK; a changed amount is either a rate change (update the expected amount from the operator's own source) or a fault.