geocode-glib issueshttps://gitlab.gnome.org/GNOME/geocode-glib/-/issues2019-11-06T15:49:00Zhttps://gitlab.gnome.org/GNOME/geocode-glib/-/issues/19geocode-nominatim: Allow the cache path to be adjusted2019-11-06T15:49:00ZBugzillageocode-nominatim: Allow the cache path to be adjusted## Submitted by Philip Withnall `@pwithnall`
**[Link to original bug (#777196)](https://bugzilla.gnome.org/show_bug.cgi?id=777196)**
## Description
Split off from discussion in https://bugzilla.gnome.org/show_bug.cgi?id=756311#c160....## Submitted by Philip Withnall `@pwithnall`
**[Link to original bug (#777196)](https://bugzilla.gnome.org/show_bug.cgi?id=777196)**
## Description
Split off from discussion in https://bugzilla.gnome.org/show_bug.cgi?id=756311#c160.
I still think it’s a good idea to allow these things to be configurable on a per-object basis rather than using global shared state ($XDG_CACHE_HOME) for them, but in the case of ensuring the unit tests don’t use a common cache, setting $XDG_CACHE_HOME works fine.https://gitlab.gnome.org/GNOME/geocode-glib/-/issues/17Support localised place names2019-03-20T10:40:00ZBugzillaSupport localised place names## Submitted by Philip Withnall `@pwithnall`
**[Link to original bug (#756566)](https://bugzilla.gnome.org/show_bug.cgi?id=756566)**
## Description
Would it be possible to pass the namedetails=1 parameter to the Nominatim query inte...## Submitted by Philip Withnall `@pwithnall`
**[Link to original bug (#756566)](https://bugzilla.gnome.org/show_bug.cgi?id=756566)**
## Description
Would it be possible to pass the namedetails=1 parameter to the Nominatim query interface to return the localised forms of place names, and expose those in the geocode-glib API so that clients can make use of them?
http://wiki.openstreetmap.org/wiki/Nominatim#Parameters_2
Version: 3.18.xhttps://gitlab.gnome.org/GNOME/geocode-glib/-/issues/16Should ignore additional postal codes2019-03-20T10:39:52ZBugzillaShould ignore additional postal codes## Submitted by Frederic Peters `@fpeters`
**[Link to original bug (#749967)](https://bugzilla.gnome.org/show_bug.cgi?id=749967)**
## Description
For Strasbourg nominatim gives such an address:
"address" : {"city":"Strasbourg","coun...## Submitted by Frederic Peters `@fpeters`
**[Link to original bug (#749967)](https://bugzilla.gnome.org/show_bug.cgi?id=749967)**
## Description
For Strasbourg nominatim gives such an address:
"address" : {"city":"Strasbourg","county":"Strasbourg","state":"Alsace","country":"France","postcode":"67000;67100;67200","country_code":"fr"},
(taken from http://nominatim.openstreetmap.org/search/fr/strasbourg?format=json&addressdetails=1)
But "67000;67100;67200" is not really nice as a postcode displayed in UI, maybe it could be cut to only include the first part.
Version: 3.17.xhttps://gitlab.gnome.org/GNOME/geocode-glib/-/issues/15Add possibility to reverse geocode based on osm_id and osm_type2019-03-20T10:39:29ZBugzillaAdd possibility to reverse geocode based on osm_id and osm_type## Submitted by Jonas Danielsson `@jonasdn`
**[Link to original bug (#742512)](https://bugzilla.gnome.org/show_bug.cgi?id=742512)**
## Description
In Maps we store GeocodePlaces (favorites and recent) in a store. We want to detect w...## Submitted by Jonas Danielsson `@jonasdn`
**[Link to original bug (#742512)](https://bugzilla.gnome.org/show_bug.cgi?id=742512)**
## Description
In Maps we store GeocodePlaces (favorites and recent) in a store. We want to detect when they are stale, based on how long they are stored. And then refresh them.
It would help if we could refresh them based on the osm_id and the osm_type.
So we do not have any doubts that we get the same place.https://gitlab.gnome.org/GNOME/geocode-glib/-/issues/14Further geoURI extensions2019-03-20T10:38:35ZBugzillaFurther geoURI extensions## Submitted by Jonas Danielsson `@jonasdn`
**[Link to original bug (#737979)](https://bugzilla.gnome.org/show_bug.cgi?id=737979)**
## Description
We already use one of the exensions used by Android, from here: https://developer.and...## Submitted by Jonas Danielsson `@jonasdn`
**[Link to original bug (#737979)](https://bugzilla.gnome.org/show_bug.cgi?id=737979)**
## Description
We already use one of the exensions used by Android, from here: https://developer.android.com/guide/components/intents-common.html
geo:0,0?q=lat,lng(label)
Show the map at the given longitude and latitude with a string label.
Example: "geo:0,0?q=34.99,-106.61(Treasure)"
^^^
This one we use. A question about that. At the moment we only support a label with no whitespace in it. So "MyLocation" would work, but not "My Location".
Should that be fixed?
geo:0,0?q=my+street+address
Show the location for "my street address" (may be a specific address or location query).
Example: "geo:0,0?q=1600+Amphitheatre+Parkway%2C+CA"
^^^
Do we want to implement that one? So that we could search via an uri?
The set_from_uri would then call out to a forward search I guess.https://gitlab.gnome.org/GNOME/geocode-glib/-/issues/13Non-distinguished answers2019-03-20T10:38:26ZBugzillaNon-distinguished answers## Submitted by Bastien Nocera `@hadess`
**[Link to original bug (#732726)](https://bugzilla.gnome.org/show_bug.cgi?id=732726)**
## Description
$ ./test-gcglib guildford
Got geocode search answer:
Guildford, Surrey, United Kingdom ...## Submitted by Bastien Nocera `@hadess`
**[Link to original bug (#732726)](https://bugzilla.gnome.org/show_bug.cgi?id=732726)**
## Description
$ ./test-gcglib guildford
Got geocode search answer:
Guildford, Surrey, United Kingdom @ 51.237195, -0.581178
Got geocode search answer:
Guildford, Surrey, United Kingdom @ 51.235267, -0.565362
`<snip>`
The 2 first answers should have different labels differentiating them.https://gitlab.gnome.org/GNOME/geocode-glib/-/issues/12geocode-glib installs icons in the gnome icon theme2019-03-20T10:38:04ZBugzillageocode-glib installs icons in the gnome icon theme## Submitted by Kalev Lember
**[Link to original bug (#730896)](https://bugzilla.gnome.org/show_bug.cgi?id=730896)**
## Description
geocode-glib currently installs its mime type icons in the gnome icon theme directories. The gnome i...## Submitted by Kalev Lember
**[Link to original bug (#730896)](https://bugzilla.gnome.org/show_bug.cgi?id=730896)**
## Description
geocode-glib currently installs its mime type icons in the gnome icon theme directories. The gnome icon theme is going away in 3.14 and is being replaced by the Adwaita icon theme.
According to mclasen, those geocode-glib icons should go in a private icon theme extension instead.
/usr/share/icons/gnome/scalable/places/poi-airport.svg
/usr/share/icons/gnome/scalable/places/poi-building.svg
/usr/share/icons/gnome/scalable/places/poi-bus-stop.svg
/usr/share/icons/gnome/scalable/places/poi-car.svg
/usr/share/icons/gnome/scalable/places/poi-marker.svg
/usr/share/icons/gnome/scalable/places/poi-railway-station.svg
/usr/share/icons/gnome/scalable/places/poi-town.svg
### Blocking
* [Bug 731587](https://bugzilla.gnome.org/show_bug.cgi?id=731587)
* [Bug 734722](https://bugzilla.gnome.org/show_bug.cgi?id=734722)https://gitlab.gnome.org/GNOME/geocode-glib/-/issues/11Searching for French town gives out wrong administrative boundaries2019-03-20T10:37:49ZBugzillaSearching for French town gives out wrong administrative boundaries## Submitted by Bastien Nocera `@hadess`
**[Link to original bug (#728114)](https://bugzilla.gnome.org/show_bug.cgi?id=728114)**
## Description
For example, searching for "Sablons" in gnome-maps will show "Sablons, Vienne, Rhone-Alp...## Submitted by Bastien Nocera `@hadess`
**[Link to original bug (#728114)](https://bugzilla.gnome.org/show_bug.cgi?id=728114)**
## Description
For example, searching for "Sablons" in gnome-maps will show "Sablons, Vienne, Rhone-Alpes, France".
"Vienne" is the name of the "sous-prefecture" and shouldn't show up in the search results (it's the name of the town inside that boundary). Admin-level is 7.
http://nominatim.openstreetmap.org/details.php?place_id=97327420https://gitlab.gnome.org/GNOME/geocode-glib/-/issues/10Add property for the unmodified name in GeocodePlace2019-03-20T10:37:31ZBugzillaAdd property for the unmodified name in GeocodePlace## Submitted by Jonas Danielsson `@jonasdn`
**[Link to original bug (#726773)](https://bugzilla.gnome.org/show_bug.cgi?id=726773)**
## Description
At the moment Geocode does some tricks to set the name of the Places returned from a ...## Submitted by Jonas Danielsson `@jonasdn`
**[Link to original bug (#726773)](https://bugzilla.gnome.org/show_bug.cgi?id=726773)**
## Description
At the moment Geocode does some tricks to set the name of the Places returned from a GeocodeForward search. It includes the name of the place a long with county, country, postcode, house number and other attributes that are needed to separate the returned item from the rest of the items.
If an application want to have it's own scheme for setting a display name then we have to do some parsing of the name attribute to get only the name and then get the attributes we want and add them on to it.
Is there anyway to make the name attribute of a returned GeocodePlace just be the name of the place? And maybe introduce a display-name attribute to have the name we compute? Or maybe just be satisfied with setting the GeocodeLocation description to the display name?
This way might be to disruptive to the API though. Thoughts?https://gitlab.gnome.org/GNOME/geocode-glib/-/issues/9Set better names on places returned by forward search2019-11-06T15:46:51ZBugzillaSet better names on places returned by forward search## Submitted by Jonas Danielsson `@jonasdn`
**[Link to original bug (#721340)](https://bugzilla.gnome.org/show_bug.cgi?id=721340)**
## Description
Created attachment 265135
Searching for high street with current master
I've been bo...## Submitted by Jonas Danielsson `@jonasdn`
**[Link to original bug (#721340)](https://bugzilla.gnome.org/show_bug.cgi?id=721340)**
## Description
Created attachment 265135
Searching for high street with current master
I've been bothered by the results returned when searching for a common street name in London. I got results that was hard to distinguish from each others.
See the attached image for what I mean.
I got to debugging a bit to see what the data from Nominatim was for each item.
Data to separate the results from each other is there, but not used by Geocode.
Or rather the code filters them out.
I will attach a patch that changes how the attributes are filtered in or out.
So that results will have the general form of:
[name], [suburb], [county], [postcode], [state], [country]
If the attributes are available.
Also, I will post a patch that fixes a typo that caused postcode never to be included.
See image attached soon, of how the same search looks with the patch.
The way geocode decides what attributes to include in the name attribute of GeocodePlace is still a bit shaky I feel. Maybe the best approach would just be to set a simple name, e.g. "High Street". And let the application that uses it construct the full name for it self using GeocodePlace attributes. Or maybe add some kind of "simple name" attribute to GeocodePlace for the same reason.
**Attachment 265135**, "Searching for high street with current master":
![current](/uploads/974af1f9133aa2df5017464ca40dc633/current.png)https://gitlab.gnome.org/GNOME/geocode-glib/-/issues/7Export bounding box when available2019-03-20T10:35:34ZBugzillaExport bounding box when available## Submitted by Zeeshan Ali
**[Link to original bug (#697174)](https://bugzilla.gnome.org/show_bug.cgi?id=697174)**
## Description
Once patches from bug#696527 are merged, we should also report accuracy of forward geocoding results....## Submitted by Zeeshan Ali
**[Link to original bug (#697174)](https://bugzilla.gnome.org/show_bug.cgi?id=697174)**
## Description
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>`