Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent pre-processing of pour-points into Route_link.nc #224

Open
AlvaroBBuoro opened this issue Nov 12, 2018 · 1 comment
Open

Inconsistent pre-processing of pour-points into Route_link.nc #224

AlvaroBBuoro opened this issue Nov 12, 2018 · 1 comment

Comments

@AlvaroBBuoro
Copy link

I established a list of 'pour_points' as gages, and pre-processed with success under reach_based routing option. Wrf-hydro runned but the output from frxst_pts.txt contained only a fraction of these pour-points.

Expected Behavior

I expected that all the pour_points would be flagged and tracked in the frxst_pts.txt

Current Behavior

I imported the Route_link.nc resulting from the pre-processing into ArcGis and plotted the results.
I found out that only 57 of the 106 gages where flagged with the correct gages number passed in the pour_points list.
AND the position of these where sometimes upstream of the position passed in the list (although still in the stream network )

Possible Solution

Steps to Reproduce (for bugs)

  1. Generate a list of pour-points (i.e. 100 points)
  2. run pre-processing in ArcGis under option channel routing
  3. analyse the position of the gages reported at Route_link.nc
  4. compare with the pour-points list and naming used

Your Environment

  • Version of the code used: Pre-processing V5
  • Operating System and version: Windows 10
  • Compiler and version: none,, just the pre-processing generate this
  • Other relevant information:
@kmsampson
Copy link
Collaborator

This appears to be related to the ArcGIS pre-processor, not necessarily the WRF-Hydro code. You may log this issue here: https://github.com/NCAR/wrf_hydro_arcgis_preprocessor or email [email protected] for more direct support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants