-
Notifications
You must be signed in to change notification settings - Fork 27
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
getting Nexzen api key error for tiles while using an api key #760
Comments
Thanks, will check it out. Likely a result of the latest changes from
Mapzen -> Nextzen keys.
…On Thu, Mar 8, 2018 at 4:26 PM, Garret ***@***.***> wrote:
Hi
Im getting this error even though Im using the Nextzen api key.
[image: untitled]
<https://user-images.githubusercontent.com/556205/37177023-c37f9c94-22e3-11e8-849f-0e0a590a113c.jpg>
Im using tangram-play locally. This is a newer error since my last git
pull.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#760>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABBXY9LH2nPoi3GmIunqZpQVWmfqaG3ks5tcaHrgaJpZM4SjXxJ>
.
|
Could you show what your |
Try removing the `?api_key=XXXXXXX` from your tile url, and providing your
API key as:
```
mapzen:
type: MVT
url: ...
url_params:
api_key: <your Nextzen api key here>
```
Does that work?
…On Mon, Mar 12, 2018 at 12:53 PM, Garret ***@***.***> wrote:
Sure! Here you go:
[image: untitled]
<https://user-images.githubusercontent.com/556205/37297545-f4dbbff6-25eb-11e8-994f-075c9bf139d0.png>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#760 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABBXYA8IWh5GRDkaP2neBNFIerlbeAIks5tdqgbgaJpZM4SjXxJ>
.
|
Doesn't seem to have an affect. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
Im getting this error even though Im using the Nextzen api key.
Im using tangram-play locally. This is a newer error since my last git pull.
The text was updated successfully, but these errors were encountered: