POST
|
That's a cool use of deep learning. In your tool results is there anything in the Messages section that may point to the problem? Do you get this error on all your photos & datasets, or just this one? If you set the Detected Class Value Field to "Class" and the Ground Truth Class Value Field to "Classname" does it still error? I wonder if it is some sort of geometry issue when it is trying to calculate the overlaps. If you export just a few detection polygons and corresponding truth polygons does it still error? Are there any issues identified if you run the Check Geometry tool over the datasets?
... View more
07-28-202111:18 PM
|
1
|
1
|
758
|
POST
|
1. Solution from here: ArcGIS Pro Global Scene Background (In your global scene) You can change the black and star background by going to this setting: Scene Map properties-> Illumination->(uncheck) Show Stars and Halo. Now in General tab of the Scene Map properties set the colour of the background 2. According to the Extent Indicators help: Extent indicators require two map frames—the map frame containing the extent indicator and the map frame with the extent you want to show—and only work with 2D maps. Because of this, the Extent Indicator button is disabled until there are at least two 2D map frames on the page. Sounds like extent indicators are not supported in scenes?
... View more
07-27-202103:21 PM
|
1
|
1
|
979
|
POST
|
If all you want to do is remove the previous highlight when doing a new query then try this (note: nu unselect function): let highlightSelect; function selectParcel() { //Remove highlights if (highlightSelect) { highlightSelect.remove(); } //Query feature first highlightSelect = layerView.highlight(feature.attributes["OBJECTID"]); } If it's a more complicated scenario than that, then you may have to post some more complete code. I recommend having a play around with that highlight point features sample I posted earlier.
... View more
07-27-202103:14 PM
|
0
|
0
|
1483
|
POST
|
You need to define the variable outside the functions in the main code (sort of like a global variable). The highlightSelect variable will know what feature was highlighted, so you don't need to query it again in the unselect function. let highlightSelect; function selectParcel() { //Query feature first highlightSelect = layerView.highlight(feature.attributes["OBJECTID"]); } function unselectParcel() { if(highlightSelect) highlightSelect.remove(); }
... View more
07-27-202102:47 PM
|
1
|
2
|
1487
|
POST
|
If you have a look at the PointAddress section on this page: Primary locator roles , it says: If there are some features that have house number ranges, you must model all features with ranges. The features that do not have house number ranges must use the same value for the house number From and To fields. Putting the same house number in the From and To fields works in my locator. For house number prefixes and suffixes you need to concatenate everything into a single field. There is a good example table on that same page with different prefixes\suffixes. So you would have: House_Number_From House_Number_To Street Street_Type 15 15 Mechanic St 15A 15A Mechanic St 70 1/2 70 1/2 Main St 100 108 Main St
... View more
07-27-202102:22 PM
|
1
|
1
|
1123
|
POST
|
According to the highlight function it returns a handler that you can use to remove the highlight. There is also a good sample showing how it works: Highlight point features First you setup a variable to hold the highlight selection handler: let highlightSelect; Then when you do a query you can remove the current highlight before doing the new one (you can see where it is assigning the handler to highlightSelect in line 11): myLayer.queryFeatures(myQuery).then((result) => { // if a feature is already highlighted, then remove the highlight if (highlightSelect) { highlightSelect.remove(); } // the feature to be highlighted const feature = result.features[0]; // use the objectID to highlight the feature highlightSelect = layerView.highlight( feature.attributes["OBJECTID"] ); You could also just remove the highlight any time you wish: highlightSelect.remove();
... View more
07-27-202101:21 PM
|
0
|
1
|
1500
|
POST
|
Something like the following should do it all in one step. It is only checking that the first name and last name have empty strings, not that they are null, so you may need to modify the if statement to match your data. expression = "getName(!USER_FNAME!,!USER_LNAME!,!USER_CORPN!)" codeblock = """ def getName(fname, lname, corpn): if fname=="" and lname=="": return corpn else: return fname + " " + lname """ arcpy.CalculateField_management(
My kudoed posts
Activity Feed
|