|
POST
|
Ah ok Amar I can see it. Probably this is limited to applyEdits. Making an internal issue.
... View more
05-07-2021
03:11 PM
|
1
|
1
|
7633
|
|
POST
|
Great! Thanks for checking back Ryan. We did merge a couple of fixes late in the release, glad to see things are significantly better for you. We have a few additional ideas on further improving ImageryTileLayers performance, hopefully we can start tackling those in the upcoming releases.
... View more
05-07-2021
03:09 PM
|
2
|
0
|
3476
|
|
POST
|
Hi Ryan -- I was looking at this with another dev yesterday, and thanks for bringing this to our attention! We might still be able to get some fixes in for 4.19, and we'll have more for 4.20. There's also potentially some low hanging fruit in terms of optimizations that we can do to improve the frame-rate for these layer types (a huge cost right now is the amount of per-pixel ops that we need to do to prepare the data for these layers) Unfortunately there's not a great way to get notifications, though I can reply to this thread with updates. You can also open a support ticket, and then we can get that mapped to the dev issue.
... View more
04-08-2021
10:21 AM
|
1
|
0
|
3566
|
|
POST
|
Hmm, if you take a look at https://developers.arcgis.com/javascript/latest/sample-code/sandbox/index.html?sample=visualization-dot-density I can see requests being canceled both for VectorTileLayers (the basemap in this case) and FeatureLayers (the dot density layer): If I switch the basemap to an TileLayer (non-vector) I can also see cancellation: For an ImageryTileLayer though I think I see what you are talking about. Some requests do still get cancelled, but it looks like less requests are getting cancelled than should be. Imagery tile layer does a lot of processing on the client and is quite expensive at the moment... I imagine what's happening here is the processing is blocked on something which might be causing requests not to get cancelled when they should. It could also be that the abort controlled isn't hooked up properly for this layer type. I'll make an internal issue to see if we see what's going on here.
... View more
04-07-2021
10:34 AM
|
0
|
2
|
3583
|
|
POST
|
Hi @RyanSutcliffe, are you referring to FeatureLayers? Requests should be getting canceled as you zoom in. If you go from LOD 1 -> 10, you should see 2-9 get canceled in the network tab. What version of the API are you using?
... View more
04-06-2021
04:02 PM
|
0
|
4
|
3596
|
|
POST
|
@wasimraja1if you have a repro I can make sure there are no other issues for your workflow.
... View more
04-02-2021
10:38 AM
|
1
|
0
|
8258
|
|
POST
|
Hi guys - sorry for the lack of reply, my notifications seem to not be working. We installed a fix for applyEdits in 4.19 that should fix both issues with labels not updating & for high-frequency edits (e.g. on cursor move).
... View more
04-02-2021
10:37 AM
|
1
|
2
|
8258
|
|
POST
|
Hi all, The FeatureCollection PBF spec can now be found here: https://github.com/Esri/arcgis-pbf Matt
... View more
03-26-2021
11:30 AM
|
0
|
0
|
3693
|
|
POST
|
Hi Scott, can you try /next (https://github.com/Esri/feedback-js-api-next) and see if that fixes your issue? We made a few changes to the way we handle updates for marker boundaries, which should hopefully help with this. Or if you can provide a repro, I can take a look.
... View more
02-16-2021
02:34 PM
|
0
|
3
|
2006
|
|
POST
|
Sorry @Namibian, I'm just a rendering dev on the JSAPI so I'm probably not the best person to ask about that 😅 Take this with a grain of salt because I'm really not sure about this, and I would definitely reach out to support for questions because they will know this stuff a lot better, but I think you need one of the paid plans (assuming commercial use, see https://developers.arcgis.com/pricing/compare-plans/) and then the credit costs are list here: https://developers.arcgis.com/pricing/credits/. For hosted feature services I would look at https://developers.arcgis.com/features/hosted-data/ (scroll to the bottom to see the pricing chart) From what I understand, you pay for storage, but not for individual feature tile requests. For caching that should be turned on automatically I believe.
... View more
12-10-2020
03:02 PM
|
1
|
0
|
2073
|
|
POST
|
Hi @Namibian! It's definitely on our road-map, but there's still quite a lot of work we need to do on our end to support all of the querying stuff that FeatureLayers are currently capable of for VTL. Probably 4.20-4.21 is the earliest possible release we might see this, but that's not a hard date and it could come significantly later. Parsing the PBF from the VTL may be problematic -- each VectorTile will return quantized data that's generalized for the LOD the tile is for ... so you would need to constantly be adding/removing features as the LOD changes. The performance for this would probably not be great, but may be OK if we are talking low feature counts. The "esri" way of handling this would be to use a FeatureService instead. A hosted feature service would have the best client performance because of the optimizations we do to handle this (esri FeatureTile PBF format, paged queries). We also recently added support for OGC Feature services which is another option. Fairly certain there are several open source service implementation for those. Performance there will be worse (unfortunately support for quantization/generalization/pbf is not yet standardized), but depending on your use case it could be sufficient.
... View more
12-10-2020
11:06 AM
|
1
|
2
|
2075
|
|
POST
|
Sorry for the late reply as well! Seems like I need to re-setup email notifications for the new site. Likely something is getting borked with the tile parsing, and I'll need to debug this to see what's going on... if you can't make the service public (which I get completely), is there any way I could get credentials to access somehow? Otherwise support is another option for this.
... View more
12-10-2020
10:42 AM
|
0
|
0
|
3172
|
|
POST
|
Ah ok great! Yes, one of the advantages of using the hosted services here is the generalization. With this, the service reduces the number of vertices one the line to what you can actually see on the screen at a given scale. This can massively reduce the amount of data the client needs to hold onto at any given point in time, loading the more precise data only when the user zooms in. Also we don't have to store all the data in the service, only the data on screen (and since 4.17 we actually keep the data the service returns to us, which is a pbf-encoded binary payload, in its compressed format always and work on the compressed data directly). Unfortunately with the feature collection, we also have to duplicate how we store the data (for threading). This is because shared memory is a bit of awkward thing in JS -- we use shared array buffers when possible (specifically for processed features we use this to store attribute data), but it's quite hard to share arbitrary json data between threads. And like you mentioned there may also be some real memory issue that was fixed in 4.17, despite there now being some other graphical problem...
... View more
12-04-2020
01:09 PM
|
0
|
0
|
1314
|
|
POST
|
@ChrisShaw if you can you provide a repro on codepen I can take a look. You can also try against /next and see if things are fixed. There were some fixes for clipping on tile boundaries that are in the 4.18 branch: https://github.com/Esri/feedback-js-api-next
... View more
12-04-2020
12:54 PM
|
0
|
0
|
1206
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 07-11-2025 09:45 AM | |
| 2 | 04-25-2025 09:43 AM | |
| 2 | 04-24-2025 03:06 PM | |
| 2 | 03-25-2024 12:13 PM | |
| 1 | 03-08-2024 10:39 AM |
| Online Status |
Offline
|
| Date Last Visited |
3 weeks ago
|