Category Archives: I Told You So

Project Connect Phase 1 Document Revealed!

I discovered this today, and it clearly shows Project Connect did, in fact, rate the top four options against each other (and some others we hadn’t heard of) in a tournament, of sorts, to get to where we are now. It’s a shame it took this long for this proof to be revealed; I regret all my complaints up to this point. Click on the image for the full-size version.

20140320ProjectConnectBracket

Project Connect Phase 1 Lie Number 1

Lie #1 during Phase 1 of Project Connect was the justification of the collapsing of the West Campus and UT “subcorridors” (zones) into the Core subcorridor/zone “so we could ensure they would both be served by any initial alignment”.

At the time, on November 1st, I made this post, which asserted that there was no way this decision was being made to ‘serve’ West Campus; that, in fact, it was being made to avoid having to serve West Campus (which would obviously imply a route on Guadalupe).

Now, the final alignment through campus has been decided. Let’s see what we got. Click on most of these to make them bigger.

From Project Connect’s presentation to the CCAG on Friday February 21st:

20140221_PC_Campus_Area

Huh. Look at that. Not only do we not even see West Campus, but we can’t even see the western half OF campus. What a shock!

But it’s probably just a misleading image, right? There’s no way Project Connect would have told everybody they were going to serve West Campus and then not do so – West Campus must be just right underneath the words on the left, right?

Let’s see how far away a couple points on San Jacinto are from a location two blocks west of Guadalupe, using Google Earth. (The center of density in West Campus is not on Guadalupe – the best height entitlements are actually several blocks to the west. A ‘population center’ of West Campus in a few years will likely be 3 or 4 blocks west of Guadalupe; so me using 2 blocks is being generous to Project Connect).

Remember that the rule of thumb in transit planning for years has been that most people will not regularly walk more than a quarter of a mile from their home to their transit stop (or from their transit stop to their office). A few will do more, but the quarter-mile rule ensures you will get most of your possible transit market. Some people lately have tried to assert that good rail transit can do the same thing with a half-mile walking radius; in my opinion, this works in some cities where parking is quite difficult, but primarily on the home end of the trip, not the office end.

First, from 21st and San Jacinto to two blocks west of Guadalupe on 21st:

20140221_21SJ_TO_WC

 

0.6 miles. The main density of West Campus is definitely not served by San Jacinto even by the most generous standard. Guadalupe itself is 0.48 miles away; served only barely by the most generous standard. In other words, the side of campus with the most activity is well outside the commonly accepted walking radius and just barely inside the most generous one.

Now let’s try 24th.

20140221_24SJ_TO_WC

 

0.58 miles to where West Campus’ density starts. West Campus is not served at all by a stop here, either.

Finally, Dean Keeton and San Jacinto:

20140221_DKSJ_TO_WC

 

 

 

Nope. 0.54 miles to the start of West Campus’ density. To the start. Still outside even the most generous reading of “served”.

Project Connect, the claim of yours made back in November is still a lie.

Lie-stamp

What bad guys can accomplish

Over the last few years, I’ve written many times on this blog that Capital Metro was eliminating half of the local service on the route 1 corridor when the route 801 (MetroRapid, or so-called “Rapid Bus”) started service. Many, many times. Here’s one example from last June. Here’s another from October, 2011.

Recently, hundreds of people have expressed surprise and dismay when the events I’ve been telling you about for years actually came to pass. Richard Whitaker came out of the woodwork and talked to me while I was practically dying of the flu on a business trip in Atlanta, shocked that the locals were being eliminated. Nobody on reddit saw it coming. Nobody in the local TV media saw it coming.

Now it’s here, and again, everybody is surprised and dismayed.

The dismay is obvious. But why the surprise?

Honestly? It’s due, in major part, to the fact that one particular employee of Capital Metro has spent years convincing decision-makers and media-members that the author of this blog is a troll who has no idea what he’s talking about. Yes, I know this for a fact.

The last major exchange that Capital Metro employee and I had is still burned into my mind. It was on the same topic as the blog link featured further down this page, but I have yet to be able to get a twitter search tool to bring up the thread. Basically, I spent a couple of hours while on a layover in the DFW airport a couple of years ago making the fact-based case in that blog post below (about the #9 being cancelled without its planned replacement) in tweet form, calmly and rationally, only to be repeatedly told by that Capital Metro employee that I was wrong; and at the end, to be cut off again and labelled a troll. After that, I lost a considerable amount of access I previously had to some members of the media, city council and staff, and other decision-makers and thought leaders. I observed some activity myself where said Capital Metro employee was undermining yours truly with media members, and heard much more from others.

Today, that same Capital Metro employee was given an attaboy by somebody who I respect for supposedly dealing with constructive criticism well. This doesn’t make me feel happy about that person I respect, and it doesn’t make me happy about trusting the organization he leads. I hope this is just a momentary mistake.

Here’s the post which begins by showing how the Capital Metro employee in question really deals with constructive criticism, and my fact-based rebuttal to his dismissive aside to a third-party. Click the big words right after this.

Whole Shakers Of Salt, from 2010

I’ve been told by the leaders of the organization I mentioned above that I’m wrong for attacking said Capital Metro employee, even after that employee lied repeatedly during the Project Connect process. I’ve let leaders of the organization I mentioned above know that the Capital Metro employee in question made some clumsy threats against another supporter of said organization which were not consistent with the image of that Capital Metro employee that they continue to firmly grasp to. After all this, I find myself wondering what it takes to make those people angry. I know I’ve done so, by taking issue with their strategy and tactics both privately and publically, but apparently actually lying in order to steal political capital to support a hare-brained, mendacious, underhanded political process is just A-OK, as long as they see you a lot and you smile and shake their hand while stabbing them in the back. You’ll still be their chum, and still get lionized for your ability to handle constructive criticism.

Again, I hope I’m wrong. But like them, I’m reading some tea leaves.

MetroRapid: What you REALLY need to know

A comment I posted to this PR fluff piece by Movability:

What you need to know is that this REDUCES frequency for current 1/101 riders north of the river, because the 1L is being eliminated along with the 101. If you’re boarding at a stop served by both the 1 and 101 today, the same total number of 1 and 801 buses will stop there in the future; the mix will just change to fewer 1s. If you’re boarding at a stop served only by the 1L/1M today, you’re going to lose half your buses.

What you need to know is that this was projected to be no faster than the 101 in early plans, and now data sent to google maps actually shows it being slower than the 101 (not sure if this is legitimate or a hiccup, but it’s not a good sign).

And finally, what you need to know is that this will cost riders a lot more to ride. Despite the fact that the 1 route was quite likely the least subsidized bus route in the city before this change, fares are going up due to this change (the 801 will cost quite a bit more than the 1 did).

The FTA and last night

if you parse Langmore’s comments it makes me think he was asking them about cancelling the project now (rather than moving the middle third in 8 years); and Project Connect staff were vocal and public at the beginning of the process that Lamar/Guadalupe was on the table and that we should not act as if rapid bus precluded urban rail there.

They either lied then or they’re lying now. Personally, I believe they lied then in order to try to get more buy-in for this process (I myself believed Rapid Bus effectively precluded urban rail and was convinced to believe it might not by those staff members); but it could be now, too; the mixed messages last night about the FTA maybe considering Rapid Bus ‘permanent’ versus what the City Council eventually threw in as a fig leaf is just one obvious indicator.

The fact that the guy who ran the Rapid Bus project at Capital Metro came up and spoke in favor of Lamar and said he doesn’t buy the FTA argument should tell you something.

No sir, I don’t buy it.

No, the Riley fig leaf last night changes nothing – it does not commit to a fair evaluation of the Lamar/Guadalupe ROUTE against whatever is shat out for Highlandmall or Highlandmueller; and it does not force a real answer about the FTA’s opinion about moving Rapid Bus in 2020 or 2022 or whenever (instead of John Langmore’s claims that made it pretty clear he implied to them he wanted an opinion on cancelling it today, in 2013). Its only tangible effect would be an attempt to delay opposition until it’s too late.

I’m continuing to urge all transit advocates to vote AGAINST the bond referendum in 2014.

Reaction from around the dial

Going backwards; reaction from around the country to the Project Connect rec and the Mayor’s endorsement of the process and the result:

Stephen Smith at Next City has just published Transit Advocates None Too Pleased About Austin’s Light Rail Corridor Selection in which I am quoted as well as several friends-of-the-crackplog.

Pretty much every urbanist/transitophile in Austin came out of the woodwork last night and contested JMVC’s spin on Project Connect, for which I am eternally grateful as I was tied up learning how to be a BB-gun rangemaster and then trying to sleep off this cold before the campout this weekend.

In Fact Daily (subscription) published a story yesterday in which I square off against the mayor quote for quote.

Friend-of-the-crackplog from LA “Let’s Go LA retweeted me: “.@JimmyFlannigan If the first line isn’t a slam dunk, overflowing with people, we never get to build line 2. Rigged process = dumb decision.”

Several folks from twitter who work in transit around the country that I mentioned during my speech on Friday included Jeff Wood from Reconnecting America (“I’m going to use this as an example of bad transit planning forever”) and Patrick McDonough from RTP (“Be on lookout for “design alternatives” under study in EIS to see if original Mueller alignment has “lower impacts.” #WhatASham”)

So far, not one single person outside of Austin with any history on transit has said they agree with this recommendation.

Summary of yesterday

Update: The video’s already up; you can see my speech here (click on Citizens Communications to jump to me).

I spoke in citizens’ communication yesterday to the CCAG. Gave up a half day to do so (had to be there to sign up at 1:15; limited slots; ended up getting there shortly after noon to make sure I got my spot). Found out as the meeting started that citizen communication is the LAST thing. Uh-oh.

My original speech was going to be about why Rapid Bus should not preclude rail in the Lamar ‘subcorridor’. Since I ended up giving my speech AFTER the ridiculous announcement that it’s going to be Highland ‘and ERC’; I ended up rewriting my speech into an indictment of the process, which has been gradually revealed to have been designed to generate the predestined conclusion that Mueller (i.e. Not Lamar) should be the initial route. (Note that Highland is, as I’m calling it, “Mueller in drag”; Kyle Keahy made sure to mention many times that it takes you right to the edge of Mueller).

Amazingly, Scott Gross had the gall to put up a slide showing an overwhelming citizen preference for Lamar over the next closest two alternatives; and then proceeded to argue it meant nothing; that their made-up or mangled data which led to misleading conclusions was somehow more valid than the opinion of the transiterati in this town. Well, he just implied that; they never went back and mentioned the overwhelming vote for Lamar again.

My thoughts on the reason for this choice largely mirror Chris Bradford, aka the Austin Contrarian, who made this excellent comment in response to Julio’s blog post:

I don’t agree with B-.

We all agree that ERC should be part of a fully built-out urban rail system. It is highly unlikely that it will be built first, though. The obstacles are just too high. Building another bridge over LBL is very tricky, and very expensive. Then they will have to lay a mile of track and get across I-35 just get to East Riverside’s western edge. Given that any initial starter line will (and should) connect downtown and UT, the next logical phase is to keep heading north. Heading across the lake and then down East Riverside for the first phase will require a really high initial bond amount, giving voters sticker shock.

If ERC isn’t a genuine first-phase option, then why was it named? I believe it is being dangled out there to prevent the Highland opponents from mobilizing for a fight. It will be pulled back as a true first-phase option at the last possible moment.

And we shouldn’t lose sight of this: Highland will be first. Going up to Highland Mall through UT’s eastern edge and Red River (or some route even further east) is a bad route. It’s a waste of money. And, yes, it will foreclose rail on Guadalupe/Lamar indefinitely. It will do so for a couple of reasons: (1) it will have relatively low ridership, which will dampen public support for further investments; and (2) although it is too far from Guad/Lamar to serve the dense neighborhoods on that route, it is too close to justify another investment on Guad/Lamar until other parts of town have been served.

I see their announcement of Highland/ERC as a cynical political strategy to dampen opposition until it’s too late. That deserves an “F,” not a B-.

If they put forward a plan to build ERC first, I’ll switch to B. But I don’t think that will happen.

WTB a new Cap Metro.

ERC is not going to be built in the first phase; this is the city staff being aware enough to group it with Highland so people will say “well, at least they hit SOME density (in ERC)”. It’s going to be Highland, which takes you right to the edge of Mueller, and then, oops, we’re right back to that predetermined conclusion that we should do exactly what the plan was in 2010.

These look so very very different.

These look so very very different. (Image courtesy @jacedeloney)

The meeting will go up soon on the city channel 6 site. I’m told I was viewed as “intense”.

Tried to make my 3 minutes at 3:00 count, but there was no reaction from the CCAG; except that afterwards I was cornered by a UT VP and lectured for not having provided them much data. Sorry, ma’am, I got a job and a family; it ought to be the job of the people you PAY TO DO THIS to provide honest data. Oh, and Dave Sullivan got mad because I didn’t mention the GPS stuff in Rapid Bus as an improvement. Dave, it was in the earlier draft. Trust me.

The Rapid Bus post will have to wait. The time I was going to spend at this chess tournament writing it up turned out to be burned up by running around after my 4 year old, although I did get to talk to Councilmember Spelman for ten minutes before Sophie insisted that enough was enough.

How do I feel? Despite popular conception, I’m apparently not completely cynical as I was surprised at how embarassingly shameless this con-job ended up being. Thrown for enough of a loop that I ended up throwing bile all over twitter last night of a caliber that the world hasn’t seen in many years. Worrying-the-coworkers level, here.

I’m most upset, though, I think, at the fact that the AURA people were conned by people like friend-of-the-blog JMVC into thinking that Rapid Bus did not, in fact, preclude urban rail. Those folks then proceeded to invest a huge amount of their time in this process, when the fix had been in since the very beginning; and they ended up giving Project Connect relevance and respect it didn’t deserve in the process. Had people been honest from the beginning, we might have been able to have an adult conversation about “why aren’t we doing more for Guadalupe than this shitty bus service that makes things worse for most people north of the river anyways?”. Now we never will. I wasted a couple of days of vacation time. The AURA executive committee spent ten times as much, each.

As for where we go from here? I will see what the AURA guys end up doing. If they continue to be suckered into believing, or even just acting like JMVC and his pals driving Project Connect are their friends rather than the obstacles they really are, then we’ll be parting ways. I said at the beginning of this process that if a non-Guadalupe route was recommended through an honest process using legitimate data and reasonable assumptions that I’d support it. THAT’S NOT EVEN CLOSE TO WHAT WE GOT.

And I don’t agree with Julio that we’ve made incredible progress. ‘We’ forced Project Connect to come up with bad data, bad analysis, and bad conclusions to justify their predetermined route, sure; but the route is still bad – it’s the same goddamn route as before – with the same 0% chance of being full-enough-of-riders to lead to a full system of urban rail instead of another RedLine-esque generation-losing one-and-done.

I definitely won’t be voting for a Highland/”ERC but really no just Mueller” alignment the way things stand now, nor should you.

Project Connect’s “response”

Doing this quickly at the car dealer to get it out. Thus, this is going to be a lot of screencaps ‘n’ paste action and poorly formatted. You are forewarned.

First, some background, via cheap and dirty screencaps of some twitter conversations; click to embiggen:

Screen shot 2013-10-24 at 7.55.28 AM

Screen shot 2013-10-24 at 7.55.48 AM

 

Screen shot 2013-10-24 at 7.56.09 AM

 

Screen shot 2013-10-24 at 7.56.21 AM

 

Screen shot 2013-10-24 at 7.56.45 AM

 

Screen shot 2013-10-24 at 7.56.55 AM

Notice how many people immediately saw the problem with this map (as soon as they looked).

Then, Project Connect finally issues an initial response; more than 24 hours later. Note that these four are in reverse order (oldest at the bottom).

Screen shot 2013-10-24 at 7.58.17 AM

Realizing right about now I should have done this in storify, but pressing onward. The first point to see here is that Project Connect is more than happy to send out updates on everything via twitter where everybody can see, but they don’t seem happy to engage with people giving feedback on that mechanism. While I understand at this point whomever’s behind the account (JMVC used to be, don’t know if he is now) is feeling a bit set upon, the fact of the matter is that if you ask for more feedback via email you’re not being transparent. People need to see both the question AND the answer for it to qualify as transparency and as Austin CDC noted earlier, previous feedback via email had been ignored.

Over the weekend and early the next week, the incredibly busy people at Project Connect who were treating this issue with the seriousness it deserved spent all their time fixing the data. Or did they?

No, they didn’t. They presented at, with the previous map book:

  1. University Area Partners
  2. Planning Commission
  3. Barton Hills NA
  4. Oak Hill Parkway Open House
  5. Mueller Neighborhood Association (link may require registration there)

About halfway through this schedule they noted:

Screen shot 2013-10-24 at 8.07.37 AM

Here’s what that release said:

It was brought to the attention of the Project Connect Central Corridor team that there was a potential
issue with the Central Corridor Map Book. The team reviewed versions 1 through 4, confirmed an error
and has made the necessary corrections.
After further review of the Bus Ridership Map featured on page 36 of Map Book version 4, we
discovered that the map had been populated using the wrong data field (bus stop rankings instead of
stop boardings). The source data set posted to ProjectConnect.com was not incorrect or incomplete, but
the map in the Central Corridor Map Book displayed the wrong data field.
The project team will publish version 5 of the Map Book online in the Central Corridor Resources, on
Wednesday Oct. 23, 2013. It will include the corrected map with fall 2011 Ridership Data as well as a
new map with spring 2013 Ridership Data. Both data sets are populated using boardings (or “ons”) at
each stop; data by route is not specified on the map.
The Central Corridor Map Book is a working document that is subject to frequent updates. We
appreciate interested community members taking a vested interest in the project and providing
feedback. The Central Corridor team reviews every comment, critique and compliment received by
members of the public, regional leaders and interested parties as part of our inclusive, deliberative
process. The Project Connect Twitter and Facebook accounts continue to be great resources for
community input but if your feedback exceeds 140 characters, please email info@projectconnect.com

The map was indeed released on Wednesday, five days after initial feedback was given. Many many people were misinformed by the previous map during that period; many more people missed the opportunity to be correctly informed by the actual data during that period; and Project Connect thinks this is no big deal.

Do you think it’s a big deal? Here’s the original map:

Screen shot 2013-10-24 at 8.10.24 AM

 

If you saw this map, your likely reaction (if you took it for the truth) might be: “Why are those Guadalupe/Lamar guys asking for rail when there’s so much existing transit demand out towards Mueller?”

Here’s the corrected map:

Screen shot 2013-10-24 at 8.12.11 AM

If you were a resident of Mueller and saw this map, you might even be honest and say “we don’t deserve rail over the obvious high-demand corridor here”. If you were on the Planning Commission, you’d definitely say so. But Project Connect robbed you of the opportunity to form that opinion with correct data.

Was it a simple accident? Well, it’s conceivable. But is that any better?

Let me make an analogy for you.

Suppose you’re a college student back in the day when we turned in physical papers instead of via email. You got an assignment to write a 500 word paper on why the Federal Transit Administration views existing bus ridership as the most key metric in determining the viability of rail service.

You write your paper. You print it out, and hand it in.

The professor returns it a day later with an F, indicating that you didn’t write enough words.

“I did,” you insist; “I remember writing for hours!”

The professor shows you the paper you turned in. It looks like this:

Screen shot 2013-10-24 at 8.15.57 AM

 

Your initial response is “that looks like my term paper, but I’ll look into it!”.

You take five days to look into it.

You finally come back to the professor and say “It looks like I only handed in the third page of my paper by accident. Here’s the next iteration of the paper” and hand the full 3 pages in.

Any professor worth their salt is going to say “Did this look like 500 words when you handed it to me? Did you even check? If this is how seriously you take my class, I’m going to explore whether I can issue a grade lower than F”.

Project Connect, if they cared at all about the data that’s theoretically informing opinions in this process, would never have let the old map go out. It was SO OBVIOUSLY WRONG that it was immediately spotted by everybody who knows anything about transit in Austin as soon as they looked at it. It’s the equivalent, for instance, of putting out a road map with Cedar Park labelled as Austin and vice-versa. There’s only two reasons this would have gone out that way – and again, the most positive one to PC is that they don’t care that peoples’ data is crap, because they don’t care about the opinions generated by those data, because they don’t intend to actually take those opinions into account.

Yeah, that’s the BETTER interpretation. The worse is that, like many other modifications to maps many of us have found, they’re messing with the data on purpose to try to get the public to actually support a lesser rail route.

Obviously I’m not among those who have, either as a political calculation, or otherwise, just politely thanked Project Connect for their corrections on this matter. As I noted above, this is not nearly enough. What would it have taken to get me not to open up on these guys?

1. An immediate and strongly worded apology last Friday for the obviously wrong map. There is no way that anybody who knows anything about transit in Austin would look at that map and say “looks fine to us!”, but that’s what they did.

2. A loud and large public relations campaign with the corrected map – show everybody who you misinformed with the old map the new map and explain the error and what it signified, instead of burying it in a PDF press release issued only from your web site. Remember, for instance, lots of people at the Mueller NA now actually think they have more bus riders going there than up Guadalupe! And they’re talking to their friends about it as we speak.

3. An immediate and serious commitment to handle all future issues of this type in a truly transparent fashion – for starters, show Austin CDC’s questions and provide answers in PUBLIC. Don’t let them go down the e-mail hole. If you feel like you can use twitter to advertise your meetings and maps, then reasonable people expect you to answer issues about them in the same forum in a timely fashion – indicating that you’d prefer such feedback via email is not acceptable.

My car’s almost done, so this is going to have to be it for now. Suffice to say these guys have not learned their lesson at ALL, and thus have not earned my trust, and they should not have earned yours either. Continue to take every thing these guys do with a hefty dose of skepticism.

 

 

 

 

Project Connect and Capital Metro need to answer some serious questions, right now

In the last several weeks, many people, most notably Central Austin CDC, have pointed out a series of errors in the “Map Book” presented as data in various public meetings by Project Connect. I myself found and commented on several at a public meeting downtown, which seemed designed to make the Mueller route look far more attractive than the facts would merit.

But the most egregious ‘error’, by far, though, was apparently discovered a day or so ago by Jace Deloney and then confirmed by the CACDC. It has to do with the “here’s how many people currently board the bus at various locations” map, which is a key baseline for anticipated rail ridership (which is, quite frankly, the most important map of all).

First, let’s see the Project Connect version.

Project Connect Map Book version of 'bus ridership 2011', courtesy Jace Deloney

Project Connect Map Book version of ‘bus ridership 2011′, courtesy Jace Deloney

If you were a novice to civic affairs trying to make up your mind, or a city staffer or council member who doesn’t ride the bus and trusts the information they’re receiving, this map makes it look like bus ridership in the Guadalupe/Lamar corridor is of roughly the same magnitude as currently exists in the corridors heading out to Mueller. But if you read this blog, or spend time on the Lamar/Guadalupe corridor, you would tend to think that can’t possibly be right, could it?

Well, it’s not. They left out the ridership from the #1L, the #1M, and the #101; three little routes that between them comprise the most heavily used lines in the entire Capital Metro system at 17,000 boardings/day. 8.5 times the boardings achieved by the Red Line, by the way. Oops.

Here’s a more accurate depiction of ridership, courtesy of Jeff Wood in a blog post last year:

Jeff Wood's visualization of bus ridership in the core (also density), courtesy Jace Deloney

Jeff Wood’s visualization of bus ridership in the core (also density), courtesy Jace Deloney

With an error this egregious, one might expect an IMMEDIATE response like “this is unacceptable. We’re going to pull the maps and do them all over again.” If, that is, you cared about giving the correct data to support an actual data-driven decision-making process, and it had been an actual error; rather than, oh, I don’t know, a willful continuation of past transparent attempts to mislead people into thinking Lamar/Guadalupe isn’t worlds ahead of Mueller in terms of existing and potential ridership.

 

 

The only actual response from people at Project Connect, so far, at the time this post was written 24 hours later, has been this one response in two tweets immediately after being confronted for the second time yesterday:

Screen shot 2013-10-18 at 12.36.05 PM

Friend-of-the-blog JMVC was asked on twitter and just said he’d look into it. 24 hours later, and nothing’s been heard from either party.

Yes, you heard right. It’s just a minor issue of the 2011 ridership being “less complete”. Yes, leaving out the top line(s) in the city on this map, but somehow leaving in the lesser ones, was just a minor blip.

Jennifer-Lawrence-ok-thumbs-up

 

If you want to do something about this – tell your city council member that you see what’s going on, and you don’t approve of the wool being pulled over your eyes by people who are supposed to be giving us the data to make an educated decision about what to pursue. Or sign yesterday’s petition. Or both. I’m going to SeaWorld.

 

Update - let me frame this more clearly: Either:

1. This is a ‘mistake’ and the people at Project Connect and Capital Metro think it of so little importance that they view it as just ‘incomplete data’, which calls into question their judgement, their commitment to the process, and, frankly, their intelligence; OR

2. This is not a ‘mistake’ but a ‘plausible deniability’ kind of scenario, and the fix is in (as I’ve thought with some of the other map issues I’ve brought up with them).

Note that others’ feedback about the map issues they’ve found has resulted in zero information back (not even confirmation) over the past few weeks from Connect Central Texas. Zero. This, in what’s supposed to be a transparent, open, public, data-driven, process. So it’s not just mean old M1EK with his crazy crackpot ways getting this treatment. Bear that in mind.