Production release 3520 - Change in the search center

[fassone]

Here's the changes we applied:
- Provide an address for the search center in /discover/here
- Improve the HTML Json rendeing
- Finland address format and Romania address formatting has been fixed
- The Size parameter against /explore influences just the number of places in the response

The search center for /discover/search /discover/explore and /discover/here has been modified, we wanted to have a future proof structure for the search center, so it would be easier for users of the api to implement against other endpoints and have consistency across all the discover endpoints.

In the old structure we had:

{

search: {

location: {

position: [lat, lon]
bbox: [w, s, e, n] //optional
title: "name of place" //optional name of the place
address: "address" //optional the neighbourhood of the location used for the search
href: "uri" //optional for moved search result shows the point form where the search started
moved: true //optional if present shows the search result is "moved"

}

}

}
The new response has the location inside the context and the title, href and moved are inside the context instead.

{

search: {

context:{

title: "name of place" //optional name of the place
typelace //optional present only if the href link is present
href: "uri" //optional for moved search result shows the point form where the search started
moved: true //optional if present shows the search result is "moved"

location: {

position: [lat, lon]
bbox: [w, s, e, n] //optional
address: "address" //optional the neighbourhood of the location used for the search

}

}

}

}

[vladestCh]

any news about search within radius?

[Maveric]

Hi there,

I am communicating this with the team developing the API and will let you know asap when I have an update.

Best Regards,
Marko

[danielmoor]

Hi,

Thank you for bringing this up again!

We will send an update on this by Wednesday.

daniel.

[danielmoor]

Hi,

Search within a radius is currently still under discussion: We understand that this is a needed feature, but we are still investigating internally what would be the best way to retrieve the data internally. Thus, the implementation won’t come soon.

What we could do easier is to provide /discover/explore results (with an optional category parameter) restricted to a given area. Would this help your use case?

daniel.