Access API Documentation | Access Technical Support Portal | Email: support@validic.com
Validic Support Center
Click Here for Latest System Status

Data Standardization and Normalization

Last Updated: Aug 28, 2017 01:50PM EDT
Q: Is the data retrieved from the Validic API standardized and/or normalized?

Yes, a major part of our value is that we give you clean, complete, actionable data. This means that data has been standardized and normalized where possible. Since various device/app vendors use different terminology for certain data, we standardize all nomenclature. Examples of this are "steps" not "steps taken", "distance" not "distance_covered", "floors" not "elevated_steps_distance", etc.

Aside from providing standardized data, we also normalize data units since data coming from various device/app vendors use different units of measure for their data. An example of this is distance metrics. You can always expect to receive values in in "meters" not in "Kilometers" and not in "miles", for duration, it is always in "seconds" not in "hours" and not in "minutes".

For added guidance on what the standardized data field attributes and normalized data units per Validic API endpoint or data types, please see our API Documentation.
 
vlogo
bc869bd0260c3360eac041337ba489f0@validic.desk-mail.com
https://cdn.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete