Add an accuracy option to the latitude and longitude of an address

[tomtwinkle]

The current latitude and longitude generation logic generates values with a maximum precision of 15 float places

Example:

• latitude -13.170896530151367
• longitude -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:

• latitude -13.17089653
• longitude -128.38621521

Therefore, we propose to change it so that the accuracy can be specified as an optional argument.

[tomtwinkle]

@bxcodec May I ask you to check?

[bxcodec]

Sorry for the late reply, been busy with something in real life.

Code wise it's okay, but can you help to add the test, please?

[rubemlrm]

@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.