Expanding on Monday’s post today I’m getting into the detail of what “A way to programmatically create the chart” means. The goal is to publicly work out a specification of what this MVP looks like.

Every report, every chart is going to be individualized. For data sets that cover the whole of the USA, it’s a fairly simple task, take the chart type, take the data set, pick out some reasonable defaults, and apply the appropriate parts of the data to the chart depending on the where the chart viewer is.

Chart data has its own GIS polygon of coverage so that local unemployment numbers are only included in the area that is covered by that data, where they have relevance. It’s all point in polygon stuff to match which subset of data gets associated with any particular user’s request for the report. But not all data sets cover 100% of the territory the project covers. When that happens, a second process has to cover the rest of the territory. In the MVP that is going to be simply a grayed out, non-functional report linking to an Indiegogo campaign to get the data.

At first, money will go to a 501(c)3 campaign to promote awareness of the principles of information sharing and 21st century style government oversight using business intelligence data techniques. If the government should not prove receptive, the campaign shifts to a 501(c)4 campaign that is a great deal more pointed.

Other, alternate solutions will be added to the options every time you hit a greyed out, dead end report. The only part of that in the MVP would be a link to a survey asking what should be there.