context is missing when requesting a place by its id

[younes0]

It may be the wrong place to raise this issue but, the context object is not included when searching by feature id https://api.maptiler.com/geocoding/region.26866992?key=XXXXX&language=en%2Cfr There shouldn't be any limitations that would prevent to include this context object right ?

[bolollo]

Hi, currently, the context is not returned if there is no context (for countries) or an object is queried by its ID. Otherwise, the context must be there.

To get context, you can perform reverse geocoding using the (center) coordinates returned in response to a query by ID. Example: https://api.maptiler.com/geocoding/115.0906400755048,-8.330497647109507.json?key=XXXXX&language=en,fr

Any other question or doubt do not hesitate to write us here or create a new issue.

[younes0]

Hi @bolollo Thanks for your response, actually this is what I'm doing currently: given: https://api.maptiler.com/geocoding/county.26994945.json ("Las Palmas" feature) I get the the center: https://api.maptiler.com/geocoding/-13.516065765662052,29.413087272089275.json

But I see 2 problems here:

• major: in the Reverse Query, the feature "Las Palmas" is not listed
• minor: in the ID Query, surely related to missing context, placeNamedoesn't include the parent's name, instead of "Las Palmas, Canarias, Spain" we have "Las Palmas"

Edit: changed URL

[younes0]

Your solution works, thanks @bolollo I was trying to get the feature "Las Palmas" in the reverse geocoding results but all I need is the first (lowest admin level).feature's context

BTW, I saw that all ids have changed recently, are these ids are stable now ?

[bolollo]

Hi @younes0, I'm glad it works for you. We are making changes to improve the geocoder; recently, we have changed the Ids. At the moment, we only have stable Ids for some elements.

I see you are looking for Las Palmas; we can speak in Spanish if you prefer.

[younes0]

hello @bolollo sorry for the late response. okay that's good to know that you have stable ids for the main elements (continents, countries, regions & big cities from what I saw)

[younes0]

Hello there,

Since our last interaction, I saw that the maptiler IDs have been changed for some elements such as subregions. I was just wondering if the IDs were now stable ?

My app would crash with unstable ids. I could rely on the OSM IDs but your API doesn't allow to get a Feature by its OSM ID.

Thanks.

[jonathanlurie]

Hello @younes0 , thanks for the feedback! I'll pass the question to the person in charge of geocoding, and let you know.

[younes0]

@jonathanlurie thank you @jonathanlurie , please let me know if this is not the appropriate place to ask this. Best.

[zdila]

Hi @younes0. Feature IDs are unfortunately not stable and change every time we update indexes. We may later introduce a service which would map osm ID to feature ID as we know about this problem.

[younes0]

Hello @zdila, is this mapping service translates to an endpoint that queries by osm ID instead of featureID ? eg: https://api.maptiler.com/geocoding/{osm-id}.json If yes, when do you plan to release this service ? Do you plant to update indexes again before its release ? Best.

[zdila]

No we don't plan this. We use various sources, not only OSM. Also some features in geocoding are derived from multiple features from OSM.

To get feature by OSM ID the best is to use OSM API directly.

[younes0]

@zdila Thank you for your answer. Unfortunately, I need stable ID.