| ArcGIS REST Services Directory |
| Home > services > 23715_Storymap_Features (FeatureServer) > All Layers and Tables | | API Reference |
Plant Observations comprise a subset of data within the Idaho Natural Heritage Program Species Diversity Database, managed by the Idaho Fish and Wildlife Information System (IFWIS) at Idaho Dept. of Fish and Game. This feature class contains observations NOT compilations in Element Occurrence (EO) format. Additionally, it includes negative data observations. To completely understand plant observations within any given area one must look at three feature classes that include plant observation point, line, and polygon observations as well as the EO polygons (four feature classes total). Plant observation information are assessed for incorporation into the NatureServe methodology EO format on an as funded basis. At this time, not all observations have been assigned to an EO and older (pre 2009) EOs may not have associated observations displayed geospatially. The user can identify if an observation is associated within an EO if the EO_ID and EONumber fields are not null. EO_ID is the unique ID that relates to the EO polygon feature class.
Roadkill is observed and collected by internal staff within ITD or IDFG, and public sources. Please not most observations are not checked for accuracy or completeness.
Core Attributes These attributes are common across all feature classes extracted as part of the SWAAI project where applicable.
UniqueID -> Unique ID for this feature type, assigned by Cyclomedia staff.
RouteID -> Route ID based on ITD’s Esri Roads & Highways linear referencing system (LRS). A copy of ITD’s LRS network was provided to Cyclomedia.
RouteDirectionCode -> Travel direction of nearest highway lane to feature, ascending (A) or descending (D).
Measure or FromMeasure/ToMeasure -> LRS measure (in the case of discrete point features) or from/to LRS measures (in the case of line or polygon features) based on ITD’s Esri Roads & Highways LRS.
SideOfRoad -> Side of road location of feature, generally L (left) or R (right). Values for B (both), C (center), and N (neither) were also included as text domain values for use where applicable.
X/Y/Z or From_X/To_X/From_Y/To_Y/From_Z/To_Z -> Longitude (X), Latitude (Y), and Elevation (Z) values were included for each extracted feature (X/Y/Z for discrete points, to/from X/Y/Z for lines and polygons) Rather than the metric northing/easting present in the Idaho Transverse Mercator (IDTM, WKID: 8826) projection, the projection used for all SWAAI datasets, X and Y are decimal-degree latitude/longitude. The elevation field, Z, is in U.S. feet.
StreetSmartLink -> URL link to the feature’s location in Cyclomedia’s browser-based Street Smart photo and LiDAR depth surface viewer. Following the link brings the user directly to the closest Street Smart collection location and angles the view to look directly at the feature in the 360° photograph.
Comments -> General comments field.
CollectedDate -> Date the feature was observed and field-collected by Cyclomedia during the vehicle-based data collection process.
Key Attributes These attributes are unique to this feature class, or are Core Attributes used differently than other feature classes extracted as part of the SWAAI project.
ApproachType -> General approach type determined by Cyclomedia extraction staff, based on the visual appearance of the property each approach provided access to. These types were limited to a few basic types of approach recognized by ITD: residential, commercial, agricultural, and public road. A fifth "median crossover" type was added during the extraction process as Cyclomedia included maintenance and emergency crossovers on interstate highways. Although not technically approaches, these interstate crossovers were included due to their visual similarity to approach accesses on non-interstate highways. This short integer field includes the ApproachType domain, with the following coded domain values:
Residential (1) Approaches that appeared to lead to private residences, either single- or multiple-family.
Commercial (2) Approaches that appeared to lead to private or public (government) places of business.
Agricultural (3) Approaches that appeared to lead to agricultural areas, typically crop fields, but also possibly grazing land.
Public Road (4) Approaches that appeared to be public roads, usually identifiable by the presence of an off-highway-system-facing stop sign or other traffic control devices. This type includes interchange on-off ramps and frontage road accesses.
Median Crossover (5) Not technically a type of approach, these were included in this dataset due to their visual similarity to approaches. Both maintenance and emergency crossovers are included in this type.
Unknown (97) A category for approaches not easily identifiable as a particular type by visual inspection.
Sidewalk -> A yes/no (No=0; Yes=1) field indicating the presence of sidewalk across the approach feature.
Paved -> A yes/no (No=0; Yes=1) field indicating whether the approach was paved with asphalt, polymer, or concrete. For the purposes of this inventory, Paved=Yes was considered to have at least a paved apron area immediately adjacent to the highway.
Gated -> A yes/no (No=0; Yes=1) field indicating the presence of a gate on the approach.
Width_ft -> Approach width measured behind the turn radii. Approach line feature locations indicate where the measurement was taken on the approach.
Spatial Reference -> All data extracted as part of the SWAAI project is projected to Idaho Transverse Mercator (WKID: 8826), using the NAD 1983 (WKID: 4269) geographic coordinate system. NAVD88 (WKID: 6360) was the vertical coordinate system used for all elevation measurements.
Core Attributes These attributes are common across all feature classes extracted as part of the SWAAI project where applicable.
UniqueID -> Unique ID for this feature type, assigned by Cyclomedia staff.
RouteID -> Route ID based on ITD’s Esri Roads & Highways linear referencing system (LRS). A copy of ITD’s LRS network was provided to Cyclomedia.
RouteDirectionCode -> Travel direction of nearest highway lane to feature, ascending (A) or descending (D).
Measure or FromMeasure/ToMeasure -> LRS measure (in the case of discrete point features) or from/to LRS measures (in the case of line or polygon features) based on ITD’s Esri Roads & Highways LRS.
SideOfRoad -> Side of road location of feature, generally L (left) or R (right). Values for B (both), C (center), and N (neither) were also included as text domain values for use where applicable.
X/Y/Z or From_X/To_X/From_Y/To_Y/From_Z/To_Z -> Longitude (X), Latitude (Y), and Elevation (Z) values were included for each extracted feature (X/Y/Z for discrete points, to/from X/Y/Z for lines and polygons) Rather than the metric northing/easting present in the Idaho Transverse Mercator (IDTM, WKID: 8826) projection, the projection used for all SWAAI datasets, X and Y are decimal-degree latitude/longitude. The elevation field, Z, is in U.S. feet.
StreetSmartLink -> URL link to the feature’s location in Cyclomedia’s browser-based Street Smart photo and LiDAR depth surface viewer. Following the link brings the user directly to the closest Street Smart collection location and angles the view to look directly at the feature in the 360° photograph.
Comments -> General comments field.
CollectedDate -> Date the feature was observed and field-collected by Cyclomedia during the vehicle-based data collection process.
Key Attributes These attributes are unique to this feature class, or are Core Attributes used differently than other feature classes extracted as part of the SWAAI project.
ApproachType -> General approach type determined by Cyclomedia extraction staff, based on the visual appearance of the property each approach provided access to. These types were limited to a few basic types of approach recognized by ITD: residential, commercial, agricultural, and public road. A fifth "median crossover" type was added during the extraction process as Cyclomedia included maintenance and emergency crossovers on interstate highways. Although not technically approaches, these interstate crossovers were included due to their visual similarity to approach accesses on non-interstate highways. This short integer field includes the ApproachType domain, with the following coded domain values:
Residential (1) Approaches that appeared to lead to private residences, either single- or multiple-family.
Commercial (2) Approaches that appeared to lead to private or public (government) places of business.
Agricultural (3) Approaches that appeared to lead to agricultural areas, typically crop fields, but also possibly grazing land.
Public Road (4) Approaches that appeared to be public roads, usually identifiable by the presence of an off-highway-system-facing stop sign or other traffic control devices. This type includes interchange on-off ramps and frontage road accesses.
Median Crossover (5) Not technically a type of approach, these were included in this dataset due to their visual similarity to approaches. Both maintenance and emergency crossovers are included in this type.
Unknown (97) A category for approaches not easily identifiable as a particular type by visual inspection.
Sidewalk -> A yes/no (No=0; Yes=1) field indicating the presence of sidewalk across the approach feature.
Paved -> A yes/no (No=0; Yes=1) field indicating whether the approach was paved with asphalt, polymer, or concrete. For the purposes of this inventory, Paved=Yes was considered to have at least a paved apron area immediately adjacent to the highway.
Gated -> A yes/no (No=0; Yes=1) field indicating the presence of a gate on the approach.
Width_ft -> Approach width measured behind the turn radii. Approach line feature locations indicate where the measurement was taken on the approach.
Spatial Reference -> All data extracted as part of the SWAAI project is projected to Idaho Transverse Mercator (WKID: 8826), using the NAD 1983 (WKID: 4269) geographic coordinate system. NAVD88 (WKID: 6360) was the vertical coordinate system used for all elevation measurements.