Closed Tasilee closed 7 months ago
TestField | Value |
---|---|
GUID | c9fc7ef1-7714-4dfa-8dea-589d5b43f432 |
Label | ISSUE_VERBATIMELEVATION_NOTEMPTY |
Description | Is there a value in dwc:verbatimElevation? |
TestType | Validation |
Darwin Core Class | Location |
Information Elements ActedUpon | dwc:verbatimElevation |
Information Elements Consulted | |
Expected Response | POTENTIAL_ISSUE if dwc:verbatimElevation is bdq:NotEmpty; otherwise NOT_ISSUE |
Data Quality Dimension | Completeness |
Term-Actions | VERBATIMELEVATION_NOTEMPTY |
Parameter(s) | |
Source Authority | |
Specification Last Updated | 2024-04-02 |
Examples | [dwc:verbatimElevation="31ft 5in": Response.status=RUN_HAS_RESULT, Response.result=POTENTIAL_ISSUE, Response.comment="dwc:verbatimElevation is bdq:NotEmpty"] |
[dwc:verbatimElevation="": Response.status=RUN_HAS_RESULT, Response.result=NOT_ISSUE, Response.comment="dwc:verbatimElevation is bdq:Empty"] | |
Source | TG2 |
References | |
Example Implementations (Mechanisms) | |
Link to Specification Source Code | |
Notes | This bdq:Supplementary test is not regarded as CORE (cf. bdq:CORE) because of one or more of the reasons: not being widely applicable; not informative; likely to return a high percentage of either bdq:COMPLIANT or bdq:NOT_COMPLIANT results (cf bdq:Response.result). A Supplementary test may be implemented as CORE when a suitable use case exists. |
Needs to consider if elevation terms contain a value, if they don't verbatimElevation may correctly not contain a value. Much spatial data correctly does not include an elevation, particularly data that is not terrestrial.
We probably want to collect the verbatim notempty tests into a single UseCase, not simply put them out as supplementary. Substantial more thought is needed on what the data quality needs are that would make us data is unfit for use when verbatim data are not present.
This test is similar to #247, #248, #251, #252 and as I commented on #247, all these should be Supplementary (and Closed) for now as they are "not informative" as they stand, and I would not like us to be further distracted. There could well be use cases, and we have commented adequately to inform future use.