Lee Belbin

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"

Checking the test data on this, I came to the same conclusion as @timrobertson100. If multiple satellite systems were used (with a good PDOP), are we moving toward sub-meter uncertainty?...

The alternative is for very small organisms (bacteria, viruses) in soil or rock that could be highly localised. I figure my discomfort is that we allow for a value of...

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"

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...

OK. I've removed references to the depth and elevation terms from the test data.

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...

Changed all Information Elements to "ActedUpon" as per Paul's Java Code

Going through the test data, I am assuming that the input data can only contain values among the Information Elements and that the Expected Response should include explicitly (or implicitly?)...

I would also suggest modifying INTERNAL_PREREQUISITES_NOT_MET if dwc:decimalLatitude and dwc:decimalLongitude were EMPTY or the value of dwc:geodeticDatum was not interpretable; AMENDED if the values of dwc:decimalLatitude, dwc:decimalLongitude, and dwc:geodeticDatum were...