Latest Contributions by Arne_Gelfert

‎06-23-2021

Getting my feet wet with he world of routing. So I started with the simple 3.x example here and wanted to expand on it. I created an item in our Enterprise Portal for the AGOL World Route service and provided my AGOL credentials. Then I plugged the URL for this item into the routeTask definition in the above referenced example, as follows: routeTask = new RouteTask(<my enterprise URL>) When I try to run this, the call ... routetask.solve(routeParams) fails and I see this: error: {code: 404, messageCode: "POR_205244", message: "Your login session has been reset. Please try again.",…} code: 404 details: [] message: "Your login session has been reset. Please try again." messageCode: "POR_205244" Anything I need to change in AGOL or in my Enterprise Portal? Is there another, entirely different, approach to tap into a Routing services besides rolling your own on prem? New territory for me. Appreciate any feedback.

‎06-23-2021

So turns out that the issue was not with refresh() or with creating the uniqueValueRenderer() but I was doing this: // inside foreach loop over mycolors list uniqueValueRenderer.addValue(attr, new SimpleMarkerSymbol().setColor(new Color(mycolor))); when I should have been doing this: // inside foreach loop over mycolors list let rendSymbol = new SimpleFillSymbol(); rendSymbol.setColor(new Color(mycolor)); uniqueValueRenderer.addValue(attr, rendSymbol); Not entirely sure why the latter but the former fails. But I got it working. Now depending on your choice of attribute, we can dynamically create a palette of colors and symbolize map features with the palette.

‎06-11-2021

Likely this is explained somewhere but I can't find it and nothing I've tried seems to work. Working in WAB DE 2.16 with corresponding JSAPI 3.x. The back and forth between the JSAPI documentation and the cryptic jimu pages is killing me. I have a dojo dropdown that allows me to set a filter expression for a particular layer. Depending on the value selected from the dropdown, only features with attribute A matching the dropdown value are shown in the map. Simple enough, right? Now I would also like to color those features based on Attribute B as part of the same dropdown event handler. Value1 = 'red', value2 = 'blue', value3 = 'green'... something like that. I have created a renderer that dynamically creates a list of colors depending on the list of values for Attribute and I seem to be updating the layers renderer. But the change is never reflected in the map. I am doing something like this: var nodeId = 'my_id' var layerStructure = LayerStructure.getInstance(); var myLayer = layerStructure.getNodeById(nodeId); myLayer.renderer = uniqueValueRenderer; I can see in Dev Tools myLayer now has this renderer with the correct number of values. But the map does not update. myLayer.refresh() doesn't work. It says: Not entirely sure what the difference is between the layerNode and layerNode.getLayerObject() but when I try this: myLayer.getLayerObject().then(function(result) { result.renderer = uniqueValueRenderer; console.log(result); result.refresh(); }); there is no error and I also see the renderer when I look at 'result'. But again, the map doesn't update. And how about RendererChooser? Where does that come in? I've looked with no luck for an example of how that's supposed to be used but I can't find one. Is this a features vs. graphics issue? Am I not seeing the trees for the forest?

‎06-10-2021

@Tim_McGinnes - so units and CRS match for view and layers but it turns out that when I use: {... ground : 'world-elevation' ...} in my map definition, I get: [esri.views.3d.layers.ElevationLayerView3D] #resolve() Failed to resolve layer view (layer title: 'Terrain3D', id: 'worldElevation') because that layers has while the scene has: And per ESRI's book of non-no's: A SceneView will only render layers that define a HeightModelInfo with an identical vertCRS to that of the scene, when using an ellipsoidal height model. So thanks for pointing me in the right direction. Not entirely sure where I have to fix this - whether before publishing my service or in the code somewhere - but the fog is lifting for sure.

‎06-10-2021

I thought about the feet/meters thing as well and turns out that my source data actually has Z in meters. But after looking at the documentation again, I realize the "units" parameters in elevationInfo has not effect on Z. I also found that using the offset = -1000 works and forces all lines down by 1000 units. But that's not really what I need. It's as if it's either ignoring or misinterpreting ground. Haven't looked at HeighModelInfo. Not sure I had come across that. So this may help with elevation. Sorry I'm not posting the a whole lot of code here. Still appreciate your feedback.

‎06-08-2021

Thanks, for chiming in, Tim. So, say I have a 3D polyline that starts at XY and has Z = 1000 (as in 1000ft above MSL), and it has an endpoint of XY with Z = -1000, 1000ft below MSL. With the following settings in ArcGIS Pro: This line plots entirely below the surface where elevation is at 1000' MSL. Great. just what I want. After publishing this to ArcGIS Server and adding as FeatureLayer to webmap, I am unable to get it to plot as in Pro. No matter what settings I try in elevationInfo, the feature will always start 1000' above the surface (ground) and extend to 1000' below surface. So everything is relative not to MSL but ground. So maybe I need to define ground differently? I've looked at the documentation and haven't found anything.

‎06-07-2021

@Tim_McGinnesThanks, Tim. Of course, I looked at that page and the observations I made were based on the different value for elevationInfo provided on that page. I've also since played with trying to use expressions but as soon as I do something as simple as : featureExpressionInfo: { expression: "Geometry($feature).z * 2" } the feature appear flat, draped across the ground.

‎06-04-2021

Trying to visualize some subsurface polyline features in 3D. Created a Scene in Pro and published to Portal/Server. Then using JSAPI 4.18 to display. The following plots my polylines. const my3DLinesLayer = new FeatureLayer({ url : 'my 3d URL', elevationInfo : { mode: 'relative-to-scene', }, renderer : myRenderer }); But so do: mode : 'absolute-height' and mode : 'relative-to-ground' What am I missing when it comes to the difference between "relative-to..." and "absolute..."? In each case, my lines plot starting above ground and then continuing into subsurface. Since the line's starting point has a Z > 0, say Z = 1000, it looks like it get plotted starting 1000 units above ground. But the Z = 1000 should really be interpreted as starting at ground where ground = 1000 because these are absolute elevations. So I can understand that 'relative-to-surface' or 'relative-to-ground' would work as described above - we're taking positive values for Z and plotting them above the ground and negative Z below - but why 'absolute-height'? Doesn't the ground elevation layer plot in relation to some approximation of sea level? So if ground is 1000 units above sea level, that's where my line-Z should be? This is what I have in my map right now: const map = new Map({ basemap: "satellite", ground: "world-elevation", fadeOnZoom: true, force3DTransforms: true, navigationMode: "classic" }); Thanks for any suggestions you may have. I'm new to 3D in web mapping, so I may not be missing something obvious. @RalucaNicola - tagging you here since I've seen some great feedback from you in other threads. 😊

‎06-04-2021

So I spent the better part of three weeks trying to dissect this issue with all kinds of help from and reporting back to ESRI. Nothing worked. The code works in 10.6.1 and fails in 10.8.1. Finally, I threw n the towel and upgraded to 10.9 on my GP Server only. I call the GP service on that machine after the upgrade and without any additional configurations, environmental changes or code tweaks it works out of the box. To me that means there is a bug in 10.8.1. Will upgrade to 10.9 and not look back. I used to consider waiting for the Dot-1 a safe practice but these days it feels like that as much stuff breaks in service packs and patches as gets fixed. So why wait!?

‎05-20-2021

Appreciate it, Mattias. Yes, it sounds like our situations are somewhat different. By now, I have a ticket open as well. I have picked my setup apart, and everything is working except the line: layout.exportToPDF( ... ) Layout is fine, so is the path I'm exporting to. But things still bomb. I've ruled all kinds of variations on the publishing and scratchFolder/scratchWorkspace theme. I've seen so many fixes in the Pro/Server release note related to "PDF,export, layout", I'm starting to think there is another one lurking in there ! Stay tuned...

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by Arne_Gelfert

Using AGOL Routing Service in JSAPI 3.x

Re: How do show updated layer renderer in map? (WAB-DE/JSAPI 3.x)

How do show updated layer renderer in map? (WAB-DE/JSAPI 3.x)

Re: JSAPI 4 - 3D Visualization relative to ground/elevation

Re: JSAPI 4 - 3D Visualization relative to ground/elevation

Re: JSAPI 4 - 3D Visualization relative to ground/elevation

Re: JSAPI 4 - 3D Visualization relative to ground/elevation

JSAPI 4 - 3D Visualization relative to ground/elevation

Re: MappingCore.dll Error with ArcGIS Server (10.8.1) GP service

Re: geoprocessing tool fails at 10.8.1, object has no attribute 'scratchFolder'