Latest Contributions by LucasDanzinger

The GeometryEditor is the next generation of sketching tools in the Maps SDK. While the GeometryEditor uses GraphicsOverlay to draw some of the map elements, that's an internal implementation detail and we don't plan on exposing raw access to those objects. There are numerous overlays and graphics at play, and actually modifying them to get a desirable output would be difficult. If there are specific additions or modifications you'd like added to the sketching experience, I'd highly recommend logging enhancements for those, as that will be the best avenue to improve the API. ... View more

Could you add some details about what your workflow is? Is it simply adding graphics on top of each other with the same symbology? A code snippet that illustrates the issue so we can reproduce it would be great. Thanks, Lucas ... View more

We currently don't listen to those values for the duration, but I can add an enhancement request to consider respecting those values. I'll need to discuss with the team on the feasibility of this. ... View more

Good question. I had to do a little digging on this one... Currently, the only way to create custom item resource caches is through portal items, so a workflow such as the following should get you on the right track. I tested it and was successful: Publish your vtpk as a service. I used ArcGIS Online and uploaded as a hosted service, but you could publish to enterprise. Make sure to enable offline export capabilities Use the vector tile style editor to make edits to the style. They've got some good tutorials to showcase how you can edit the style. Save your edits as a new item Using the newly created item, call the ExportVectorTileTask:: exportStyleResourceCache to export the resource cache - https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-exportvectortilestask.html#exportStyleResourceCache   Export how every many resource caches you want and place them next to your VTPK. The resource cache will be a folder with a json file and a zip. Screenshot 2024-07-09 at 1.30.31 PM.png Construct your local vector tile layer using the vector tile cache and the new item resource cache   VectorTileCache* vtc = new VectorTileCache("/Users/<username>/Desktop/nz_bndl.vtpk", this); ItemResourceCache* irc = new ItemResourceCache("/Users/<username>/Desktop/nz_bndl_resourcecache1", this); ArcGISVectorTiledLayer* lyr = new ArcGISVectorTiledLayer(vtc, irc, this); Basemap* bmap = new Basemap(lyr, this); m_map = new Map(bmap, this);         ... View more

From the description, it seems like labels with leader lines might suit your use case well. Leader lines are unfortunately not supported in the Maps SDK yet, but it is something we have had a lot of requests for. If you have access to ArcGIS Pro and can try to prototype Label callouts with leader lines, that would be useful to know if that satisfies your requirements. If so, if you could message me some details about your organization/app so I can add it to our tracking issue internally, that would be great.   The other avenue as you mentioned is using the Callout. Unfortunately, it is pretty tightly coupled to having 1 display at a time. However, since it is open source, you do have the option of poking around and seeing if you get something to suit your needs.   I have some ideas that may or may not help get you on the right track. One thing you can do with the Callout is set the contentItem to display whatever you want (doesn't need to be tied to title/description properties)   Callout { contentItem: Column { spacing: 10 anchors.fill: parent Text { text: "Custom Callout" font.bold: true font.pixelSize: 18 } Text { text: "This is a custom callout" } } palette.windowText: "black" }   This solves the display customization question, but the remaining problem at this point is that the location the callout displays at is tied to the location provided from the callout data. Since we want multiple callouts, we can't rely on that single location. However, Callout itself is just a QML Pane, so you can theoretically display it wherever you like (as QML allows). The nice thing that CalloutData does for you is that it converts the map coordinate to a screen coordinate for you, and it updates whenever the viewpoint changes or the data changes. However, you could theoretically explicitly set the XY location of the Callout, and update each at any given interval. Here is a contrived example of showing 2 callouts at the same time at a different location. The bit you'd need to work out is updating the various callouts to be in the right place all the time. This could involve some custom app code or even modification of the Callout.qml code itself.   import QtQuick import QtQuick.Controls import QtQuick.Layouts import Esri.ArcGISRuntime import Esri.ArcGISRuntime.Toolkit import DemoApp DemoPage { mapViewContents: Component { MapView { id:view Callout { id: callout calloutData : view.calloutData //binding to parent. Any change is reflected on this accessoryButtonVisible: false implicitHeight: 100 leaderPosition: Callout.LeaderPosition.Automatic x: 200 y: 200 maxWidth: 250 background: Rectangle { radius: 5 border.width: 2 border.color: "black" } contentItem: Column { spacing: 10 anchors.fill: parent Text { text: "Custom Callout" font.bold: true font.pixelSize: 18 } Text { text: "This is a custom callout" } } palette.windowText: "black" } Callout { id: callout2 calloutData : view.calloutData //binding to parent. Any change is reflected on this accessoryButtonVisible: false implicitHeight: 100 leaderPosition: Callout.LeaderPosition.Automatic x: 350 y: 350 maxWidth: 250 background: Rectangle { radius: 5 border.width: 2 border.color: "black" } contentItem: Column { spacing: 10 anchors.fill: parent Text { text: "Custom Callout 2" font.bold: true font.pixelSize: 18 } Text { text: "This is a custom callout 2" } } palette.windowText: "black" } CalloutDemo { geoView: view } } } } (modification of https://github.com/Esri/arcgis-maps-sdk-toolkit-qt/blob/main/uitools/examples/cpp_quick/src/demos/CalloutDemoForm.qml)     I wish we had something that worked for you right out of the box, but hopefully this gives you some ideas to pursue. ... View more

We are pleased to announce that we now have a public beta available for ArcGIS Maps SDK for Flutter! https://www.esri.com/arcgis-blog/products/developers/announcements/announcing-arcgis-maps-sdk-for-flutter-beta/  ... View more

We can log an enhancement for that if you like. Otherwise, you can log an enhancement through Esri Support (or through your distributor if you are international). Ultimately, factors that influence whether we prioritize something like this include number of people impacted, business case, whether there are suitable workarounds, etc. If you can, please email me ([email protected]) with details about your company, project, etc. Perhaps we could also setup a call with our product managers to better understand your use cases and what other priorities you have. ... View more

Thanks for the video, I understand better what you mean now. Unfortunately, the resize and snap effect you see is part of the implementation. We use a different rendering path for ENC due to the large, complex features. This is similar to our "static" rendering mode for graphics (as opposed to dynamic)   https://developers.arcgis.com/qt/qml/api-reference/enums-graphicsrenderingmode.html   https://github.com/Esri/arcgis-maps-sdk-samples-qt/tree/main/ArcGISRuntimeSDKQt_CppSamples/Layers/FeatureLayerRenderingModeMap     ... View more

Have you looked at using setViewpoint method that takes an AnimationCurve - https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-mapview.html#setViewpointAsync? You could listen to the various mouse/wheel signals on the mapview and implement your own custom logic https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-mapquickview.html  ... View more