Post #258: 4/30/2019 Transportation Safety Commission meeting and a few oddities from recent Town public meetings

About 15 people attended last night’s Transportation Safety Commission (TSC) meeting.  The bulk of the meeting dealt with petitions and complaints from several neighborhoods regarding cut-through traffic, speeding, and the need for pedestrian crosswalks.   Among the streets discussed were Tazewall, Casmar, and John Marshall.

My main interest was in the Town’s replacement for the Citizen’s Guide to Traffic Calming.  You can find the current version — in use since 2002 — on this page on the Town’s website.  It outlines the process you would have to go through if you wanted your street to have (e.g.) speed bumps, a pedestrian crosswalk, a flashing pedestrian crosswalk sign, or other traffic safety measures.  You can find a draft of the proposed replacement on this page on the Town’s website.

Continue reading Post #258: 4/30/2019 Transportation Safety Commission meeting and a few oddities from recent Town public meetings

Post #250: Oh, you never said that it had to be the same building.

InsideNova reported on Maro Polo yesterday. And while they got the details right, I really think that they are missing the big picture.  Among the responses I have seen is a sentiment of “good for the Board of Architectural Review”.  And that sentiment — while nice –is definitely missing the forest for the trees in this case.

In some sense, valuing the role of the BAR here is like valuing the services of a trauma surgeon after you’ve had a car wreck.  It would be a much smarter policy to avoid the car wreck in the first place.

In this post, I’m going to try to point out just one big-picture issue.  The Town did not review one building.  The Town reviewed two very different buildings, at different times.  And despite that, the claim is that this meets the letter of the law.

To be clear, the original design — and the only design seen by the BAR — was for an ornate, turn-of-the-century Georgetown-style stone/red brick/wrought iron building.  But the final design appears to be a plain-vanilla brown-brick building with more-or-less blank walls facing both Maple and (particularly) Church.

Let me explain why that’s crazy, from the standpoint of logic.  For a building to be approved under MAC, it has to pass review by:

  1.  The Board of Architectural Review (BAR), primarily focused on how the building looks, and whether it will fit in with the Town
  2. Planning Commission (PC), which asks whether the building fits into the Town’s master plan and appears to conform to all the zoning rules.
  3. Town Council (TC), which … does what it does.  Near as I can tell, the Town Council can approve or disapprove things without a whole lot of justification.

Here’s the crazy part:  Up to now, we had been assuming that the same building had to pass all three stages.  But now — if this flies — that no longer appears to be true.  You can present materially different buildings, to different parts of Town government, and still claim to have satisfied the letter of the law. The BAR only saw the Georgetown-style building.  They saw nothing of the building that the developer is getting ready to build.  The Planning Commission saw only the Georgetown building at their first meeting, and then were given a mix of renderings of the old (Georgetown) and new (Chicago alley) buildings at their second meeting.  Town Council was given renderings of both buildings, but seemed fully aware that the new (Chicago alley) building is what was going to be built.  Only in passing was it mentioned that the BAR reviewed the Georgetown building.  It was never made explicit that the BAR had never even seen the building that the Town Council was getting ready to approve.

But the Town Council approved it, with a fairly cavalier acknowledgement that this would have to be re-reviewed by the BAR before it was built.

And now, here we are.  This building — that the BAR has never before seen — gets tossed to it for “re”-review.

The upshot is that instead of asking the BAR to guide the architecture, we’re asking them to clean up end results.   For example, Town Council repeatedly pointed out the blank end walls facing Maple, on the revised version of the building.  And noted that something needed to be done about them.

These are ugly blank walls that didn’t exist in the version the BAR approved.  They are part of a building that the BAR had never seen before.  And yet, it’s now the BAR’s problem to deal with them.  If they can.  Almost a year after the Town Council approved the building on 5/7/2018.

But here’s the kicker:  The BAR may not have the final say-so in how the building will look.  As I read MAC statute, the Director of Planning and Zoning is the sole arbiter of whether a variation of a building is “in substantial conformity” with the proposed plans.  The BAR can do anything they want to, and Planning and Zoning can overrule that at any time, just by declaring there to be “substantial conformity” with the original (October 2, 2017) submitted plans.

Just in case you haven’t gotten it by now, I’ll say it plainly.  This is NOT how this system is supposed to work.

 

Post 247: The hundred-day rule

This is a re-posting of material that I posted earlier this year, with just a little additional information.  The gist of this is, maybe now is a good time to review the 100-day rule that the Town adheres to in rezoning matters.

Nearly every other government entity in the Commonwealth of Virginia gives the governing body (.e.g., Town Council, City Council, County Board of Supervisors) one year to make rezoning decisions, once the Planning Commission has reached a decision.  But in the Town of Vienna, we say that the Town has just 100 days to make such decisions, including both the decision by the Planning Commission and the decision by the Town Council.

And when you figure out how long it takes the Planning Commission to come to its decision, then factor in the need for a public hearing by the Town Council, this means is that you get some very rushed decision-making by the Town Council.  Continue reading Post 247: The hundred-day rule

Post #246: 4/18/2019 BAR meeting, audio file

I’ve decided to put all these files audio recordings of meetings into a single Google Drive directory, accessible at this link.  For this meeting, there is no “index” file because, for me, there were only two items of interest.

Discussion of the Wawa property line fence starts at 15 minutes 45 seconds and ends at around 21 minutes into the recording.

Discussion of Vienna Market/Marco Polo starts at 39 minutes 30 seconds into the recording, and ends around 1 hour 36 minutes.

There are some unintelligible bits due to poor microphone use.  Presumably the Town will post its own audio within a few days, and as always, their audio is better than mine.  You can find the link to the Town’s audio on their website (fifth item down the list, it includes the word “video”, click that, then follow the links.)

 

Post #243: NARFE candidate forum, 4/16/2019

I attended an hour-long candidate forum this afternoon at the Vienna Community Center today.  This was sponsored by the Vienna/Oakton chapter of NARFE (rhymes with scarf), the National Active and Retired Federal Employees Association.  They normally meet the 2nd Tuesday of most months, 1 PM, Vienna Community Center.  And the first hour of this meeting was devoted to listening to the candidates for Vienna Town Council. Continue reading Post #243: NARFE candidate forum, 4/16/2019

Post #240: Last day to register to vote

Today 4/15/2019 is the last day to register to vote for the May 7th Town of Vienna elections.  If you are not registered in Virginia, or may be registered at an address outside of the Town of Vienna, changing your registration is easy enough.  If you have a Virginia driver’s license, you can do that entirely on-line.  Without that, you’ll have to mail or hand-deliver a signed form.  You can see this post for more details.

You can find the full schedule on the Fairfax County website.  The ins-and-outs of absentee voting are show at this link on that Fairfax County website page.

•April 15: Voter Registration Deadline. In person: 5:00 pm, online: 11:59 pm
•April 30: Deadline to request an absentee ballot by mail, 5:00 pm
•May 4: Final day to vote absentee in person, 5:00 pm
•May 7: Deadline to return your ballot to the Office of Elections, 7:00 pm

Post #238: Wade Hampton Parking, revisited (error fixed 5/22/2019).

Corrected 5/22/2019 for my mixing up Park Street and Center Street in Google Maps satellite view.

My earlier contention (Post #232) is that 11 people can park legally on Wade Hampton now, and that, looking at the diagram of the future Wade Hampton, with the majority of it striped to accommodate three lanes at the end, almost all of that parking would be eliminated.

The Town, as reported by the developer, says otherwise.  In particular, the report was that no parking would be eliminated on the side of the street across from 380 Maple West.

What’s the correct explanation?  Somebody has to be wrong here.  At this point, the easiest way to resolve those two views is to suggest that the diagram of the street, as offered by the builder, is incorrect.  As long as you take away almost all the lane striping that is shown, and make the street more of a free-for-all, then you can plausibly claim more-or-less no loss of parking on the west side of Wade Hampton.

To be clear, you have to assume that the lane striping on the 32′-wide Wade Hampton will be nothing like the striping on the 32′-wide Park Center Street, as it meets Maple. Even though the setup (one lane incoming, two lanes outgoing) and width (32′) are the same.  And even though the striping on Park Center Street is almost identical to the builder’s diagram.  But if the Town stripes Wade Hampton as it did Park Center, all streetside parking would be eliminated.

So, I could be dead wrong.  But I had some help getting there.  To get to the Town’s reported position: you have to ignore the Builder’s drawing of Wade Hampton, you have to ignore the real-world example of Park Center Street at Maple, and you have to ignore one legal space on Wade Hampton that nobody uses anyway.  And if you do that, and leave most of Wade Hampton as a free-for-all, so that we can drive down the middle of the road as we see fit — then you can see that the Town’s reported claim of no parking loss is credible.

Detail follows:

Continue reading Post #238: Wade Hampton Parking, revisited (error fixed 5/22/2019).

Post #235: Please keep the sidewalks open

I got an email today from a reader asking about the sidewalks.  Specifically, is the Town going to keep the sidewalks open as developers build the three (four?  more?) MAC buildings on Maple?

Turns out, all I can say is, that’s a great question, I can’t even come close to an answer, and please start asking the Town about this. This has the sound of one of those decisions that might (e.g.) be made by Fairfax County months before we even know there’s a decision to be made.  It would be nice to think that the Town of Vienna was on the case and acting on our behalf.

Sidewalk closure on the west end of Maple will (e.g.) inconvenience students walking to Madison.  If 444 closes the sidewalks,  students walking to Madison from my neighborhood will first have to walk away from Madison (to Nutley/Courthouse or to Maple/Pleasant HAWK light), cross the road, and the continue to Madison.  Not the end of the world, but clearly a disincentive to walking.

Continue reading Post #235: Please keep the sidewalks open

Post #231: Credit where credit is due

The Town has made good on its recent promise to make recordings of public meetings accessible in a timely fashion.  I didn’t want to pipe up about this until I started seeing all of the public meetings showing up.  But if you will go to this page on the Town website, you can see, for the first time, recordings of the Transportation Safety Commission (TSC) and associated sub-committees.

Mostly I want to say, kudos to the Town’s audio engineer.  I sat in and recorded the bicycle portion of the TSC meeting.  Those folks were not used to being recorded.  It was a mess, from an audio standpoint.   People didn’t use the microphones, they forgot to turn the microphones on, they banged the microphones — you name it.  And as much as I may appreciate low-key soft-spoken people in real life, they are a right pain to deal with when setting sound levels in an audio recording.

Producing clear audio is not as easy as you might think.  As I was recording it, I was wondering how the Town was going to deal with all that.  And the Town’s audio is clear as a bell. Despite the absolute hash that the speakers made of their own sound levels.  I have no idea how they managed that.

There are still various “work sessions” that the Town does not record, and so there would be some rationale for me continuing to record.  But I believe that everything that is of official record — where people could in theory vote on stuff — is now recorded and posted on the Town’s website.  At this point, for any of my recordings, it’s always preferable to use the Town recording if it exists.  Their audio is much better than anything I can manage to do.

This is a boon for anyone who wants to know what the Town is doing.  I did not stay for the TSC portion of this meeting, but I now know (in hindsight) that they discussed, in part, the process for petitioning for traffic calming in Vienna.  I need to listen to that.  And now I can.  Without this, I would have no idea what went on in that meeting.

My only other comment, to the Town, would be to take this full circle and post the agendas for every committee, before each meeting.  On this one, for example, I only realized after-the-fact that traffic calming was on the agenda.

Post #228: Maple Avenue Corridor Multimodal Transportation and Land Use Study

For those of you who are already confused, merely by the title, I’m talking about the Maple Avenue traffic study.  That official title is why I keep referring to it as the (thing formerly known as the) Maple Avenue traffic study.  For the official title, I literally cannot remember all the buzzwords in the correct order.

I’m eventually going to have a lot to say about this, but here I’m just going to say two things.  First, the study, as scoped, is fundamentally inconsistent.  Briefly, if taken at face value 1) it’s impossible to predict traffic 10 years ahead, so we’re not going to do that and instead 2) we’re going to talk about “multi-modal strategies” that could only have significant impact decades into the future.  Second, I’m going to do my own analysis of these issues.  That part will take a while.

Continue reading Post #228: Maple Avenue Corridor Multimodal Transportation and Land Use Study