Washington, DC Economic Partnership Erases Park View from 2012 Neighborhood Profiles and Maps
Well here’s one for the record books. What started out as a harmless and possibly interesting Tweet by Councilmember Jack Evans turned into a very strange journey attempting to find out where our neighborhood had disappeared to. At 4:44 p.m. yesterday (Feb. 24), Councilmember Evans posted the following Tweet:As someone who is interested in what’s going on in the neighborhood I clicked the link. I was especially interested because the profiles are produced by the Washington, DC Economic Partnership which, according to their Web site, ” is your first point of contact for development and business opportunities in the District of Columbia. [They] partner with all parties, public and private, interested in making DC a great place to do business.” Or, in other words, they market DC to businesses around the country with the goal of bringing new businesses to the District.
So I was completely shocked when I went to the Web site, looked at the neighborhoods, and no longer saw Petworth/Park View. For some reason, in 2012 Park View was completely erased from the profile and map — even though all surrounding neighborhoods have now been added to the map for the very first time. While the 2009 profile and map had its issues, it was correctly labeled with both neighborhoods. Similarly, the 2011 profile was also correctly labeled.
The accuracy of the neighborhood profiles is important since they are used to attract new businesses. The target economic zone of the Petworth/Park View map is the area 1/2 mile around the Georgia Avenue Metro station. Yet with no mention of Park View in the text and the use of only photographs showing businesses in Petworth, this neighborhood profile is clearly biased toward attracting new businesses north of the Metro Station at the expense of development south of the station.
In contacting the Washington, DC Economic Partnership and explaining the problem I was quickly informed that the change was made due to a request made by Councilmember Muriel Bowser. When I questioned this the representative on the other end became less sure and stated they would look into it and get back to me. (See update below)
I assured them that I was happy to contact Councilmember Graham and have him give a call, at which point I was informed that the Washington, DC Economic Partnership is an apolitical organization. I quickly pointed out that an apolitical organization would not be removing facts or accurate details from a promotional brochure due to a request from a Councilmember.
Still, I did notice one ironic thing about the profile listing. When looking at the “Petworth” profile, I noticed that the associated URL still clearly includes Park View. See the following: http://wdcep.com/dc-profile/neighborhoods/petworthpark-view/
We’ll have to see how this shakes out, but from my point of view, the only correct course is to correct the information online and destroy any copies that may have been printed. You can voice your support of this action by contacting either Mr. Shuskey (WDCEP) or Councilmember Graham. Their contact information is below:
Chad Shuskey | Vice President, Research & Visual Communications
202.661.8674
Email Chad Shuskey
Councilmember Jim Graham
202.724.8181
Email Councilmember Graham
UPDATE (2/24/12 @ 8:50): According to WDCEP, the neighborhood names come from the Office of the Deputy Mayor for Planning and Economic Development. What would make them change what to call the corridor from past years is still a mystery.
UPDATE (2/24/12 @ 7 p.m.): In checking the Web site tonight — and after a phone conversation with WDCEP — the online profile for the half mile around the Metro has been changed to Petworth/Park View.
Explore posts in the same categories: Development, PoliticsTags: Economic Growth, neighborhoods, Park View
You can comment below, or link to this permanent URL from your own site.
February 24, 2012 at 9:14 am
Were you really ‘shocked’?
I’ll AGREE with you that they should change the digital file to say Park View (that is easy enough to do). But destroying every already printed hard copy seems a little much? Dare I say it; Nazi-ish? As has been said elsewhere you are quite sensitive about the Park View name…
I think you should aim for the middle ground. And yes I live in “Park View.”
February 24, 2012 at 10:07 am
As another resident and homeowner in the neighborhood, I can understand why Kent is so sensitive. We have chosen to make a financial and emotional investment in the place we live. It is only right that we do what we can to make sure we get the respect and quality of life we deserve.
February 24, 2012 at 10:42 am
FACT: Park View is an existing neighborhood in Washington, DC.
February 24, 2012 at 6:13 pm
Shock is not a strong enough word. According to the WDCEP website, this is their most highly anticipated, most popular publication, and a central part of their business attraction and retention efforts. This “oversight” has the potential to seriously impact development south of the metro station. Every effort must be made to correct this — to add Park View to both the digital and print publications. And a press release needs to go out with the updated information.
February 24, 2012 at 7:00 pm
Here’s some good news. WDCEP has updated their online neighborhood profile to Petworth/Park View, just like the previous year’s profiles.
Click to access gapetworth.pdf
February 25, 2012 at 7:09 am
Thanks for being vigilant Kent.
February 26, 2012 at 9:53 pm
Thanks from me, too….
February 26, 2012 at 10:35 am
Preferably these two would become different neighborhoods. Petworth is very distinct from Parkview
February 26, 2012 at 6:13 pm
Thanks for getting them to correct this mistake….though it still reads Petworth only on the map
February 27, 2012 at 11:33 am
You’re the man, Kent!
May 31, 2013 at 7:02 am
[…] missed the mark and got everything wrong. Last year, when they released their 2012 profiles, they completely erased Park View from the publication. After meeting with the WDCEP folks last year, they corrected the mistake by including Park View in […]