|
IDEA
|
02-14-2023
04:58 AM
|
0
|
0
|
1389
|
|
IDEA
|
02-10-2023
12:41 AM
|
0
|
0
|
3902
|
|
BLOG
|
@JianT The 'polylineJSON' is the basis for updating the features' geometry, but a single calculation rule can update multiple fields (shp, name, ...). Check out this video to learn more.
... View more
02-01-2023
08:49 AM
|
0
|
0
|
2637
|
|
IDEA
|
01-26-2023
07:13 AM
|
0
|
0
|
3295
|
|
POST
|
@Kathleen_Crombez We discourage using subtypes unless they are absolutely needed (see above) A historic parcel is a parcel where 'RetiredByRecord IS NOT NULL'. This is not a 'long' field type and therefore cannot be used to control subtypes. Using an attribute rule to change another long field is also not allowed. Furthermore, geodatabase topology only works on 'feature classes' and not on layers, so you cannot run a rule on a table that contains both historic and current parcels. However, validating a subset of the data might be achieved using attribute rules validation (arcade has spatial analysis methods, filtering and more).
... View more
01-25-2023
08:03 AM
|
0
|
0
|
4808
|
|
POST
|
@JasonBessert If you are referring to the "Ready To Use Rules" those are the Data Reviewer Extension rules. If your customer has a license to that extension they can use that when performing Data Reviewer evaluation workflows. You might need to take a Data Reviewer training to understand how to use the extension. Unlike geodatabase topology, Data Reviewer will not change the source data (cracking and clustering) when evaluating the rules.
... View more
01-24-2023
03:59 PM
|
0
|
8
|
7210
|
|
POST
|
@AndrewWallick We have an idea to auto-snap line endpoint to a parcel point or another line extremity if within a given tolerance and if the line is 'COGO-enabled'. This idea is similar
... View more
01-20-2023
12:40 AM
|
3
|
10
|
7293
|
|
BLOG
|
You guys MAKE A DIFFERENCE that impacts so many! Looking forward to meeting more of you in person.
... View more
01-12-2023
03:25 AM
|
10
|
0
|
49283
|
|
POST
|
@Eliot_Reid The bug number is "BUG-000151086" It has been fixed in ArcGIS Pro 3.1 but has not been ported to 3.0.x yet. I'll update this thread once we patch it in 3.0.
... View more
01-12-2023
02:56 AM
|
2
|
1
|
4274
|
|
IDEA
|
Check the Reconstruct Boundaries tool (introduced in ArcGIS Pro 3.0)
... View more
01-04-2023
05:05 AM
|
0
|
0
|
2342
|
|
IDEA
|
No plans to invest in ArcMap which will be deprecated in a few years.
... View more
01-04-2023
05:04 AM
|
0
|
0
|
2343
|
|
IDEA
|
No plans to invest in ArcMap which will be deprecated in a few years.
... View more
01-04-2023
05:03 AM
|
0
|
0
|
1425
|
|
POST
|
Thanks for confirming. If you want to symbolize based on a field (Category) as well as the Seed, you might need a few lines in Arcade. I think something like this would work: If ($feature.IsSeed == 1) return 'Seed';
return $feature.<your field name>; You enter it in the symbology pane:
... View more
12-15-2022
04:07 AM
|
2
|
0
|
2062
|
|
POST
|
@VassilisTrigkas1974 I suspect it is your seed symbology. The Seed is actually a small round polygon. You can symbolize it as you please. If you click on the Seed symbol you can modify the symbology to make sure this is a symbology issue you can always add the parcel fabric to a new map, get the default symbology and see how it looks. Other thoughts: could also be 2 overlapping parcels from different types, a small round parcel that looks like a seed. Please confirm if this is indeed a symbology issue
... View more
12-15-2022
03:37 AM
|
0
|
1
|
2070
|
|
IDEA
|
Implemented in ArcGIS Pro 3.1. Make sure to add a field called 'FloorOrder' (long) on the lines and polygon feature class that belong to the same parcel type
... View more
12-13-2022
03:56 AM
|
0
|
0
|
3218
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 06-26-2026 01:32 AM | |
| 1 | 06-24-2026 07:42 AM | |
| 3 | 06-24-2026 07:43 AM | |
| 2 | 06-24-2026 06:46 AM | |
| 1 | 06-12-2023 01:26 AM |
| Online Status |
Online
|
| Date Last Visited |
Monday
|