Latest Contributions by mgeorge

Andrew Murdoch‌ do you see any adverse affects in your apps when you see the above error (i.e., the "infinite-loop" bug in the OP), or just the error?  Likely this is a race that has to do with a layer being added/removed very quickly (probably with 100 ms of being added). When you create a FeatureLayer, that spins up a connection to a worker which communicate over a message port. The error "Can't invoke, port is closed" coming from the AttributeStore means that while the worker was trying to setup the shared memory region (which happens immediately when the connection is established), the connection was closed. We can potentially move this error behind a flag, as this likely shouldn't have any adverse consequences.  Does this sound about right for your case? Does your app add/remove a layer very quickly?  ... View more

Thanks Andrew Murdoch‌, I'll be looking out for this as well.  ... View more

Strange. I actually use Linux + chrome for my daily driver but have not yet seen this -- if you are able to provide me a repro I can take a look at this personally. The error is related to setting up the shared memory region that eventually gets pushed to the GPU (via a texture) to pass per-feature information (visual variables, filter states, etc). Does this happen when loading? ... View more

Hi all, Sorry for the lack of response on this. If you are experiencing this issue, are you able to provide a link to a repro on codepen? Are you seeing this in IE only or in other browsers? ... View more

Hi all,  Sorry for the lack of information on this, things are a bit hectic with UC. I'll follow-up internally.  Matt ... View more

Hi Sang Hyouk Oum‌ Thanks for bringing this to our attention. Definitely the underlying engine should be able to handle more than this number of points, I'll take a look and see what's going on. ... View more

Hi Eric, There is no per-labelClass priority at the moment. Likely whatever comes first would drive the priority, and that depends loosely on how the data is loaded, spatially indexed, and patched to the individual tiles. There is per-layer priority, with labels from top labels take precedence over those in the lower lays. Matt ... View more

Thanks Eric. We don't have a time frame for this yet, but I would probably guess in 2-3 releases. Will likely depend on how much feedback we get concerning this. Matt ... View more

Hi Eric Rydgren‌, Yes I don't think we yet have a great way of doing what you are asking for, however I have heard a request for something similar from other users in the past. Can you give us a few more details? - Would supporting a LabelClass.priority property be enough to fit your use case? - Do you only want to pin a specific feature's label? - Do you want the priority to differ between features of a given labelClass? (make it attribute-driven) Matt ... View more

Hi Ashraf Elhakim‌, This is a known issue and something we're working on as part of our ongoing effort to expand CIM support (in fact just yesterday I was looking at a prototype for CIM arrows). Once that work is done, we'll be able to bring back that line symbol property, which under the hood will use the new CIM rendering logic. We don't yet want to commit to a time table for this, but it is in active development. Matt ... View more

Hi John. Sorry for the confusion -- yes, cluster labeling is definitely planned, and it will likely arrive before cluster queries. Currently it's not in the plan for the MapViewer yet because it's not in the API, but once it lands in the API I imagine it would come very quickly to the MapViewer. (I'll double check with the MapViewer team on this) Main difficulty here is that we need to both persist this information (webmap spec change), and we're thinking we might want to provide the ability to not just label counts, but label other aggregate info (e.g., maybe instead of counts you clusters representing temperature observations and want to label the average temperate). That second part involves adding an API to specify how input fields can map to statistic fields (internally the engine logic to handle this is pretty much done).  If we go with more extensive labeling, clusters should be able to support the full LabelClass API. Otherwise we might expose this as some kind of `showClusterCounts` property on the featureReduction instead. If we do decide to go with the full `featureReduction.labelingInfo` approach, we may be able to get this out before we have the full statistic fields logic as that way it could still be used with the implicit `CLUSTER_COUNT` field.  Really trying to get this in (in at least some form) for 4.15 or 4.16. So far in the 4.15 cycle we've been working on a very large internal refactor of the way labeling is handled to make way for this.  ... View more

While Robert Scheitlin, GISP‌ is right that we don't yet have a stable way of handling composite symbology in the JSAPI yet, we do have beta CIM support which I think should allow you to achieve what you are looking for. You could also go the FeatureColletion + label route if you want deconfliction (adding support for an option to disable label deconfliction is in the works).  I would take a look at CIMSymbol | ArcGIS API for JavaScript 4.14  ... View more

Very, very soon (you should hear more in the next few days). Beta clustering will be added in 4.14, but we won't have cluster labeling initially. Right now we're thinking either 4.15/4.16 (can't guarantee this) depending on how other issues get prioritized. Once clustering does land, there are a few more areas specific to clustering that we need to work on before labeling, including adding some basic querying capability for the clusters, as well as supporting arcade. We'd also like to improve some of the rendering quality as well (have better transitions when zooming in), but that would likely happen after we have all of this functionality in place.  ... View more

Thanks for the response! We're marking these versions down internally as known bad drivers for the Intel HD 630.  ... View more

Roman König‌ Matthieu Thery‌ I just got access to a device with an Intel HD 630, but unfortunately I'm not able to reproduce the issue. Can you try updating your Intel display drivers? Seems like this could be a driver bug that is fixed with the newer drivers (my machine has driver 26.20.100.6951). Looks like the machines where we are seeing this problem have version 22.20.16.4836 or 23.20.16.4973. ... View more