So far, accuracy sounds like that whatever methods or algorithm that Google or Apple or FB or any other company used to estimate user's location information based on cell tower, AP location, GPS coordinate information and its combination, it is their own estimate of accuracy to the longitude and latitude information provided in their(Apple or Google's or FB or other company) location API with say, given 95% Confidence Interval Level.
\n\nYet the algorithm calculating the user's location coordination is a black box to us. If my conjecture, which based on other well-known practice, is right, the accuracy is incurred by the method chosen to estimate a user's location. The scatter plot of accuracy, provided in script section, will provide good insight on what accuracy can be.
", "messages": [ { "id": "120505", "postDate": "05/18/2016 18:28:04", "content": "So far, accuracy sounds like that whatever methods or algorithm that Google or Apple or FB or any other company used to estimate user's location information based on cell tower, AP location, GPS coordinate information and its combination, it is their own estimate of accuracy to the longitude and latitude information provided in their(Apple or Google's or FB or other company) location API with say, given 95% Confidence Interval Level.
\n\nYet the algorithm calculating the user's location coordination is a black box to us. If my conjecture, which based on other well-known practice, is right, the accuracy is incurred by the method chosen to estimate a user's location. The scatter plot of accuracy, provided in script section, will provide good insight on what accuracy can be.
", "rawMarkdown": "So far, accuracy sounds like that whatever methods or algorithm that Google or Apple or FB or any other company used to estimate user's location information based on cell tower, AP location, GPS coordinate information and its combination, it is their own estimate of accuracy to the longitude and latitude information provided in their(Apple or Google's or FB or other company) location API with say, given 95% Confidence Interval Level. \r\n \r\nYet the algorithm calculating the user's location coordination is a black box to us. If my conjecture, which based on other well-known practice, is right, the accuracy is incurred by the method chosen to estimate a user's location. The scatter plot of accuracy, provided in script section, will provide good insight on what accuracy can be.", "votes": null }, { "id": "120530", "postDate": "05/18/2016 21:34:34", "content": "The timestamp attribute represents the time when the Position object was acquired and is represented as a DOMTimeStamp [DOMTIMESTAMP].
\n\nDOMTimeStamp
\n\nIDL\ntypedef unsigned long long DOMTimeStamp;\nThe DOMTimeStamp type is used for representing a number of milliseconds, either as an absolute time (relative to some epoch) or as a relative amount of time. Specifications that use this type will need to define how the number of milliseconds is to be interpreted.
\n\nThe definition above is one of a standardized way, but not sure whether this is the correct representation here as well, I haven't looked at it yet.
", "rawMarkdown": "The timestamp attribute represents the time when the Position object was acquired and is represented as a DOMTimeStamp [DOMTIMESTAMP].\r\n\r\nDOMTimeStamp\r\n\r\nIDL\r\ntypedef unsigned long long DOMTimeStamp;\r\nThe DOMTimeStamp type is used for representing a number of milliseconds, either as an absolute time (relative to some epoch) or as a relative amount of time. Specifications that use this type will need to define how the number of milliseconds is to be interpreted.\r\n\r\nThe definition above is one of a standardized way, but not sure whether this is the correct representation here as well, I haven't looked at it yet.", "votes": null } ], "comments": [ { "id": 120530, "author_name": "ykim007", "author_url": "", "post_date": "05/18/2016 21:34:34", "content": "The timestamp attribute represents the time when the Position object was acquired and is represented as a DOMTimeStamp [DOMTIMESTAMP].
\n\nDOMTimeStamp
\n\nIDL\ntypedef unsigned long long DOMTimeStamp;\nThe DOMTimeStamp type is used for representing a number of milliseconds, either as an absolute time (relative to some epoch) or as a relative amount of time. Specifications that use this type will need to define how the number of milliseconds is to be interpreted.
\n\nThe definition above is one of a standardized way, but not sure whether this is the correct representation here as well, I haven't looked at it yet.
", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "120505": "So far, accuracy sounds like that whatever methods or algorithm that Google or Apple or FB or any other company used to estimate user's location information based on cell tower, AP location, GPS coordinate information and its combination, it is their own estimate of accuracy to the longitude and latitude information provided in their(Apple or Google's or FB or other company) location API with say, given 95% Confidence Interval Level. \r\n \r\nYet the algorithm calculating the user's location coordination is a black box to us. If my conjecture, which based on other well-known practice, is right, the accuracy is incurred by the method chosen to estimate a user's location. The scatter plot of accuracy, provided in script section, will provide good insight on what accuracy can be.", "120530": "The timestamp attribute represents the time when the Position object was acquired and is represented as a DOMTimeStamp [DOMTIMESTAMP].\r\n\r\nDOMTimeStamp\r\n\r\nIDL\r\ntypedef unsigned long long DOMTimeStamp;\r\nThe DOMTimeStamp type is used for representing a number of milliseconds, either as an absolute time (relative to some epoch) or as a relative amount of time. Specifications that use this type will need to define how the number of milliseconds is to be interpreted.\r\n\r\nThe definition above is one of a standardized way, but not sure whether this is the correct representation here as well, I haven't looked at it yet." }, "source": "meta" }