Latest Contributions by dotMorten_esri

Oh did you try without elevation? I wonder if it is just ending up underground. That would match the behavior of sometimes briefly seeing it before the elevation data loads. ... View more

aaah gotcha. I misunderstood that bit. So adding online basemap makes it so it doesn't render? I'll have someone investigate. Thank you for sharing the data. I'd be curious what happens if you manually add the basemap programmatically after loading the mspk.  ... View more

This is unfortunately an android quirk: The files you deploy with android aren't directly accessible with a file path, whereas on iOS and Windows you can just give it the relative path. On Android you'll need to copy the deployed data out into a local folder instead and use that path to open the data. Also instead of using "Resource", use "Content" for the build action. ... View more

> Also included how the Table and FeatureLayer are loaded I was referring to the feature itself. Try adding (feature as ILoadable)?.LoadAsync(); before assigning it to the popup. Also assert that the feature itself does have that attribute populated. Lastly set a breakpoint on the Popup that is returned from identify, call "await Popup.EvaluateExpressionsAsync()" and inspect "EvaluatedElements" and verify the fields are present ... View more

Is the JOIN_STRAP field name correct? Did you make sure the feature you got is fully loaded and has that attribute in it? You can ignore the binding errors for now ... View more

Thanks for confirming. On second look I realize you're adding to Fields and not Elements. Try this instead: PopupDefinition newP = new PopupDefinition() { Title = "My Custom Title" }; PopupField newF = new PopupField() { Label = "Strap", FieldName = "JOIN_STRAP", IsEditable = true, IsVisible = true, StringFieldOption = PopupStringFieldOption.SingleLine }; newP.Elements.Add(new TextPopupElement("This is just some <b>generic text</b> you can add")); newP.Elements.Add(new FieldsPopupElement(new[] { newF }) { Title = "Attributes" }); ... View more

This is pretty typical database behavior. In this case the underlying database is a sqlite database, and it would need a vacuum operation. See: https://sqlite.org/lang_vacuum.html The SDK doesn't provide vacuum out of the box, but any sqlite API or tool should be able to do this for you. If the geodatabase is sync enabled, it still needs to track deleted features, so this can be synchronized with the server later. ... View more

There is no location where you tapped on the line. The identify is done with some pixel tolerance and finds any geometry intersecting within that distance visually. Since a line is infinitely thin, you most likely didn't actually click the line but right next to it. The identify operation is all done in the rendered pixel space, so the calculation for where they intersect isn't ever made. The best you get is to nearest vertex like @GKmieliauskas points out. I get that gets tricky in 3D since you're really talking about the nearest point between the polyline and the ray from the camera to the location on the surface. There's no out-of-the box way to calculate this position, so you might be in for doing a little bit of 3D trigonometry between those two line segments. ... View more

I just retried the repro on 200.4, then upgraded to 200.5 on Maui WinUI and observed the problem go away. Could you try doing a full clean and forced rebuild, to make sure no old 200.4 assemblies are left around?     ... View more

I think I see what you're getting at but not 100% sure. Could you provide a small application that demonstrates the problem that we can use to investigate? ... View more