|
POST
|
Thank you. No, there haven't been any schema changes. I did use those tools to create and rebuild my locator.
... View more
12-03-2024
12:29 PM
|
0
|
0
|
2439
|
|
POST
|
Thanks for your reply. Well, since we have to stay on Server 11.3 for the foreseeable future, we don't want to use Pro 3.4 yet, since 3.3. is the one that's officially compatible with Server 11.3. But I can keep that idea in mind in case we want to at least test it out, like you said, just in case it provides any interesting information.
... View more
11-26-2024
09:59 AM
|
0
|
0
|
2514
|
|
POST
|
I kept digging into this and discovered that the warning was accurate - there really were unique ID fields mapped to all of the "join" role fields, for all of our address locators. Yet no one had done it. We do not even use alternate name tables for our address locators, which is what those fields are for. My guess is that this happened automatically in the software somewhere between Pro 2.7/2.8 and 3.0, when Pro gained the capability to have locators with alternate name tables joined to them (we have had the same address locators since around Pro 2.8 or so). And then the fields caused this warning to occur in 3.3. Anyway, it looks like we will have to re-create all of our locators anew with Pro 3.3, because it is not possible to edit out the fields mapped to those join ID role fields, even though the documentation says the configurations are editable. If anyone else is experiencing this situation, I'd be very interested to hear about it. I'm curious if we are the only ones or not.
... View more
11-26-2024
09:34 AM
|
0
|
0
|
1006
|
|
POST
|
I've discovered that, since upgrading to Pro 3.3.2 from 3.0.3, rebuilding address locators takes about 20 minutes, whereas before, it took about 1 minute. This is the case both with a Python script and when doing it manually. It even happens when rebuilding an address locator I created from scratch in Pro 3.3.2 (as opposed to the existing locators I had made with Pro 3.0.3). This worries me because I'm wondering if it means something is wrong...? Does anyone know why this is happening? Has anyone else experienced this behavior? Thank you! Allen
... View more
11-26-2024
09:27 AM
|
0
|
12
|
2951
|
|
IDEA
|
Hello @urquidid , Thanks for your comment. No, I haven't found a solution, although I haven't dug into it in a while. Thank you for the link - I will read up on it and see if it's something we'd want to use. Thanks! Allen
... View more
11-26-2024
08:45 AM
|
0
|
0
|
738
|
|
POST
|
Dear Esri, Has this been changed in the November 2024 ArcGIS Online update? I'm seeing behavior that makes me think you can now zoom to a feature even when using a map image layer, rather than a feature layer. Can I trust my eyes? ha I read all the documentation (at least all that I could find) about the update but didn't see anything about this.
... View more
11-21-2024
04:21 PM
|
1
|
0
|
1623
|
|
POST
|
I recently upgraded Pro from 3.0.3 to 3.3.2. Now, right after upgrading, I am suddenly having a problem with rebuilding address locators. The problem is that rebuilding takes 30 minutes; it used to take under 1 minute. I got Warning 003106: "The 'Point Address' dataset has a unique ID field mapped to the 'Address Join ID' role field. This join strategy is not optimal and may lead to degradation in performance and increased locator size." I had not changed anything in the locator's configuration in the meantime. The locator was working perfectly before this Pro upgrade. Why is this happening?? I mean, why is the version of Pro causing this to happen now? Is this a bug or a real problem with my locator?
... View more
11-15-2024
10:58 AM
|
0
|
3
|
1112
|
|
POST
|
I ran into this, with the same tutorial, also. I hope Esri adds a way to resize the chart's legend, like a way to specify the legend height as well as the width, or a drag bar to resize the legend. I'd be sad if I ran into this issue while creating a real app.
... View more
11-12-2024
02:11 PM
|
0
|
0
|
2540
|
|
POST
|
I have been having this problem, and I found this bug documentation from Esri: https://support.esri.com/en-us/bug/create-locator-returns-the-error-message-error-002777-t-bug-000153036 My path does have periods in it, in the server name, which includes "name.dmz". So I guess that's the problem. The bug was found in Pro 3.0.2 and fixed in 3.1. I am using 3.0.3. Time to upgrade!
... View more
10-22-2024
01:39 PM
|
0
|
0
|
2353
|
|
POST
|
Hi there, I'm sorry you're having this problem, and sorry to say I have no idea why this would be happening! Perhaps Esri Support could help troubleshoot it with you? Good luck! Allen
... View more
10-17-2024
08:13 AM
|
0
|
0
|
3491
|
|
POST
|
Hi there, It would help to see your code in the code-style font/format. You can do that by clicking the button to expand the toolbar (when you are writing a reply here), then click the </> icon to insert code. I see that you are using the variable "thisFD" for arcpy.ListFeatureClasses(). For me, this variable name could cause a little confusion and obscure a possible reason for your error. I would expect "thisFD" to represent the feature dataset name or object, so I would not expect it to end up as None, because how would you have a feature dataset name for a nonexistent feature dataset? But since the variable is representing the list of feature classes within the dataset, you could have a feature dataset with nothing in it. So the variable could represent None (no feature classes). That's where I find it could cause confusion. Personally, I find it helpful to use variable names that very literally indicate what they represent. I think if the variable name was something like "fc_list", it would very clearly indicate what it represents, and it would indicate that it could be empty/None, because a list can be empty. I agree with what the previous person said, to add handling to deal with an empty list.
... View more
08-28-2024
09:30 AM
|
0
|
0
|
2831
|
|
POST
|
Hi, Have you made sure that your connection file is pointing to the version?
... View more
08-20-2024
09:28 AM
|
2
|
3
|
2362
|
|
POST
|
Hello, I am unable to access or find label placement settings for a polygon layer in the "new" Map Viewer. The documentation doesn't seem to indicate that placement is only available for line layers, so I am confused about why I am not able to access placement. Here is what I see in the label properties: Any help would be much appreciated! Thank you!
... View more
07-05-2024
01:26 PM
|
0
|
1
|
3445
|
|
POST
|
I'm also facing this issue with the "new" Map Viewer. I have a layer in my map consisting of cities, as polygons. The labels are only placed on the center of the polygon. If I zoom into a corner of the city, even a large area like a couple of entire neighborhoods, the city label does not appear there at all - it is off-screen in the center of the city. That is really not ideal; the main purpose of my map is to show users if a certain location is in a city, and which one. I can achieve this through symbology, pop-ups, and perhaps special functionality in an app I will use the web map in. But it's pretty basic to have a city label show up if you're looking at part of the city. I hope Esri will make this happen soon.
... View more
07-05-2024
01:17 PM
|
4
|
0
|
1085
|
|
POST
|
I've run into this issue myself. I discovered this piece of Esri documentation that says that zooming to a feature is only available for feature services. In my own map, in the "new" map viewer, I am unable to zoom to features in a layer that's from a map service I published. I added this map service, which contains 4 layers, to the map by adding the whole service as an ArcGIS Online (AGOL) content item, and then adding this whole service / content item into my map. Not one layer at a time. However, I can zoom to features in a layer that was brought into ArcGIS Online as an individual layer; the service it is part of contains many layers, but these layers were brought into AGOL as one layer per content item, not one service per content item. So it would appear that in order to be able to zoom to a feature via the attribute table in the new map viewer, the layer has to be its own separate content item in AGOL, rather than part of a content item for a whole map service. This feels pretty inconvenient to me.
... View more
05-16-2024
11:22 AM
|
0
|
1
|
1891
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 09-30-2025 05:49 PM | |
| 1 | 09-30-2025 03:01 PM | |
| 1 | 09-30-2025 05:42 PM | |
| 1 | 11-01-2023 11:39 AM | |
| 1 | 11-21-2024 04:21 PM |
| Online Status |
Offline
|
| Date Last Visited |
a week ago
|