What's new in release 20201111

Subfields support

Previously, if you wished to specify which fields to include in an API response, then (with some exceptions) it was only possible to do so for the top-level objects returned; any nested objects always had their default set of fields, with no way to change it. It is now possible to specify which fields to return for any given type for any endpoint. See the documentation for more details.

Note that this feature has been backported to all supported API versions.

Deprecated fields not included by default

Now that it is possible to specify which fields to return for nested types, we no longer include by default any fields that are deprecated (this affects the article, image and tour types).

Improved and updated data

We have improved our data, adding better support for overseas departments and territories. As part of this, many such territories are now treated as top-level locations. We also put some effort in getting more national parks and nature reserves and improving the algorithms that decide which POIs should be assigned to them.

As usual, this release contains many other small improvements to our algorithms as well as refreshed data.


What's new in release 20200803

New or improved tags

We have added a number of new tag labels and improved the coverage of others, in particular:

  • feature-Delivery (new tag label)
  • feature-Drive_through (new tag label)
  • feature-Takeaway (new tag label)
  • feature-Outdoor_seating (improved coverage)
  • character-Chain (new tag label)

See the reference documentation for more information about the available tag labels.

Updated data

As always, this release contains refreshed data and various fixes and improvements to our algorithms.

Merging of our enterprise and non-enterprise releases

With this release, we no longer have separate data versions for our enterprise customers. The biggest impact for our non-enterprise customers is that we no longer include content (text or images) from Facebook. For our enterprise customers, combining the releases means a significant increase in the number of objects in the database (e.g. 13% more POIs than the last enterprise release, including nearly 50% more restaurants).

Location ID changes

In general, we try to keep IDs as stable as practical between data releases. However, in order to solve some issues and improve things going forward, we've made changes that mean that you might notice a higher rate of change in location IDs in this release than usual (but still small).


What's new in release 20200405

New beach-related tags

We have added a number of new tag labels related to beaches:

  • character-Clean
  • character-Dirty
  • character-Crowded
  • character-Quiet
  • character-Safe_swim
  • character-Dangerous_swim
  • character-Sandy_beach
  • character-Shingle_beach
  • character-Rocky_beach
  • character-Wheelchair_friendly
  • feature-Seasonal_lifeguard
  • feature-Shower
  • feature-Toilet
  • feature-Lockers
  • feature-Transport_access
  • feature-Has_parking

See the reference documentation for more details.

New adult content tag

We have added a new tag label character-Adult_content. This is applied to adult-oriented POIs, POIs where the description contains adult content, and POIs where adult themes are likely to be encountered (e.g. a square known as a hangout for prostitutes). This tag label can be used to exclude these kinds of POIs if one is trying to present a family-friendly experience.

Updated data

As always, this release contains refreshed data and various fixes and improvements to our algorithms.