Hi,
I've been asked to investigate using select link functionality in Cube 6.4.5 to extract subsets of public transport demand which use a certain part of a station. Each station is represented by a single node but we want to distinguish between services using different parts of the station. This cannot always be expressed in a combination of link and operator conditions, and listing all the individual line names would result in an impractically long select link expression.
Since mode and operator can be used as select link conditions, I wondered if other LINE attributes could be used - e.g. user-defined attributes such as USERA3, but this yields an error "unrecognised key USERA3" when I try it in a select link expression.
Are there any LINE attributes other than name, mode and operator that can be used in public transport select link expressions?
Thanks,
Jack
Hi Jack.
It is not possible to use other attributes than line name, node, link, mode, operator, or combination of those. Nevertheless, I think that it might be possible to obtain something like what you are describing in two possible ways:
1. By defining the line names with a criteria that satisfies what you are trying to obtain, e.g., starting with a certain code. This allows you to use conditions with masks such as below:
2. Using "not" condition in case you just need to exclude few lines instead
Hi Filippo,
Thanks for your reply - that matches the best solution I could come up in testing with last week which was to add a code to the beginning of the line names and use masks. We'll stick with this for now.
I think it would be useful to consider including user-defined attributes in select link criteria in a future version, which would enable more flexibility in building criteria without changing existing attributes and so minimise interactions with other processes.
Thank you Jack for your suggestion, I added this topic for future investigation.