After trying turf.js with plain ole leaflet and getting confused because the most basic stuff wouldn't work, I'm thinking that turf.js requires Mapbox.js and access token. Can anyone confirm or deny this??

If this is the case, I have either totally overlooked it on the turf github and the turf API site, or that information is nowhere to be found, which is kind of annoying.

  • For what I know...this should not require Mapbox.js nor the token. I'm interested in also knowing this. If it depends on Mapbox infrastructure...well. – George Silva Feb 19 '15 at 17:43
  • I wouldn't think so either... I've got to look in to it more. – Tangnar Feb 19 '15 at 18:10
  • We're happy to help with any turf-related questions on the issue tracker if you can provide code examples of what's not working with Leaflet. – tmcw Mar 1 '15 at 23:39

Turf.js is not dependent on Mapbox.js or access token. I was initially confused with the documentation, I think, but it works fine with plain leaflet.js.


Turf has no visualization dependencies at all. It does not require any map display, and works with raw GeoJSON data. For example, I often use Turf on my desktop (via Node.js) for running analysis that outputs the results to files I open in QGIS. The code runs 100% on your machine, so there are no access tokens or servers involved anywhere in the process.


Turf.js does not require Mapbox map or Mapbox access token. It can be intergrated well with leaflet, which I have tried and it worked. Also it can be integrated with ArcGIS JS API too.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.