Latest Contributions by ShellyGill1

Hi @YasunariTosa1 , I think this could be down to expecations of the input & output spatial reference of a transformation, and the doc not being good enough here. Transformations deal with a change in datum, and that's part of the underlying geographic coordinate system. If your input or output spatial references are projected (which they both are in your case above - IsProjected==true), then instead of checking the WKID directly, check the BaseGeographic.WKID property instead. E.g I'd expect the inSP.BaseGeographic.WKID to be 4269, and equal to defaultDT.InputSpatialReference.WKID. This isnt detailed in API reference for DatumTransformation though - I'll submit an issue to get this documentation updated with this information - thanks for highlighting it to us. ... View more

One thing I forgot to mention in my initial query: even though the shapes are drawn correctly, there’s still a bit of inconsistency. For example, when the zoom level is very high and I draw a rectangle or circle, the shape loads and draws again with the correct coordinates, but its position appears slightly off. When I hover over the area, it gives me the correct location, and due to the high zoom, the hover difference is minimal. However, the shape’s visual placement is still slightly off. From your info above, the geometry you're drawing on your map is not the same geometry as the one that you get back from the geometry editor, so I imagine there will be some differences here - if you try your same workflow but save & reload exactly the same geometry as you got back from the geometry editor, do you see the same discrepancy, or does the shape then appear exactly where you expect? Other things to look at would be if you have any reprojection happening in your workflow - different transformations can vary in their accuracy a little. You might find it helpful to read the following info if you're not already familiar with how data is reprojected - https://developers.arcgis.com/qt/spatial-and-data-analysis/spatial-references/#when-you-need-to-know-about-spatial-references, and this ref contains info on how the geometry of a GeometryEditor is returned with regard to spatial references which might help: https://developers.arcgis.com/qt/cpp/api-reference/esri-arcgisruntime-geometryeditor.html#geometry  ... View more

@SWE Glad your shape is looking better. >  the shape loads and draws again with the correct coordinates, but its position appears slightly off.  I'm not sure there's enough information here to tell what problem you're seeing, but worth mentioning a couple of things in case these help. The geometry editor is not creating a geodesic ellipse, whereas you're recreating the shape as a geodesic shape, so you might see some differences due to that I'd expect - more noticable at smaller scales though. Also you've not mentiond how you're preserving spatial references throughout your workflow, so could there be some reprojection of your recreated shape happening? ... View more

@SatyaraySingh  - if your map point is always WGS84, could this be because WGS84 is always magnetic north aligned anyway? If there's no difference then the method will always return 0. If you use a projected coordinate system that is not magnetic north aligned then I'd expect a non-0 result - for example, if have a point in British National Grid as below (WKID 27700), then I get a result of -0.984136. var bngPoint = new MapPoint(325847, 674007, SpatialReference.Create(27700)); var ConvergenceAngle = bngPoint.getSpatialReference().getConvergenceAngle(bngPoint); ... View more

Hi @MichaelDavis3 - I'm not sure on the details of the implementation, so I will see if I can get this confirmed for you. ... View more

> If I needed to find bearing from True North to a particular Mappoint. is there any method to do so?  Hi @MichaelDavis3 - I think that theGetConvergenceAngle method on SpatialReference could be helpful here in figuring out a difference between True North and Grid North for a specific point: https://developers.arcgis.com/net/api-reference/api/net/Esri.ArcGISRuntime/Esri.ArcGISRuntime.Geometry.SpatialReference.GetConvergenceAngle.html ... View more

No worries, glad it's working for you now @StefanKallin  😀.. ... View more

Hi @StefanKallin - can you describe the scenario where you're not getting the event? If you're using the default VertexTool, and have clicked/tapped to add a vertex - for example - I'd expect it to fire at that point, or any other time the geometry value changes (like when you start the geometry editor with an existing geometry object). However I wonder if your situation is that you want the event during a drag operation - for example in the middle of dragging/moving a vertex from one location to another using the VertexTool, or maybe during the initial creation of a circle or ellipse with the ShapeTool? I'd expect in both these cases that during the drag operation you dont get geometryChanged event on every mouse move increment of the drag operation, but it should happen when you release the mouse (or release the touch pointer if you're working on a touch device), as that's when the geometry property value is updated. Also same goes for the drag operation of a rotate or scale or move of a whole geometry or a part. If that is the specific case you're dealing with then we'd love to hear about your use case and perhaps you could post in ArcGIS Ideas for Native Maps SDKs about this requirement - we could consider enhancing the events in a future release. ... View more

Hi @jokerjoker - is there anything specific about the snapping in ArcGIS Pro which is essential for you? Do you need to be able to choose what part of a geometry (vertex or edge/segment for example) to snap to? Do you need to be able to adjust the tolerance? It's possible that we may add basic snap-to-feature functionality initially and then add future enhancements based on user demand, so it's great if we know which parts of snapping functionality are the most in demand from users like yourself - if you have specific use cases you could describe that's really useful (please feel free to message me directly if you prefer). ... View more

Hi @noodle - I'd also add another option, which might be useful if you don't want to stop the GeometryEditor after adding two points, but want you user to be able to continue to move existing points, and to be able to rotate, scale, and move the geometry. As @JenniferNery says you can monitor for the number of points in the polyline geometry. Once you have 2 points, you could get the current tool (I'm assuming you're working with the VertexTool here) and then change it's InteractionConfiguration.allowVertexCreation property to false. If you also want the user to be able to delete an existing vertex and re-add it, then ensure the config property is set back to true when the vertex number is less than 2. ... View more

Hi @jokerjoker  - although there is not currently any snapping functionality in the ArcGIS Maps SDK for Kotlin GeometryEditor it is something that is on the roadmap for future releases. Do let us know what specific snapping functionality you're looking for when capturing geometry edits.   Regards, Shelly ... View more

Hi @ofirrosner , We don't have any specific plans to add more geodetic methods to GeometryEngine in upcoming releases, but perhaps you might like to post this request on ArcGIS Maps SDKs Native Ideas place where we can monitor interest in this enhancement. We are adding a few new GeometryEngine methods in an uncoming release, so this is a continuing area of development that we can consider enhancements for.   ... View more

Thanks for the information @tanqidi. We're not actively working on this, but it's something that has been mentioned by a number of users, and we'll use your comments to contibute to our planning process for future releases.  ... View more