|
POST
|
I'm trying to run an interpolation of well measurements using the ArcGIS Pro 2.2.3 Geostatistical Wizard (specifically to interpolate the depth in feet of floating contaminants). I've used the stand-alone IDW tool in both ArcMap and Pro in the past without issue but wanted to try the Geostat Wiz to streamline the process. The interpolation seemed to run fine but the resulting symbology isn't showing correctly: Notice in the screen capture that the identify tool shows the correct interpolated value at the blue dot (0.88) yet the symbology shown for the whole area is the -0.2 to 0.14 class range. When I export to a feature class this problem persists, resulting in useless contours that show much lower values than an exact interpolator like IDW could possibly produce given the input values. Am I missing a key setting/explanation or is this a bug? I can't see why this behavior would make sense. *7/26/2019 Update* I'm still seeing this problem in Pro 2.3.2. Has there been any movement to fix this problem in new releases? *1/24/2020 Update* Pro 2.4.2, still no response or resolution...
... View more
01-28-2019
01:57 PM
|
0
|
7
|
2733
|
|
POST
|
Thanks for your response Wendy, I'm glad to hear the capability to combine annotations is on the docket to be added. It is good to know that the feature class name and text symbol have an impact on the output annotation classes. In my case though I believe the underlying problem is that I mistakenly checked the Combine Annotation Classes option in the Append Annotation Feature Classes tool. With that option unchecked, my combined annotations did create separate annotation classes for each input. It took some finagling to figure out how to change the class names (Annotation Feature Class Properties in catalog) but otherwise seems to work fine. This whole process is still more steps and work than it was in ArcMap, but at least it's workable. As an improvement over ArcMap though, I was happy to see that the tool allows annotations with different extents to be combined and will automatically adjust the font/symbol size of the different class extents to fit into a single annotation feature class. (ex: reducing the font of a 1:180 class from 12 to 7 so that it shows correctly despite the annotation feature class having a 1:240 extent).
... View more
01-03-2019
11:42 AM
|
0
|
0
|
3542
|
|
POST
|
I'm having trouble getting ArcGIS Pro to display different annotation classes within a single feature class. A common workflow for me in ArcMap involved converting multiple sets of labels to a single annotation feature class (I would create it and then append new subtypes to it). I'm trying to mimic this workflow in Pro by using the Convert Labels to Annotation tool and then the Append Annotation Feature Classes tool to merge the multiple different annotations into a single file. This worked but now instead of the different subclasses showing up in the contents pane, there is only the Default shown. I've tried field calculating the AnnotationClassID field to match the subclass codes in the SymbolID field and shown in Annotation Feature Class Properties, and have also tried creating Subtypes based on the SymbolID or updated AnnotationClassID fields; no matter what only Default shows as a togglable option in the Contents pane. I realize I could work around this by using definition queries, but it was so easy to switch between different annotation subclasses in ArcMap and I don't see why this option isn't available in Pro. I've attached a screenshot of the window showing the issue. P.S. If this is a bug, an even better fix would be to just have the subclasses be maintained when using the Append Annotation Feature Classes tool, or to allow a single annotation to be created with the Convert Labels to Annotation tool.
... View more
12-18-2018
02:24 PM
|
1
|
5
|
3915
|
|
POST
|
The layout file was based on an mxd import. I just recreated the initial problem in an mxd-based layout in Pro 2.2.3. When I inserted a new Legend, the column displayed properly down the center; then I discovered that the issue seems to be related to the legend title. When I don't show the Legend title a single column will center properly. However if I show the title then a single column will always left align.
... View more
12-14-2018
01:01 PM
|
2
|
8
|
5917
|
|
POST
|
Thanks a lot Tom, that's exactly the type of solution I was looking for! Seems kind of obvious in retrospect but didn't occur to me for some reason. Also great to see that it does an even better job than ArcMap of keeping the 1 inch scale once I set the size, even when that means dividing it into 5s (i.e. 75ft for 1:900). Thanks again.
... View more
11-20-2018
11:59 AM
|
0
|
1
|
6708
|
|
POST
|
I'm using ArcGIS Pro 2.2.3 and want to set my layout scale bar to have a fixed length (1 inch) regardless of the map extent. The Adjust Division Value resize behavior usually worked in ArcMap (it would round to the nearest 10 but otherwise would keep the length static), but in Pro it always resizes smaller than I want. For example, my current map has an extent of 1,680 which means a scale of 140 feet should be exactly 1 inch. When I manually set the length to 140 though and then set the behavior back to Adjust Division Value, it drops the length to 130 feet (see attachment): It does this regardless of the chosen extent. Does anyone know a way to resolve this issue?
... View more
11-16-2018
12:35 PM
|
0
|
3
|
7236
|
|
POST
|
Thanks for the reply Mitch. The placement and Size & Position tabs seem to offer the same functionality. It's strange cause when I set the position to the center or bottom rows the contents adjust accordingly, but they won't shift right no matter whether I set the center or right columns (see screenshots). Bottom-Left Alignment: Top-Right Alignment:
... View more
09-25-2018
01:50 PM
|
0
|
13
|
5917
|
|
POST
|
I've been working with Pro for a few months now and recently ran into an issue after upgrading from 2.0 to 2.2.2. While the legend items used to center when there was only 1 column, now they always align left. I've tried every option I can think of to resetting "Size & Position" to top center, to setting Text Symbol - Position to center horizontal alignment. I've included two screenshots, the first of a map legend from 2.0 and the second of the same map legend in 2.2.2 with no changes made to any layout/legend settings. If this is a new setting I can change, I'd really appreciate anyone who can point it out. Thanks.
... View more
09-25-2018
01:26 PM
|
0
|
17
|
9508
|
|
POST
|
I'm putting in a request for our engineering systems department to publish Pro 2.2.0, so hopefully I'll have access to it in the coming days. Unfortunately since all our software is accessed through a central location I can't use the latest version on any company computer until they upgrade it, but hopefully it won't take long. It's just as well since I'm looking forward to some of the new 2.2 features like pause drawing. Thanks a lot for your help.
... View more
07-31-2018
09:54 AM
|
0
|
0
|
2576
|
|
POST
|
If you think the freezing will resolve itself by upgrading to 2.2.0 I can try to push that, though my company's software setup doesn't give me direct control of software versions/updates so this may take some time (ArcMap & Pro are run through a mixed local/remote setup).
... View more
07-31-2018
09:40 AM
|
0
|
2
|
2576
|
|
POST
|
My team often has to create data "post-it note" maps for sample results at remediation sites. We create labels using cursor-based python expressions that pull results for each sample location from a separate geodatabase table. We then convert these labels to annotation feature classes and position them around the map: We're trying to switch to Pro but are having trouble accomplishing this critical task in Pro (using Pro 2.0.0). The only tool I've found to move annotation without also moving the leader line is the Annotation Modify Feature tool. This works but it can be tedious to move the annotation instead of resizing or text editing by accident since a single click activates all 3 capabilities. Editing also seems even slower than in ArcMap, which I was surprised by given how much faster Pro is supposed to be (we also edit with an activated map in a layout since otherwise we can't see the layout map extent). Finally, Pro consistently freezes while trying to move annotations on the map, forcing me to restart Pro and lose any unsaved edits (the processing wheel spins just spins forever). *Edit* I should also note that when Pro crashes or freezes I've twice had it corrupt the annotation feature class I was working with when it crashed. Given that we often store numerous subclasses of post-its within a single feature class, this issue could result in the loss of a lot of work. Does anyone have suggestions for editing annotations in Pro that might help? I'd really like to switch to Pro but don't think we'll be able to unless we fix the issue of Pro freezing. I'd really appreciate any advice for working with annotations in Pro.
... View more
07-31-2018
08:51 AM
|
1
|
8
|
2973
|
|
POST
|
Thanks for the suggestion Robert. In this particular case I was trying to snap with the measure tool which can't be used with classic snapping, but this is still a good strategy to keep in mind for when this happens again. I tested it and classic snapping does indeed work on this map for operations like creating a new feature. I guess overall I'm going to assume that this is a case of ArcMap snapping being overloaded by my feature class being joined to 2-3 csv tables (the joined tables are also referenced for symbology and labeling). In the future it might be a good idea for me to export these layers as a shapefile or feature class to improve performance. Thanks for all your suggestions!
... View more
07-26-2018
11:41 AM
|
2
|
0
|
7188
|
|
POST
|
Thanks for the suggestion Michael. Testing in Pro just now, snapping with the measure tool took a few seconds to engage for most of the features but it did work. I was hoping to identify a fix in ArcMap though since we haven't switched over to Pro yet. We're hoping to switch over to Pro soon but still have some workflow and learning-curve obstacles before then. The file geodatabases are stored on a server but I'm hoping this isn't much of an issue since the server is in the same office I am. I don't tend to have connection issues using it for all my other GIS work.
... View more
07-24-2018
11:52 AM
|
0
|
0
|
7188
|
|
POST
|
Thanks for your reply Luba. In my case we use file geodatabase feature classes for everything. Based on reading the ArcMap Overview of Spatial Indexes page and looking in the feature class properties, I believe spatial indexes for feature classes are created and updated automatically. Please let me know if this is incorrect. For the map in question, I found that turning off the layers with table joins allowed snapping to function normally. Removing the joins also re-enabled snapping. Is it possible that snapping fails when a visible feature class has an active join? This is frustrating in this case since these joined features are what I wanted to snap & measure, but knowing this could help me avoid the problem in the future. Though as stated in my original post, I've also experienced this issue in the past with non-joined feature classes and had to resolve it by turning off most of the mxd layers.
... View more
07-24-2018
10:44 AM
|
0
|
2
|
7188
|
|
POST
|
I'm using ArcMap 10.5.1 and have been having issues with snapping not engaging for some time. I will have snapping engaged in an edit session and try to use it with the measure or create feature tool, but snapping won't engage. When I move the mouse to try to engage it, it switches to the hourglass for a moment before continuing not to snap. I've tried modifying the snapping tolerance and the snapping types (edge, vertex, etc.) to no avail. Sometimes zooming in or out will suddenly allow snapping to work, but when I pan/zoom again it won't work. The only solution I've found to this so far is to reduce the number of layers displayed (turning off the basemap layers group, topographic lines, etc.), but I'm working with a map now that I can't get to work even after turning off all unused layers. This map does use two point feature classes with multiple tables joined to them. I assume the main issue is that the snapping function is being overloaded, but I just finished another map using the same layers without snapping issues even without turning off extra basemap layers. Does anyone else experience this issue, and has anyone identified the cause of the problem or a solution? Thanks.
... View more
07-24-2018
08:30 AM
|
1
|
6
|
12790
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 12-18-2018 02:24 PM | |
| 1 | 02-13-2019 10:34 AM | |
| 1 | 06-06-2019 11:17 AM | |
| 2 | 09-17-2021 06:01 AM | |
| 2 | 12-21-2020 09:17 AM |
| Online Status |
Offline
|
| Date Last Visited |
10-16-2025
07:59 AM
|