You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to report River Distance in miles rather than feet, however 3 decimal places are needed for river mile in order to differentiate cross sections. When creating a new database, I made sure that river distance precision was set to 3. However when plotting the XS, they are shown to contain only 2 decimal places.
Reproduction steps
I determined the River Miles and needed three decimal places to properly differentiate cross sections.
I created a new database for XS viewer and selected river distance precision as "3" instead of "2."
I imported the cross sections and then went to "Plot Cross Sections."
Under "Cross Section Selections" only 2 decimal places are displayed making it confusing as to what cross section is what as some have the same names/numbers as others.
To work around this I converted data to feet (example river distances values include 21593 & 21627 - which are in the units of feet.) However, I'd like to keep as miles for future to reduce length and following typical USACE formatting.
Anything else?
Use the attached csv and divide the RiverDistance column by 5280 ft to get cross sections from feet to miles and then import into XS Viewer to recreate problem. McconnellCedar2023XSViewer.csv
The text was updated successfully, but these errors were encountered:
The Problem
I would like to report River Distance in miles rather than feet, however 3 decimal places are needed for river mile in order to differentiate cross sections. When creating a new database, I made sure that river distance precision was set to 3. However when plotting the XS, they are shown to contain only 2 decimal places.
Reproduction steps
Anything else?
Use the attached csv and divide the RiverDistance column by 5280 ft to get cross sections from feet to miles and then import into XS Viewer to recreate problem.
McconnellCedar2023XSViewer.csv
The text was updated successfully, but these errors were encountered: