Error Number: eRvX0008

Why the error occurred & solution:

RivEX always checks before it starts a stream ordering process to see if node ID values for each polyline are unique.  If they are not then this will cause unexpected errors in the stream ordering process.  RivEX will stop at the first occurrence of a polyline with node IDs the same. This error can typically occur if the network has been edited by the addition of new polylines but their node fields have not been updated.  This problem can be resolved by running the Update Attribute Table process within RivEX.

Error Number: eRvX0009

Why the error occurred & solution:

RivEX always checks before it starts a process to see if all polylines in the field you specified as a unique ID field actually contains unique IDs.  RivEX will stop at the first occurrence of a non-unique ID value informing you which polyline ID has failed.  Click here to find out how to create unique ID values for a field.

Error Number: eRvX0010

Why the error occurred & solution:

A general error has occurred in this procedure and you need to read the full message returned by RivEX. The error log file will list the current variable settings such as polyline ID or node number and this will help you understand at what point the procedure failed.  It is possible that some of errors returned at this point are caused by geometric problems such as null length polylines. These can be easily identified by adding a temporary field (of type double) to your river network and setting this to the length of the polyline (you would use the calculate geometry option). Sort your table by this field and any zero length polylines would need to be deleted.

Error Number: eRvX0018

Why the error occurred & solution:

RivEX attempted to locate a Geodatabase in the C:\RivEX\Output folder. The Geodatabase name was constructed using the original layer name. If you have subsequently renamed your layer (eg. riv1 to riv2) then RivEX attempted to find a Geodatabase called riv2_Tables.mdb which obviously does not exist! Ensure the segment ID table Geodatabase

starts with the river layer name it was built from.

Error Number: eRvX0028

Why the error occurred & solution:

This warning dialog is informing you that of your bank side data was not attributed corrected and this could be for a variety of reasons, please review the bank side help page here.

Error Number: eRvX0077

Why the error occurred & solution:

This error occurs because you have built the data dictionaries using an ID field which is not the same ID field you used to build the segment identifier tables.  For example, when you ran the segment identifier tool you may have used a field "FID" as the unique polyline ID.  Later you are using the find sources tool but you selected the "ComID" field as the unique ID polyline.  Whilst they could both identify the polyline uniquely it is "FID" values that are store in the segment identifier tables, so they will never match.

Error Number: eRvX0104

Why the error occurred & solution:

MS Excel has a column limit of 256 and your input data will exceed this limit crashing Excel.  You need to reduce the amount of data in your input dataset.

Error Number: eRvX0140

Why the error occurred & solution:

You have provided RivEX a network which has some illogical network feature, for example two polylines flowing to a single point within the network.  This may be a real world feature such as a sink hole in a karst region but RivEX is unable to resolve this problem and gets itself into a loop and bails out. Review the returned polyline ID and edit the network accordingly. Running your network through the quality control tools before using any RivEX tool is highly recommended.

Error Number: eRvX0167

Why the error occurred & solution:

Getting this error message means RivEX+ has tried 200 times to find a location on the network but failed. This could occur for a variety of reasons. If you have set a large exclusion zone around points then eventually you will hit a point when there is not enough space on the network for your desired number of points. Consider reducing the size of the exclusion zone or sample for less points.  More advice on how RivEX+ generates point can be found here.

Error Number: eRvX0168

Why the error occurred & solution:

Getting this error message means RivEX+ has tried 200 times to find a location on the network within a grid cell but failed. This could occur for a variety of reasons. If you have set a large exclusion zone around points then eventually you will hit a point when there is not enough space on the network for your desired number of points. You may simply have very little length of the network in the grid cell. Consider reducing the size of the exclusion zone or sample for less points.  More advice on how RivEX+ generates point can be found here.

Error Number: eRvX0169

Why the error occurred & solution:

You specified that the grids used for sampling were to be removed at the end of the processing but RivEX+ has failed to do this.  Maybe they are file locked by another application?  This grid shape files are stored in C:\RivEX\Output and need to be removed manually.

Error Number: eRvX0172

Why the error occurred & solution:

Getting this error message means RivEX+ has tried 200 times to find a location on the network within a polygon but failed. This could occur for a variety of reasons. If you have set a large exclusion zone around points then eventually you will hit a point when there is not enough space on the network for your desired number of points. You may simply have very little length of the network in the polygon. Consider reducing the size of the exclusion zone or sample for less points.  More advice on how RivEX+ generates point can be found here.

Error Number: eRvX0173

Why the error occurred & solution:

This warning is simply to inform you that you are processing a very large river network ( > 100,000 polylines) and RivEX+ may take some time to complete the task, please be patient.

Error Number: eRvX0202

Why the error occurred & solution:

No data was returned from the segment ID table. This could be due to you specifying the incorrect polyline ID field. When you built the segment ID tables you had to specify the polyline ID (#2 drop down list in Layer to Process panel) but now you have specified an alternate polyline ID, which will not exist in the segment tables. For example the American NHD dataset has a ComID field which you can select, but the segment tables may have been built using the ObjectID field. Try an alternate ID field?  As best practise you should consider using only one field that unique identifies the polyline.

Error Number: eRvX0209

Why the error occurred & solution:

RivEX has done a quick check on the Strahler Order output and found X number of polylines to have an order value of ZERO. This is not possible for Strahler Order as the minimum value should always be ONE.  This indicates a topological error, such as the polyline pointing in an upstream direction. 

You must do an attribute query on your data to select the polylines where Strahler = 0 and examine why. 

It is highly recommended that you run your network through ALL quality controls before using the Strahler Ordering tool. If you need to edit your network (e.g. flip the direction of a polyline) then you can find advice here.

Error Number: eRvX0223

Why the error occurred & solution:

RivEX cannot find the Segment ID Geodatabase in C:\RivEX\Output. Have you moved the database or renamed the network layer since you created the segment ID Geodatabase? RivEX is building a path name based upon your currently selected river layer but if this is a different name to what was used when the segment ID Geodatabase was built then it will not find the Geodatabase.  Do not change the name of your river layer whilst processing it with RivEX.

Error Number: eRvX0263

Why the error occurred & solution:

You have at least 2 layers loaded with identical names. RivEX and RivEX+ would not be able to determine which layer is which in later processing steps. Simply rename the layer (highlight layer in the TOC and press F2) to resolve this problem.

Error Number: eRvX0269

Why the error occurred & solution:

This warning message is to inform you that your data must contain fields generated by RivEX as it is searching for specific field names. If it cannot find these fields then it will fail to transfer the information.  You may have used another tool for generating node information but this will almost certainly have created different field names which RivEX will not recognise.

Error Number: eRvX0270

Why the error occurred & solution:

This warning message is informing you that you must ensure that your site data you wish to process is snapped to the network. A "snapped" point is a point that lies directly onto of the river polyline. RivEX provides a tool for snapping sites.

Error Number: eRvX0298

Why the error occurred & solution:

RivEX requires that your site data has its coordinate system set.  It is possible to create a dataset without setting the projection.  For example you have imported XY data from Excel and saved the event layer to a Shapefile without setting the projection.  This can be easily rectified by using the Geo-processing tool "Define Projection". Open the Arc Tool Box and locate the Define Projection tool which is usually located under Data Management Tools > Projections and Transformations.  This creates a .prj file with the same name as your site layer and is used by ArcMap.

Error Number: eRvX0299

Why the error occurred & solution:

Some of the RivEX processing tasks requires the Data Frame map units to have been set.  The default units are "Unknown".  You need set the units by right clicking on the data frame > select properties > select general tab and then choose the correct map units.  You can also set the map units by importing a dataset which has a projection (typically the prj file associated with a Shapefile).  If you are using the American NHD dataset you can import the coordinate system from a Feature dataset in your Geodatabase under the coordinate system tab.

Error Number: eRvX0310

Why the error occurred & solution:

For this tool to function correctly you must provide a point layer which represents the network mouths. These points must be snapped to the end vertex of the polyline. If your point layer was created manually without snapping the points then these would almost certainly not intersect.

You need to provide these points as they define the starting point at which an upstream search can progress from.

You can ensure correct snapping has occurred by setting the snapping environment in the editor options dialog. Alternatively you can generate such points by extracting the nodes (which will guarantee that they intersect the end vertex of a polyline) and then delete all unwanted non-mouth nodes.

Error Number: eRvX0312

Why the error occurred & solution:

This error message is occurring as some of your mouth points are intersecting polylines but not at the end vertex. If your points are definitely snapped to what appears to be the end vertex of a polyline then you are probably looking at a multi-part polyline. In this case you'll need to explode your multi-part polylines into single parts before you can use this tool.

If you had set the snapping environment to snap to edge, then when you created your mouth points this means you could have snapped any location along a polyline. You should have used snap to end to ensure your mouth points intersect the end vertex of the polyline.

You need to move your points so they are snapped to the end vertex of a polyline.

If you do not understand what a vertex is then please refer to the online Glossary

Error Number: eRvX0314

Why the error occurred & solution:

This warning message is simply to remind you of the limitations of this tool. The algorithm is not robust enough to deal with multi-threading channels and will fail to process them correctly. This is because the tool uses the topology (connectivity) of the network and a known starting point (the snapped mouth points) to traverse the network.  There are scenarios such a drain linking across sub-catchments which mean that direction cannot be logically determined. Currently the algorithm is unable to flag which polylines are indeterminate.