Geolocation accuracy on hire notes: what the radius means
Read a browser location accuracy figure with its source, units and document version. A practical hire-record example using the 5 November 2026 W3C draft.
By AuditIt Editorial Team · Fact checked
What to know
- The 5 November 2026 W3C draft defines a meter radius and uses 68% confidence wording.
- An unexplained 8 m reading still needs its own source and confidence basis.
- Keep a position acquisition timestamp separate from the photograph capture time.
A browser location reading needs its source and units beside the number. The W3C Geolocation draft dated 5 November 2026 describes accuracy as a radius in meters, with 68% confidence wording in its acquisition algorithm. That definition alone cannot establish where a condition photograph was taken.
Why the document version matters
The 5 November W3C document is a Candidate Recommendation Draft: work in progress that may change. Its section 9.1 defines the radius; section 6.6 supplies the confidence wording. The 30 October draft we checked did not contain that 68% wording.
MDN's accuracy reference, updated on 6 November 2026, also describes latitude and longitude accuracy in meters at 68% confidence. These sources explain documentation. They are not a test of the software or phone that supplied an individual reading.
For the broader product labels, see location accuracy in condition records. That guide cites an earlier specification version; keep the version with any percentage you quote rather than silently applying a newer definition to an older record.
An eight-meter reading with information missing
Consider fictional training asset HX-22. A colleague supplies a browser line labeled accuracy, with a value of 8 m, alongside a photograph named HX-22-return.jpg. The originating application, request settings and position timestamp are missing. No photograph capture time was supplied.
A suggested note would read: “HX-22 — submitted browser accuracy: 8 m. Source application, request settings and position timestamp not supplied; confidence basis not confirmed. Separate photograph: HX-22-return.jpg; capture time not supplied.” This is an editorial example, not a customer record or a required form.
The next useful question is which application produced the line and what source details accompanied it. Until the sender answers, leave those gaps visible. A small number should not become a claim that the photograph was taken within that distance of a yard pin.
Keep request settings and clocks with their own source
The draft treats enableHighAccuracy as a hint that the implementation can ignore. A high-accuracy request therefore cannot identify the location provider or establish that GPS was used. Keep a supplied request label with the reading; avoid filling in a missing setting from the label alone.
W3C defines the position timestamp as the time the device's geographic position was acquired. It is not a photograph's capture time. If the question concerns an older reading, the cached-geolocation guide covers acquisition time and cache acceptance separately.
Connect the note to the condition record
A typed browser reading remains a submitted statement about another source. AuditIt capture facts can include location and accuracy when enabled for a live camera capture. Import facts describe when and how a gallery file entered AuditIt; they do not stand in for that file's capture time or location.
Choose the workflow for the condition-record job: the equipment checkout-and-return starter has before-and-after stages, while the damage and pre-hire starters are single-visit records. The equipment checkout-and-return guide explains the two-stage workflow.
The web specification does not establish how AuditIt's mobile capture interprets an accuracy value. Keep the submitted location, the photograph and any unresolved source questions available for a person to review.
AuditIt creates tamper-evident, human-review-ready records. It is not legal certification and does not determine liability.
Prepared with AI assistance and checked against the linked sources.
Direct answers
Frequently asked questions
Does an accuracy figure of 8 meters place the photograph within 8 meters of a pin?
A radius describes the location reading's accuracy under its stated definition. The 5 November W3C draft uses 68% confidence wording, rather than a maximum-error guarantee. An unexplained reading also needs its own source information before you apply that definition to it.
Does a high-accuracy request prove GPS was used?
The request is a hint, and the implementation can ignore it. Keep the request setting as supplied information; it does not identify which provider produced the reading.
Is the position timestamp the time the condition photograph was taken?
The W3C timestamp identifies position acquisition. Record a photograph's capture time separately when it is available, and leave it unknown when it was not supplied.
Sources
- equipment rental
- location accuracy
- condition records
- geolocation
