2020-01-26 GLOBE API - Change Announcement - GLOBE Data User Guide
GLOBE Data User Guide
GLOBE Data User Guide
The purpose of the GLOBE Data User Guide is to help scientists and researchers understand, access, and use available GLOBE data. The scope includes data collected by GLOBE-trained teachers, students, and citizen scientists as well as data collected from automated weather stations and data loggers.
Узлы Wiki (GLOBE Data User Guide)
2020-01-26 GLOBE API - Change Announcement
Summary of Changes:
We are modifying the GLOBE API so that variables currently output as strings are output as integers, floats, and booleans. This will provide data type consistency between the source files, ADAT data, and Elasticsearch data stores. We are upgrading the servers associated with the GLOBE API to improve performance and stability.
Primarily - GLOBE API
Secondarily - The GLOBE database will be under greater than usual load which may impact overall system performance.
Secondarily - The GLOBE Advanced Data Access Tool (ADAT) may return incomplete data for a given protocol when that protocol is being processed. Users will be informed which protocol is being processed on the ADAT main page.
All GLOBE protocols
All users who currently consume data from the GLOBE API may be affected. Users of GLOBE's ADAT tool may be intermittently affected.
Data Migration in Production: 1/22/2020 - 1/26/2020
Test and Validation of new server environment: 1/26/2020 - 1/30/2020
New API server "live"in production - 1/30/2020
Send Comments to: firstname.lastname@example.org
The current implementation of Elasticsearch (which drives the GLOBE API) returns data in GeoJSON or JSON formats. Both formats have the capability to allow JSON values to have the simple data types string (with double-quotes), number (integers and floats), boolean (true or false, without double-quotes), and null. However, all JSON values within the GLOBE API "data" subset are being returned as strings (which include numbers and booleans). For example, the userId is currently output as a string when it should be an integer. The planned changes will modify records which are currently incorrectly output as strings to their appropriate numeric or boolean format.
For example, JSON is currently being returned that looks like:
After this change, it will look like:
It is possible if you have written a program to read from the API that this change may impact your program's ability to read the data.