Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Map.getStreetView() now incurs a usage cost #159

Open
soames-sparks opened this issue Sep 10, 2018 · 1 comment
Open

Map.getStreetView() now incurs a usage cost #159

soames-sparks opened this issue Sep 10, 2018 · 1 comment
Assignees

Comments

@soames-sparks
Copy link

soames-sparks commented Sep 10, 2018

Not so much a code issue, but more of a usage issue/caveat. The OverlappingMarkerSpiderfier script calls the Map.getStreetView() method (specifically to ensure markers are not spiderfied in street view), with which Google's new pricing schedule may incur a charge where it would not have done so previously.

See:
https://developers.google.com/maps/billing/understanding-cost-of-use#dynamic-street-view

In JavaScript, with the google.maps.StreetViewPanorama() class or Map.getStreetView() method (prior to the new pricing, Map.getStreetView() was not charged). Usage of the StreetViewService() class is not charged.

I haven't checked to see if there's any other quick way to determine whether StreetView is being used without calling getStreetView(), but unless you're specifically using street view (the control is disabled in our case) it should suffice simply to remove the this.map.getStreetView().getVisible() condition.

@jawj
Copy link
Owner

jawj commented Sep 10, 2018

Huh — interesting. As an interim fix I should maybe put the Street View check behind a constructor option.

@jawj jawj self-assigned this Sep 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants