nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Record phenomenon... HELP!

-_Ashley-B-Potter_-

I have identified 308 records that have a zero value for both area and length. To troubleshoot this issue, I deleted and recreated one of the records; however, the area and length still remain at zero. The active and retired parcels are appearing in the records. For example

Additionally, I encountered a situation yesterday where duplicate records appeared, which should not occur since the system does not permit the use of the same name for multiple records. I am currently unable to replicate this issue.

Has anyone else experienced similar problems?

Encuentra más publicaciones etiquetadas con

Accepted answers

JasonCamerano

For the the first issue, you'll notice you have more than 2000 parcel features assosciated to that record. There is a configurable limit to how many parcels a record can have before we do not generate a geometry for the Record. That limit is by default 2000. We do this to improve performance and not have record features that are incredibly large. This will not affect any record driven workflows if the Record has no geometry. All the parcels are still properly associated / retired from that record.

As for the duplicate names, yes this is a bug and if you can find a way to reproduce it we would like to know how it happened. We have noticed that sometimes Create Parcel Records GP tool will create duplicate records and there is a fix coming in for 3.4 to address that.

Thanks for the feedback!

All comments

jcarlson

I haven't run into duplicate records like that, but I see the empty area and length from time to time when a record "loses" its parcels. For instance, I have a parcel that was imported, so it is assigned to a generic placeholder record. Later, I assign that parcel to a real record for historic purposes. When I build the fabric, my generic placeholder now has no parcels associated with it, and it collapses down to an empty geometry. I've never seen empty geometry when the created parcel count was > 0, though.

Can you select the related features on each record? Or run build on the whole area? I can't tell from your symbology, but if you select the record, does it actually show you anything in the map?

-_Ashley-B-Potter_-

In certain records, I have the ability to select the associated features. The purple line visible in the top image indicates the parcels that are connected to the selected record. While I would typically not be overly concerned with these issues, it is important to note that some of them pertain to brand new records. This is the first time I have noticed or witness this.

JasonCamerano

Thanks for the feedback!

-_Ashley-B-Potter_-

The maximum parcel count clarifies one issue, while the bug addresses another. Is it possible for us to adjust the maximum parcel count? Typically, I do not handle records of this size; however, I am unable to utilize duplicate parcels without an existing record. In the future, the size of my records will not be this extensive.

-_Ashley-B-Potter_-

@JasonCamerano

One possible explanation for this issue is that when an individual creates a record while the records layer is selected, it may inadvertently result in the duplication of a null record with information from the previous entry, resembling an attempt to retire the original record. I have observed a trend where, after the creation of a new record, the existing record appears to become invalid. This is evidenced by the presence of null values in Shape.STArea() and Shape.STLength(), which may correlate with my initial hypothesis.

Update 10-9-24:

When I assigned these two parcels to an existing record that was not completed (assigned both parcels to record) I noticed the original records changed the values in Shape.STArea() and Shape.STLength() to null.

Update 10-10-24: I have confirmed that Assigning to record causes the original records changed the values in Shape.STArea() and Shape.STLength() to null.

I am using Pro version 3.3.2. My team is on 3.3.1.

Enterprise version: 11

Parcel Fabric: 5

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.