GNOME Bugzilla – Bug 697174
Export bounding box when available
Last modified: 2019-03-20 10:36:39 UTC
Once patches from bug#696527 are merged, we should also report accuracy of forward geocoding results. The yahoo API we are using provides a bounding box end-points of the location and we already have code to find distance between two locations: <centroid> <latitude>60.171162</latitude> <longitude>24.932581</longitude> </centroid> <boundingBox> <southWest> <latitude>60.090611</latitude> <longitude>24.828320</longitude> </southWest> <northEast> <latitude>60.289291</latitude> <longitude>25.369360</longitude> </northEast> </boundingBox>
Can I have a patch for this, please?
(In reply to comment #1) > Can I have a patch for this, please? Yeah :) Hopefully this week.
Actually I'm not so sure this is a good idea anymore. Firstly, the BoundingBox give by yahoo seems more like boundaries of the place itself rather than any accuracy information. Secondly, I don't see the relevance of accuracy in geocoding results as the coordinates of the returned places is supposed to be always pretty accurate. This would also explain why neither yahoo nor google provide any accuracy info in the results: https://developers.google.com/maps/documentation/geocoding/#GeocodingResponses
Based on comment#3.
It think it would be good to export the bounding box to the results though, which would be useful to present it on a map.
(In reply to comment #5) > It think it would be good to export the bounding box to the results though, > which would be useful to present it on a map. Yeah, we could use that to decide the zoom-level for example.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/geocode-glib/issues/7.