POST
|
Try this: https://pro.arcgis.com/en/pro-app/latest/help/mapping/exploratory-analysis/interactive-elevation-profile-basics.htm First step is to set your DEM as the elevation source for your map: https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/elevation-surfaces.htm
... View more
yesterday
|
1
|
0
|
40
|
POST
|
@KaraUtter2 does Check Geometry on the original data return any errors? seems similar to https://community.esri.com/t5/arcgis-pro-questions/line-segments-create-giant-circular-arcs-after-re/m-p/1367948
... View more
Monday
|
0
|
0
|
32
|
POST
|
@AndrewDeLuca After digging around a bit, I think this crash was fixed in 3.3, so most likely still reproducing in 3.2.2. If you need a bug number, Esri Technical Support can help with that.
... View more
Monday
|
0
|
1
|
77
|
POST
|
Hi @AndrewDeLuca I can't reproduce a crash like that, but that could be for a number of reasons. Is the data source a factor? Is the data source a shapefile, File Geodatabase, Enterprise geodatabase (if Enterprise is it versioned? if so, type of versioning?) Last but not least, is it a feature service? There could be other factors, but I would start with that.
... View more
Monday
|
0
|
1
|
102
|
POST
|
Hey @GISAdminSHN I like the breakdown of your testing. Thanks for sharing! Considering you are only seeing the offset when snapping to an edge, it actually might be expected. Why? If you were to draw a 2-point line where the endpoints are snapped to the coordinate grid (defined by the XY resolution), you can't really guarantee that any given point along that line will intersect the grid exactly. Regarding your test: If you plug those 2 sets of coordinates into a distance formula, you get something like 0.00019 units. Assuming those are meters, that is less than the default XY tolerance of 0.001 m. I'd say that's an acceptable distance, however, I do agree that it causes a bit of anxiety to see that on display in your map. Something interesting about that: only starting in version 2.5, did Pro start allowing you to zoom in beyond 1:1 - so these types of things wouldn't ever be noticed prior to that. As far as I know, ArcMap didn't allow zooming in beyond 1:1. I can't account for every version of ArcMap, but the last version seems to not allow it. One thing you can do is create a topology with the default cluster tolerance (0.001 m) with no rules and validate it. Once you validate everything within 0.001 m will snap together. This will change the data by adding vertices to edges where they intersect to allow for clustering to occur.
... View more
a week ago
|
1
|
0
|
72
|
POST
|
Hi @GISAdminSHN , I like your idea of having some additional documentation regarding editing and XY tolerance/resolution. I haven't seen a case where the default XY tolerance/resolution (0.001 meters/0.0001 meters) weren't good enough for most every mapping use case, but I may not have seen _every_ use case :). I'll bring it up with the documentation folks. Also, it sounds like you may be running into a similar issue to what @SLouq saw? If that's the case, and you are willing to contact Esri Technical Support with details on how to reproduce it, I'd be more than curious to dig deeper into it with the development team. If you end up doing that, please reach out by sending me a direct message on here, or have the analyst reach out to me to let me know.
... View more
a week ago
|
0
|
0
|
94
|
POST
|
@dgregory_coconino based on the error message, it seems to match up with this bug: https://support.esri.com/es-es/bug/editing-traditionally-versioned-data-in-a-single-worksp-bug-000167096 Which only seems to occur in a single workspace edit session and doesn't actually cause the features to stop drawing (so it's a false alarm and shouldn't be showing as a drawing alert). You can contact Esri Technical Support and have your case attached to the defect to receive updates about it.
... View more
2 weeks ago
|
0
|
0
|
152
|
IDEA
|
@JohnShain I'm just curious, what kind of features are you creating where having this functionality would be helpful?
... View more
4 weeks ago
|
0
|
0
|
90
|
IDEA
|
@Michele Have you tried Single Workspace editing? It would prevent the scenario you are referring to. It is similar to how ArcMap works with different workspaces.
... View more
4 weeks ago
|
0
|
0
|
76
|
POST
|
@qnadeem possibly, I'd first try using the Snap geoprocessing tool within a python script. You can also look at the answers provided in https://community.esri.com/t5/python-questions/extend-line-to-specific-distance-or-a-line/td-p/227535
... View more
07-16-2024
05:35 AM
|
0
|
0
|
62
|
POST
|
@Gurunara that is expected behavior: From the doc When the Version Management capability is enabled on the web feature layer, you cannot undo and redo edits you make to data in the default version.
... View more
06-17-2024
07:29 AM
|
0
|
0
|
132
|
POST
|
@DrewPhillips You should be able to split a line by clicking on the edge with edge snapping on. If not, try making sure your data is in the same coordinate system as you map to see if that fixes it. That is one of the improvements we are making in the next release: not having to avoid projecting on the fly.
... View more
06-07-2024
05:41 AM
|
1
|
1
|
376
|
POST
|
@AmeWunderle this will be possible in the next release of ArcGIS Pro. Thank you!
... View more
06-04-2024
06:22 AM
|
0
|
0
|
165
|
POST
|
@DamienPyne The next time you see this issue try resetting the grid's origin closer to where you are editing using this tool:
... View more
06-04-2024
05:27 AM
|
0
|
1
|
188
|
POST
|
@ChadKopplin did you contact Esri Technical Support about the software slowing down for you? I would want to show them the behavior so they can rule out a bug.
... View more
05-28-2024
12:20 PM
|
0
|
1
|
393
|
Title | Kudos | Posted |
---|---|---|
1 | yesterday | |
1 | a week ago | |
1 | 03-06-2024 04:04 PM | |
1 | 06-07-2024 05:41 AM | |
1 | 05-07-2024 11:11 AM |
Online Status |
Offline
|
Date Last Visited |
yesterday
|