Bugs
Search the entire project
This project's trackers
This project's releases
This project's news
Projects
People
Documents
Advanced search
Log In
New Account
Home
My Page
Projects
GREAT-ER
Summary
Activity
Tracker
Lists
News
SCM
Files
[#2558] Name mismatch with analysis tool gegerated tables
View Trackers
Bugs
Export CSV
Date:
2011-07-11 13:03
Priority:
3
State:
Open
Submitted by:
Bjoern Ricks (
bricks
)
Assigned to:
Nobody (None)
Version:
none
Operating System:
none
Component:
none
Severity:
none
Resolution:
none
URL:
http://intevation.de/rt/webrt?serial_num=2888&display=History
Summary:
Name mismatch with analysis tool gegerated tables
Detailed description
Request by frank Subject: Name mismatch with analysis tool gegerated tables The naming of result tables and further tables generated by the analysis tools is quite intransparent and confusing: Initially a table named Join of Join of RIVERNET and Stretch Attributes and Stretch Results is available. This seems to be analog to the Result Layer Attribute Table Apply e.g. the Analysis Tool "Calculate CSim X" results in a second table named Join of Join of RIVERNET and Stretch Attributes and Stretch Results which has one more column and seems to be analog to the CSim X Layer Attribute table. Applying e.g. "Combine CSIM/Flow" results in a third table with the same name. Is this intended? Shouldn't the Tables be named after their contents? Our should they be completely removed from the sessions Table list since they are accessible as layer attribute table?
Request by frank
Subject: Name mismatch with analysis tool gegerated tables
The naming of result tables and further tables generated by the analysis tools
is quite intransparent and confusing:
Initially a table named
Join of Join of RIVERNET and Stretch Attributes and Stretch Results
is available. This seems to be analog to the Result Layer Attribute Table
Apply e.g. the Analysis Tool "Calculate CSim X"
results in a second table named
Join of Join of RIVERNET and Stretch Attributes and Stretch Results
which has one more column and seems to be analog to the CSim X Layer Attribute
table.
Applying e.g. "Combine CSIM/Flow" results in a third table with the same name.
Is this intended? Shouldn't the Tables be named after their contents? Our
should they be completely removed from the sessions Table list since they are
accessible as layer attribute table?
Comments
Attachments
Changes
No comments have been posted
No attached documents
No changes have been made to this item
This site is hosted by
(
Datenschutzerklärung und Impressum
|
Privacy Policy and Imprint
)