Latest Contributions by Noah-Sager

Thanks @kaleb_integralNZ, that is helpful. I tried to build an app that reproduces the issue based on the information you've shared, but I am unable to reproduce. Can you look at the test-app and check your behavior, and see if you can reproduce the issue using the sample data? https://codepen.io/noash/pen/QwjYqaP   ... View more

Hi @GISExpertPL, thanks for posting your question here. It looks like that line near the circled building is an angled height line, and does not encompass that circled building. It also looks like that circled building is not included because it is still white (like the buildings in the background) and not green/red like the buildings inside the viewshed analysis. ... View more

Hi @JeffreyThompson2, thanks for posting your question here. We have 3 different labeling implementations in the ArcGIS Maps SDK for Javascript - 2D featureLayer, 2D mapImageLayer, and 3D. We document the differences in implementation and usage in this guide topic: https://developers.arcgis.com/javascript/latest/labeling/ While we don't explicitly callout the differences between 2D featureLayer and 2D mapImageLayer behavior, the reason we have different fonts is because we have different labeling implementation. For example, mapImageLayer is a server-side only layer. As such, we cannot define a deconfliction strategy for 2D mapImageLayer, only for 2D featureLayer (and associated layers): https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-LabelClass.html#deconflictionStrategy We constantly work on improving our labeling behavior for every possible use case. Please continue to share your stories and workflows and pain points so we can discuss and address as appropriate.   ... View more

Hi @kaleb_integralNZ, thanks for posting your question here. Any chance you have a simplified reproducible test-app that I could take a look at? That would really help see what's going on. You can use dummy data for the layer URL(s). If not, take a look at the print request in the Network traffic and see if anything looks goofy in the webmap_as_json. ... View more

Hi @GILBERTNG1, thank you for posting your idea here. We are going to review our download story and improve it to explain how to get the components locally. It won't be zipped and included with the API, but you can download directly from npm registry url. More information is available in this guide topic: https://developers.arcgis.com/javascript/latest/working-with-assets/  For components, the CDN files are available thru npm in the "dist/cdn" folder. You can get them with npm or direct http. For example: npm install @arcgis/map-components or curl https://registry.npmjs.org/@arcgis/map-components/-/map-components-4.33.16.tgz ... View more

Here is the link for contacting Esri Technical Support: https://support.esri.com/en-us/contact   ... View more

Hi @CharanpreetKaur, I understand. It sounds like you did not make any code changes, and the app still works without labels when you upgraded from 4.30 to 4.33. But if you use labels, it crashes at 4.33. Updating to a new version of the ArcGIS Maps SDK for JavaScript can require code changes. We list the breaking changes at every release. Here are the breaking changes for 4.31 and 4.32 and 4.33 that might be affecting your app. https://developers.arcgis.com/javascript/latest/4.31/#breaking-changes https://developers.arcgis.com/javascript/latest/4.32/#breaking-changes https://developers.arcgis.com/javascript/latest/release-notes/#breaking-changes Even if changes were not made to labelingInfo, internally, perhaps in conjunction with loading multiple versions of Lit, changes may be needed in order to update the app to consume different versions of APIs and/or frameworks. The difficulty here is there is no way for me to debug without a simplified reproducible test-app. I would recommend trying older versions of the SDK (4.31, then 4.32) and see if they work, or if they break in a useful or revealing way. Also, if you have the ability, I would contact Technical Support and open an issue. ... View more

Hi @no33mis, thanks for posting your question here. I'm not 100% sure what's occurring, but I have some hunches. When you upgraded the Portal version, did this update the default travel mode? Or did you have some other customizations that might have reverted back to default values during the upgrade? Additionally, you can use the fetchServiceDescription() method to return the travel mode of the service. https://developers.arcgis.com/javascript/latest/api-reference/esri-rest-networkService.html#fetchServiceDescription const { supportedTravelModes } = await networkService.fetchServiceDescription(    config.routeServiceUrl,    apiKey, ); const driveTravelMode = supportedTravelModes.find(({ name }) => name === "Driving Distance"); ... View more

Hi @rVeloz, thanks for posting your question here. To add that information from that tutorial, you need to use the "result" object, around line 128 if you pop the tutorial into Codepen. To prove this, you can add a couple statements like this to print-out the info to the browser Console: console.log("route length (miles): ", result.route.attributes.Total_Miles); console.log("route length (kilometers): ", result.route.attributes.Total_Kilometers); Here is a slightly modified version of the tutorial to test. Just supply your API Key and open the browser Console and run the app. https://codepen.io/noash/pen/ogjdWOB?editors=1000   ... View more

Hi @CharanpreetKaur, it's difficult to debug from those errors/warnings. I haven't worked with Lit much, and can only focus on our core product. I noticed that in layers where the labeling info is empty under Drawing Info, there is no issue. This is curious. You mean in the service definition from REST right, not in the code? I would test each version individually. Try 4.31, and then 4.32. See if it works in an earlier version. Without a simplified reproducible test-app that demonstrates this issue, it's tricky for me to help more. ... View more

Hi @CharanpreetKaur, thanks for posting your question here. There should not be an issue with labeling at 4.33 with a React app, but it's difficult to diagnose from the above information. If you open the browser Developer Tools, do you see any warning or error messages in the Console? Can you create a simplified reproducible test-app that demonstrates this issue with and without React? Lastly, there were some breaking changes between version 4.30 and 4.33, you might want to review the changes and see if the app needs to be updated: https://developers.arcgis.com/javascript/latest/breaking-changes/   ... View more

Hi @vijaybadugu, thanks for posting your question here. I think it might be helpful to review the doc for layers and layerviews: https://developers.arcgis.com/javascript/latest/query-filter/ And here are some samples for inspiration: https://developers.arcgis.com/javascript/latest/sample-code/featurelayerview-query-geometry/ https://developers.arcgis.com/javascript/latest/sample-code/featurelayer-query/   ... View more

Hi @MichaelWen_Timmons, thanks for posting your question here. It sounds like the Angular upgrade is the key to this issue. I will do some digging, but in the meantime, can you test a simple FeatureLayer + label app with Angular 18 (and maybe using different browsers) and see if you get different results? ... View more

Hi @FionaCarey1, thank you for contributing your use case to this discussion, and I appreciate that printing is part of the workflow. This will help us to better understand user requirements. ... View more

Sorry for the tardy reply. Ahh, if it doesn't print from ArcGIS Pro, then it will not print in any other environment. The print service is published from ArcGIS Pro. You might get better help in the Desktop space. ... View more