4 ms·
Because the value, as presented, is wrong. "[but it's being used for] non-scientific, non-metrological purposes" which doesn't change that it's the wrong value.
by falcolas 7y ago
Because the value, as presented, is wrong. "[but it's being used for] non-scientific, non-metrological purposes" which doesn't change that it's the wrong value.
Imagine, for a moment, that someone uses these values to put up a fence. Is the fence on their property? Those crap values beyond the actual significant digits of the measurement may tell you that you are, when you're not. That will cost you time and money down the road.
- izacus 7y agoThese values are as right as setting least significant digits to 0 would be. The sensor has limited precision and the other digits might as well be 0 or 584985948 and the value would be no more precise.
- jgtrosh 7y agoI believe you're wrong. https://en.wikipedia.org/wiki/Significant_figures https://en.wikipedia.org/wiki/Significant_figures
- hamandcheese 7y agoI would never assume the displayed digits are significant in any non-scientific context.
- frenchyatwork 7y agoPeople use significant digits colloquially, though with a lot less rigour. For example, If I say I'm 6 feet tall, people will probably guess that I'm between 5 ft 10 in and 6 ft 2 in. If I say I'm 5 ft 11 in, people will probably guess that I'm between 5 ft 10.5 in and 5 ft 11.5 in.
- seandougall 7y agoYeah, but "-37.80467681 144.9659498" has no meaning colloquially to almost anybody, because normal humans don't think in latitude and longitude in the first place. To me, those are just values to copy and paste into a maps app to see where something is, and if it's pointing to more or less the right location, I'm happy. They're like the physical-world equivalent of a URL; I don't honestly care if there's an unused query string parameter tacked onto the end of it or if it redirects to https or something; all I care about is that the link I clicked on gets me to the correct cat video.
- falcolas 7y agoIf you're given 8 significant digits, how many of those are correct? 3? 4? 5? The difference between those three is the difference between a position on a street block and the position of a person in a room (to quote XKCD). At least with 0's, you can approximate how accurate the value is. With garbage, all you can do is hope you've guessed correctly.
- jstewartmobile 7y agoThat is a misunderstanding of floating point. The relationship between trailing non-zero digits in the decimal representation and trailing non-zero bits in the significand is not one-to-one. One third in a trinary representation would be 0.1. In decimal, 0.33333333333... Mostly fruitless overprocessing. Only time I'd consider doing this would be for an epic ASCII dump of coordinates.
- jjoonathan 7y agoIt's wrong if you ignore context -- but then, everything is. The context is that it's in a database serving up business locations. How is the geographic area owned (or occupied?) by a business reduced to a point? They don't say, so it's clearly unreasonable to expect accuracy and precision beyond, say, property boundaries, and perhaps not even that. It would be madness to infer that the extra digits denote precision beyond the crude bounds set by context. It would be further madness to reverse engineer a property boundary -- an entire path of points -- from a single point in a database.
- falcolas 7y agoYou can click at arbitrary positions on those maps and get 6+ sig-fig values for those positions. And since the map displays a satellite representation of the property, is it really that extraordinary that people might consider it to be sufficiently precise enough to put in a fence? FWIW, the error margin for 6 significant digits is around 11 cm. Accurate enough to point at a computer mouse.
- jjoonathan 7y agoIf the page in question listed something that could be construed as a property boundary, sure. It doesn't.
- falcolas 7y agoEvery new home owner gets a "plat" that outlines the boundaries of their property, including GPS coordinates. Using a tool (like Google Maps) to overlay a coordinate with a ground feature isn't exactly absurd.
- jjoonathan 7y agoWhat does that have to do with the Melbourne Open Data Portal? If you want to argue that Google Maps could do more to highlight the accuracy/precision limitations of its projected imagery, I'd completely agree -- but that's a different argument.
- 7952 7y agoA lot of these kind of coordinates have no right answer anyway. They are just an abstract approximation of something else, like a parcel, address, or place to eat. And the lat/long will be completely useless for the vast majority of people. In any serious application you should have known error values and probably be using a more appropriate projection. If you need to accurately locate something you need someone trained to do that with the right equipment.
- falcolas 7y agoThey aren't approximations; you can verify this yourself. Pull up Google Maps, pick an arbitrary spot with no businesses, and click. You will get at least 6 significant digit coordinates.
- 7952 7y agoNo, I meant that it is an approximation or the thing in the real world that it represents. For example, consider a restraunt. Should the point be at the entrance to the building, in the middle of the building, or maybe at the door round the back where mail is delivered, or at the centroid of the parcel. In order to actually use this excessive precision you would need to know that. In the examle cases the data is not formal enough for this to matter. It is an approximation of some real world thing and never meant to be used for highly precise work.
- falcolas 7y agoThen the coordinates presented should match that approximation. Anyone who has worked with plans knows that the number of significant digits presented on the plans has a meaning; it represents the margin of error. Online maps aren't respecting this, they're giving decimeter precision values on maps that are lucky if they're accurate to within meters, if not tens of meters. That's the problem.
- 7952 7y agoI think that makes sense on plans that are using a proper coordinate system and have sub-metre accuracy. But removing digits further just causes confusion. You are just using the grid ref as a proxy for something else, like a circle or square which represents the error. Except in these examples it doesn't matter. No one actually needs the data to be super accurate. The coordinate length is just a style thing. Are you working with plans that show decimal degrees at a specific precision? I am curious what domain that is.
- rumanator 7y ago> Because the value, as presented, is wrong. That's not true nor is it the problem at all. The thesis was that the values, albeit correct, have too many significant digits, which in turn reflect differences which lie somewhere between having no practical use or being absurd. > Imagine, for a moment, that someone uses these values to put up a fence. That example is very poor. Any engineer can tell you that a measurement is meaningless without tolerances/margin of error, and the tolerance in effect when putting up a fence is not expressed in a microscopic scale.
- ramshorns 7y ago> a measurement is meaningless without tolerances/margin of error Reporting a value with too many significant digits is the same as reporting an incorrect margin of error, which (arguably) makes the value wrong.
- seandougall 7y agoThat's certainly true in a scientific paper, where the concept of significant digits is relevant and widely recognized. In a "please remove dead animal" web request, the value is only wrong if it points to the wrong location (i.e. a location that does not contain a dead animal).
- kbutler 7y ago> Any engineer can tell you that a measurement is meaningless without tolerances/margin of error, and the tolerance in effect when putting up a fence is not expressed in a microscopic scale. But these locations are very precise, indicating high accuracy/low margin of error, but they don't have that high accuracy. In fact, the error could be in meters, rather than in the implied millimeters, so it definitely could be a problem for a fence. Here is a college textbook chapter detailing types of precision and accuracy errors in GIS systems: https://www.e-education.psu.edu/geog469/book/export/html/252 https://www.e-education.psu.edu/geog469/book/export/html/252 "GIS users are not always aware of the difficult problems caused by error, inaccuracy, and imprecision. They often fall prey to False Precision and False Accuracy, that is they report their findings to a level of precision or accuracy that is impossible to achieve with their source materials. If locations on a GIS coverage are only measured within a hundred feet of their true position, it makes no sense to report predicted locations in a solution to a tenth of a foot. That is, just because computers can store numeric figures down many decimal places does not mean that all those decimal places are "significant." It is important for GIS solutions to be reported honestly, and only to the level of accuracy and precision they can support." Or in other words, don't build a fence relying on naked coordinates of high precision but unknown accuracy.
- jiveturkey 7y ago> Is the fence on their property? Even if the values were precise, the fence can never be precisely located. Land/parcel demarcations don't work that way. Also, GPS coordinates change over time. Or rather, the land underneath moves. Fence or other land locations are always relative (to an official surveyor's point), not absolute. Rewinding a little: > Imagine, for a moment, that someone uses these values to put up a fence. There's your first problem.