|
POST
|
Perhaps you have multipart features from the result of some merge operation previously. Try https://pro.arcgis.com/en/pro-app/3.0/tool-reference/data-management/multipart-to-singlepart.htm which might then allow the other tools to work as intended.
... View more
03-14-2023
05:31 AM
|
0
|
1
|
1789
|
|
POST
|
Are the field names and field data type the same across the merged datasets? Otherwise obviously there would be null values from one dataset which doesn't match the same field name or type and a new field has to be added to the merged output. There's not quite enough info to go on from your current screenshots.
... View more
03-13-2023
04:11 PM
|
0
|
1
|
2505
|
|
POST
|
Might also be worth testing against the base table rather than evw to confirm this as the likely cause of the inefficiency (appreciate record count would differ however).
... View more
03-13-2023
11:28 AM
|
0
|
1
|
2030
|
|
POST
|
What happens if you set this as the else else {return $feature["date_diag"]} what are you data types for periodicite? string or numbers?
... View more
03-13-2023
05:42 AM
|
0
|
0
|
1528
|
|
POST
|
I'd just highlight an error in your post - Esri is clockwise outer rings and anti-clockwise inner rings/holes.
... View more
03-12-2023
08:41 AM
|
1
|
1
|
4377
|
|
POST
|
Probably the easiest method would be the Split by Attributes tool. https://pro.arcgis.com/en/pro-app/latest/tool-reference/analysis/split-by-attributes.htm You just select an output workspace (geodatabase) and the field to group/split attributes by - 'Stahler'
... View more
03-11-2023
06:18 AM
|
3
|
2
|
2421
|
|
POST
|
Impressive stuff there. Yes on looking back, 'else if' makes no difference since a return statement is used each time. 'When' is certainly more readable also.
... View more
03-11-2023
04:41 AM
|
0
|
0
|
3745
|
|
POST
|
How big is the dataset? One thing to check is that you have a spatial index, it is much faster if so. Maybe the 'disjoint' test is faster. When was the last time the database was compressed (I'm guessing versioned as you have _evw)? Is it going to state 1 or 0? Otherwise the versioned view query is quite expensive to work through - checking on the delta tables and the base table differences.
... View more
03-11-2023
04:18 AM
|
0
|
3
|
2047
|
|
POST
|
The simplest way to looks at it is that row selection treats the feature class as a table with no geometry and can't be used as an input for a geoprocessing tool which requires a geometry operation (e.g. buffer, select by location). Feature selection includes the geometry, and can be used in subsequent geoprocessing tools in the same way as the original feature class. row selection - outputs the row of the attribute table feature selection - outputs as if a selection from the feature class, including the geometry/shape.
... View more
03-11-2023
04:13 AM
|
0
|
0
|
1945
|
|
POST
|
Looks like your code logic doesn't really work. If inspectionResult is always either pass or fail, then only the first 2 if statements would ever be evaluated since a return breaks any subsequent evaluations (also consider using 'else if' to make the code more efficient. you need some more detailed logic such as //8 possible permutations (2^3) (ermmmm I think - a while since my statistics classses!)
var Stage1= $feature.inspectionresult
var Stage2= $feature.installationresults
var Stage3= $feature.ns_serviceentrance
if (Stage1=="Pass" && Stage2=="Fail" && Stage3=="Fail")
return "Stage 1 Pass Stage 2-3 Fail"
else if (Stage1=="Pass" && Stage2=="Pass" && Stage3=="Fail")
return "Stage 1-2 Pass Stage 3 Fail"
else if (Stage1=="Pass" && Stage2=="Fail" && Stage3=="Pass")
return "Stage 1-3 Pass Stage 2 Fail"
else if (Stage1=="Pass" && Stage2=="Pass" && Stage3=="Pass")
return "Stage 1-2-3 Pass"
else if (Stage1=="Fail" && Stage2=="Pass" && Stage3=="Pass")
return "Stage 1 Fail Stage 2-3 pass"
else if (Stage1=="Fail" && Stage2=="Fail" && Stage3=="Pass")
return "Stage 1-2 Fail Stage 3 pass"
else if (Stage1=="Fail" && Stage2=="Pass" && Stage3=="Fail")
return "Stage 1-3 Fail Stage 2 pass"
else if (Stage1=="Fail" && Stage2=="Fail" && Stage3=="Fail")
return "Stage 1-2-3 Fail"
... View more
03-10-2023
04:16 PM
|
0
|
4
|
3753
|
|
POST
|
It's an ArcMap tool also. What version do you have? I think it goes all the way back.
... View more
03-10-2023
04:50 AM
|
1
|
0
|
2035
|
|
POST
|
Tabulate intersection https://pro.arcgis.com/en/pro-app/latest/tool-reference/analysis/tabulate-intersection.htm would achieve the end goal without needing this clipping step.
... View more
03-09-2023
12:44 PM
|
1
|
0
|
2045
|
|
POST
|
if ($feature["note_diag"] != "" && $feature.periodicite == "1") {
return Dateadd($feature["date_diag"],1,'years')
}
else if($feature["note_diag"] != "" && $feature.periodicite == "2") {
return Dateadd($feature["date_diag"],2,'years')
}
else if($feature["note_diag"] != "" && $feature.periodicite == "3") {
return Dateadd($feature["date_diag"],3,'years')
}
else if($feature["note_diag"] != "" && $feature.periodicite == "4") {
return Dateadd($feature["date_diag"],4,'years')
}
//else {return something}
... View more
03-09-2023
09:51 AM
|
0
|
2
|
1564
|
|
POST
|
On reviewing your original question I'm not entirely sure you want pie chart symbology. You're aware you can symbolise by attribute? https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/unique-value.htm I'd get a second opinion before you add any fields to do the pie chart as I just don't understand your data or exactly what you need. Hopefully someone else understands what you need to achieve and can assist.
... View more
03-08-2023
12:30 PM
|
1
|
1
|
4148
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-17-2023 12:44 PM | |
| 1 | 06-13-2025 01:08 PM | |
| 1 | 09-25-2025 03:19 PM | |
| 1 | 09-24-2025 02:35 PM | |
| 1 | 09-17-2025 02:42 PM |
| Online Status |
Offline
|
| Date Last Visited |
07-06-2026
06:42 AM
|