Latest Contributions by JohnGravois

the easiest thing to do would just be to listen for the 'click' event of your featureLayer and use that opportunity to retrieve its bounds and pass them to the map. featureLayer.on('click', function(evt) {     // http://leafletjs.com/reference.html#featuregroup-getbounds     var bounds = evt.layer.getBounds()     // http://leafletjs.com/reference.html#map-fitbounds     map.fitBounds(bounds); }); this is possible because 'L.esri.FeatureLayer' extends 'L.geoJson' and 'L.geoJson' extends 'L.featureGroup', which has a method 'getBounds()'.  you can find a working example here. between all the inheritance and the fact that the documentation for Esri Leaflet and Leaflet itself are in two different places, stuff like this can be confusing until you get the hang of it. ... View more

Esri Leaflet only falls back onto JSONP when POSTing from a client browser that doesn't support CORS.  if you'd like to trick our plugin into thinking that the end users browser doesn't support CORS, you can call... L.esri.Support.cors = false; Afterward, when calling L.esri.request(), JSONP will be used if its necessary to POST. // to send a single JSONP ajax request L.esri.request('http://sampleserver6.arcgisonline.com/arcgis/rest/services/', {   fakeParam: 'value that will push the request length past 2000 characters' }, function (error, response) {   if (error) {     console.log(error)   } else {     console.log(response)   } }) If you need to POST across domains, please remember that it will be necessary to invoke a proxy. we'll be updating the API reference soon, so i'll make sure the new information pertaining to L.esri.request() is as clear as possible. ... View more

as explained in the esri-leaflet 1.0.0 release notes, we introduced the breaking change that tasks and layers constructors now expect the url of the corresponding resource to be provided within an options object L.esri.Tasks.query(yourUrl) // becomes L.esri.Tasks.query({ url: yourUrl }) the API reference for L.esri.Tasks.query reflects this change as well. you can find information about an equivalent change in the release notes for esri-leaflet-related 0.0.1-beta.2. ... View more

yeah, sorry about all the confusion.  i know exactly whats going on. i am in the middle of making some fairly broad sweeping changes to the website and the master branch is currently expecting that you'll insert your own build of the compiled source in order to run the site locally. you have two options: 1. make the same changes in the commit below locally to ensure that you are pointing at the CDN instead. start using esri leaflet cdn · Esri/esri-leaflet@dc3b1c0 · GitHub 2. place your own new build inside site/build/js/ the tl;dr is that now we are using grunt only for building/running the documentation site.  in order to compile the source code locally, all you need to do is call 'npm run build'. i expect thats clear as mud.  let me know if you have any other questions. ... View more