Latest Contributions by JoseBanuelos

‎07-23-2021

Hello @SS12 , This just looks like a simple service max request configuration on your server endpoint. By default 2000 is the limit of max features you can return on a query to a service published to ArcGIS Online. The following is a knowledge article on how you can update this to a larger number: https://support.esri.com/en/technical-article/000012383 If you have an ArcGIS Enterprise setup the workflow would be to go to Server Manager and update the properties on the service. Thanks, Jose

‎07-23-2021

Hello Keith, @kgcroteau You are welcome, and yes please take a look at maybe republishing the service. I went back and ran some testing on our test services and I was able to start snapping immediately with millions of features on a service that eventually timed out on the full extent request. Therefore, that request never completed and snapping was still possible immediately. If republishing still doesn't resolve this, we can take our conversation via direct message on Esri Community, so I can maybe take a note of some of your service configurations. Lastly, I setup a test sample you can use in your testing with over 1 million features. Its hosted on ArcGIS Online so its a different implementation, but in case you want to use it as a reference when testing, this would be a good example: https://codepen.io/banuelosj/pen/zYwPwVN Thanks, Jose

‎07-22-2021

Hello Keith, @kgcroteau In version 4.20, we removed the requirement to wait for the extent to complete before we can start snapping. It is strange to see that it looks like your service is still being affected. Especially with less than 200,000 features. Are these features polylines, polygons, or points? Do you have other services experiencing this same issue? Just to double-check. Are you currently using version 4.20, and does the layer finish drawing before you attempt to start snapping? The server we tested with the service provided in the original post was a 10.6.1 service with nearly 4 million polygons. Thanks, Jose

‎07-19-2021

Hello @VigneshSuresh , Thanks for your question. You are running into a known issue with 2D Sketch. At the moment, it is not possible to utilize the Sketch widget with geometries containing a different spatial reference than the view's spatial reference. This means taking advantage of the selection tools and the graphic resizing and transforming tools that come with the Sketch widget. The geometries in your code use wkid: 4326, but the view's spatialReference is wkid: 102100. You can test this by removing the basemap in your code. You will now be able to select and update those graphics. By adding the Esri basemap to your app, your MapView will utilize its spatialReference (which is Web Mercator). This is an issue in 2D that we are aware of and will be working on resolving in the future. This is not an issue in 3D, so you can also test this by switching your MapView to a SceneView instead. If you would like to use the Sketch widget in 2D with existing geometries on the Map, make sure those geometries' spatial reference match the view's spatial Reference. In this case they would need to be in Web Mercator. Thanks, Jose

‎07-19-2021

Hello Keith, Appreciate the feedback. Would you be able to share the service url for us to test? While working on this bug last release, we tested layers with millions of features, including the service from the original post here. After running our tests on the bug fix through these layers, we were comfortable enough to say that this issue was resolved. However, you may have an example of a dataset where this is not completely resolved. Therefore, it would be very helpful if you could provide the service url if possible to test. If you don't feel comfortable posting your data here, feel free to message me directly via Esri Community. Thanks, Jose

‎07-15-2021

Hello @kawishabbas , The issue in the valueExpression you have there is that you are using AND instead of &&. Also you need a default value at the end of the When() method in case all of the conditions resolve to false. Here is an example of a valid valueExpression using two fields, similar to what you have. The 10 at the end is the default value in case all of the expressions return false. const name = "$feature.state_name"; const pop = "$feature.pop2000"; const valueExpression = `When(${pop} < 20000, 0, ${pop} > 20000 && ${pop} < 60000, 1, ${pop} > 60000 && ${pop} < 100000, 2, ${pop} > 100000 && ${name} == 'California', 3, ${pop} > 100000 && ${name} == 'Texas', 4, 10)`; const renderer = { type: 'unique-value', field2: "pop2000", valueExpression: valueExpression, uniqueValueInfos: [ { value: 0, symbol: { type: "simple-fill", color: "#2D2670", style: "solid", outline: { width: 2, color: "#ffffff" } } }, { value: 1, symbol: { type: "simple-fill", color: "#FFBA39", style: "solid", outline: { width: 2, color: "#ffffff" } } } ... ] } Here is a codepen of a sample application with this working. Sample App. Thanks, Jose

‎07-14-2021

Hello @HenryKo2 , Could you provide a simplified reproducible test case on codepen? I have not been able to reproduce this issue at 3.37 or 3.35. Could you also test 3.37 if possible? Thanks, Jose

‎07-14-2021

Hello @EthanBodin1 We purposely did not publicly document the activeLineSymbol property. There was demand to document the activeFillSymbol but not for the activeLineSymbol. I believe, as you may feel as well, it would make more sense to publicly document this. We will strongly consider this for next release. There were some concerns initially on exposing this, but we will be looking into this again. Appreciate your feedback. You can use the activeLineSymbol in the meantime, there is just no documentation on this at the moment. Thanks, Jose

‎07-08-2021

@GertConradie , I am seeing the request (where: 1=1) being sent when you add the feature service with a definition expression as a feature snapping layer source. We will be looking into this. Thanks again for bringing up this issue you found. Thanks, Jose

‎07-06-2021

Hello @JoelBennett , The RotateEventInfo.angle was a bug fix for SceneView. The angle value being returned was not in correct degrees. This was fixed in this release, so it should actually be in the bug fixes section and not the breaking changes. I apologize for that misunderstanding, I will fix this.

‎07-06-2021

Looking into this, this could potentially be a bug. Thanks for bringing this up @GertConradie !

‎06-25-2021

Hello, At the moment, the Sketch widget's labels cannot be overridden. Is there something wrong you found with the translation? If you want to set your custom labels, using the SketchViewModel and your own custom UI would be the workaround. Thanks, Jose

‎06-18-2021

Hello Keith and Johnny, I would like to inform you that this issue has been resolved at 4.20. Thanks, Jose

‎06-18-2021

Hi Ethan, This is a pretty solid use case. Creating your own tracing logic via the snapping events is pretty interesting, and this would be a good enhancement. At the moment the snapping engine used is under the hood, so we will look into potentially exposing some of these events. Thank you so much for your feedback, Jose

‎06-15-2021

Hi Ethan, Thanks for the feedback on the snapping enhancements you would like to see in the future. We would like to be able to have the options to control whether to snap to edges, vertices, etc. just like ArcGIS Pro does it. This is currently being discussed on how to port this into the Sketch widget, so thanks for the feedback! In regards to event emitting, this could be something we discuss as well. Is there a specific use case in which this would be useful to you or to others as well? Thanks, Jose

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by JoseBanuelos

Re: Arcgis JS how to add buffer to large data service (56K point data)

Re: Snapping performance issue in version 4.19

Re: Snapping performance issue in version 4.19

Re: Unable to edit polygon drawn using graphics.add()

Re: Snapping performance issue in version 4.19

Re: Arcade expression in Uniquevalue

Re: Snapping Issue with ArcGIS API for JavaScript 3.x

Re: SketchViewModel.activeLineSymbol

Re: Snapping events and options enhancements for 4.x

Re: ArcGIS API for JavaScript 4.20 and 3.37

Re: Snapping events and options enhancements for 4.x

Re: Change Sketch's tools labels

Re: Snapping performance issue in version 4.19

Re: Snapping events and options enhancements for 4.x

Re: Snapping events and options enhancements for 4.x

Re: Editor Component and layerInfos

Re: 4.32: translations missing

Re: Viewing related records on a subtype group lay...

Re: How to fix " Error: Can't resolve '@arcgis/cor...

Re: 4.28 Sketch Tool - View click events not worki...