We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be really great if we could have a static image of a map next to:
EDIT: Not sure if the Google Maps API route is the only way, there might be other ways that don't require money.
We can use this cloud service, but the issue of course is money: https://developers.google.com/maps/documentation/maps-static/usage-and-billing
However, given that there is a real potential for adoption, individual states could potentially be able to fund cloud services like this.
The ask in this issue is to be able to add in the static maps for development testing and have a flag to turn it on or off.
So if we decide we want it, we can turn it on, and add in the appropriate API key.
And if we decide a particular deployment doesn't need it. Then we can leave it off.
The API key for testing and development can be shared privately
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It would be really great if we could have a static image of a map next to:
EDIT: Not sure if the Google Maps API route is the only way, there might be other ways that don't require money.
We can use this cloud service, but the issue of course is money:
https://developers.google.com/maps/documentation/maps-static/usage-and-billing
However, given that there is a real potential for adoption, individual states could potentially be able to fund cloud services like this.
The ask in this issue is to be able to add in the static maps for development testing and have a flag to turn it on or off.
So if we decide we want it, we can turn it on, and add in the appropriate API key.
And if we decide a particular deployment doesn't need it. Then we can leave it off.
The API key for testing and development can be shared privately
The text was updated successfully, but these errors were encountered: