Latest Contributions by JohnGravois

‎08-09-2017

happy to look at a simplified repro case if you can log a new issue in the esri-leaflet-vector github repo. i don't see any problems with popups when using L.esri.featureLayer http://jsbin.com/pudiyih/edit?html,output

‎08-09-2017

> Any tips on how I could speed things up in the sample? i wish i did. i've noticed startup times that are slower than i'd expect with esri vector tile sources before and i don't know what causes it. and the 300kb wrapped plugin certainly helping.

‎08-09-2017

you're in luck. that great sample is plug and play in Leaflet 1.x by making one small tweak // line 1 of leaflet.points-layer.js L.PointsLayer = L.Layer.extend({ // instead of L.Class includes: L.Evented.prototype, // instead of L.Mixin.Events

‎08-04-2017

all that said, i'd highly recommend you consider using the functionality we built into esri leaflet for this, as it makes it substantially more straightforward to ensure the appropriate request is made. L.esri.FeatureLayer | Esri Leaflet map.on("click", function (evt) { // http://leafletjs.com/reference-1.1.0.html#marker-togeojson let newFeature = L.marker(evt.latlng).toGeoJSON(); newFeature.properties.inspector = 'john'; myFeatureLayer.addFeature(newFeature, function (err, response) { console.log(response); }); }); ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ http://jsbin.com/kufesac/edit?html,output

‎08-04-2017

i noticed a few unexplainable errors with that sample server too, so i found a different test server to play with. there are several problems with your approach: 1. "type" : "Point" is not valid to include within a JSON geometry object 2. you forgot to remove a trailing comma from your "attributes" object 3. you absolutely must provide a spatial reference object to let the service know you are passing lat/long coordinates when the service itself stores its data in a different CRS. { "x" : -118.15, "y" : 33.80, "spatialReference" : { "wkid" : 4326 }} 4. i don't know why, but in my own testing i encountered more predictable, appropriate responses when i used the generic "/applyEdits" operation than when i made requests to "/addFeatures" http://jsbin.com/lafarap/edit?html,output edit: i tested a bit more and realized the only reason i was having trouble with /addFeatures was because i was using it to try and add geometries that were way outside the source extent of the original data. both endpoints are consistent, as they should be.

‎08-02-2017

please share a small reproducible test case with the bare minimum of code necessary to demonstrate the problem. i'd be happy to take a look at it and help. you're welcome to use this demo feature service if yours isn't publicly accessible.

‎07-28-2017

i forgot to thank @strajuser for creating (and sharing) TypeScript typings on DefinitelyTyped!

‎07-28-2017

Yesterday we released Esri Leaflet v2.1.0. If you've been keeping up with current events you're aware that Leaflet itself recently released v1.1.0. These two pair nicely together, but our previous release was compatible with Leaflet v1.1.0 too. To make a long story long, the Leaflet maintainers latest release is a refactor of their raw source into ES6 modules. Our own Patrick Arlt, trailblazer that he is, helped with the initial research (and migrated our own plugin codebase) way back in 2015. On the other hand, our new release is pure features (and a few bug fixes) and includes four different contributions from userland: @Saulzi introduced error handling for DynamicMapLayer and ImageMapLayer (courtesy of another patch he made in Leaflet core) Thanks to @scaddenp its now possible to use DynamicMapLayer in maps with polar projections. A contribution from @bbehling means that you can now pass input geometry types other than points when identifying features. @jordanparfitt patched a bug that caused problems when setting definition expressions on layers that aren't currently being displayed. We also ported a couple new features from ArcGIS Server 10.5, including adding the ability to retrieve raw unformatted features from Find and Identify and making sure you can apply a datum transformation when calling Query. You can find information in the v2.1.0 changelog. If you're interested in learning more JavaScript and getting involved, feel free to reach out to us on GitHub or in the #leafletjs or #arcgis-web channels in The Spatial Community. We're looking forward to seeing what you build with it!

‎07-28-2017

after downloading and unzipping your sample and commenting out the <link> tags to .css files that weren't available, <script> tag for the TOC widget that was unavailable and references to the widget within the actual JavaScript i was finally able to get it to run locally and was not able to reproduce the error you describe. each time i clicked on the map, a single address and lat/long coordinate pair were displayed. when creating future posts, please consider using something like jsbin/codepen or jsfiddle to share your simplified reproducible test case so that folks can dedicate more time to debugging and less to set up.

‎06-18-2017

i'm a bit out of my depth here, but internal research has pointed me to something that seems relevant. "WebContextURL" in the ArcGIS Server Admin API should allow for forcing href urls to match whatever is specified there. One caveat is that the server will apply the webContextUrl only if it determines the request to be made via a proxy since such requests have X-FORWARDED-FOR or X-FORWARDED-HOST request headers. In one case I found, a customer decided to bypass their web adaptor entirely and point a load balancer directly at the GIS Server on port 6080 to resolve the problem. to be frank, ArcGIS Server architectures can get pretty gnarly and I'm just pointing you at a little doc and regurgitating internal notes. i'd highly recommend logging your own support call and referencing the rejected bug NIM091395 in order to receive assistance from someone on our team in diagnosing where your own problem lies.

‎06-12-2017

sorry about that. i forgot that specifying a proxy overrides that option... https://github.com/Esri/esri-leaflet/blob/v1.0.5/src/Layers/DynamicMapLayer.js#L17 why exactly are you proxying a service thats visible publicly? is this just a repro case to demonstrate the problem you're seeing with a different secure service?

‎06-12-2017

what happens exactly when you set f:'image' in the dynamicMapLayer constructor? either way I'll reach out to a few other Esri folks to see if they can help us configure the service to return https urls

‎06-11-2017

neither esri leaflet, the proxy, nor the JSONP callback parameter are the cause of the problem you're seeing. https://argis.ualr.edu/arcgis/rest/services/DF/MapServer/export?bbox=-10865064.948568093%2C3830412.361426751%2C-9690992.… as i mentioned in the issue below (which you already replied to), some misconfiguration of ArcGIS Server is causing it to return `https` urls in its map service export operation JSON payloads instead of preserving the protocol of the initial request. https://github.com/Esri/esri-leaflet/issues/955#issuecomment-307445374 were you able to workaround the problem by asking for a raw image?

‎05-30-2017

If you append "Loc_name" as an additional outField in your requests you'll see which specific locators are producing the match. Its just my two cents, but I don't think its appropriate to expect matches produced by IND.Postal or Gaz.WorldGazetteer.POI1 locators to always include values for City or Region. For example, postal codes don't have a 1:1 correspondence with administrative boundaries.

‎05-25-2017

if/when they migrate Shiny to utilize Leaflet 1.x, i'd be willing to take a shot at proposing a formal integration https://github.com/rstudio/leaflet/issues/357 in the meantime, you could try the technique described here.

Online Status	Offline
Date Last Visited	‎11-11-2020 02:22 AM

My Ideas

Latest Contributions by JohnGravois

Re: Trouble vector basemap with d3 sample

Re: Trouble vector basemap with d3 sample

Re: Trouble vector basemap with d3 sample

Re: Having trouble adding a feature to a feature service through leaflet.

Re: Having trouble adding a feature to a feature service through leaflet.

Re: Having trouble adding a feature to a feature service through leaflet.

Re: Esri Leaflet v2.1.0!

Esri Leaflet v2.1.0!

Re: Multiple layers info in one popup window

Re: Esri leaflet callback returns http not https

Re: Esri leaflet callback returns http not https

Re: Esri leaflet callback returns http not https

Re: Esri leaflet callback returns http not https

Re: Single line and multiline search with FindAddressCandidates doesn’t populate city, region in many cases.

Re: Integrate AGOL with Shiny

Re: Get the outFields of a selected polygon in a f...

Re: Proxy setting - Unable to Load - Status 403

Re: Adding Secured Service Error

Re: Adding administrative layer to Oceans basemap ...

Re: Adding administrative layer to Oceans basemap ...