Please fix stream mode digitizing

1276
6
01-26-2021 06:54 PM
Status: Implemented
Labels (1)
IanPryor1
New Contributor III

Stream mode digitizing is still nonfunctional and essentially broken in Pro 2.7. In Arcmap you set a stream tolerance and vertices are created at the specified interval and visibly appear as the mouse is dragged along. In Pro, it is seemingly random how the software decides to create a new vertex while engaged in streaming mode digitizing. Setting the tolerance to 20 feet results in vertices roughly 80-100 feet apart, setting at less than 5 feet results in 4-10 feet spacing, setting it at zero results in imprecise "jagged" results. The results are so horribly inconsistent the tool is practically useless (for my purposes and especially when compared to Arcmap). Please just implement this tool in the same manner as Arcmap or at least give that option.

6 Comments
Scott_Harris
Status changed to: In Product Plan
 
KoryKramer
Status changed to: Implemented

Stream mode was improved in ArcGIS Pro 2.9.  See Ideas in ArcGIS Pro 2.9 for a number of other ideas you can expect to find when you update to 2.9.

IanPryor1

Appreciate the improved stream mode digitizing performance with version 2.9 but suggest it is still lacking when compared with the implementation in ArcMap. Stream mode tolerance remains somewhat random, vertices are created at very irregular intervals no matter what tolerance is entered. One of the most significant differences is how how vertices are shown in real time and "on-the-fly" in ArcMap, this improves the overall experience. In Pro you see a dashed line and vertices only appear after completing the edit.

MarcHunter1

To add, this issue is still a major hurdle for mappers who rely on streaming, and is unreliable in Pro v3.0.2. 

 

IanPryor1

shouting into a hurricane on this one, I think esri considers this resolved even though its still essentially useless.

BrianKreb

We are having the same issue on 3.0.1 and rely heavily on streaming to make large vegetation maps. It would be great if this was fixed sooner than later ESRI!