Forums / New Reports / Advanced Reporting

Advanced Reporting

14 posts, 0 answered
  • Nicole Tancreto
    NTancreto@psmfc.org avatar
    61 posts
    Registered:
    21 Feb 2012
    16 Oct 2012
    Use this thread to suggest new features for the advanced reporting tool.
    Link to this post
  • Scott Putnam
    sputnam avatar
    7 posts
    Registered:
    25 Oct 2012
    18 Dec 2012 in reply to NTancreto@psmfc.org
    It would be useful to get information about activity upstream of site X.  For example, it would save time and minimize file sizes if I could get all releases upstream of the Salmon River smolt trap by entering Release Site RKM ">522.33.103".
    Link to this post
  • Dave Marvin
    Dave.Marvin avatar
    13 posts
    Registered:
    02 Nov 2012
    10 Mar 2013 in reply to sputnam
    Scott, et al:

    Since you're only interested in Salmon River Basin releases above the SALTRP, so what you REALLY want is River_KM >"522.303.103" AND HUC_Code between 17060201 and 17060299.  If you can use the tertiary HUC code rather than the quaternary, then your pseudo-code for the parameter might be something like "river_km >'522.303.103' and HUC3=170602".  Without the HUC-Code constraint, your query will return the release data for the Yakima and mid-Columbia above the confluence with the Snake River.

    It becomes a bit more complicated if you want to run the same query for the Snake River Trap (SNKTRP).  Now you want all the releases in the Salmon River (170602*), the releases in the Snake River proper (17060101 and 17060103 above the Lewiston trap), releases in the Grande Ronde Basin (upper and lower Grande Ronde River, and Catherine Creek, each with their own quaternary HUC), and the Imnaha River (17060102).  Your pseudo-code parameter request is now something like "release_km >'522.225' and ( (huc_code between 17060101 and 17060106) or (huc_code like '170602??') )".  If you can use the tertiary HUC definitions instead of the quaternary codes, then the parameter p-code can be simplified to "release_km >'522.225' and HUC3 in (170601, 170602).

    Of course, the HUC constraints are in addition to your excellent suggestion of gt/lt/eq constraints against the river_km string.
    Link to this post
    Last modified on 10 Mar 2013 22:03 by Dave.Marvin
  • Jeremy Bender
    jeremybender avatar
    3 posts
    Registered:
    29 Oct 2012
    11 Mar 2013 in reply to NTancreto@psmfc.org
    I think a feature that allowed for sharing of custom reports between users would be useful.  The options to share the output of a report with other people via email are great, however I would like  to be able to send the actual raw query to someone so that they can have it in their profile to run whenever they want. 
    Link to this post
  • Nicole Tancreto
    NTancreto@psmfc.org avatar
    61 posts
    Registered:
    21 Feb 2012
    12 Mar 2013 in reply to jeremybender
    I can see why that would be a useful feature and will look into the possibility of implementing something like this. 
    Link to this post
  • Kyle Martens
    kmartens avatar
    6 posts
    Registered:
    18 May 2012
    25 Apr 2013 in reply to NTancreto@psmfc.org
    Could you add observation site and year as filtering criteria in the Complete Tag History in Query Builder 2?  It is nice to get all information of fish that you detect at a reader.   
    Link to this post
  • Kyle Martens
    kmartens avatar
    6 posts
    Registered:
    18 May 2012
    25 Apr 2013 in reply to NTancreto@psmfc.org
    It would also be nice to have "release rkm" as a filter option in the Complete tag history query.  It would make it easier to know the fate of fish tagged in each reach of a stream.
    Link to this post
  • Kyle Martens
    kmartens avatar
    6 posts
    Registered:
    18 May 2012
    26 Apr 2013 in reply to NTancreto@psmfc.org
    Just another thought on the complete tag history query.  Could you add a filter to add or subtract types of events?  It would be good if I wanted to create a mark/release file and I want tagging details combined with recaptured details, but I don't need the observation or mort details.

    Link to this post
  • Nicole Tancreto
    NTancreto@psmfc.org avatar
    61 posts
    Registered:
    21 Feb 2012
    29 Apr 2013 in reply to kmartens
    You can get the complete tag history of all fish detected at an interrogation site by using a saved report as a filter on a Complete Tag History report.

    Create an Interrogation Detail report for the interrogation site and time period in which you are interested. Make sure the report only has the Tag attribute in it (and the Count metric) and save it as static (not prompted). 

    Run the Complete Tag History report and select Tag-Saved Report as your filter parameter. Then select the report you saved in the step above. You will get the complete tag history for all tags reported in your first report.

    See this page for step-by-step instructions: http://beta.ptagis.org/support/documentation/lists/documentation/how-to-use-a-saved-report-as-a-filter-on-tag-code

    Link to this post
    Last modified on 29 Apr 2013 16:04 by NTancreto@psmfc.org
  • Nicole Tancreto
    NTancreto@psmfc.org avatar
    61 posts
    Registered:
    21 Feb 2012
    29 Apr 2013 in reply to kmartens
    kmartens said:Just another thought on the complete tag history query.  Could you add a filter to add or subtract types of events?  It would be good if I wanted to create a mark/release file and I want tagging details combined with recaptured details, but I don't need the observation or mort details.


    You can do this by using the View Filter after you have the complete tag history report filtered to the group of fish in which you are interested.

    1. Turn on the View Filter, if it is not already showing, by selecting it from the Tools pull-down menu
    2. Click Add Condition
    3. Select Event Type from the Filter On combo-box
    4. Select the Mark/Release and Recap event types and click the check mark to apply the filter. 

    See the attached screen shot.
    Link to this post
  • Nicole Tancreto
    NTancreto@psmfc.org avatar
    61 posts
    Registered:
    21 Feb 2012
    29 Apr 2013 in reply to kmartens
    kmartens said:It would also be nice to have "release rkm" as a filter option in the Complete tag history query.  It would make it easier to know the fate of fish tagged in each reach of a stream.


    We are working on adding the Release RKM as a filter option and I will post here when it is available.

    Thanks for your suggestions and questions.
    Link to this post
  • Nicole Tancreto
    NTancreto@psmfc.org avatar
    61 posts
    Registered:
    21 Feb 2012
    21 May 2013 in reply to kmartens
    kmartens said:It would also be nice to have "release rkm" as a filter option in the Complete tag history query.  It would make it easier to know the fate of fish tagged in each reach of a stream.

    We have added Release Site RKM as a filter option in all of the Query Builder 2 and Pit Pro reports. Give it a try and let us know if you need any other filter options.
    Link to this post
  • Ryan Richmond
    ryanr72 avatar
    4 posts
    Registered:
    02 Nov 2012
    01 May 2014 in reply to NTancreto@psmfc.org
    Would it be possible to add "Additional Positional Comments" to the list of available attributes for advanced reporting?  We are using the additional positional comment to identify release groups and would like to have them displayed in our queries.  Thanks!
    Link to this post
  • Nicole Tancreto
    NTancreto@psmfc.org avatar
    61 posts
    Registered:
    21 Feb 2012
    01 May 2014 in reply to ryanr72
    Per the 2009 Specification Document, Additional Positional Comments are not recorded into the PTAGIS database, and are not available through the reporting system. Textual Comments are available through the reporting system and could be used instead.
    Link to this post