Latest Contributions by JeffWard

This was very helpful, thanks for posting - it fixed the errors I have been experiencing. ... View more

I always try things in the Python window before I actually run it in the field calculator. I got this to work- ' '.join([!FieldName!.split()[-1], ' '.join(!FieldName!.split()[:-1])]) ... View more

I realize this is pretty old, but I think I see what the issue is. You are double entering your curves. The a at the end of your values in the Chord Length field indicate you are overriding the chord length with the arc length, but you are entering two lines for each curve, one using the chord length expressed as the arc length and the other as the arc length expressed correctly as the arc length. You only need one line in the traverse grid per curve and only one of these three parameters in the final field - delta (central angle), arc length, or chord length. You can fix it by entering things this way:   Don't enter the a after your chord distance and don't enter the second line for each curve.   I hope that helps. ... View more

Thank you @DanPatterson! This saved me a lot of extra frustration. My field aliases were using . instead of underscores. ... View more

This one was great! Thanks! ... View more

@JasonFullerYou are able to specify the curve parameters in the drop down at the top of  each field, but you have to do it before entering any data. I usually select Chord in the Direction field, and I use the delta in the final field. I guess you are locked in on the radius, but I can't remember the last time a description didn't use the radius. And as far as the ArcMap traverse tool goes, the Pro traverse entry grid is much faster than the ArcMap traverse tool. I hate having to change between direction-distance, curve and tangent curve it slows everything down. ... View more

I'm glad it worked for you. I run in fear from spaces in file names and folder names. I am mocked by my younger colleagues. 🙂 ... View more

Pro is notorious for needing the file system "refreshed" you most likely need to click the refresh button on the dialog to load your traverse.     ... View more

Those old hand drawn plats are fun. I'm wondering if you are experiencing the phenomenon that I have observed where they will push all of their errors into one area of the plat. On the plats I have seen this, they usually have the correct bearing and distance labeled, but the line is definitely shorter or longer than what is labeled. I would try entering just that lot with the 100' back lot line and see if it closes. Does the plat georeference very well? ... View more

They have an edit tool that works like one. I use it by creating a line or polygon feature, click once on the map to start a sketch, then right click and choose "Circular Arc", I then fill it in with the parameters I have, let's say I know the arc length but want to know the delta angle. I enter the arc length, then change the parameter type to delta angle. ... View more

@NickN  great idea! Until they implement it, you don't have to break out the calculator to do the math on your own. You can make Pro do it for you, but you have to be creating a line or polygon feature. Start your sketch, then right click and choose Circular Arc, then fill in the parameters that you have, after you enter the chord length, change it to Arc Length and Pro will do that math for you. ... View more

You are able to use the traverse tool with polygon layers and non-cogo line layers that don't have cogo attributes.     ... View more

I had to close and restart Pro to see it in the Add-In Manger section of the backstage. ... View more