POST
|
You do run into duplicating data and would want to have IDs for the duplicates to collapse them as described in the following topic, https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/collapse-duplicate-features-in-the-data.htm. The other option is to create a PointAddress role locator with the address point layer and a PointAddress role locator with the state polygon parcel layer and then combine them in a composite locator. If the address point layer has the parcel ID you could set that as a custom output field, the same for the parcel based locator, then when you geocode the result will have the parcel id in one of the output fields.
... View more
4 weeks ago
|
1
|
0
|
143
|
POST
|
@JessMiller1 What locator was used to geocode your table? If you are using a custom locator based on reference data that has a projection of NAD_1983_StatePlane_North_Carolina_FIPS_3200_Feet, then the locator will output the result in that coordinate system. The coordinates in your screenshot are US Feet. There are a few things you can do : 1. In the Geocode Addresses dialog specify a different coordinate system for the output. 2. If using the Geocode Addresses geoprocessing tool, click environments button and expand output coordinate system and specify a geographic coordinate system 3. You could use the Project geoprocessing tool to reproject the geocode result to a geographic coordinate system like WGS 1984, then use the result in the Add XY Coordinates tool.
... View more
02-16-2024
10:14 AM
|
0
|
0
|
101
|
POST
|
@GeoGuy99 What format are you trying to export the shapefile to? Are you getting any errors in Pro when attempting to export the shapefile?
... View more
02-16-2024
07:44 AM
|
0
|
0
|
42
|
POST
|
@RobertCox87 One option is to start with a new project that contains the data you need and add the USA locator to the project, then create a project template. When you start a new project select the template you created and the USA locator will be available.
... View more
02-16-2024
07:38 AM
|
0
|
0
|
34
|
POST
|
@SarahHurley1 The issue is with how the locator is created. Is the purpose of the locator to search for an address such as '380 New York St, Redlands, Ca' or to search for the parcel ID? The Parcel role is designed to search the parcel ID (APN, PIN), parcel ID + address or just the address of the parcel. If the value in the parcel address field is '380 New York St' in your data you will want o use that field as the input field in the Split Address Into Components tool. Then use the output as input to the Create Locator tool. If you do not have a parcel ID in this data, after using the Split Address Into Components tool, the output can be used to create a locator with the PointAddress role.
... View more
02-16-2024
07:26 AM
|
1
|
2
|
178
|
POST
|
Which tool was used to create the locators that are in the composite? The bug is related to locators based on polygon features that are published as services and not zooming to an appropriate scale or extent in the Map Viewer compared to the local composite in ArcGIS Pro. It was reported at 10.9.1. If you are up to date on maintenance you should be able to search for the bug number in myesri or the Support site. The only workaround found was to convert the polygons to points and rebuild the locator with the point data, but this might not be feasible for some. polygon based locator published as a service and used in ArcGIS Pro and the map not
... View more
02-01-2024
11:23 PM
|
0
|
0
|
171
|
POST
|
In order to rename the "locator" in the web map rename the layer in the Contents pane in ArcGIS Pro before configuring it for search and publishing the map to the portal. Regarding the zoom behavior, were you experiencing this with a local locator in ArcGIS Pro or with the locator published to Enterprise portal used in the web map or? If published was the published locator used in ArcGIS Pro. If it was published was it a single role locator that referenced polygon data or a composite locator that consisted of locators based on polygon data? I'm asking to try and figure out if you are running into BUG-000162951, which is not reproducible with Enterprise 11.2.
... View more
01-31-2024
07:45 PM
|
0
|
2
|
184
|
POST
|
Also, have you considered configuring the polygons for search, then publishing the map from ArcGIS Pro as a web map to your Enterprise portal and using the feature service to search in the web map? https://enterprise.arcgis.com/en/portal/latest/use/configure-feature-search.htm
... View more
01-29-2024
02:59 PM
|
0
|
4
|
203
|
POST
|
@MicBry When you build a locator and search addresses or places you will always get a point as a result, regardless of the geometry of the data used to build the locator. If polygon features were the reference data for the locator, the centroid of the polygon is used. You may want to try adding the coordinates for the extent of the polygon features, then using those coordinates when building the locator to see if you get better results when searching for the zip code for example. The following topic describes this and when building the locator you need to map the Min X, Max X, Min Y, and Max Y locator role fields. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/fundamentals-of-zooming-to-geocode-results.htm
... View more
01-29-2024
02:41 PM
|
1
|
0
|
204
|
POST
|
@JoshBillings You should rebuild or recreate the participating locators before overwriting or republishing the composite service. The following topic describes the workflow for Pro, but the same concept applies to ArcMap if the participating locators were created with the Create Address Locator tool in ArcMap or ArcGIS Pro 2.6 and earlier. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/keep-your-locator-up-to-date.htm#ESRI_SECTION1_12AA5C7DF3B44701B13DD015F6D1BA02
... View more
01-29-2024
02:30 PM
|
0
|
1
|
140
|
POST
|
@ChelseaRozek The new locators do not have an option to specify additional recognized input field names. I'd suggest submitting/posting an enhancement on Ideas thread. Since it's not possible to add more recognized field names for the input field names of the locator, you will have to manually select the field that contains the data (address, parcel PIN) that you want to geocode in the table when using the Geocode Table or Geocode Addresses tool. If you build a multirole locator with PointAddress and Parcel role, the input address field is always going to be 'Address' in the batch geocoding tools. If you wanted to add recognized field names for input fields, so that Geocode Addresses tool automatically populates the 'Address' input field, create a composite locator that contains individual role locators or a multirole locator and modify the recognized field names for 'Address'. I would also update Region to add 'State' and Postal to add 'zip' , 'zipcode' , and 'zip5', or whatever field name is used for the postal values in your data.
... View more
12-21-2023
08:48 PM
|
0
|
0
|
318
|
POST
|
@ChelseaRozek If we use the data from my reply on 12/3/2020 and created a multirole locator that include PointAddress and Parcel role, the input table could look like the following. Then you could use multiple input fields and map Address, City, State, Zip or use single input field and map FullAddress. You could even use multiple fields and just map FullAddress to Address. The same would go for your composite. In both cases you don't need a ParcelID field for input, the parcel is considered the address and does not need it's own input field. If you used the Locate pane to search for the address or parcel PIN you will get candidates back. Is this more clear with the illustration? In the Geocode Addresses tool the first field to map is called "Address or Place", so the field that you map to it can contain only addresses, only places, or a mix of addresses, places, asset IDs, etc.
... View more
12-08-2023
11:27 AM
|
0
|
2
|
349
|
POST
|
@ChelseaRozek I think a better solution would be to build the multirole locator that included point addresses and parcels, then set up the table you are geocoding with a single field that contains the full address (380 new york st, redlands, ca) or Parcel ID and use this single field when geocoding the table. You can also use an address field that contains the ParcelID or address (380 new york st) and use the city, state, zip fields, which could be empty for the Parcel ID records. Does that make sense? The following image shows different table formats.
... View more
12-06-2023
04:07 PM
|
0
|
4
|
355
|
POST
|
To clarify, for reverse you want an address returned and not the xy? When I interactively reverse geocode in ArcGIS Pro I get the xy coordinate returned as part of the result whether it's a StreetAddress or StreetName match for reverse. Are the REST requests from using the REST endpoint or requests in applications? Are you able to provide an example of the app using the REST requests?
... View more
12-04-2023
11:26 AM
|
0
|
1
|
604
|
POST
|
Locators do not support wild card searches, that is more of a query than geocoding. Suggestions provide candidates based on the tokens (strings) that are typed at the beginning like an autocomplete of typing the beginning of the value in the data. What you have described is more like what is described in the following topic for layer search. The layer used in configured layer search can be shared as part of a web map and used for searching using the contains search mode. - https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/find-places-on-the-map.htm - https://enterprise.arcgis.com/en/portal/latest/use/configure-feature-search.htm Another option is to create multiple Feature or POI locators based on the zone_id, site_id, site_name, description fields and add them to a composite locator. For the description field, you would need to type the exact string or the beginning of the string to get find results or suggestions. The description could be added as a custom output field for the POI locators and this value would be returned in the geocode results. Custom output fields were added to the Create Feature Locator tool in ArcGIS Pro 3.2.
... View more
12-04-2023
10:19 AM
|
0
|
0
|
80
|
Title | Kudos | Posted |
---|---|---|
1 | 4 weeks ago | |
1 | 02-16-2024 07:26 AM | |
1 | 01-29-2024 02:41 PM | |
1 | 09-02-2020 11:07 PM | |
1 | 06-27-2023 01:02 AM |
Online Status |
Offline
|
Date Last Visited |
2 weeks ago
|