NEONScience / NEONScience/neon-data-api

How to match a sensor_positions.csv entry with a NEON location

Open
#20 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
35
Forks
4
PR merge metrics
No merged PRs in 30d

Description

In my project working with NEON soil temperature and water content data, the information about soil sensor location and depth is important.
When I download data for a specific site, product and month via the API, there is a sensor_positions.csv file. For example: site Dead Lake (DELA), product DP1.00041.001, month 2018-09 has 32 entries in file NEON.D08.DELA.DP1.00041.001.sensor_positions.20181106T192857Z.csv:

HOR.VER,xOffset,yOffset,zOffset,pitch,roll,azimuth,referenceLatitude,referenceLongitude,referenceElevation
001.501,3.02,4.90,-0.02,2.50,0.00,0.00,32.541770,-87.804284,24.04
001.502,3.02,4.90,-0.06,2.50,0.00,0.00,32.541770,-87.804284,24.04
001.503,3.02,4.90,-0.16,2.50,0.00,0.00,32.541770,-87.804284,24.04
....
005.505,4.93,3.28,-0.47,0.00,0.00,1.00,32.541013,-87.805900,24.27
....

From the locations API, I can browse to locations such as: http://data.neonscience.org/api/v0/locations/DELA -> SOILAR100543 -> SOILPL100546 -> SOILTP108242 ->CFGLOC108243 with location description "Dead Lake Soil Temp Profile SP5, Z5 Depth". However, it is not clear which HOR.VER code corresponds to CFGLOC108243.

Given a HOR.VER location index from sensor_positions.csv (for example 005.505), Is there a way to automatically identify a matching NEON location provided by the /locations/ API (for example CFGLOC108243)?

In a future version of the API, would it be possible to include the location name (for example "CFGLOC108243") as another column in sensor_positions.csv? that would solve my issue.

Any workaround suggestion how to match a HOR.VER sensor_positions.csv entry with a CFGLOC.... name from the /locations/ API response would be very much appreciated!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the /locations/ API response for DELA with the sensor_positions.csv example for DP1.00041.001, focusing on how HOR.VER values and CFGLOC identifiers could be related. Done means documenting a reliable matching method or specifying the API/CSV change needed to expose the location name.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.