Description: Each point feature shows the location where a street or park lighting fixture is located. Information about ownership, bulb type, approximate installation date, and Xcel Energy’s billing rate coding is also included.
Description: By default, residential areas are not lit by streetlights. Over the years, residents have petitioned for streetlights to be installed in their neighborhoods and assessed the bill for powering these streetlights. The Street Lighting Districts represents these residential areas served by streetlights.
Description: Each point feature shows the location of a traffic signal base. Signal ownership is given as city, county, or state, as well as other details about mounting structure, approach direction, and approximate date installed.
Description: Each point feature shows the location of a signal cabinet and includes data about the cabinet’s ownership, base material, controller type, and controller model.
Description: Each point feature shows the location of a street or park sign owned by the city. Bus route signs are also included but are owned by MetroTransit. The type of sign is indicated by the MUTCD Code and description. Additional data is collected, when available, such as the approximate date it was installed and the direction the sign itself is facing.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: Linear features (on either or both sides of a street) to show where parking is prohibited, restricted by hours, restricted seasonally, or restricted to residents only.
Description: Assorted traffic count studies performed throughout the years. Points are placed on the approximate location the data was collected. Studies are typically preformed during the work week for a few days and then averaged to calculate the ADT (Average Daily Traffic).
Description: These linear features show the locations of fences, walls, retaining walls, and guardrails. Each feature includes data about material, purpose, gates, height, and assumed ownership. Actual ownership may differ depending on agreements in place; research of each fence/wall was not performed with this mapping effort.
Description: Points showing the location of each bridge in the city. This layer includes bridges owned by the city or by another entity. It also includes bridges designated for use by vehicle traffic, railroad traffic, pedestrian traffic, or golf cart traffic.
Description: Points representing locations where a train track intersects a road. Most crossings are at-grade; however, several are grade-separated where a bridge separates the two levels. Each crossing is attributed with characteristics that railroad operators are interested in, such as the railroad name/agency, the official crossing number that was assigned by the railroad, and the mile marker. The phone number for contacting the railroad is listed.
Description: All trails, sidewalks, and bikeways that are within Golden Valley. Focus is on the publicly accessible network, only a few private trails and sidewalks are mapped. Each line segment includes information such as the material, the designed use (pedestrian, road bikes, or shared), and winter maintenance.This dataset is closely aligned with the Bikeways Data Standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/bikeways/index.html
Description: These linear features represent the centerline of the railroad routes that cross Golden Valley. Spurs are mapped but individual tracks are not detailed. The railroads that cross Golden Valley are: Union Pacific, Canadian Pacific Kansas City, and Burlington Northern Santa Fe.
Description: These linear features contain information about each street including its name, owner, one-way status, route system, route number, and functional classification.This dataset is based on and is closely aligned with the Road Centerline Data Standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/roadcenterline/index.html
ST_CONCAT
(
type: esriFieldTypeString, alias: Street Name Full, editable: true, nullable: true, length: 150, defaultValue: null, modelName: ST_CONCAT
)
ONEWAY
(
type: esriFieldTypeString, alias: One Way, editable: true, nullable: true, length: 1, defaultValue: null, modelName: ONEWAY
, Coded Values:
[T: Traffic flows from to point (against the arc)]
, [F: Traffic flows from from point (with the arc)]
, [B: Traffic flows both directions]
)
Description: This road centerline data is used for internal maintenance tracking. It contains similar data as the road centerline layer, but it is limited to city owned streets. The field for ‘Todays OCI’ is an estimated Overall Condition Index which rates each street on a scale from 0-100. Ratings are calculated based on recent field inspections, improvements made to the road, and elapsed time.