|
POST
|
The new style locators are a complete paradigm shift so you'll need to sort of wrap your head around that. In the graphic below I'm using a multi-role locator that has a point address role and a street address role in it with the locate tool. If I enter and address and it matches, I can then click details to see what role the entered address matched against. In the first case the address entered matched against as a StreetAddress which equates to matching against my street centerlines data. In the second case the entered address matched as a PointAddress which equates to matching against my site address point data.
... View more
05-27-2021
08:51 AM
|
1
|
0
|
4439
|
|
POST
|
A Global ID and OBJECTID are similar in that the database assigns the values and if a a record is deleted, the Global ID and/or OBJECTID are 'retired' and not reused. They are different in that there is no sequence (that I can tell) to a Global ID as there is to an OBJECTID. I consider the OBJECTID to be a database sequence that is internally controlled. The ESRI Global ID does need to be present for Attribute Rules to function (as I mentioned in your other post). They are also used as the key between parent and child in database replication. However, you mention that you are using an ArcMap Extension and you need to know that once you apply attribute rules to a feature layer, it is no longer available to ArcMap.
... View more
05-27-2021
08:20 AM
|
0
|
0
|
4469
|
|
POST
|
Are you talking about a GUID type field or an actual Global ID? They are similar but very different. A global id is assigned and maintained internally by the database. A GUID type field is similar in format but can be calculated by the user. I've never been a huge fan of Global IDs as a means for relationship classes and/or unique identifiers as they will change if a database object (feature) is moved to a different database. What I do like though for unique identifiers is a database sequence. You can deploy them in concert with an attribute rule and if the feature changes databases, the value will persist.
... View more
05-27-2021
07:20 AM
|
2
|
1
|
4483
|
|
POST
|
Can't tell you why but yes, for attribute rules to function your feature layer must have global ids.
... View more
05-27-2021
07:14 AM
|
1
|
0
|
4939
|
|
POST
|
I'm not familiar at with VB any more and not too familiar with the tools now available in Network Analyst, but if you look at the online help for Update Analysis Layer Attribute Parameter and click on the Python tab, it provides the parameters the tool is expecting. I don't know if that'll help you or not.
... View more
05-25-2021
01:39 PM
|
1
|
1
|
3681
|
|
POST
|
Is there a question here or just a rant? Does your application load when you have a reliable internet connection? Could it be related to your wireless carrier?
... View more
05-25-2021
10:20 AM
|
0
|
0
|
2596
|
|
POST
|
I apologize for not explaining what @JayantaPoddar did. Create Address Locator was deprecated at ArcGIS Pro version 2.6. It did have it's glory days: I dispatched countless 9-1-1 calls for years using the old style locators. However, the new style locators have gained a solid maturity level and truth be told, I don't miss the old ones at all...
... View more
05-24-2021
02:17 PM
|
0
|
0
|
4238
|
|
POST
|
@GuillermoMartinez-Espinosa ; how are you searching for the tool? You should be able to click first on the Analysis Tab, then select Tools and then search in the Geoprocessing Pane for Create Locator:
... View more
05-24-2021
01:49 PM
|
0
|
3
|
4252
|
|
POST
|
ArcGIS Pro 2.7.2 Just started using the Create Composite Locator tool and now I am scripting it in python to automate the process. My python works, but I don't understand the field mapping portion of the tool and subsequently what I am providing to my script. Here is a snapshot of the tool and parameters: I purposely whittled down all the various input fields that appear by default, since I don't understand what they provide the tool. When creating python scripts for geocoding, I always use the tool history details as a means to provide me the parameters of a successful tool run: The resulting function in my script creates the composite locator just fine: def compositeLocator():
addressLocators = r"N:\GIS\Geocoding\NewGeocoding\MsdMultiRoleLocator.loc MsdLocator;"\
r"N:\GIS\Geocoding\NewGeocoding\NonMSDMultiRoleLocator.loc NonMsdLocator"
fieldMap = r'Address "Address or Place" true true false 100 Text 0 0,First,#,N:\GIS\Geocoding\NewGeocoding\MsdMultiRoleLocator.loc,Address,0,0,N:\GIS\Geocoding\NewGeocoding\NonMSDMultiRoleLocator.loc,Address,0,0'
selectionCriteria = "MsdLocator #;"\
"NonMsdLocator #"
outLocator = r'N:\GIS\Geocoding\NewGeocoding\CityWorksLocator'
arcpy.geocoding.CreateCompositeAddressLocator(addressLocators, fieldMap, selectionCriteria, outLocator) My question is this: in the fieldMap variable what are the various arguments such as: Address "Address or Place" true true false 100 Text 0 0,First,#,(etc,etc, etc..) Is there any documentation on this? I haven't stumbled upon any as of yet. @BradNiemand @ShanaBritt
... View more
05-24-2021
09:22 AM
|
0
|
2
|
2930
|
|
POST
|
Not sure if this will help or not: https://stackoverflow.com/questions/46818040/how-to-work-with-german-umlaut-characters-in-python
... View more
05-20-2021
08:38 AM
|
0
|
0
|
2036
|
|
POST
|
@AnnaStam I'm not aware that this has been fixed, and I'm using 2.7.2.... @BradNiemand or @ShanaBritt , any comments on this?
... View more
05-19-2021
10:11 AM
|
0
|
0
|
4013
|
|
POST
|
Don't delete the post! You aren't the first nor the last to make that very simple mistake. Enjoy another cup of coffee!
... View more
05-18-2021
08:57 AM
|
2
|
0
|
8834
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 10-11-2018 07:12 AM | |
| 1 | 05-17-2021 11:18 AM | |
| 1 | 06-29-2021 11:42 AM | |
| 1 | 07-05-2012 07:49 AM | |
| 1 | 09-03-2016 06:16 AM |
| Online Status |
Offline
|
| Date Last Visited |
05-19-2026
11:56 AM
|