M: Would you mind finding out, if any studies have been made, and if so, what their results have been regarding the relationship between, how would I put it, block length, speed limit, and traffic flow? What I'm talking about is the idea that if you have a certain speed limit and a certain distance between stoplights in an urban or suburban setup, is there any kind of quantification of the advantages and disadvantages of having turns and stuff every X feet or something dependent upon that speed limit? Like I just was at a turn that I had to take that was not at a stoplight, and I'm sitting watching the flow of traffic based on the lights in front of and behind me, and I realized that if things were timed badly at certain times of day, there would be a situation in which my turn would be nearly impossible simply because of that. So please go online and see what you can find for me about that.

G: [Non-text content: thoughts; content_type=thoughts]

G: [Non-text content: thoughts; content_type=thoughts]

G: [Non-text content: reasoning_recap; content_type=reasoning_recap]

G: TL;DR: Yes—there’s a lot of research. In short, (a) signal spacing / block length and (b) the speed you coordinate for (often close to but not always the posted speed) jointly determine whether traffic “platoons” move in waves with usable gaps between them. Closer spacing and/or badly chosen coordination speeds create more stops, fewer gaps, and tougher unsignalized turns. Wider spacing (to a point), clean access spacing, and well-set offsets grow the green “bandwidth,” keep speeds steadier, and make those between-platoon gaps big enough to turn across traffic. citeturn0search19turn0search13turn0search5

What studies actually say

Practical takeaways (you can picture these on your corridor)

  1. If signals are too close (<500 ft): expect queue spillbacks and weak green-wave effects; turning across traffic becomes hard because platoons keep arriving without healthy gaps. citeturn0search19
  2. Around 0.2–0.5 mi spacing with a coordinated progression speed matched to the corridor (often near the posted speed, sometimes a little lower) you get stronger platoons and longer inter-platoon gaps—that’s when mid-block turns are most feasible. citeturn0search7turn0search21
  3. At higher posted speeds (e.g., 45 mph suburban arterials), longer spacing (½–1 mi) can still coordinate well, often with longer cycles—again producing predictable gaps between waves. citeturn0search19
  4. Irregular block lengths complicate offsets; dispersion between signals eats your bandwidth. The fix is better offsets or, if geometry is baked in, access consolidation so fewer people must turn across the stream mid-block. citeturn0search13turn0search5

Why your unsignalized turn sometimes felt “nearly impossible”

When a corridor is coordinated for through traffic, vehicles leave each upstream signal in platoons. If the green waves and offsets are tuned tightly (or if spacing is short/uneven), those platoons can overlap, leaving very few usable gaps at your driveway or side street. Change the offsets—or widen spacing / reduce access points—and usable gaps reappear between platoons. citeturn0search13turn0search19

Design/ops levers agencies use

If you want, tell me a typical posted speed and approximate block length you see on the corridor you’re thinking of, and I’ll sketch a quick, numbers-based scenario (cycle length, progression speed, expected platoon headways) to show when those turns will feel easy vs impossible.