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; } } }

Get Previous Feature Using FeatureCursor

Corbinde_Bruin

Hello all,

What is the best practice for stepping backwards in a FeatureCursor. I use the NextFeature() method to loop through a FeatureCursor and make edits, but now I need tot be able to scroll back and forth between features in a FeatureCursor.

If there is another way, I do not need to use the FeatureCursor. I just don't know of another way.

I looked into using an enumerator, but that looks like it has the same exact problem. I see a Next() method and a Reset() method, but no Previous() method.

I feel I am missing something basic here. Right now I am requerying the database every time I want to access a 'previous' feature. I'd love to see some ArcObjects best practices here. I've searched the documentation and forums, but I was unable to find anything related.

Thank you,
Corbin de Bruin

Finde mehr Beiträge mit dem Tag

Accepted answers

kenbuja

You could put the features into a collection (an array, dictionary, hashtable, etc). After running the feature cursor once to build the collection, you can access the features as you need.

One of my projects involved doing a series of calculations on the attributes of a group of features. Many of the calculations used values that were the result of previous calculations. The person who originally wrote the code used a separate cursor for each individual calculation, which took forever. I was able to rewrite the code where all of the attributes for the features where written into an array using a featurecursor. All the calculations where then done by looping through this array, which speed things up immensely.

All comments

Corbinde_Bruin

Neil,

That's good to know. I've added a QueryFilterDefinition.PostfixClause to fix this issue.

Thank you,
Corbin de Bruin

NeilClemmons_GISinc

Unless you're using an ORDER BY clause in the query or doing something else to sort the results, the features in a feature cursor will not be in any reliable order. For example, if the ObjectId of the current feature is 2 you can't assume that the ObjectId of the previous feature was 1. This may or may not apply to your specific scenario but I just wanted to point it out in case it does matter.

kenbuja

I didn't need to look for particular feature, so I never played around with Array.FindIndex

Corbinde_Bruin

Writing to an array is another method I had toyed around with, and it's what I have moved to using today.

Do you use Array.FindIndex at all? This is what I would up using to loop through my records and find the previous record.

gRow = Array.FindLastIndex(rowArray, AddressOf previousPhotoRowPredicate)

 Private Function previousPhotoRowPredicate(ByVal pRow As Row) As Boolean

        If pRow.OID < gCurrentRow.OID Then
            Return True
        Else
            Return False
        End If

    End Function

kenbuja

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

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