Add latitude and longitude to ContactAddress interface?

[stpeter]

Would it make sense to add optional latitude and longitude fields to the PaymentAddress construct? I see at least two potential use cases:

(1) Providing a location hint in cases where a navigation system can yield ambiguous results (this happens to me all the time at home - delivery drivers will end up 20 miles away at a street with the same name in the next county).

(2) Providing an accurate location in parts of the world where things like street names aren't used (e.g., https://hackernoon.com/online-shopping-in-africa-doesnt-work-because-of-this-web-form-e4974a8d165a describes this kind of scenario).

[ianbjacobs]

This issue was raised in Payment Request, but closed once we removed addresses from that API. Since the features are now part of Contact Picker, we are transferring the issue here.