The District of Columbia

Single Member District

Single Member District

by Office of Planning on 20100701

Keywords
About: SMD, Single Member District, Ward, boundaries, ANC
Taking place at: Washington DC, District of Columbia, DC, DC GIS, DCGIS

Abstract

Single Member District or SMD's.

Advisory Neighborhood Commissions were created pursuant to legislation approving the District of Columbia's "Home Rule" charter in 1973,. These neighborhood groups were to provide the neophyte District electorate with "grass-roots" experience in the electoral process. These groups were to be based on the latest Census Bureau records of the District's population. Each Single Member District (SMD) was to have approximately 2,000 residents, with boundaries to be developed by the new DC City Council. Candidates elected for each Single Member District sit as Advisory Neighborhood Commissioners. The first elections for these newly-formed Advisory Neighborhood Commissions (ANCs) were conducted in 1976. This data set reflects modifications to SMD boundaries approved by the Council in May, 2002, for official 2003 SMD boundaries.

All DC GIS data is stored and exported in Maryland State Plane coordinates NAD 83 meters.

METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.

Purpose

SMDs are used for the planning and management of Washington by local government agencies. This specific data set was created for the specific purpose of printing maps of the various SMDs, each on a letter-sized sheet of paper. Boundaries have been digitized with sufficient accuracy for this purpose, and may or may not be sufficiently accurate for other purposes.

Use constraints

Acknowledgment of the DC Geographic Information Systems Program (DC GIS). The District of Columbia Government makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred with respect to the information or data furnished herein.

Point of contact

Charlie Richman
in DC Office of Planning

801 N Capitol St, NE # 4000
Washington DC, 20002, USA

fax: 202-442-7637
hours: 8:30am - 5pm

Data accuracy

Accuracy
Data believed to be complete and accurate, subject to change.

Completeness
Data believed to be complete and accurate, subject to change.

Lineage / Sources


  • Digital,
  • SMD representatives
    database, attributes
    ANC and SMD representatives
    by Office of Advisory Neighborhood Commissions, 20091202
Lineage / Processes
GIS Data Coordinator
in D.C. Office of the Chief Technology Officer

441 4th St NW, Suite 930 South
Washington DC, 20001, USA

fax: (202) 727-5660
hours: 8:30 am - 5:00 pm
SMD boundaries were digitized on-screen between the scales of 1:5000 and 1:800 and snapped to an existing planimetric base layer. Although snapped to the existing base features, the digitized boundaries are not identical to those base features. Differences are not significant at scales that allow each SMD to be plotted on a letter-sized page, but differences may become apparent when zoomed in further.

SMD boundaries follow the legal boundary descriptions from the DC Council and Board of Elections and Ethics.

Gottlieb Simon (ANC staff) originally created boundaries for SMDs and ANCs reflecting redistricting using Atlas GIS and a TIGER/line base map. This product had important limitations because the TIGER/line base was not up to date, contained inaccurate and sometimes incorrect street data, and did not overlay properly over the other map data sets used by the District.

On a quick-turnaround basis, the Office of Planning created a set of SMD/ANC boundaries using ArcGIS 8.1 and a DC GIS planimetric base map. The design goal for this edition of these boundaries was not to create a topologically-correct product that overlaid precisely atop the corresponding planimetric features. Instead, it was to create boundaries that were of sufficient accuracy to allow rapid creation of 8 ? by 11 paper maps for each of the various SMDs and ANCs.

An ArcGIS 8.1 snap environment was used to snap to underlying features in the DC GIS snapbase layer. After a quick manual process to snap the TIGER-based boundaries to the corresponding planimetric boundaries, OP held a series of working sessions with BOEE, ANC, and Council staff to review each boundary against the appropriate legal description. Where needed, mapped boundaries were adjusted to fit legal descriptions using the "Shared Edit Tool" and the snapping environment. In many instances, this process highlighted inconsistencies in the legal descriptions, and BOEE and ANC staff created technical amendments as necessary to amend the defining legislation.

This manual editing process of snapping boundaries to features in the snapbase layer did not produce boundaries that were identical to the underlying features, but resulted merely in boundaries that shared selected vertices with the underlying features. At the design scales for this product, this difference is not visible on printed maps. These files, however, were not suitable for use in automated processes for developing lists of addresses in each SMD by overlay with street data.

After these files were transmitted to OCTO, one erratum was discovered and corrected. Thereafter, OCTO employed Michael Baker Corporation to conflate the SMD boundaries geodatabase to the snapbase GIS file. Michael Baker conducted the conflation effort, but consulted OCTO when there was a question with SMD boundary location. Since OCTO did not conduct the Phase 1 effort, and Michael Baker did not have the legal text, the generic rule was to conflate to the nearest snapbase when there was a question.

Finally, the SMD layer was updated and dissolved into the ANC layer.
GIS Coordinator
in D.C. Office of the Chief Technology Officer

441 4th St NW, Suite 930 South
Washington DC, 20001, USA

fax: (202) 727-5660
hours: 8:30am - 5pm
Quality Control:

Step 1 - Initial Check against prior edition
The Office of Planning conducted an initial quality check that compared the updated boundaries to those originally delivered to OCTO. Each SMD was reviewed for anomalies, and flagged for future review with council staff and the legal text.

Step 2 - Detailed review with Edward Elders of Council Member Mendelson's staff
OP staff reviewed those areas with Edward Elders of Council Member Mendelson's staff and the controlling legal text. The product of that review is a shapefile that is to be used as a guide for editing the final SMD boundary geodatabase. The SMD_edit_line is only a guide. Edits to the SMD geodatabase should use the snapbase where the SMD_edit_line follows snapbase features. Where the SMD_edit_line does not follow a snapbase feature, the exact path of the SMD_edit_line should be followed. Each line segment has attributes describing how edits should be conducted.
The attributed SMD_edit_line is being transmitted to OCTO for use in editing the final SMD boundary geodatabase.
GIS Data Coordinator
in OCTO



fax: 202-727-5660
hours: 8:30am - 5pm
Through the comparison of 2000 ward, 2002 ANC, 2002 SMD, and the snapbase features, OCTO staff performed several edits to align these layers. In this effort, staff corrected six issues.
Dataset copied.
GIS Data Coordinator
in Office of the Chief Technology Officer

441 4th St NW, Suite 930 South
Washington DC, 20001, USA

fax: 202-727-5660
hours: 8:30am - 5:30pm
OCTO GIS staff reviewed this layer for any changes with none to post at this time.

in OCTO



OCTO added SMD representative contact information to the database from a spreadsheet the ANC office provided.
Updated boundaries of SMD 3D01 & 3D06 based on the D.C. Law 14-133, 14-310, 14-213. Also cleaned up the name column, made it more consistent with the ANC naming.
Updated boundaries of SMD 8D04 & 8D05 based on the D.C. Law.

Distribution

Most DC GIS datasets can be downloaded from "http://dcgis.dc.gov" on the data center page. Orders can also be made by contacting OCTO GIS at "dcgis@dc.gov", especially for datasets not available for download.

Distribution liability
Acknowledgment of the DC Geographic Information Systems Program (DC GIS). The District of Columbia Government makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred with respect to the information or data furnished herein.

Distributed by
GIS Data Coordinator
in D.C. Office of the Chief Technology Officer

441 4th St NW, Suite 930 South
Washington DC, 20001, USA

fax: (202) 727-5660
hours: 8:30 am - 5:00 pm

Entity

SMD02Ply / DCOP
DC Template

Attributes

  • SHAPE_LEN / ESRI
    Internal feature number.
  • OBJECTID / ESRI
    Internal feature number.
  • WEB_URL / ESRI
    Web site url
  • Shape / ESRI
    Feature geometry.
  • GIS_ID
    Sequential OCTO-GIS number
  • SMD_ID
    SMD identifier
  • ANC_ID
    ANC identifier
  • NAME / ESRI
    SMD Name
  • SHAPE / ESRI
    Feature geometry.
  • CHAIR
  • REP_NAME
  • LAST_NAME
  • FIRST_NAME
  • ADDRESS
  • MIDDLE_NAM
  • EMAIL
  • ZIP / ESRI
    Length of feature in internal units.
  • APT / ESRI
    Internal feature number.
  • SF / ESRI
    Length of feature in internal units.
  • SHAPE_AREA / ESRI
    Area of feature in internal units squared.

Metadata

FGDC Content Standards for Digital Geospatial Metadata / FGDC-STD-001-1998 as of 20100727

Provided by
GIS Data Coordinator
in D.C. Office of the Chief Technology Officer

441 4th St NW, Suite 930 South
Washington DC, 20001, USA

fax: (202) 727-5660
hours: 8:30 am - 5:00 pm

m/B