Others express concern about using a parcel that is unencumbered by Capitol View Corridors. Capitol View Corridors limit the height in some parts of the city so that the State Capitol can be seen from a number of angles. There are ways to mitigate this problem. One approach is state legislative action. A second approach is for the Austin City Council to expand the number of blocks in downtown or near downtown entitled for central business district-style development.
It is true that others have expressed concern about CVCs. And it’s true that getting them modified is very very hard.
It’s also true that if getting the CVC preventing full use of the blocks around the existing courthouse is hard, like, running a marathon hard, getting more blocks around downtown zoned CBD is hard like running a marathon underwater without a scuba tank or snorkel while being attacked by sharks hard.
It’s fundamentally dishonest (in the disingenous) sense to just answer, as Julio has done, “we should expand downtown” as if it’s some kind of answer to the “they didn’t try very hard to get CVCs out of the way so they could use one of the several existing blocks that don’t generate tax revenue and are already owned by the county and already on the transit spine”. It’s basically the equivalent of a repeating gag on one of my favorite new shows, modified here with my favorite tools: google image search, cut and paste, and MSPaint. Nothing but the best thing zero dollars, zero skill, zero talent, and negative five minutes can buy is good enough for the artistic sensibilities of my readers!
The insiders who messed up Proposition 1 still haven’t come to terms with what they did, so I’m not going to let it sit either. Here’s something not to forget; when certain political actors try to pretend there was some kind of consensus behind the choice that got spanked at the polls instead of the one that was never allowed to be studied:
This VMU on Lamar at North Loop (google maps link; as of 9/5/2014 the streetview picture is from construction) is open now. I like it. It has a bus stop right in front of it! Streetscape is good. There’s actually a new Taco Cabana across North Loop from it, unfortunately with a drive-thru, where the pretty image to the right has a grassy field1. The property to the south of the Taco Cabana appears ripe for redevelopment soon as another VMU; I’d be surprised not to see it go that way within a couple of years.
Let’s imagine the resident of one of these new apartments wants to take the bus to Wheatsville Co-Op, an urban grocer located at about 31st and Guadalupe. Lots of people used to ride the bus to Wheatsville last I checked.
For background, the VMU ordinance was enacted as a quid-pro-quo for the McMansion ordinance – the logic was that we would build tall apartments (for Austin, anyways) over walkable retail on corridors where transit frequencies and usefulness was high. Lamar/Guadalupe definitely fit that bill, at least originally.
Before the implementation of “Rapid Bus”, the #1 ran about every 13 minutes during peak periods on this route. Google maps says that the bus portion of this trip takes 8 minutes on the #1. Note that Google doesn’t even consider the 801 a viable option for this trip, unlike Capital Metro themselves. We’ll get to that in a minute.
We can use the same “show up and go” calculations from this post to come up with this graph. Short summary: If transit service is to be truly useful as a replacement for the car, it needs to be frequent enough that you don’t bother to check a schedule; you just show up at the stop and a bus comes pretty soon (and by the way this was one of the big marketing points for the #801; so this isn’t just a condition I’m placing on them to be mean). Note that the walking time on either end for the #1 trip is essentially zero – there are bus stops for the #1 (but not the #801) directly in front of the VMU building and the grocer.
Originally, when frequency was every 13 minutes, a trip to the grocery store would involve a 0 minute walk, an average 6.5 minute wait (half of frequency), and a 8 minute trip on the bus, for an expected trip time of 14.5 minutes. Not bad.
However, in the world we live in now, Capital Metro has cut half of the #1s and imposed instead the #801 in place of the #101, stealing the local frequency for the express. How does that service work for our apartment resident?
Same calculations as above – we end up with an expected wait of 13 minutes (it runs every 26 minutes during peak)2. Total trip time is now 21 minutes, if you can get a seat on this bus, which has been a problem ever since the 801 change happened.
But surely the 801 made up for this drop in service, right?
Again, Google won’t even give this as a trip; but Capital Metro’s trip planner does.
Huh. Cap Metro expects the user of this ‘service’ to walk about a half mile north to the “Brentwood Station”, wait (12 minute frequencies during peak), ride the bus to the “Hyde Park Station” (7 minutes), then walk about a half mile south to Wheatsville. Hey Google, how long will those walks take? Google says 8 minutes each, roughly.
So let’s graph those new trips, shall we?
The results show that, and all of this is compared to the conditions before the #801 started (“old #1” in the graph), a resident of this apartment building can now either pay the same amount of money for a much less frequent service (#1) that will now take about 50% longer to get where they want to go, or they can pay double the price for a reasonably frequent service (#801) that will take more than twice as long to go where they want to go. People boarding a bus at this stop and travelling to Wheatsville have seen a significant degradation in quality of bus service.
What’s the conclusion? Well, even if you are foolish enough to think a 26 minute frequency local service still qualifies as “show up and go”, the residents of this VMU and many others in the area are unquestionably much worse off after the implementation of MetroRapid. And what’s worse – the developments resulting from the VMU ordinance were sold to surrounding neighborhoods as less of an impact on their daily lives because we all assumed many of its residents would ride the bus.
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.
My work situation is going to prevent me from making much effort on this today so please assume I endorse this product and/or service 100%.
No, and 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, bronchi 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.
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, apoplexy 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.
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”.
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:
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:
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.
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:
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.
The prevailing wisdom has been that a project in Smart-Grown Austin, gynecologist serving major trip generators like UT and the Capitol complex, supported by Cap Met’s ample sales tax revenue, would be a slam dunk for a “highly recommended” rating. (Conversely, the original Red Line, which had far lower ridership and — even though it was on existing rail right of way — only marginally lower projected costs, was headed, Cap Met insiders say, for a “not recommended” kiss-of-death rating, which is why the transit authority switched tracks at the 11th hour.)
The key here is that from about 1997-1999, Capital Metro’s plan of record was to take the entire Red Line (what we use now for commuter rail), build two new tracks, put up electric wire, and run light rail trains on it all day long at high frequencies.
The Federal government said the ridership would be low, negligibly higher than what we’re seeing today, and hinted to Capital Metro that they would not fund that line. Capital Metro quickly switched to what became the 2000 light rail proposal – the “Red/Green” line, using the Red Line’s ROW only from Leander to Airport/Lamar, then going in the street from there.
You can use the 1997 proposal as, effectively, a ceiling for what can be accomplished with further investment in the Red Line we have today. Nothing has truly changed since then – Capital Metro anticipated infill then around the stations in the far northwest, and they anticipate it now, and it still turns out to be low-density crap if it ever gets built. No more jobs have moved to be close to the MLK station instead of at UT.
Folks, there isn’t that much more that can be accomplished with a train that doesn’t go very many places worth going. The real action is, as it always has been, around Congress Avenue downtown (not the Convention Center); at the University of Texas (preferably its front door on Guadalupe), and at the Capitol; and no, you aren’t going to convince suburbanites to transfer to a shuttle-bus(*) to get to those places (as we’ve finally, I hope, proven by now).
This is why further investment in the Red Line is best characterized as wasting money trying to disprove the sunk cost fallacy. There’s very little new ridership there, even if the train gets a little faster, or runs a few more hours on the weekend.
* – no, urban rail doesn’t help either. Suburbanites own cars. Two train trips in our commuting environment, even if the second one goes closer to where they want to go, is fundamentally uncompetitive. Believe me, or not, but remember: I’m the guy who predicted the Year 1 ridership correctly, and called that nobody would want to ride shuttlebuses when everybody else said they would.
Don’t bother clicking to embiggen. I had to make that in five seconds with PowerPoint.
Original for lower picture from StreetsBlog; I forget where I got the upper.
Yes, patient I know I never got to “the formula”. Things went to hell at work. But I can’t pass on the chance to pass along this link. Relevant quote first:
The takeaway here is that it’s better for transit to be reactionary – that is, cardiology serving travel demand that already exists – than it is for it to be anticipatory – that is, this web serving travel demand that may theoretically exist in the future.
Relevance to Austin is that the Lamar/Guadalupe corridor has travel demand that already exists today; AND an equal or greater amount of travel demand that may theoretically exist in the future than Mueller. Despite this, certain elements at the city and Capital Metro are, as we speak, stacking the deck in favor of a supposedly data-driven decision for Mueller over Lamar/Guadalupe (the latest effort to do so involves eliminating “West Campus” as a separate subcorridor and instead lumping it in with “Core”, which basically allows a Mueller route to pretend to serve West Campus by touching somewhere in the (now very very large) “Core” box – as if somebody living a few blocks west of Guadalupe would ever walk all the way to San Jacinto just to ride a train two miles or so back to downtown – the trip would be quicker if they just walked straight there). But I digress.
(For non-Texas readers who may have wandered in from Jeff’s excellent transit portal, hospital almost all limited-access highways in this state are built from pre-existing major arterial roadways – where property access is maintained via the construction of new “frontage roads” which unlike perimeter roads often used for that purpose in other states, also serve as on-and-off-ramps. The incredibly wide road footprint that results makes it far more expensive to build new or maintain existing crossings over or under the highway).
Both images from google transit; click through for full details. This is basically the “how do I get from the drop-off for the express bus at the park-and-ride on the west side of the road to the entrance to all the office parks on the east side of the road”. Note that the address for the park-and-ride you sometimes get (12400 Research) doesn’t match the actual location, which is on Pavilion Boulevard back towards Jollyville.
First, the transit directions, which look pretty good at first:
Then, the driving directions, which look like this:
Huh. Wait a minute. If I can just jump across the road, why do the driving directions have me go down a mile and back? Let’s look at the satellite image:
Oh. Now I see. Note that the bus stop images you see on the other side of the road are for a poorly performing cross-town route which suffers from the same basic problem – if you need to leave an office on that side of the street and go southbound on 183 back home, you get to walk to the next crossing – which on a normal street wouldn’t be that big of a deal, but crossings of frontage roads are few and far between. Farther to the northwest, crossings are even less frequent – you face a walk of close to 3 miles in spots to make this trip across the freeway. Taking that cross-town route would be even worse than taking the express plus the incredibly long walk, because it would require a long slow trip down the frontage road and then a transfer to a second bus, and because the service on the frontage road is inevitably low-demand, it doesn’t run very often either.
Keep in mind that this is just to cross the freeway. If you work at the Riata office park, you then face another walk of a half-mile or so inside the complex. I used to do this commute on my bike, with bus boost in the morning at times and am very familiar with the area – ironically, proximity to the Pavilion transit center was supposedly touted as a positive for this development when it was originally proposed. I was always pretty sure Pavilion used to connect with what is now called Riata Trace Parkway when 183 was just a six-lane divided arterial but have never been able to find a clear enough old satellite image to confirm, but our Tennessee correspondent has already confirmed in comments that it did cross.
For reference, my last job before this one was also on US 183, but between Balcones Woods and Braker Lane, which was much more accessible by transit – and yes, I did sometimes take the bus even on days where I wasn’t biking. I tried the bus commute once to Riata and never did it again – that walk, in addition to being far too long even for a nice comfortable express bus, is just dreadful, even compared to conditions down by Braker.
And, yes, there’s a personal reason this is coming up now too. All I can say now is dammit, dammit.
Folks, store the deck is being stacked against rail on Lamar/Guadalupe – as I alliuded to yesterday – the data-driven process is being co-opted by the people who want and need it to go to Mueller for political reasons. leading to a set of ridiculous assertions in the map book, and then a set of ridiculous changes TO the map book when the map book wasn’t ridiculous enough the first time.
The only thing that you can do right now to help right this is to sign this petition. Please do so as soon as possible. Stay tuned for further actions.
So I spent about three hours around lunch yesterday for a 1.75 hour meeting moderated by AURA where we could ask questions of Project Connect staff. One of my questions was following up Lyndon Henry by complaining that the size of the subcorridors (or in Lyndon’s better term, discount “sectors”) was ludicrous and pushing us away from a more sensible decision-making process.
At one point later on, pulmonologist a very good pal of mine who is working on the program answered John Lawler (UT student government)’s question about why that decision was made to suddenly include UT and West Campus with the Core with a blistering diatribe about how inappropriate and offensive it was to be so cynical about the motives behind said change, while occasionally looking right at yours truly. Message received, loud and clear. (Not just by me; others asked me if I thought you were speaking to John or to me when you went there).
Before I link to my brand new slide deck you just motivated me to write this morning, know this: Before this meeting, I only mentioned this change in an aside in a couple of places. I never talked to the University Area Partners or Mr. Lawler; they didn’t get their complaints from me. If anything, I may actually have heard about it from them, indirectly. I was like the tenth person in the scene to even notice the change.
But by incorrectly assuming that just because it was a complaint, it must have been only from me, or by trying to score points by making an attack about it by tying it to me, whom you presumed was held in low regard by the room, you just brought me into it. Congratulations, now I’m all-in.
If your (paid to do this) feelings were hurt by the implication that the motivation for the change might have been less than aboveboard, consider the converse: I took vacation time to spend my lunch hour only to get attacked by you (who, again, unlike me, is getting paid to do this).
Click the little expanders in the lower right to embiggen.
In the last several weeks, approved many people, recipe 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.
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.
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:
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.
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 he’s had have received 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.
Doing this quickly at the car dealer to get it out. Thus, page 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:
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).
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:
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 email@example.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:
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:
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:
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.