View In:   ArcGIS Online Map Viewer

Name: Boundary Stones Location

Display Field: STONE_NUM

Type: Feature Layer

Geometry Type: esriGeometryPoint

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. The Washington D.C. Historic Boundary Stones were then connected to form the Washington D.C. Historic Boundary. However, this 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

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

Extent:

XMin: -8590809.148995837
YMin: 4691667.79012873
XMax: -8561474.766581649
YMax: 4721094.486695701
Spatial Reference: 102100  (3857)  LatestVCSWkid(0)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
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: true
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: false
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field:

Fields:

• CREATION_DT ( type: esriFieldTypeDate, alias: CREATION_DT, editable: true, nullable: true, length: 8, defaultValue: null, modelName: CREATION_DT )
• NARRATIVE ( type: esriFieldTypeString, alias: NARRATIVE, editable: true, nullable: true, length: 200, defaultValue: null, modelName: NARRATIVE )
• LOCATION_DESCRIPTION ( type: esriFieldTypeString, alias: LOCATION_DESCRIPTION, editable: true, nullable: true, length: 200, defaultValue: null, modelName: LOCATION_DESCRIPTION )
• STONE_NUM ( type: esriFieldTypeString, alias: STONE_NUM, editable: true, nullable: true, length: 10, defaultValue: null, modelName: STONE_NUM )
• PIC_LINK ( type: esriFieldTypeString, alias: PIC_LINK, editable: true, nullable: true, length: 100, defaultValue: null, modelName: PIC_LINK )
• Z ( type: esriFieldTypeDouble, alias: Z, editable: true, nullable: true, defaultValue: null, modelName: Z )
• Z_FT ( type: esriFieldTypeDouble, alias: Z_FT, editable: true, nullable: true, defaultValue: null, modelName: Z_FT )
• XCOORD ( type: esriFieldTypeDouble, alias: XCOORD, editable: true, nullable: true, defaultValue: null, modelName: XCOORD )
• YCOORD ( type: esriFieldTypeDouble, alias: YCOORD, editable: true, nullable: true, defaultValue: null, modelName: YCOORD )
• GIS_ID ( type: esriFieldTypeString, alias: GIS_ID, editable: true, nullable: true, length: 50, defaultValue: null, modelName: GIS_ID )
• GLOBALID ( type: esriFieldTypeGlobalID, alias: GLOBALID, editable: false, nullable: false, length: 38, defaultValue: null, modelName: GLOBALID )
• CREATOR ( type: esriFieldTypeString, alias: CREATOR, editable: true, nullable: true, length: 255, defaultValue: null, modelName: CREATOR )
• CREATED ( type: esriFieldTypeDate, alias: CREATED, editable: true, nullable: true, length: 8, defaultValue: null, modelName: CREATED )
• EDITOR ( type: esriFieldTypeString, alias: EDITOR, editable: true, nullable: true, length: 255, defaultValue: null, modelName: EDITOR )
• EDITED ( type: esriFieldTypeDate, alias: EDITED, editable: true, nullable: true, length: 8, defaultValue: null, modelName: EDITED )
• LATITUDE ( type: esriFieldTypeDouble, alias: LATITUDE, editable: true, nullable: true, defaultValue: null, modelName: LATITUDE )
• LONGITUDE ( type: esriFieldTypeDouble, alias: LONGITUDE, editable: true, nullable: true, defaultValue: null, modelName: LONGITUDE )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID, editable: false, nullable: false, defaultValue: null, modelName: OBJECTID )

Templates:

• Name: Boundary Stones Location
  Description:
  Prototype:
  LATITUDE: null
  CREATION_DT: null
  NARRATIVE: null
  LOCATION_DESCRIPTION: null
  STONE_NUM: null
  PIC_LINK: null
  Z: null
  Z_FT: null
  XCOORD: null
  YCOORD: null
  GIS_ID: null
  LONGITUDE: null
  CREATOR: null
  CREATED: null
  EDITOR: null
  EDITED: null
  
  Drawing Tool: esriFeatureEditToolPoint

Capabilities: Query,Extract

Sync Can Return Changes: false

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: false

Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Child Resources:   Field Groups   Contingent Values

Supported Operations:   Query   Query Analytic   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata   Update Metadata