Data Dictionary template for Tempe Open Data.

An in-depth description of the Building Footprint GIS data layer outlining terms of use, update frequency, attribute explanations, and more.

Attribute field definitions for data created by Forest Practice GIS on plans and notices for timber harvesting either submitted to, approved, or accepted by, the California Department of Forestry and Fire Protection. Includes roads and hydrology within and adjacent to harvest areas.

Data Dictionary for State Parks.

An in-depth description of the various Natural Resources GIS data layers outlining terms of use, update frequency, attribute explanations, and more. District data layers include: Forest Preserve Boundaries and State Park Boundaries.

An in-depth description of the Street Centerline GIS dataset outlining terms of use, update frequency, attribute explanations, and more.

This is the data dictionary that accompanies the OSE Points of Diversion. It explains the various codes in the PODs. It is the 8th version of this data dictionary to assist with new codes included in the dataset.

Data dictionary for Tax Parcel Boundaries.

An in-depth description of the Trail Centerline GIS dataset outlining terms of use, update frequency, attribute explanations, and more.

An in-depth description of the Hydrology Lines GIS dataset outlining terms of use, update frequency, attribute explanations, and more.

An in-depth description of the various Political Boundaries GIS data layers outlining terms of use, update frequency, attribute explanations, and more. District data layers include: Lake County Boundary, County Board, Judicial Circuit Court Subcircuits, Political Townships, State Representative Districts, State Senate, Congressional Districts, and Voting Precincts.

City of Newton, MA GIS Data Dictionary

Data dictionary providing explanation on attributes and fields used in the shared shape file.

GIS Data Disclaimer: The data provided is approximate and does not meet the standards for mapping, surveying, or engineering. The data was compiled from various sources and is not a replacement for the authoritative source (i.e. Record Drawings, As-Built Plans, Legal Descriptions, etc.) or a field survey. The data is subject to constant change and may not be complete, accurate, or represent current conditions. The Department expressly disclaims all warranties of any type, expressed or implied, including but not limited to, any warranty as to the accuracy of the data, merchantability, or fitness for a particular purpose. The Department does not assume and specifically disclaims any liability for any errors, omissions, or inaccuracies in the information provided regardless of the cause of such or for any decision made, action taken, or action not taken by the user in reliance upon any data provided herein. Any use, including but not limited to download, reproduction or reprinting of this data in whole or in part is subject to this disclaimer and the Department does not warrant its use for any purpose.

An in-depth description of the Railroad Centerlines GIS data layers outlining terms of use, update frequency, attribute explanations, and more.

An in-depth description of the Hydrology Polygons GIS dataset outlining terms of use, update frequency, attribute explanations, and more.

An in-depth description of the Soils GIS data layers outlining terms of use, update frequency, attribute explanations, and more.

An in-depth description of the Edge of Pavement GIS data layer outlining terms of use, update frequency, attribute explanations, and more.

The City of Cambridge owns and maintains most street lights in the City. These were purchased from NSTAR in 2005. Types of lights include Cobrahead (most typical), and various types of decorative lighting. Park Lights are in a separate layer. Some street lights are owned by other organizations. DCR, the State, and Universities all own lights along the roadways they maintain. These street lights are in a layer 'StreetLightsNonCity'Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription PoleID type: Stringwidth: 15precision: 0 Unique ID for each street light. This number is also marked on each pole.

StreetName type: Stringwidth: 24precision: 0 Name of street the light is on

StreetSuffix type: Stringwidth: 4precision: 0 Street suffix for the street which the light is on.

Intersection type: Stringwidth: 20precision: 0 Street intersection if the light is at one

NumLamps type: Integerwidth: 4precision: 10 Number of lamps on a pole

EditDate type: Stringwidth: 8precision: 0 Date (year) lasted edited

Description type: Stringwidth: 25precision: 0 Type of head on the light.

Owner type: Stringwidth: 25precision: 0 Owner - always City of Cambridge

LEDchk type: Stringwidth: 6precision: 0 Field check by Cambridge GIS

Neighborhood type: Doublewidth: 8precision: 38 CDD Neighborhood each light is in.

Street_ID type: Stringwidth: 254precision: 0 Street ID. Each street has a unique ID. The first part of the PoleID.

Pole_Num type: Stringwidth: 254precision: 0 ID for each pole on a street. Part of the unique PoleID

FixtureType type: Stringwidth: 254precision: 0 Coding for LED project. Corresponds to the number of LED lights in a fixture. A1 = 120 bulbs, A2 = 80 bulbs, A3 = 40 bulbs per lamp

Lamp1 type: Stringwidth: 50precision: 0 Unique ID for a pole with 2 lamps.

Lamp2 type: Stringwidth: 50precision: 0 Unique ID for a pole with 2 lamps.

created_date type: Datewidth: 8precision: 0

last_edited_date type: Datewidth: 8precision: 0

30-year household forecasts at a parcel level within Fairfax County developed on the VALID_TO date in the attribute table.

For methodology and a data dictionary please view the IPLS data dictionary