ArcGIS REST Services Directory Login
JSON

Layer: ABI_LRT_NEPA (ID: 0)

View In:   ArcGIS Online Map Viewer

Name: ABI_LRT_NEPA

Display Field: name

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: The Atlanta Streetcar System Plan (SSP) was developed by Atlanta BeltLine, Inc. (ABI) and adopted by Atlanta City Council in December 2015. The SSP envisions a 50+ mile network of light rail transit across the City of Atlanta. The National Environmental Policy Act (NEPA) requires that impacts to the environment be considered prior to Federal action. As implementation of the SSP will require federal funding, ABI developed its NEPA Program to take the base information from the SSP and refine the concepts to “environmentally clear” the various LRT expansion alignments. ABI began its NEPA1 program in FY2013. The NEPA1 alignments are going through the Federal Transit Administration (FTA) review process and are expected to receive environmental clearance in FY2018. NEPA2 and NEPA3 program alignments are subsequent planning phases and have not yet been submitted for FTA review. The NEPA2 program is expected to begin in FY2018 and the NEPA3 program is expected to begin in FY2019.The NEPA1 dataset has been refined from the SSP corridors to reflect the most recent planning, concept design and other updates to the system expansion program, and reflects the alignments as of March 2017. The NEPA1 alignments are street-specific, as they are based on engineered concept alignments. The NEPA2 and NEPA3 datasets reflect the LRT corridors as set forth in the SSP. The NEPA2 and NEPA3 corridors are not yet street-specific, but rather intend to identify a general service area across the City of Atlanta. The NEPA2 and NEPA3 alignments will be refined and datasets updated over the next several years.

Service Item Id: d43c97849e064855b6c8be7c368f3a15

Copyright Text: City of Atlanta Department of Planning and Community Development City of Atlanta Department of Public Works Atlanta BeltLine, Inc.

Default Visibility: true

MaxRecordCount: 1000

MaxSelectionCount: 0

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

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field:

Fields: Templates:
Capabilities: Query

Sync Can Return Changes: true

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: true

Supports ApplyEdits By Upload Id: true

Edit Fields Info:
Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Child Resources:

Supported Operations:   Query   Query Attachments   Query Analytic   Query Top Features   Query Bins   Append   Validate SQL   Generate Renderer   Return Updates   Metadata   Update Metadata