Thanks for the thoughts and feelings, Rich theoretically, I guess the location of a sensor can be considered a dimensionless point but that has no practical use for me - especially given the need to record attributes of an area with very real dimensions.
I'm glad you mentioned precision. I'm only as precise as the instrument performing the measurement. with my cheap GPS handheld, I suspect I'm getting 5-10 m diameter resolution. I could use a discretely designated area defined in a system that allows me to add a few digits to increase the resolution by a factor of 16, 64 or 400. I can get down to that 5m area in 11 digits with a base-20 triangular mesh. so I'm not really throwing away precision. I'm dealing with it in a practical way. I know what I'm measuring. as far as other polygons go, surface area defined by three boundaries is the most practical. (is that why they call it trigonometry?) that's where the regular triangular polyhedra: tetrahedron, octahedron and icosahedron are represented above as capable of resolution factors of 16, 64 and 400 respectively at every iteration of the recursive method. do you have some other polygons in mind? as far as those who attempt to profit from a developing a standard? good luck. take solace in that they'll soon be gone, Rich. - brian > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Rich Gibson > Sent: Thursday, June 14, 2007 2:58 PM > To: [email protected] > Subject: Re: [Geowanking] Open Street View > > > Hi Brian, > > I have a couple of thoughts on what you are asking for. The first is > that it seems that the sensor location is a point, not an area. Why > do you want to throw away precision? > > I do understand converting that point data to an area for > presentation, but even there I wonder what is wrong with defining your > areas as polygons? > > > http://www.nacgeo.com/nacsite/documents/nac.asp > > I read your 'open to anyone for free' line, but after checking out > their site I need to say that the so-called 'natural' area coding > system is an actively evil enterprise, and all of the people behind it > are scum. > > It is deeply wrong to claim ownership over basically the idea of > transforming the numbers 0-9 into base 30... > > Here is their 'secret sauce' subject to "The algorithm, the character > set and the concept of the Natural Area Coding System are copyrighted > content of NAC Geographic Products Inc. and protected by the > International Copyright Law. " > > So just to be clear: They are assholes who should fuck off and die. > > > > LONG = (Longitude + 180)/360 > x1 = Integer part of( LONG*30) > x2 = Integer part of(( LONG*30-x1)*30) > x3 = Integer part of((( LONG*30-x1)*30-x2)*30) > x4 = Integer part of((((LONG*30-x1)*30-x2)*30-x3)*30) > ... > > LAT = (Latitude + 90)/180 > y1 = Integer part of( LAT*30 ) > y2 = Integer part of(( LAT*30-y1)*30) > y3 = Integer part of((( LAT*30-y1)*30-y2)*30) > y4 = Integer part of((((LAT*30-y1)*30-y2)*30-y3)*30) > ... > > ALT = Arctan(Altitude/R)/90 > z1 = Integer part of( ALT*30) > z2 = Integer part of(( ALT*30-z1)*30) > z3 = Integer part of((( ALT*30-z1)*30-z2)*30) > z4 = Integer part of((((ALT*30-z1)*30-z2)*30-z3)*30) > > > On 6/14/07, brian grant <[EMAIL PROTECTED]> wrote: > > I want to capture everything as well but store data such that sensor > > location is defined by its area not an orthogonal point on a sphere - > > and that is the problem looking for a solution - for sensors, photos and > > lots of other attributes. > > > > I'm happy to start with a lat/lon reading but I want to place it in a > > globally defined area - a universal zip code not unlike the > attempt here: > > > > http://www.nacgeo.com/nacsite/documents/nac.asp > > > > but open to anyone for free, of course. > > > > what a Recursive Triangular Mesh (as opposed to the > Hierarchical variety) > > offers is a method of defining a spherical area from any point > of origin - > > this discussion has obviously focussed on geospatial but RTM > can be applied > > to any celestial or terrestrial object. > > > > > > - brian > > > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] Behalf Of stephen white > > > Sent: Thursday, June 14, 2007 2:16 AM > > > To: [email protected] > > > Subject: Re: [Geowanking] Open Street View > > > > > > > > > On 13/06/2007, at 10:54 PM, brian grant wrote: > > > > the street view focus on the visual seems to be an effort to > > > > capture the > > > > transient but my needs are to capture repeatedly over time and not > > > > just the > > > > visual - I need temperature, humidity, particulate and other > > > > atmospheric > > > > > > When you have your measurements, where do you put them? Both groups > > > of data are transient, and you may as well put your temperature and > > > humidity and particulate data in the same place as something that > > > lets you look around to see what's there. > > > > > > If you have a high particulate reading, wouldn't it be useful to pop > > > into that point and look to see that there's a factory just up the > > > road that is impacting on the sensor? If something's more humid than > > > it should be, you can see there's a fire hydrant spraying water on > > > your node! > > > > > > Why separate the two? Photos are sensor captures of light, right > > > alongside sensor captures of any other type. Throw in radiation, > > > throw in cosmic rays, throw in anything you like, and all of that > > > information is forever changing and transient in nature. > > > > > > I want to capture EVERYTHING, and make it just as accessible as being > > > there. If there was a tricorder that captured all the other data that > > > you want, then all that data could be represented in Open Street > > > View's databases, with an overlay saying "34 degrees" while you view! > > > > > > There is no conflict. It is the same problem. > > > > > > -- > > > [EMAIL PROTECTED] > > > > > > > > > _______________________________________________ > > > Geowanking mailing list > > > [email protected] > > > http://lists.burri.to/mailman/listinfo/geowanking > > > > > > > _______________________________________________ > > Geowanking mailing list > > [email protected] > > http://lists.burri.to/mailman/listinfo/geowanking > > > > > -- > Now offering training and consulting in maximizing corporate > efficiency using Web 2.0 tools and techniques. > > Rich Gibson > Chief Scientist (and bottle washer), Locative Technologies > http://mappinghacks.com > http://geocoder.us > http://testingrange.com > AIM period3equals > _______________________________________________ > Geowanking mailing list > [email protected] > http://lists.burri.to/mailman/listinfo/geowanking > _______________________________________________ Geowanking mailing list [email protected] http://lists.burri.to/mailman/listinfo/geowanking
