6 Replies Latest reply: Nov 5, 2012 7:21 PM by mark133
mark133 Level 1 (65 points)

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.

  • K T Level 7 (23,705 points)

    It's a consumer-leverl device. Accuracy is measured in +/- meters. I'm not sure all of your examples would approve that level of trust, etc.

  • mark133 Level 1 (65 points)

    Thank you very much for your expert views.


    I was thinking OSX is better for that actual analysis (or OSX servers) and the iOS devices are better for entering data in the field.


    Most of the resistance to sharing data can be overcome if the data sets are transformed to the common scale for sharing (in cases where there is resistance to sharing data or else good reason for concealing actual measures).

  • mark133 Level 1 (65 points)

    For a good common scale, simply set max,min and mean to a base of one (or -1,0,1).

  • mark133 Level 1 (65 points)

    It should be easy for 'consumers' to enter and share data sets. You never know how a data set collected from the internet for all base1 data on any particular place, time, or topic might relate to any other data set or data sets. And millions of 'consumers' might have more time to play around with the data sets, looking for the appearance of relationships in changes.

  • mark133 Level 1 (65 points)

    Here are these standards on accuracy. All references are to feet and inches in the United States.




  • mark133 Level 1 (65 points)

    But it shouldn't matter if decimal divided feet are used (as is common for all American manufacturing and industrial standards) or decimal divided meters. The measures are somewhat similar, and if the difference is critical, I expect the label will have more information about the measure that can be filtered in a search and transformed if necessary.