search

DATEX-II-EU / DatexII

Main repository for issues and bugs for the DATEXII standard
0 stars 0 forks source link

Multiple specifications for "no precipitation" (Bugzilla Bug 487) #487

Open datexii opened 5 months ago

datexii commented 5 months ago

This issue was created automatically with bugzilla2github.py

Bugzilla Bug 487

Date: 2024-06-03T11:36:08+02:00 From: @JoergFst To: @JoergFst

Last updated: 2024-06-03T11:36:08+02:00

datexii commented 5 months ago

Comment 1967

Date: 2024-06-03 11:36:08 +0200 From: @JoergFst

Original comment from GB:

The noPrecipitation attribute of PrecipitationInformation is technically redundant because the same effect can be achieved by an associated PrecipitationDetail object containing only a preciptationType of “noPrecipitation”. This may be an intentional denormalization for optimisation, but GB prefers to omit the attribute – perhaps because it is usually raining here. Removing the attribute would remove the possibility of duplication and inconsistency, at the cost of 1 more data element only in the case that no further information about the precipitation is known.

Remove the attribute because it is redundant.

Furhter comment from unknown publisher, potentially France:

Strictly speaking it is a bit strange to find among the values of the "PrecipitationTypeEnum" enumeration the "noPrecipitation" value (which is the absolute negation of a precipitation type). As well, the "PrecipitationDetail" also contains an attribute: "PrecipitationIntensityGrade" which contains the literal "noPhenomenon". That means there are three possibilities to mean "noPrecipitation". The most natural way is to use the Boolean "noPrecipitation" rather than using one of the aforementioned enumeration literals.

Note that also Part 5 is effected!