- From: Gannon Dick <gannon_dick@yahoo.com>
- Date: Wed, 10 Sep 2014 12:07:34 -0700
- To: Andrea Perego <andrea.perego@jrc.ec.europa.eu>, Frans Knibbe | Geodan <frans.knibbe@geodan.nl>
- Cc: Simon Cox <Simon.Cox@csiro.au>, Oscar Corcho <ocorcho@fi.upm.es>, LocAdd W3C CG Public Mailing list <public-locadd@w3.org>
--------------------------------------------
On Wed, 9/10/14, Frans Knibbe | Geodan <frans.knibbe@geodan.nl> wrote:
So now I tend to agree that using a value and a unit to specify the spatial resolution could be the best solution. Perhaps we can make the unit default to meter, if it is not specified?
-----------------------------------------------
Yes, use the metric system (metre). It is now based on (frequency^2) not (velocity^2). Originally it was based on the distance between the Equator and the North Pole (http://en.wikipedia.org/wiki/Metre). The subtle "problem" here is that the range of the Latitude "parameter" (0-90 Degrees, 0-91.3125 Days, 0-100 Centigrade) is is cut in half (again, since the defininition already limited the range to the Northern Hemisphere) while the Longitude range (0-360 Degrees, 0-365.25 Days, or Gradians/Centigrade 0-400) remains full scale. "Temperature" on an absolute scale does not range well. The apparent length of day depends on Latitude alone. I cannot get the graph objects in MS Excel and ODS to play nicely, so unfortunately I can't show you the true-up.
What I can do is demonstrate that the small yearly variation in the 365.25 day long "Year" and the 24 Hour long "Day" average out over a Julian Century. Americans and the British are already using the metric system, they just don't know it.
http://www.rustprivacy.org/2014/balance/wake-sleep.zip
(Please let me know if the graphs are working. The Sleep, Work, Lunch and Commute parameters are input on the "Control" page)
--Gannon
Received on Wednesday, 10 September 2014 19:08:04 UTC