I've been doing some work with geographic coordinates, and been giving it a lot of thought to how it might work in context of Haystack. For all the same reasons that we package a floating point number and unit together as a single scalar value, I'm thinking coordinates should also be a single scalar value. That allows us to treat it uniformly just like other sensor data which is an scalar analog, digital, or enum value.
So here is my proposal:
Create a new first class tag kind "Coor"
Encoding of Coor is in decimal degrees as "C(<lat>, <lon>)", such as "C(37.5,-77.45)"
On fixed assets like a site, we use single geoCoor tag instead of geoLat and geoLon
GPS sensors on a mobile piece of equipment are modeled as point with current and/or historized trend. The point kind is "Coor" and the point uses the geoCoor marker tag
Sound good?
Kevin KelleyFri 19 Oct 2012
"Coor" struck me as odd, so I googled it; Wikipedia seems to have superseded coor with coord, and I like that better too.
Brian FrankFri 19 Oct 2012
I like that, great idea. So lets say Kind is "Coord" and tag is "geoCoord"
Brian Frank Fri 19 Oct 2012
I've been doing some work with geographic coordinates, and been giving it a lot of thought to how it might work in context of Haystack. For all the same reasons that we package a floating point number and unit together as a single scalar value, I'm thinking coordinates should also be a single scalar value. That allows us to treat it uniformly just like other sensor data which is an scalar analog, digital, or enum value.
So here is my proposal:
geoCoortag instead ofgeoLatandgeoLongeoCoormarker tagSound good?
Kevin Kelley Fri 19 Oct 2012
"Coor" struck me as odd, so I googled it; Wikipedia seems to have superseded coor with coord, and I like that better too.
Brian Frank Fri 19 Oct 2012
I like that, great idea. So lets say Kind is "Coord" and tag is "geoCoord"
Jason Briggs Fri 19 Oct 2012
I like the idea too