I tend to interpret accuracy as a theoretical circle around the given point, indicating that the actual point probably lies somewhere within that circle. 
Unless accuracy means something else in this context, I'm not sure how you imagine using the accuracy value to extrapolate the "real" point?
                
     
                                    
            So what does that accuracy of 5.229 etc mean?
Realistically speaking, with lat/lon values collected by a mobile app that amount of decimal places is completely unnecessary.  12 decimal places in degrees puts you in the nanometer range, "atomic scale". Using a CoordinateRounder  to bring that back to manageable values.
 
This is something I have taped to my monitor to keep things in check

                
     
                                    
            So what does that accuracy of 5.229 etc mean?
Realistically speaking, with lat/lon values collected by a mobile app that amount of decimal places is completely unnecessary.  12 decimal places in degrees puts you in the nanometer range, "atomic scale". Using a CoordinateRounder  to bring that back to manageable values.
 
This is something I have taped to my monitor to keep things in check

@Hans van der Maarel 
if I understand you well we need to round those coordinate in order to get a realistic location?
Let me put you in context
the mobile  used to collect info from gas station on the road 
each station will have some services around it such as restaurant play area ..ext
du to the accuracy of the GPS reader some time we getting services close to B but in reality   its close to Station A 
we did use a buffer  for each station  , but  we still have some  the same issue as described 
we though using  with the accuracy value we could adjust the coordinate 
Any thoughts?