bdq
bdq copied to clipboard
TG2-VALIDATION_LOCATION_NOTEMPTY
TestField | Value |
---|---|
GUID | 58486cb6-1114-4a8a-ba1e-bd89cfe887e9 |
Label | VALIDATION_LOCATION_NOTEMPTY |
Description | Is there a value in any of the Darwin Core spatial terms that could specify a location? |
TestType | Validation |
Darwin Core Class | dcterms:Location |
Information Elements ActedUpon | dwc:higherGeographyID |
dwc:higherGeography | |
dwc:continent | |
dwc:country | |
dwc:countryCode | |
dwc:stateProvince | |
dwc:county | |
dwc:municipality | |
dwc:waterBody | |
dwc:island | |
dwc:islandGroup | |
dwc:locality | |
dwc:locationID | |
dwc:verbatimLocality | |
dwc:decimalLatitude | |
dwc:decimalLongitude | |
dwc:verbatimCoordinates | |
dwc:verbatimLatitude | |
dwc:verbatimLongitude | |
dwc:footprintWKT | |
Information Elements Consulted | |
Expected Response | COMPLIANT if at least one term needed to determine the location of the entity exists and is bdq:NotEmpty; otherwise NOT_COMPLIANT |
Data Quality Dimension | Completeness |
Term-Actions | LOCATION_NOTEMPTY |
Parameter(s) | |
Source Authority | |
Specification Last Updated | 2023-09-18 |
Examples | [dwc:locationID="https://opencontext.org/subjects/e54377f7-4452-4315-b676-40679b10c4d9", dwc:higherGeographyID="", dwc:higherGeography="", dwc:continent="", dwc:waterBody="", dwc:islandGroup="", dwc:island="", dwc:country="", dwc:countryCode="", dwc:stateProvince="", dwc:county="", dwc:municipality="", dwc:locality="", dwc:verbatimLocality="", dwc:decimalLatitude="", dwc:decimalLongitude="", dwc:coordinateUncertaintyInMeters="", dwc:geodeticDatum="", dwc:verbatimCoordinates="", dwc:verbatimLatitude="", dwc:verbatimLongitude="", dwc:footprintWKT="": Response.status=RUN_HAS_RESULT, Response.result=COMPLIANT, Response.comment="dwc:LocationID is bdq:NotEmpty"] |
[dwc:locationID="", dwc:higherGeographyID="", dwc:higherGeography="", dwc:continent="", dwc:waterBody="", dwc:islandGroup="", dwc:island="", dwc:country="", dwc:countryCode="", dwc:stateProvince="", dwc:county="", dwc:municipality="", dwc:locality="", dwc:verbatimLocality="", dwc:decimalLatitude="", dwc:decimalLongitude="", dwc:coordinateUncertaintyInMeters="", dwc:geodeticDatum="", dwc:verbatimCoordinates="", dwc:verbatimLatitude="", dwc:verbatimLongitude="", dwc:footprintWKT="": Response.status=RUN_HAS_RESULT, Response.result=NOT_COMPLIANT, Response.comment="All location fields are bdq:Empty"] | |
Source | Lee Belbin |
References |
|
Example Implementations (Mechanisms) | |
Link to Specification Source Code | |
Notes | Only fails if all of the relevant fields of the Darwin Core Location class are EMPTY or do not exist. Relevant Darwin Core fields include dwc:locationID, dwc:higherGeographyID, dwc:higherGeography, dwc:continent, dwc:waterBody, dwc:islandGroup, dwc:island, dwc:country, dwc:countryCode, dwc:stateProvince, dwc:county, dwc:municipality, dwc:locality, dwc:verbatimLocality, dwc:decimalLatitude, dwc:decimalLongitude, dwc:verbatimCoordinates, dwc:verbatimLatitude, dwc:verbatimLongitude, dwc:footprintWKT. Elevation and/or depth alone are deemed insufficient to meaningfully locate a position on the earth. |
Comment by Paula Zermoglio (@pzermoglio) migrated from spreadsheet: I believe DwC terms should include some more, e.g., island, islandGroup, waterbody, county, municipality, continent, countryCode.
This is a complicated test - needs more work to document. Not georeferenced or not georeferenceable.. Need to add many dwc:terms. If all relevant spatial terms are blank or uninterpretable.
Extensive discussion in the meeting - has georeference or is georeferencable is one possible interpretation, but a very complex one to implement, and supported by other more granular tests. We decided to constrain this test to a simple test of minimal presence of some sort of spatial data.
Going through the test data, I'm wondering if
dwc:minimumElevationInMeters dwc:maximumElevationInMeters dwc:minimumDepthInMeters dwc:maximumDepthInMeters
should be included in Information Elements? @tucotuco did include the terms in the test data and some were NOT_EMPTY
I don't think I'd include them - except for a few minor exceptions, you can't tell a location on those alone.
I agree from the perspective of a test for usable location information based on the Expected Response, "at least one term needed to determine the location of the entity."
OK. I've removed references to the depth and elevation terms from the test data.
I suggest the Description:
'Is there a value in any of the Darwin Core spatial terms that could specify a location?'
in place of:
'Is there a value in any of the Darwin Core spatial terms that could identify a location?'
Changed note to add the "dwc:" namespace to all the Darwin Core terms cited.
Splitting bdqffdq:Information Elements into "Information Elements ActedUpon" and "Information Elements Consulted"
Also changed "Fields" to TestFields" and "Output Type" to "TestType", and will go back and add these to prior changes and then work forward
Changed all Information Elements to "ActedUpon" as per Paul's Java Code