re: "audit for reproducible results" Brand, When you get a chance, I'd like to hear about the UCGIS Symposium ... The Census Study of Commuting used "Network Effects" (value=1.25) to measure Commutes to and from work. Fine, as far as it goes ... although there is another triangulation solution at (1+(2/3)). This permits flattening of Continental Drift, Glaciers and Orbit wobbles of all sorts over wide ranges of time. NOAA uses elliptical flattening to arrive at a 365.242196 day year (good for the next 3800 years, I think). Map Makers are comfy with spherical projections and their reflexive habits. The element which bothers me about the Census Study is that their flattening assumes an employer will tolerate a constant 1/2 hour and a fraction of paid clock watching per week. (For Map Makers, the meridional radius of curvature is 3949.99 for 100 weeks - i.e. 39.4999 hours a week) Not sure where these generous, understanding employers are. Not surprised the Commerce Department says they are out there. NASA and NOAA don't do data like this. To squeeze the last little ounce of PR value out of physical data would make them look clueless in short order. But this also presents a problem for governments below the Federal Level because it makes distance, even conceptual distance on a map projection, non-reproducible. Integrations are done with very limited precision (translation:Bits of value must be made to vanish; loose change is left over). If you told Texans that this made fair High School Football schedules impossible, the world would officially end. With a little honest discussion of goals and intents the math methods can be sorted out and should be so that Linked Data loose ends are not perceived as errors, but rather reproducible results. --Gannon On 23 May 2013 14:30, Brand Niemann <bniemann@cox.net> wrote: Irina, Thank you. I heard Doug Nebert announce this yesterday at the UCGIS 2013 Symposium: http://ucgis2.org/event-item/preliminary-program My audit for reproducible results is at: http://semanticommunity.info/An_Open_Data_Policy
Received on Thursday, 23 May 2013 21:06:36 UTC