search

qpowell / google_places

A Ruby wrapper around the Google Places API
MIT License
382 stars 188 forks source link

Issue with Field specification – Atmospheric Data is being called even when a related field is not specified. #137

Open richardsondx opened 2 years ago

richardsondx commented 2 years ago

The api mentioned that Atmosphere data is charged when these fields are used on the web service: price_level, rating, review or user_ratings_total https://developers.google.com/maps/documentation/places/web-service/usage-and-billing

We have specified the following fields in our query: place_id,name,lat,lng,types,vicinity

google_place_client.spots(
        lat,
        lng,
        radius: radius_in_meter,
        types: types,
        fields: 'place_id,name,lat,lng,types,vicinity'
      )

but it seems that Atmosphere Data is still being called.

thehungrycoder commented 2 years ago

+1

We're not using those fields but also getting billed Atmosphere data.

wangela commented 2 years ago

I recommend opening a Support case to investigate your bill. The support team can take a closer look at the SKUs that are being triggered. It may not be this particular request that is calling Atmosphere data and the Support team can look at the quantities of SKU requests to help diagnose this.