Forums / Proposed MRR Fields / Release Site Latitude/Longitude

Release Site Latitude/Longitude

4 posts, 0 answered
  • Sebastian Dudek
    sdudek@psmfc.org avatar
    38 posts
    Registered:
    17 Feb 2012
    25 Mar 2014
    Nicole suggests recording the Release Site latitude and longitude. This would be in addition to the normal Release Site code, but might be able to replace the release river kilometers field.
    Link to this post
    Last modified on 13 May 2014 23:05 by NTancreto@psmfc.org
  • Kyle Martens
    kmartens avatar
    6 posts
    Registered:
    18 May 2012
    16 Jun 2014 in reply to sdudek@psmfc.org
    Please do not remove release rkm.  I find it very helpful for querying  data from reaches within release sites.  I like the addition of gps coordinates, but I don't want to lose the ability to do a quick query with rkms.  I know the streams I work on by rkm, but not by gps coordinates without ARC view or google earth.  I would be ok with just having gps coordinates in P4 and then having PTAGIS automatically calculate them into rkms in the database.
    Link to this post
  • Keith van den Broek
    keith.vdb avatar
    1 posts
    Registered:
    20 Nov 2012
    16 Jun 2014 in reply to kmartens
    Lat/Long as an MRR reporting field, with rkm as a query option on the backend would be much more usable in our work.  If that is feasible I would suggest adding additional spatial scales as available query tools as well- eg. HUC5, HUC6, stream name, major spawning area.  Lat/Long is an easy metric for reporting, but is more involved for queries outside your own dataset without more advanced geospatial analysis tools.  
    Link to this post
  • Dave Marvin
    Dave.Marvin avatar
    13 posts
    Registered:
    02 Nov 2012
    08 Jul 2014
    Geo-spatial coordinates and river kilometer values provide separate but complementary information.  The Lat/Lon coordinates allow the data consumer to visually navigate to a given location, and allow the data analyst to identify all locations within a predetermined boundary.  The rkm hierarchy provides information on the descendant and antecedent path(s) available to anadromous or potamodromous fish, the position of an MRR event relative to other locations upstream or downstream, and the absolute migratory distance from that position within the Columbia Basin to the Pacific Ocean.  That last usage makes it possible to compute the migratory distance between any two stream points.  Depending on the sinuosity of the stream path, this distance may be substantially longer than the linear (aerial) distance between two Lat/Lon points.

    Since all of the "fixed" MRR locations (e.g., Bonneville Dam or the Clearwater River Trap) have immutable rkm values and Lat/Lon coordinates as part of their definition, these values only need to be added or appended to MRR event data sets when the events occur on or along a stream or river.  If the current watershed mapping tools and libraries are robust enough, then perhaps the river kilometer value within a stream or river segment can be calculated directly from the reported GPS coordinates.  Otherwise, or perhaps as a cross-check, the instream RKM can be calculated the old-fashioned way, from a USGS topographic map.
    Link to this post