nwehner
commented
6 years ago Hey all,
I have a Mapbox account already and apparently I have both the Moore Foundation high-zoom and low-zoom tilesets saved therein.
Here’s my public token: pk.eyJ1IjoibndlaG5lciIsImEiOiJFczJwTmhJIn0.WMMEvcVfAsPS6SJV9GlVqA
Let me know if there’s anything else you need.
Cheers! -Nick
Nick Wehner Director of Open Initiatives OCTO | Open Communications for The Ocean https://www.octogroup.org | https://www.openchannels.org | https://marxiv.org nick@octogroup.org | nwehner@protonmail.com Office: +1-206-420-1175 Signal: +1-206-745-2138 Learn about the importance of making your research freely-available with MarXiv from Oceans Deeply: https://oct.to/marxivod
On Feb 27, 2018, at 3:25 PM, Alan McConchie notifications@github.com wrote:
I've been doing an audit of the Mapbox traffic on Stamen's Mapbox account, and it looks like the oceanplanning tiles still live on Stamen's account. The traffic is very small, but at some point we should move these to a separate Mapbox account administered by @nwehner https://github.com/nwehner or whoever is still handling this project. (hi!)
I'm also surprised that we're still using v3 of the Mapbox API, which could stop working at any time. Mapbox wants everyone to move over to v4 of the API which requires us to specify an API key.
https://www.mapbox.com/help/blank-tiles/#youre-using-v3-of-the-mapbox-maps-api https://www.mapbox.com/help/blank-tiles/#youre-using-v3-of-the-mapbox-maps-api Note that the only reason I started doing this audit is because we're going to need to disable our current Stamen API key and replace it with a new one. Because oceanplanning.org uses the v3 API which doesn't require a key, I figure nothing will change when I revoke our existing API key, but it's possible that would make the v3 requests stop working.
It looks like the site is still running on github pages, so I think that means it will be easy to make this change (as opposed to having to redeploy this code somewhere else).
@nwehner https://github.com/nwehner do you mind creating a Mapbox account for oceanplanning.org, so we can start the process of moving stuff over to you? I'm pretty sure that the level of traffic you have will qualify for the free tier on Mapbox.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/oceanplanning/oceanplanning.org/issues/4, or mute the thread https://github.com/notifications/unsubscribe-auth/AEBZMWk7KhxfHS-QpJ6vGykh93_Cn3FWks5tZI7lgaJpZM4SV0TN.
I've been doing an audit of the Mapbox traffic on Stamen's Mapbox account, and it looks like the oceanplanning tiles still live on Stamen's account. The traffic is very small, but at some point we should move these to a separate Mapbox account administered by @nwehner or whoever is still handling this project. (hi!)
I'm also surprised that we're still using v3 of the Mapbox API, which could stop working at any time. Mapbox wants everyone to move over to v4 of the API which requires us to specify an API key.
https://www.mapbox.com/help/blank-tiles/#youre-using-v3-of-the-mapbox-maps-api
Note that the only reason I started doing this audit is because we're going to need to disable our current Stamen API key and replace it with a new one. Because oceanplanning.org uses the v3 API which doesn't require a key, I figure nothing will change when I revoke our existing API key, but it's possible that would make the v3 requests stop working.
It looks like the site is still running on github pages, so I think that means it will be easy to make this change (as opposed to having to redeploy this code somewhere else).
@nwehner do you mind creating a Mapbox account for oceanplanning.org, so we can start the process of moving stuff over to you? I'm pretty sure that the level of traffic you have will qualify for the free tier on Mapbox.