Chris, This is Jefferson, Adrians boss. Thank you for being so responsive to us. We like what you have built and were trying to test its possibilities and limitations to see if we could get it working well for our use case. We would love to use this tool for our needs of data entry to aid in the generation of closure reports. Adrian and I both think we have a bead on the first two points he brought up. Thank you. The big reason we wanted the angle field to possibly store the textual bearing string rather than just azimuth is so we could get it to display in the labels of the parcel/traverse. We can get the angle to show up, however it only shows in the azimuth form. If we could change the label display that would also solve the issue. Storing the textual bearing in a separate field would work well for us as well. The fourth point Adrian brought up is important, but secondary in my mind to a few other problems. The first would be data entry for curves. Your method is limited to the following: Radius and Chord Length actually requires Chord Bearing, Radius, and Chord Length, Radius and Arc Length actually requires Chord Bearing, Radius, and Curve Length. The options labels are a bit misleading in this regard. Curves in documents are more diverse than these options. Much more, actually. A tool like this would be useful when diversity in data entry was available. Here is a screen shot of software we use now (that we would like to abandon) showing the different types of curve information that show up in legal documents. Generally any three elements of a curve can accurately draw the curve. They would still generally work within the fields you have created. Are you familiar with these possible definitions.
... View more