-
Notifications
You must be signed in to change notification settings - Fork 5
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
Multiplicity of Relationships (Lights and Transponder Beacons) in FC 1.2.0 #114
Comments
RadarTransponderBeacon has the same affliction - mandatory relationships which aren't in the DCEG. |
These are all Composition/StructureEquipment and role SupportedBy so they shouldn't be different groups, they should all be a single F->F relationship with the features in a single list. Not sure why they've been split into subgroups. It's not a validation problem but it's inconsistent and it makes automated validation and editing a problem as they have to be joined together first. |
CautionArea. FC 1.2.0 says every CautionArea must have at least one association to an ASL or TSS. |
TrafficSeparationScheme. Seems to have mandatory relationships in 4 associations. |
Fairway. |
FogSignal (I think) |
signalStationWarning and signalStastionTraffic. All seem to be composition relationships set to 1 |
RangeSystem |
I automated the search, eventually. Below is a list of all duplicate relationships (i.e. the same role/association/roletype) and also any mandatory relationships (some I think are ok, e.g. TextPlacement and IslandAggregation). These should all be fixed in the FC prior to 2.0.0 (and, really, in the 1.2.X timeframe as they affect validation of any test data). Quite a few of the mandatories are fixed in the 1.2.X that is in the PC repo. I may fix the grouping issues too, time permitting. If I can find someone I will get the other issues fixed too. F UpdateInformation: WARNING: Mandatory relationship ASSOCIATION:UpdatedInformation:identifies [178 features ] |
KHOA is now preparing an updated FC which will address these changes, Issue to be closed once this version is available. |
Received new version of feature catalogue. There are still some mandatory relationships which aren't in the DCEG and should be removed. These are listed below. Additionally, the FairwaySystem and TwoWayRoute mandatory associations in the feature catalogue I believe should also be of type "AGGREGATION" and are in the FC as "ASSOCIATION" type which is a mismatch. These are listed below (don't delete these :) :
these are still present and, I believe, incorrect with respect of the DCEG.
|
I think this Issue has been overtaken by events (including the creation of the new Issue #140). Close issue, pending further requirements. |
There seems to be three mandatory relationships required for LightAllAround according to the latest FC 1.2.0
Mandatory Feature Bindings from the 1.2.0 FC for LightAllAround. this would require one from each group to be associated. They also all have the same asssociation and role, so could all be combined. DCEG doesn't mandate any relationships at all.
Seems to also affect Fog, Sectored and Air Obstruction Lights too.
The text was updated successfully, but these errors were encountered: