Latest Contributions by AlexGonzalez2

‎04-26-2022

Sure, that makes sense. I feel like it should be documented somewhere in the documentation so that it's more clear to developers on what the expected behavior is. What happened was we upgraded from 100.7 to 100.13 and somewhere along the line that caused an issue to surface where we were converting a point to an small envelope and using that to get intersecting features. What was happening was the query started returning many more features than expected due to the change in spatial relationship on that call. So this caused a bug in our software. We've corrected the issue now. But there was no information conveyed, that I could find, on when or why the changes were made.

‎04-25-2022

Hi Jennifer, I was able to solve the issue by converting my geometry to a point for the time being. But, I did talk to someone named Wesley through chat support and they were able to reproduce the issue and logged it as BUG-000148414. So I have a solution for the time being.

‎04-05-2022

I've run into a strange issue with the use of ServiceFeatureTable.QueryFeaturesAsync() in .Net Runtime 100.13. I currently have some code that looks like this: QueryParameters parameters = new QueryParameters { Geometry = selectionGeometry, SpatialRelationship = SpatialRelationship.Intersects, ReturnGeometry = true, OutSpatialReference = new SpatialReference(102100), MaxAllowableOffset = 0.5 }; return await ServiceFeatureTable.QueryFeaturesAsync(parameters, QueryFeatureFields.LoadAll); And if the selectionGeometry is an envelope the request coming out of the application in Fiddler is changing the spatial relationship in the request to esriSpatialRelEnvelopeIntersects instead of submitting it as esriSpatialRelIntersects. This is causing issues becuase it is returning too many features. This is what the request coming out of the application looks like. (paths omitted due to sensitive data): GET https://portalserver/rest/services/FeatureLayer/MapServer/0/query?f=json&geometry=%7B%22xmin%22%3A-10862928.215694556%2C%22ymin%22%3A6103526.6903118202%2C%22xmax%22%3A-10862918.214113874%2C%22ymax%22%3A6103536.6918925019%7D&geometryType=esriGeometryEnvelope&inSR=3857&maxAllowableOffset=0.5&outFields=%2A&outSR=3857&returnDistinctValues=false&returnGeometry=true&returnM=true&returnZ=true&spatialRel=esriSpatialRelEnvelopeIntersects If I change the query to use PopulateFromServiceAsync like this: return await ServiceFeatureTable.PopulateFromServiceAsync(parameters, false, new List<string> { "*" }); The request that comes across in Fiddler with a SpatialRelationship set to esriSpatialRelIntersects and executes appropriately. This is what that request looks like in Fiddler: GET https://portalserver/rest/services/FeatureLayer/MapServer/0/query?f=json&geometry={%22xmin%22%3A-10862793.19435535%2C%22ymin%22%3A6103651.7100703456%2C%22xmax%22%3A-10862783.192774668%2C%22ymax%22%3A6103661.7116510272}&geometryType=esriGeometryEnvelope&inSR=3857&maxAllowableOffset=0.5&outFields=*&outSR=3857&returnDistinctValues=false&returnGeometry=true&returnM=true&returnZ=true&spatialRel=esriSpatialRelIntersects The issue is the performance of that method is much slower than QueryFeaturesAsync due to skipping the local cache. So I need to be able to use QueryFeaturesAsync. Is there some way I can get QueryFeaturesAsync to request the correct spatial relationship? Or is this a runtime bug?

‎04-08-2021

We would like to move some of our enterprise application work off of the thick client and into services for geometry manipulation and processing. We also would have a use-case for handling geometry operations for incoming flat files that we import from third parties for import into our clients. Loading features from service tables would also be helpful for inspecting and validating data in some of our automated services as well. Geocoding is also another instance we would like to leverage. We also have document generation services that currently export maps via REST export requests we could expand a bit on the functionality in there if we could load feature attributes and shape data. There would also be a use-case for serialization to some of our internal auditing apps when we hit edge cases during data imports and some of the year-to-year rollover processes we use.

‎07-21-2020

This is a custom application that's using the .Net ArcGIS Runtime. We're using the 100.6 WPF SDK and as the MapView requests tiles from the server during the user session the geodatabase temp files are growing quite large. We could attempt to clean all of the temporary files but some of them are still in use by our application. So we're looking for a way to determine which file(s) belong to the map view so we can remove them when the window using the map view closes to free up hard disk space.

‎07-21-2020

I'm currently running into some issues with our Citrix environment where the local temp file geodatabase is consuming a large amount of hard disk space. Some of them are reaching over 1GB in size during a heavy use session. I've opened several of these larger files and they appear to be SQL Lite databases with tiles cached in them. Is there a way to clear out that temporary cache once the window inside of our application that uses it has closed rather than waiting for it to be cleaned up when the application shuts down? I came across the documentation for shutting down the LocalServer. But that doesn't seem to be quite what I'm looking for. Any suggestions would be helpful.

‎04-14-2020

I'm currently having issues with a basic map application and some of our vector tile layers. Our VTL has valid tiles starting at a level of detail of 10 and higher. And when I add the tile layer to the map and zoom in the application is never requesting a tile at a higher level than 9. The code in the window looks like this: Whenever, we zoom into a scale where the layer would be visible the application is only requesting a tile with a level of detail of 8 or 9. The layer starts at a level of detail of 10. Here is the fiddler log: You'll notice that there are no requests at a higher LOD than 8 in the logs. Does anyone know why the map is not requesting tiles at a higher level of detail that would allow them to become visible?

‎11-07-2018

I'm currently working on a WPF application using the map view and we're seeing the same error. Were you able to solve this one? Here's our stack trace: DirectX failure CreateQuery code = 0x887a0005: c:\daily_r\rtc\runtimecore\c_api\src\mapping\map_view\geo_view.cpp(203) : error : Exception caught in RT_GeoView_pulse at Esri.ArcGISRuntime.ArcGISException.HandleCoreError(CoreError error, Boolean throwException) at RuntimeCoreNet.GeneratedWrappers.Interop.CheckError(IntPtr errorHandle, Boolean throwOnFailure, GCHandle wrapperHandle) at RuntimeCoreNet.GeneratedWrappers.CoreGeoView.Pulse() at Esri.ArcGISRuntime.UI.Controls.GeoView.Esri.ArcGISRuntime.Internal.IDxSurfaceSource.Pulse() at Esri.ArcGISRuntime.Internal.HostedSurfaceElement.CompositionTarget_Rendering(Object sender, EventArgs e) at System.Windows.WeakEventManager.ListenerList`1.DeliverEvent(Object sender, EventArgs e, Type managerType) at System.Windows.WeakEventManager.DeliverEvent(Object sender, EventArgs args) at Esri.ArcGISRuntime.Internal.RenderingWeakEventManager.OnCompositeTargetRendering(Object sender, EventArgs e) at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget) at System.Windows.Media.MediaContext.AnimatedRenderMessageHandler(Object resizedCompositionTarget) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam) at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg) at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame) at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame) at Esri.ArcGISRuntime.Internal.HostedSurfaceElement.SurfaceBackgroundUiWorker(Object arg) at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart(Object obj)

Online Status	Offline
Date Last Visited	‎10-26-2022 09:50 PM

My Ideas

Latest Contributions by AlexGonzalez2

Re: ServiceFeatureTable.QueryFeatureAsync changing the Spatial Relationship on the query parameters when requesting features from the service

Re: ServiceFeatureTable.QueryFeatureAsync changing the Spatial Relationship on the query parameters when requesting features from the service

ServiceFeatureTable.QueryFeatureAsync changing the Spatial Relationship on the query parameters when requesting features from the service

Re: Runtime in services functionality

Re: Cleaning up temporary Geodatabase files

Cleaning up temporary Geodatabase files

MapView is not requesting vector tiles with a level of detail higher than 9

Re: Map crash runtime .Net 100.3