Closed tomtwinkle closed 2 weeks ago
@bxcodec May I ask you to check?
@tomtwinkle Hi,
Do you still have interest in adding this feature to faker? Since we have had this PR on hold for some time, we may have to close or have someone do the missing tests.
I'll close this, and please re-pen if anyone still have interest to work on this
The current latitude and longitude generation logic generates values with a maximum precision of 15 float places
Example:
-13.170896530151367
-128.38621520996094
This is larger than the actual latitude and longitude accuracy returned by GoogleMaps GeocodeAPI, etc., and the generated values cannot be stored with accurate accuracy when mapped to json or stored in a database such as MySQL.
Example:
-13.17089653
-128.38621521
Therefore, we propose to change it so that the accuracy can be specified as an optional argument.