|
POST
|
Upon further investigation into the behavior, it is the M values that is causing the problem and not the Z values. You should be able to run the feature class to feature class tool and just drop the M values, then create the locator based on the new feature class and maintain the Z values if you need them for display in 3D workspace. The default extent of the M values are out of range or are not valid ranges and is what is causing the output not to display on the map.
... View more
06-24-2019
04:09 PM
|
0
|
0
|
2482
|
|
POST
|
Branden: Did the filter work in ArcMap 9.x or in ArcMap 10.4.1 with a 9.x locator? You have the option to create your own query of just the tied results and once the query is created it will be available to you in subsequent sessions of ArcMap. This query would show all the records that have a status of tied or tied with a score > 0. You could also create a query of Status = 'T' AND Score = 100 The other option for you is to set the 'Match if best candidates tie' setting in the locator properties to 'No', which means you will only have matched and unmatched addresses to review in the Interactive Review/Rematch dialog. NO records in the geocode result will have a Status of 'T' in the attribute table, which means you'd have to review all of the unmatched. Match if best candidates tie If an address locator finds two or more reference features that have the same highest match score but the geometry of the features is different, you can specify whether to match an address arbitrarily to one of these features. Use this setting to specify whether to arbitrarily match these addresses or leave them unmatched. In either case, you can review addresses with tied candidates whether or not they are matched during the interactive review process.
... View more
06-24-2019
04:05 PM
|
0
|
0
|
2325
|
|
POST
|
My understanding is that ArcGIS 2.4 is targeted to be available by the User Conference.
... View more
06-21-2019
04:15 PM
|
0
|
0
|
2820
|
|
POST
|
William: I am able to reproduce this behavior in 2.3.3, but not in ArcGIS Pro 2.4. You are correct, user defined queries that are maintained in ArcMap are not available in the same way as in Pro. We do have this item in our backlog of issues to address in a future release. The way to get around it is to create your custom query when the Select Layer By Attribute tool opens and click the Save button to save the query as an expression file that you can then load again. You would have to do that for each ArcGIS Pro session. ArcMap stores the reference to the custom ones in the registry.
... View more
06-21-2019
03:14 PM
|
1
|
3
|
2820
|
|
POST
|
Jot: Based on the screenshots provided it looks like you have two different locators that are being used in the Find tool in ArcMap, one of them being a Composite locator (Single Line Input) and the other the Single House locator (Full Address). You would at a minimum need to provide a screen shot of the locator properties of the two locators you've displayed in the screenshots of the Find tool. As well as the Geocoding Options setting in the locator properties.
... View more
06-21-2019
08:37 AM
|
0
|
0
|
1592
|
|
POST
|
1. If you use the locator created in Pro in the Find tool in ArcMap do you get the same or different behavior? I'm trying to narrow down if the issue is the locator or the application. 2. Are the properties exactly the same for the two locators 3. Are you able to provide the locators as locator packages for review with a sample address?
... View more
06-19-2019
10:53 AM
|
0
|
0
|
1592
|
|
POST
|
Grace: Does this behavior only occur when the composite is published to ArcGIS Server 10.3? Does this behavior occur when the composite locator that contains the locators created in ArcMap 10.5 are published to Server 10.5?
... View more
06-19-2019
10:43 AM
|
0
|
3
|
3063
|
|
POST
|
Rickey: It is possible to do what you want, you will likely need to create a new address locator using the Create Address Locator tool based on the US Address - StreetName locator style and add it to your composite locator. The StreetName locator style allows you to search based on street name only and it does not require a house number. What locator styles were used to create the locators that are currently participating in the composite locator you are using as a service in ArcGIS Online? Which tool in ArcGIS Pro did you use to create the locators that participate in the composite locator?
... View more
06-18-2019
06:08 PM
|
0
|
4
|
4099
|
|
POST
|
William: Are you able to provide a screen shot of the behavior in the Rematch Addresses pane? Does the behavior in the Rematch Addresses pane where it becomes blank occur with one of the locators that participates in the composite locator? The screenshot below shows how to get to the location where you can create a Custom Query, which will open the Select by Attributes tool. The upper section of the Rematch Addresses pane should update based on your query. If the query only includes records with an unmatched status, you will only see the 'Unmatched' tab at the top.
... View more
06-18-2019
06:02 PM
|
0
|
5
|
2820
|
|
POST
|
An unmatch button was added to the Rematch Addresses pane to allow you to unmatch matched or tied addresses in ArcGIS Pro 2.4. An option to match all selected records as well as the ability to auto rematch were also added for 2.4. "Click Match All Selected if you have selected a group of records manually or created a selection set based on a custom query and need to match all of the selected records to a single candidate. For example, a group of records contains the same wrong city or postal code and you want to match them all to the same candidate at once. Using Match All Selected will speed up the process of rematching your geocoded feature class." "There are cases when you may want to perform a bulk update of multiple records without going through each one manually. This can be due to changes made to any of the locator properties, such as minimum match score or categories to support. In this case, you can initiate the auto rematch functionality to redo the matching process by clicking Auto Rematch . This will only apply to the selected records if you have selected one of the Predefined Queries, created a selection based on a custom query, or manually selected records in the Attribute Table of the geocoded feature class. If no selection is defined, all records will be processed."
... View more
06-18-2019
12:19 AM
|
1
|
1
|
4224
|
|
POST
|
Can you provide more details such as... The application the locator was created in. The tool used to create the locator? What version of Portal was the locator published to? What is the role or style used for the locators that participate in the composite locator?
... View more
05-29-2019
11:09 PM
|
0
|
0
|
810
|
|
POST
|
Dave: I would suggest the following because of the size of the reference data: Install 64-bit Background Geocprocessing if you have not already, https://desktop.arcgis.com/en/arcmap/latest/analyze/executing-tools/64bit-background.htm Enable background geoprocessing in ArcMap/ArcCatalog Build the locator with the Create Address Locator tool If you have access to ArcGIS Pro, I'd also suggest building the locator with the Create Address Locator tool since Pro is a 64-bit application and would be able to process the data better than 32-bit ArcMap.
... View more
05-29-2019
04:12 PM
|
0
|
2
|
647
|
|
POST
|
David: It is not possible to configure the output label or turn off the country code. However, we will evaluate the issue with "USA" being added to the end of the output label if country code was not part of the field mapping.
... View more
05-29-2019
04:03 PM
|
0
|
0
|
842
|
|
POST
|
Can you provide more details about the problem? What tool was used to create the locator Which application was used to create the locator in? (ArcMap or ArcGIS Pro) Where was the locator stored when it was created? Is the locator that gets created only disappearing in the project or on the file system where the locator was saved as well?
... View more
05-29-2019
12:13 AM
|
0
|
0
|
3008
|
|
POST
|
John, Check out my responses in the following thread. https://community.esri.com/thread/230989-address-locator-106-release-fails-to-locate-intersections-of-numbered-streets#comment-847156
... View more
05-06-2019
11:15 AM
|
0
|
0
|
2605
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 02-08-2023 11:15 AM | |
| 1 | 01-28-2025 09:04 AM | |
| 1 | 06-05-2025 08:01 AM | |
| 2 | 07-14-2025 12:11 PM | |
| 1 | 09-25-2024 12:04 AM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|