Latest Contributions by Jay_Gregory

Does anyone know if it's possible for the ArcGIS Enterprise Portal application to make server side network requests to data sources of Living Atlas layers (when Portal is configured with Living Atlas subscriber content)?  I assume that a Living Atlas layer in Enterprise, which have internal URLs (i.e. https://portal.domain.com/arcgis/sharing/servers/bd0375ee649b4a06804bd21ccf6c280f/rest/services/LiveFeeds/NOAA_storm_repo… ), will only make client side requests once a user adds the layer to a map, but am curious if there are intermediary requests that Portal might make as well.  For instance, 1. client requests Living Atlas layer from portal.  2. Portal gets layer information like renderer and other basic information from the source 3. Portal returns layer information to the client. 4. Client makes request directly to source for features.  Or something like that.   The reason I'm asking is that there seem to be some network requests from the server hosting Portal to some external resources, and I'm trying to rule out Portal making them.   ... View more

Esri's JS API worked beautifully with VueJS 2.x - however trying to incorporate into a VueJS 3.0 application is proving to be challenging, and I'm wondering if the incompatibilities are irreconcilable without significant changes to the API.  Although I can't know for sure, I think the issue revolves around that Vue3.0 wraps all reactive objects in a JavaScript Proxy object, which allows it to intercept / trap getters and setters.  From Vue's own documentation: The use of Proxy does introduce a new caveat to be aware with: the proxied object is not equal to the original object in terms of identity comparison ( === ). For example:  The original and the wrapped version will behave the same in most cases, but be aware that they will fail operations that rely on strong identity comparisons. Creating a simple map with a feature layer, for example, if the feature layer is a reactive object in the VueJS 3.0 ecosystem, gives some strange errors and requires a workaround.  The following code is using the new Composition API in Vue (that is why I reference everything with the value property but it is the correct programming pattern here), and throws an error at the last line - the layer is never added to the map. To those familiar with the Composition API, using a reactive object (instead of ref like in the code) generates the same issues.  let featurelayer = ref(null) featurelayer.value = new FeatureLayer(url); map.add(featurelayer.value);‍‍‍  Uncaught (in promise) TypeError: 'get' on proxy: property '__accessor__' is a read-only and non-configurable data property on the proxy target but the proxy did not return its actual value (expected '#<a>' but got '[object Object]') However, if I change the last line to  map.add(featurelayer.value.load());‍ The layer is successfully added.  An acceptable but annoying workaround as an application scales.  There are other issues however for which I have been unable to find a workaround.   For example: mapView.whenLayerView(featurelayer.value).then((layerView) => { console.log(layerView); });‍‍‍‍‍‍‍‍‍‍‍‍ throws the following error:  Uncaught (in promise) e {name: "view:no-layerview-for-layer", details: {…}, message: "No layerview has been found for the layer".  Using featurelayer.value.load() or featurelayer.value.createLayerView() does not work.   So ultimately I'm curious if anyone knows what is happening with these seeming incompatibilities, and more specifically, if the Esri JS API team would ever consider making the changes necessary to play well with a (increasing in popularity) framework such as VueJS 3.x. ... View more

I'm having some issues with using tokens I generate from a Python script by hitting a public ArcGIS Server's generateToken endpoint.   Our IT routes traffic in some convoluted ways (which is to say dynamically) such that using a token generated from a generateToken request using 'client':'requestip' in the parameters sometimes will end up with a token denied error.  Basically, if the generateToken request first comes from ip address B, but then the REST request comes from IP address B but uses the token generated from ip address A, I'll get an error.   I'm curious if there is a way around this somehow without going through IT. I'm unclear how I would use 'client':'referer' in the generateToken request, since this is coming from a Python script being run on a server and not a webapp.  Is this even possible?  ... View more