Skip to content

geospatial data for automated assignment by GPS location #4

Description

@emiliom

Summary of Discussion between Emma, Keshav and Emilio, 4/27/2018

Codes preceding the category are as follows: <desirability (D)>-<accessibility (A)>, where 1 is the most desirable / accessible

  • (1D-1A) climate
    • precipitation and temperature
    • PRISM for lower 48, other dataset for Puerto Rico (probably good approach, b/c PR climate is so different!)
    • mean annual averages vs more refined estimates/indices?
    • data for the actual day when samples were collected? can we hunt for nearby stations that would give us data for the actual day. Keshav will do the leg work. Start with CUAHSI HydroClient
  • (2D-?TBD) soil type and subtypes
    • I'll follow up with USDA/USFS guy
    • characteristic properties
  • (3D-?TBD) land cover/use
    • I'll bring a couple of options, including the national veg map and a remote-sensing based map. Should include PR.
  • (4D-?TBD) topography
  • (5D-?TBD) atmospheric composition
    • CO2 and CH4 column abundance (GOSAT data, CH4 only?). But may not be as useful
    • AmeriFlux flux? Promising. But let's focus first on the other 4 mapped data types!

Some general comments, notes

Climate

Soil types

Land cover/use

Elevation and derivatives (slope & aspect)

  • The National Map - Elevation Point Query Service. This is what I used in the demos at the CZIMEA Aug 2017 Portland meeting.
  • Roland's email for additional resources (edited a bit):

    WCSs for NLCD and elevation currently exist, although the latter is characterized as a prototype. Those and other National Map services are listed here. There are a number of avenues for accessing 3DEP content (point clouds, interpolated rasters), including through the National Map viewer. There's also point query service--not sure if the content is different for this endpoint than via WCS tho.

    I will check to see about plans for web services around elevation derivatives. My understanding is that 3DEP is not supporting these because the 3DEP program is focusing its energy on building infrastructure for distributing CONUS-wide lidar in the coming years

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions