Hi, I'm trying to refresh a featureLayer in Esri Leaflet 3.0.3 (but this also happens in previous versions) that calls an AGOL FeatureServer service, with the refresh() method and setInterval, but it does not work as expected. The implementation is very simple: var testIcons = { 'A': L.icon({ iconUrl: 'A.png', iconSize: [35, 35], iconAnchor: [6, 6], popupAnchor: [-3, -5], }), 'B': L.icon({ iconUrl: 'B.png', iconSize: [35, 35], iconAnchor: [6, 6], popupAnchor: [-3, -5], }), }; var testLayer = L.esri.featureLayer({ url: 'https://services5.arcgis.com/xyz/ArcGIS/rest/services/NAME/FeatureServer/0', pointToLayer: function (geojson, latlng) { return L.marker(latlng, { icon: testIcons[geojson.properties.Status] }); } }).addTo(map); testLayer.bindPopup(function (layer) { return L.Util.template(' Name: {Name} Status: {Status}', layer.feature.properties); }); setInterval(function() { testLayer.refresh(); }, 120000);//2min Looking at the browser console, the layer refreshes at the given interval, but it loads the same data again. Sometimes, after a long period with the same data on map, it changes, but very outdated when compared with the service. I've some other layers working fine and configured exactly the same way, but they are MapServer services. So, my question is, refresh() method does not work well with FeatureServer services in featureLayers? The implementation needs to be different than with MapServer services? Or this should work and it can be a bug? Thank you very much!

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Esri Leaflet refresh() method not working

PedroVenancio

Hi,

I'm trying to refresh a featureLayer in Esri Leaflet 3.0.3 (but this also happens in previous versions) that calls an AGOL FeatureServer service, with the refresh() method and setInterval, but it does not work as expected.

The implementation is very simple:

var testIcons = {
    'A': L.icon({
    iconUrl: 'A.png',
    iconSize:     [35, 35],
    iconAnchor:   [6, 6],
    popupAnchor:  [-3, -5],
    }),
    'B': L.icon({
    iconUrl: 'B.png',
    iconSize:     [35, 35],
    iconAnchor:   [6, 6],
    popupAnchor:  [-3, -5],
    }),
};

var testLayer = L.esri.featureLayer({
    url: 'https://services5.arcgis.com/xyz/ArcGIS/rest/services/NAME/FeatureServer/0',
    pointToLayer: function (geojson, latlng) {
      return L.marker(latlng, {
        icon: testIcons[geojson.properties.Status]
      });
    }
  }).addTo(map);
  testLayer.bindPopup(function (layer) {
    return L.Util.template('<b>Name:</b> {Name}</br><b>Status:</b> {Status}', layer.feature.properties);
  });

setInterval(function() {
    testLayer.refresh();
}, 120000);//2min

Looking at the browser console, the layer refreshes at the given interval, but it loads the same data again. Sometimes, after a long period with the same data on map, it changes, but very outdated when compared with the service.

I've some other layers working fine and configured exactly the same way, but they are MapServer services.

So, my question is, refresh() method does not work well with FeatureServer services in featureLayers? The implementation needs to be different than with MapServer services? Or this should work and it can be a bug?

Thank you very much!

Encuentra más publicaciones etiquetadas con

Esri Leaflet

Accepted answers

Anonymous User

Thanks for the clarifying info! We may have a fix brewing and ready soon. Look for an update early in the week. https://github.com/Esri/esri-leaflet/pull/1304

All comments

Anonymous User

Thanks for the clarifying info! We may have a fix brewing and ready soon. Look for an update early in the week. https://github.com/Esri/esri-leaflet/pull/1304

PedroVenancio

Hi @Anonymous User

Thanks again for taking a look on this!

There are just attribute and geometry updates. For instance, a new point is added with it's attributes, then it is regularly updated until it is deleted / hidded (in this case I don't know if it's permanently deleted or just hidded). Anyway, once a new point is added, at least the "EstadoAgrupado" field evolves from "Em Curso", to "Em Resolução" and finally to "Em Conclusão". The point position can also change slightly in the process.

The FeatureServer layer exists and is static, what changes is the content, both geometries and attributes.

Thanks!

Anonymous User

Hi Pedro,

We began doing more investigation on our side and trying out manual edits and the refresh() method, and I've a follow up question for you.

Is the point feature in question on your FeatureServer layer being added and deleted, or is it being updated with new attributes and/or geometry?

Thanks

PedroVenancio

Hi @Anonymous User

Any update on this issue? Can I provide any other information?

Thank you very much! Best regards!

PedroVenancio

Hi @Anonymous User

Thank you very much for taking a look at this!

This service represent real incidents going on, and so, they are always changing randomly. First they appear with a status of "Em Curso" = "Open"; then they change to "Em Resolução" = "In resolution"; then they change to "Em Conclusão" = "In conclusion"; and finally they disappear from the map/service.

What I see with these FeatureServer services in featureLayers, is that they do not update with refresh(), and they only are updated with complete reload of the browser, that is what you are seeing when you completely refresh the codepen. The service itself is being updated in background, but refresh() does not push these updates to the map until the entire application is reloaded.

You can check the updated service at: http://bit.do/fSDPq

Just make "Query" and compare with the codepen map without reload the entire app. The fied "EstadoAgrupado" is the "Status" in codepen.

Thanks again!

Anonymous User

Pedro,

I spent some more time with this and I am indeed seeing odd behavior when calling refresh() or at different zoom levels (sometimes it doesn't show up), or when completely refreshing the codepen (I see an entirely different feature point on the map in a new location).

We will continue investigating.

Anonymous User

Hi Pedro,

Thank you for creating this, it is very helpful! I'm not familiar with the data in your FeatureServer/0 layer, so it is difficult for me to know what to look for in the source data versus what esri-leaflet is showing on the map.

Here are some things I want to highlight from your codepen sample.

I changed your 1min interval to a map click handler to call refresh() on the layer, just for my convenience.
In the developer network tools for your feature service layer, we are checking and comparing the GET request headers to see what parameters were sent to the query endpoint. In this case, for a single refresh(), 4 unique requests were sent (using automated "tiling" logic).

In the developer network tools for your feature service layer, we are checking and comparing the GET response headers to see what the feature service layer is returning. In one of the 4 responses, I routinely see 1 feature come back.
Here I am unsure how long I have to wait for the data to change what specifically about the data changes:
- different features?
- different geometry?
- different attributes?

Can you please try to recreate such a situation where you can see "before and after" network traffic that shows the data changes from the server, and compared with what is incorrectly shown on the Leaflet map?

Thanks

PedroVenancio

Hi again,

Since FeatureLayer's refresh() calls the layer's setWhere(), I configured a query to filter features of the layer, and this way try to force the "refresh" at least when the filters are applied (https://codepen.io/PedroNGV/pen/rNzoQeE?editors=1111). However, it does not refresh features at all, they still appears the same, returning to show all. So, filters are applied to the features loaded, and do not refresh the layer.

To check the updated service: http://bit.do/fSDPq

Can this be some kind of a bug?

Thanks!

PedroVenancio

Hi @Anonymous User

Here is a working demo: https://codepen.io/PedroNGV/pen/rNzoQeE

I set the refresh to run every minute, but it does not refresh. You can see the difference comparing to when the page is reloaded (simply add a space in HTML code). Only when the layer is reloaded, the data is updated. Refresh does not take effect. Just wait about 30 minutes, to be sure the underlaying data is updated, and add a space. Or make a query directly in the service, to check when it is updated.

As I said before, you will notice that sometimes, after a long period with the same data on map, it changes some point(s), but very outdated when compared with the service and somehow randomly.

I don't see this when using MapServer services, that refresh as expected.

Thanks for taking a look at this!

Anonymous User

Hi @PedroVenancio, can you expand your code snippet into a public demo we can use to help investigate?

Checking our API docs, indeed the FeatureLayer's refresh() is described as "Redraws all features from the feature layer that exist on the map."

The source code in turn appears to call the layer's setWhere(). I think we'd have to use your reproduction demo case and step through and take a closer look.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.