I use the Traverse Tool to run out legal descriptions on deeds and recorded subdivision plats. I'm looking for a way to display the survey calls once I'm done. Is there a way to do that? I'm using ArcMap 10.0.
ArcGIS Desktop – How to Display Survey Calls Using the Traverse Tool
arcgis-10.0arcgis-desktopcogoland-surveymetes-and-bounds
Related Solutions
I've developed the PetroGIS add-in, which has some tools for importing different seismic formats (such as UKOOA P1-90, SEG-P1, SPS) directly into ArcGIS point feature classes. However, it is for ArcGIS 10 only. Note also, it is not free, but you can get a fully-functional free trial from http://gis-media.com/petrogis/.
Legal plans (plats) and legal descriptions are not in any projection (grid) system; they are on a local, ground-based plane. Hence the need for grid-to-ground and ground-to-grid conversions. As a minimum, there are usually scaling and rotation issues to deal with.
So, it is quite possible that neither GIS nor legal description are wrong.
Once we get more details and give more advice, you'll probably find you can use your GIS.
Now, based on your mapped area and legal traverse, it looks like your traverse does indeed close but it needs to swing clockwise, about the commencing section corner, by a significant amount. The swing will probably be the difference in the so-called "basis of bearing" between the GIS map and the land survey.
In case it helps, I have just used Copan -- a free Windows package, for legal survey traverses -- on your data:
Checking Bearing-Distance Traverses at 20:51 on 6 Jan 2014
MapTrav file C:\Users\Martin\Documents\Copan\pine-ridge.mt
1) Map Traverse Results [1 - 1]
Leg Count 20
Total Distance 2134.00
Coordinate Misclosure
N -0.02 Dist 0.02 <-- Warning: Large Misclosure!
E 0.01 Brng S28°19'34"E
Relative precision 1 : 105415
Start or Curve
Bearing Distance To Point Code
1
S62°38'44"E 41.22 2
S 8°16'40"E 58.01 3
S36°39'50"E 37.14 4 BC
N53°20'10"E 50.00 5 CC
S 6°44'26"E 50.00 6 EC
N83°15'34"E 73.05 7 BC
S 6°44'26"E 35.00 8 C
N73°20'20"E 35.00 9 EC
S16°39'40"E 43.41 10 BC
N73°20'20"E 200.00 11 CC
S53°12'28"W 200.00 12 EC
S36°47'32"E 36.59 13
S 3°29'58"E 42.66 14
S29°29'29"E 237.38 15
S20°05'15"E 249.68 16
S69°51'47"W 125.25 17
N19°59'03"W 142.92 18 BC
S70°00'57"W 50.00 19 CC
N 7°06'29"E 50.00 20 EC
N82°53'31"W 57.65 21 BC
N 7°06'29"E 50.00 22 C
S53°52'07"W 50.00 23 EC
N36°07'53"W 500.73 24 BC
N53°52'07"E 30.00 25 C
N59°20'49"W 30.00 26 EC
N30°39'11"E 198.42 1
Curve results
Beg Cent End Arc Chord Radius Angle
4 5 6 52.43 50.06 50.00 - 60°04'36"
7 8 9 48.92 45.03 35.00 + 80°04'46"
10 11 12 70.27 69.91 200.00 - 20°07'52"
18 19 20 54.90 52.18 50.00 - 62°54'28"
21 22 23 40.81 39.68 50.00 + 46°45'38"
24 25 26 34.97 33.02 30.00 + 66°47'04"
NB: The Total distance (quoted above and used to determine Relative precision)
excludes curve radials and includes curve chords.
The Perimeter Total (below) excludes both radials and chords but includes curve arcs.
Perimeter
segments 1844.11
arcs 302.29
Total 2146.40
Area 181568 (sq. units)
Although it warns of a "large" misclosure = 0.02 ft, this represents a good relative precision = 1 : 105415
Note, I began from the "true point of beginning", where the loop begins-ends, and assigned point numbers 1-26 including curve centers. It gives the area, as a bonus.
If/when you know the bearing correction and ground-to-grid scale factor, they can be applied.
PS: I know a lot about Copan because I was a developer.
I'm guessing that, if the first course of the legal description is along the section line (due West) yet its stated bearing is N87°52'23"W
, then the bearing correction should be -02°07'37"
(the difference).
What happens if you try that value?
Ultimately, you need proper, professional confirmation. At least try http://surveyorconnect.com/ for further advice.
Best Answer
Yes, there is. If you did not save your traverse to a text file when finished, you can:
You can then right-click again in the description window (may need to click one of the calls first) and save that traverse out to a text file for future reference. They can be loaded from text files as well.
Now if you want to label the lines with the calls, that's another animal. Parcel Fabrics automatically track the details of the calls in attributes, but just creating a shapefile/feature class and inputting with COGO doesn't. To add those attributes, there's a tool you can run on the shapefile or feature class from within ArcCatalog. It's only available in ArcCatalog (the actual program, not the window within ArcMap) and not visible by default, so you have to right-click somewhere in the menu space and choose Customize. Then go to the Commands tab and type COGO into the search box. There should be only one result - Add COGO Fields. Add that button to a tool bar, then click it to run. Note since you're adding fields, you can't have the file open in an edit session, and in fact you probably shouldn't have it open at all in ArcMap (or ArcMap even running for that matter) because Catalog and Map tend to lock each other out of access to files.
Note that it only works on line shapes. If you're creating polygon parcels, you'll have to first convert them to a line geometry and run the tool on those. It will add fields to hold the bearing and distance of the lines as attributes. Once that's done, you can open the shapefile/feature class up again in ArcMap and use the Update COGO Attributes button (last on the COGO toolbar) to actually populate the fields. Then you can create labels using those attributes. Of course, if you want to label the polygons you'll have to have the line layer in there too with a null symbology, and if you change polygons you have to re-export to lines and re-update the COGO attributes every time.
For this reason, you might want to consider using Parcel Fabrics. Not only does it track more information, but it's all integrated. However, it does require a higher license level (Advanced), has a bit of a learning curve, and is actually much more complex on the back end.