Good Standard for Base1 Analysis?
Anyway, if anyone wants to get into development for Base1 Analysis, the idea is to use iOS interfaces to take measurements on site with time stamps and geo-location stamps.
The analysis applications take the data and plot graphs on a common scale or else map the data using GoogleMaps or AppleMaps. Available data-list libraries must eventually include common data, like moon cycles, tides, temperatures, even government data like crimes, forestry measurements and construction.
The best maps should have animated overlays with various time-frame adjustments to help look for patterns in relations of changes.
The graphing applications can have division between two data sets (ratios), addition and subtraction (re-plotting the combined graphs onto the common scale) and even multiplication. A persistent store can manage the investigation as the operations are applied to selected graphs, thereby keeping the data necessary to re-generate an equation for any apparent data-matches that are discovered.
To allow all of these possibilities to be integrated for all professions that involve measurement, and for any application that applies such a comparative analysis to the data sets, it is only necessary to follow a simple standard.
The standard I will be using is a label for each set of data-point objects, including at least something about what is measured and contact information for the person responsible for the quality of the measurements. Each data-point object consists of:
{LatitudeCenterPoint, LatitudeAccuracyRadius: LongitudeCenterPoint, LongitudeAccuracyRadius: AltitudeCenterPoint, AltitudeAccuracyRadius: TimeCenterPoint, TimeAccuracyRadius: MeasurementCenterPoint, MeasurementAccuracyRadius}
Please let me know if anyone has any constructive views on this.
I will be using floats for all values, time in seconds from 1970GMT (with negative values prior to 1970), and spatial radius in feet.
iMac