You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rather than only return the bels_match_string for matching records with coordinates, the BELS web API could also return the hash/bels_match_string for unmatched records. This would provide a way for users to discover all the identical localities in their dataset thereby making it easier to prioritize georeferencing of the most prevalent localities.
The web UI currently returns all hashes/match strings (as bels_matchwithcoords, bels_matchverbatimcoords, bels_matchsanscoords) even when none match records with coordinates.
The text was updated successfully, but these errors were encountered:
Now that I understand match strings vs hashes, I've removed the request for returning hashes.
jbest
changed the title
Include location hash/bels_match_string for all records submitted to BELS web service API
Include location bels_match_string for all records submitted to BELS web service API
Jun 29, 2022
Rather than only return the bels_match_string for matching records with coordinates, the BELS web API could also return the
hash/bels_match_string for unmatched records. This would provide a way for users to discover all the identical localities in their dataset thereby making it easier to prioritize georeferencing of the most prevalent localities.The web UI currently returns all
hashes/match strings (as bels_matchwithcoords, bels_matchverbatimcoords, bels_matchsanscoords) even when none match records with coordinates.The text was updated successfully, but these errors were encountered: