Skip to content
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.

Sign up for GitHub

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

Jump to bottom

TG2-VALIDATION_DECIMALLATITUDE_INRANGE #79

Open
iDigBioBot opened this issue Jan 5, 2018 · 5 comments
Open

TG2-VALIDATION_DECIMALLATITUDE_INRANGE #79

iDigBioBot opened this issue Jan 5, 2018 · 5 comments
Labels
Conformance CORE TG2 CORE tests SPACE Test Tests created by TG2, either CORE, Supplementary or DO NOT IMPLEMENT TG2 Validation
Projects
Core Tests and Assertions (TG2)

Comments

@iDigBioBot
Copy link
Collaborator

iDigBioBot commented Jan 5, 2018 •
edited by ArthurChapman

TestField Value
GUID b6ecda2a-ce36-437a-b515-3ae94948fe83
Label VALIDATION_DECIMALLATITUDE_INRANGE
Description Is the value of dwc:decimalLatitude a number between -90 and 90 inclusive?
TestType Validation
Darwin Core Class dcterms:Location
Information Elements ActedUpon dwc:decimalLatitude
Information Elements Consulted
Expected Response INTERNAL_PREREQUISITES_NOT_MET if dwc:decimalLatitude is EMPTY or the value is not interpretable as a number; COMPLIANT if the value of dwc:decimalLatitude is between -90 and 90, inclusive; otherwise NOT_COMPLIANT
Data Quality Dimension Conformance
Term-Actions DECIMALLATITUDE_INRANGE
Parameter(s)
Source Authority
Specification Last Updated 2023-09-18
Examples [dwc:decimalLatitude="0.0": Response.status=RUN_HAS_RESULT, Response.result=COMPLIANT, Response.comment="dwc:decimalLatitude is in RANGE"]
[dwc:decimalLatitude="121.0534": Response.status=RUN_HAS_RESULT, Response.result=NOT_COMPLIANT, Response.comment="dwc:decimalLatitude is in not in RANGE"]
Source ALA, GBIF, OBIS
References
Example Implementations (Mechanisms)
Link to Specification Source Code
Notes
@iDigBioBot
Copy link
Collaborator Author

Comment by Paula Zermoglio (@pzermoglio) migrated from spreadsheet:
Idem, order matters, useful AFTER interpretation of verbatim if no decimalLat and decimaLong were provided.

@ArthurChapman ArthurChapman added the Test Tests created by TG2, either CORE, Supplementary or DO NOT IMPLEMENT label Jan 16, 2018
@ArthurChapman ArthurChapman mentioned this issue Aug 28, 2019
Closed
@Tasilee Tasilee mentioned this issue Oct 4, 2020
Open
@Tasilee
Copy link
Collaborator

Tasilee commented Mar 3, 2022

In the light of recent comments, changed the Expected Response to

INTERNAL_PREREQUISITES_NOT_MET if dwc:decimalLatitude is EMPTY or the value is not interpretable as a number; COMPLIANT if the value of dwc:decimalLatitude is between -90 and 90 degrees, inclusive; otherwise NOT_COMPLIANT

@Tasilee Tasilee changed the title TG2-VALIDATION_DECIMALLATITUDE_OUTOFRANGE TG2-VALIDATION_DECIMALLATITUDE_INRANGE Mar 22, 2022
@ArthurChapman
Copy link
Collaborator

I believe the word "degrees" should be removed from - the value is a number between -90 and 90, not "-90 and 90 degrees"

| Expected Response | INTERNAL_PREREQUISITES_NOT_MET if dwc:decimalLatitude is EMPTY or the value is not interpretable as a number; COMPLIANT if the value of dwc:decimalLatitude is between -90 and 90 degrees, inclusive; otherwise NOT_COMPLIANT |

@ArthurChapman ArthurChapman mentioned this issue Mar 25, 2022
Open
@ArthurChapman
Copy link
Collaborator

Removed the word "degrees" from COMPLIANT

@tucotuco tucotuco mentioned this issue Jan 27, 2023
Open
@ymgan ymgan mentioned this issue Feb 28, 2023
Open
chicoreus added a commit to FilteredPush/geo_ref_qc that referenced this issue Jun 15, 2023
@chicoreus
Work in progress checking implementation of DwCEventDQ methods agains…
e8b7a67 
…t current (2023-06-12) test descriptions. Removing ISSUE_DATAGENERALIZATIONS_NOTEMPTY from geo_ref_qc belongs in rec_occur_qc as test relevant to multiple areas. Adding code to support AMENDMENT_COORDINATES_CONVERTED, appears to work, but may not be correctly calculating datum transformations, test case not working, need to identify known datum transformation examples and test against those, also not yet supporting precision and uncertainty. Adding or updating implementations for tdwg/bdq#79 VALIDATION_DECIMALLATITUDE_INRANGE, tdwg/bdq#30 VALIDATION_DECIMALLONGITUDE_INRANGE, tdwg/bdq#78 VALIDATION_GEODETICDATUM_NOTEMPTY. and tdwg/bdq#59 VALIDATION_GEODETICDATUM_STANDARD.  Adding class AssumeCRS to transform a few typical datum strings (e.g. WGS84) into EPSG codes assuming geographic coordinate system CRS.   Adding ProvidesVersion annotations.   Removing now empty file stubs for checked methods.  Adding some unit tests.
@Tasilee
Copy link
Collaborator

Tasilee commented Sep 18, 2023

Splitting bdqffdq:Information Elements into "Information Elements ActedUpon" and "Information Elements Consulted".

Also changed "Field" to "TestField", "Output Type" to "TestType" and updated "Specification Last Updated"

@chicoreus chicoreus added the CORE TG2 CORE tests label Sep 18, 2023
@debpaul debpaul mentioned this issue Mar 13, 2024
Open
chicoreus added a commit to FilteredPush/geo_ref_qc that referenced this issue Aug 19, 2024
@chicoreus
Updating metadata for tdwg/bdq#79 to current version, no changes need…
242cedb 
…ed to implementation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Conformance CORE TG2 CORE tests SPACE Test Tests created by TG2, either CORE, Supplementary or DO NOT IMPLEMENT TG2 Validation
Projects
Core Tests and Assertions (TG2)
SPACE TESTS
Milestone
No milestone
Development

No branches or pull requests
4 participants
@chicoreus @Tasilee @iDigBioBot @ArthurChapman