Name: District Boundary as defined by boundary Stones

Display Field: CITY_NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: In 2011, the District of Columbia government commissioned a project to survey the Washington D.C. historic boundary stones set in 1791 and 1792 that define the Maryland and (then Virginia) border with the new Federal District. The majority of the stones were located using a field survey which employed a GPS-RTK. Surveyed accuracy is +/- 5cm horizontal and +/- 9cm vertical. This Washington D.C. historic boundary area was created by connecting all the boundary stone locations to form the DC Maryland border. And, on the DC Virginia border the line follows the western shoreline of the Potomac River.The Washington D.C. Historic Boundary is not used for the planning, administration, or management of Washington D.C. The boundary stones do not form a perfect 10 mile by 10 mile square of DC, and are not perfectly aligned on each side. Given that they were placed over 200 years ago the survey is impressive, however they do not accurately reflect today's DC Administrative Boundary which was produced with more advanced methods and data.Excerpts from Boundarystone.org:The Residence Act of July 16, 1790, as amended March 3, 1791, authorized President George Washington to select a 100-square-mile site for the national capital on the Potomac River between Alexandria, Virginia, and Williamsport, Maryland. President Washington selected the southernmost location within these limits so that the capital would include all of present-day Old Town Alexandria, then one of the busiest ports in the country. Acting on instructions from Secretary of State Thomas Jefferson, Major Andrew Ellicott began his initial observations for a rough survey of the ten-mile square on Friday, February 11, 1791.Ellicott, a prominent professional surveyor, hired Benjamin Banneker, an astronomer and surveyor from Maryland, to make the astronomical observations and calculations necessary to establish the south corner of the square at Jones Point in Alexandria. According to legend, "Banneker fixed the position of the first stone by lying on his back to find the exact starting point for the survey ... and plotting six stars as they crossed his spot at a particular time of night." From there, Ellicott's team embarked on a forty-mile journey, surveying ten-mile lines first along the southwest line, then along The northwest line, next along the northeast line, and finally along the southeast line. The team completed this rough survey in April 1791.Ellicott's team then began the formal survey by clearing twenty feet of land on both sides of each boundary line and placing other stones, made of Aquia Creek sandstone, at one-mile intervals. The boundary stones are the oldest federal monuments. Although several stones have been moved or severely damaged, thirty-six stones from the 1790s are in or near their original locations, including all fourteen in the land that was returned to Virginia in the 1846-1847 retrocession. Three other locations have substitute stones (SW2, SE4, and SE8), and one location (NE1) is marked only by a plaque.Learn more at boundarystone.org.

Copyright Text: Office of the Chief Technology Officer

Default Visibility: false

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: 389612.306999996
YMin: 124868.954999998
XMax: 407880.11999999697
YMax: 147558.136999998
Spatial Reference: 26985  (26985)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [0, 0, 0, 0]
Outline:
Style: esriSLSSolid
Color: [0, 0, 0, 255]
Width: 2
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeNone

Type ID Field: null

Fields:

• CITY_NAME ( type: esriFieldTypeString, alias: Name, length: 25 )
• STATE_CITY ( type: esriFieldTypeDouble, alias: City )
• WEB_URL ( type: esriFieldTypeString, alias: Web URL, length: 50 )
• AREAKM ( type: esriFieldTypeDouble, alias: Area (km) )
• AREAMILES ( type: esriFieldTypeDouble, alias: Area (Miles) )
• GIS_ID ( type: esriFieldTypeString, alias: GIS Identifier, length: 50 )
• GLOBALID ( type: esriFieldTypeGlobalID, alias: GLOBALID, length: 38 )
• CREATED ( type: esriFieldTypeDate, alias: CREATED, length: 8 )
• EDITED ( type: esriFieldTypeDate, alias: EDITED, length: 8 )
• SHAPE.AREA ( type: esriFieldTypeDouble, alias: SHAPE.AREA )
• SHAPE.LEN ( type: esriFieldTypeDouble, alias: SHAPE.LEN )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata