Latest Contributions by BradNiemand

Michael, The goal of this patch was to address issues with composite locators that contain locators created with the Create Locator tool.  There may be some additional benefits that would be seen with composites that contain classics locators as well but that was not a focus of the testing for this patch.  I would say it wouldn't hurt to give it a try but I can't guarantee that it will help. If the patch does not help, I would suggest that you reopen or follow up with the tech support analyst and have them contact me about this.  They might be able to walk me through the issue or provide me with data to reproduce it on my side so I have more information for you because I am still not sure I understand the issue completely. All that being said, I am not sure if you have looked into the new locators but I would suggest that you do because they have a lot of benefits over the classic locators (size, performance, quality, new features, etc....).  The locators can be used in Pro 2.3 or newer or published to ArcGIS Enterprise 10.6.1 or newer (with the patch(s)) and used from other Esri clients, including ArcMap. Brad  ... View more

Michael, Can you explain the exact workflow that you do with potentially an example?  I am still unsure what the exact issue is that you are having.  In general though, this patch is specific to locators created with the Create Locator tool in Pro so it will not address issues related composite locator that contain locators created with the classic tool, Create Address Locator. Are you entering an address, getting a suggestion, passing in that suggestion text with magicKey to findAddressCandidates and then not getting a result?  If so, does the address actually exist in the data?  The classic locators had a limitation that would not verify the house number for performance reasons so in some cases you would get back suggestions for addresses that didn't exist in the data.  In that case if a suggestion with an incorrect house number was sent to the locator, you would get no match because it doesn't exist. The limitation is resolved with locators created with the Create Locator tool. Brad ... View more

Michael, What issue are you referring to with Composite Address Locators created in ArcMap?  Can you be more specific? Brad ... View more

Joe, I think what is happening is that the Locate Pane in Pro is always returning all candidates instead of just the matching candidates like it did in ArcMap without the "Show all candidates" checkbox checked.  You can check that by turning on the details (the 4 square button on the left of the search box) and seeing the scores for the candidates. We are targeting adding that option back in for a future release of Pro so that users can get back just the matching candidates instead of all candidates. Brad ... View more

Joe, It looks correct to me except maybe in the field mapping you have double quotes around Key where in an example I have it looks like it should be single quotes (maybe even no quotes would work if it is a single word). i am not a Python guy though so maybe Victor Bhattacharyya can help with this if my suggestions doesn't help. Brad ... View more

Elizabeth, All you need to do in ArcMap is right click in any folder in Catalog and select New > File Geodatabase As far as I know, everything else would still be the same.  The only difference is writing to and reading from the FGDB now. Brad ... View more

Elizabeth, This is what you would need to do to switch to using a File Geodatabase.  First create one in ArcMap in some folder of choice.  Next you will need to modify your code to write to and read from that File Geodatabase instead.  From the code I have seen that would be modifications to the following: The output featureClass when doing the geocoding would look something like this now: String outputFC = @"C:\geocoding\redlands\GeocodingResults.gdb\redlands_addr_geocoded"; Also when getting the geocoded featureClass you would need to change this to open the FGDB instead: IWorkspaceFactory2 workspaceFactory = new FileGDBWorkspaceFactoryClass() as IWorkspaceFactory2; IWorkspace workspace = workspaceFactory.OpenFromFile(@"C:\geocoding\redlands\GeocodingResults.gdb", 0); That should be it. Brad ... View more

Elizabeth,   Sorry, FGDB is short or internal slang for File Geodatabase.  Are you required to use Shapefiles or can you write out a geocoded points to a newer type of format?  If you can write the geocoding results into a File Geodatabase instead of a Shapefile, you might get rid of your locking issue.   Brad ... View more

Elizabeth, You released the IGeoProcessor COM object, is that what you are saying?  Have you tried using a FGDB instead of a Shapefile?  I have test code that geocodes a table, counts the geocoded features and then deletes the result and I have no locking issues so I don't think it is the GP.Execute() code that is doing this.  It might be time to call tech support if you are still having issues.  Maybe a tech support SDK specialist will have some additional suggestions for you. Brad ... View more

Elizabeth, I don't know if this will fix it but you can give it a try.  At the end of some of my test code, I do the following for a lot of the ArcObjects COM objects to clean them up so that they are not getting held onto by lazy .NET garbage collection. if (workspace != null) { System.Runtime.InteropServices.Marshal.ReleaseComObject(workspace); workspace = null; } if (ocatorWorkspace != null) { System.Runtime.InteropServices.Marshal.ReleaseComObject(locatorWorkspace); locatorWorkspace = null; } Then I call into this helper method I created: cleanupCOM(); Here it is: public void cleanupCOM() { do { System.GC.Collect(); System.GC.WaitForPendingFinalizers(); } while (System.Runtime.InteropServices.Marshal.AreComObjectsAvailableForCleanup()); CoFreeUnusedLibraries(); } You can try doing that for the interfaces like IWorkspaceFactory2, IWorkspace, IFeatureClass, etc.... Brad ... View more

Elizabeth, Maybe try adding quotes around the field name "Status" like this. qf.WhereClause = "\"Status\" = 'M' OR \"Status\" = 'T'"; I am to 100% sure but I found a link to the IQueryFilter doc that states "If you are querying data in a file geodatabase, shapefile, dBase table, coverage, INFO table, then field names are enclosed in double quotes:" Brad ... View more

Elizabeth, You got me on this one.  I am not sure what that error means at all.  This is out of my area of expertise. Brad ... View more

Elizabeth, That is pretty simple.  After the GP.Execute() code, just add the following: IWorkspaceFactory2 workspaceFactory = new ShapefileWorkspaceFactoryClass() as IWorkspaceFactory2; IWorkspace workspace = workspaceFactory.OpenFromFile(@"C:\geocoding", 0); IFeatureClass featureClass = (workspace as IFeatureWorkspace).OpenFeatureClass(@"redlands_addr_geocoded"); ITable geocodedTable = featureClass as ITable; IQueryFilter QF = new QueryFilterClass(); QF.WhereClause = "Status = 'M' OR Status = 'T'"; int numGeocodes = geocodedTable.RowCount(QF) This will give you only the matched and tied geocoded records.  If you just want to get a total count of the records including unmatched records, just pass in null instead of QF to RowCount(). Brad ... View more

Elizabeth, I am not sure what you are asking for here:  "So is there a way I can get a count of the number of calls that were created?" Do you want to know how many records are in the input CSV file or how many geocodes there are in the geocoded featureClass or something else? Brad ... View more

Elizabeth, Somehow I missed that.  What you should do instead is use the Standardize Addresses tool to break the input dataset (VernonCountyMO_Addresses.shp) single field address (StreetName) into its components and then build a Single House locator off of that data. After that, you will have a Single House locator off of the new dataset.  You should then have "Street" and "City" as your input locator field names (the first name in the field mapping) and the second field in the field mapping would be the name of the field in your CSV file. You will notice that the geocoding will be much better as well because the Single House locator style allows for missing components, misspelled words, and other flexibility that the Singe Field style does not because it is an exact match locator.  The single field locator style is really for assets or something that has a unique value. I think the reason it is failing right now is because the Single Field locator only takes in a Single Field for input. Brad ... View more