Having a method or methods of helping the system identify parts of a description that it missed would be helpful. Namely in my document shown, the system missed the bearing and distance that is described from a section corner. Ordinarily I would put this information in the Connection Lines; and in this case the bearing needs to be inverted to assign the starting point at the section corner.
I'm really excited about this tool, but we need more control. Please implement this idea.
The first release of COGO Reader does not support PLSS. Thank you for attaching the deed - it let's us see that it failed to read cardinal directions ('running north', 'running south').
We consider COGO reader missing reading the directions as a BUG and recommend opening a technical support case for those.
Is your idea about pointing out to where COGO Reader has failed? Like selecting the text, right clicking and choosing 'Add as direction' or 'add as distance'?
Or is the idea about teaching COGO Reader that 'running south' means 180 degrees (north azimuth format)?
@AmirBar-Maor Fundamentally yes, my idea is about pointing out when the cogoreader misses a bearing and or distance. So in this case it was unclear to me how I might get the reader to detect that the bearing from the section corner is apart of the connection line. My experience was that the reader did not detect this bearing and distance.
And yes I added s90°e for the bearings that were south. And for North I did the similar thing. After adding this to the text, the reader used these bearings to get the rectangular polygon.
Including the document is definitely an aspect that I initially failed to do. So for others reading this and posting here: adding the document is a good practice. It definitely helps that you seemingly had a similar experience as I did with this legal description with the Cogoreader
It is really exciting that it worked so well. And interesting that the PLSS reference is well a tough problem. I am in Colorado and so the most common legal description pattern is just like this one. The bearing from the section corner is inverted in the traverse tool to get to the starting point.
Thanks for the quick response.
When developing and testing COGO Reader we tested with deeds from many states, but not all them, and surely not with enough deeds from Colorado.
I've created a bug for missing out on those directions. The words 'bears' and 'running' are throwing it off.
If you remove those words it will pick it up correctly, including the connection line:
That worked for me too. Removing the Word "Bears" empowered the CogoReader to pick up the bearing and dimension and put it into the Connection Line. In this instance, the keyword "whence" usually gives me the clue that the Bearing in the description is a 'Backwards' looking direction, Thus SouthEast becomes NorthWest; and I always imagine it as if I were standing at the starting point and looking back at the PLSS Section Corner; and that's how it is written; but the traverse tool needs to have the forward direction from the starting point of the section corner; and then moving around the traverse. This inverted pattern of getting from the section corner to the point of beginning is very common.
Ideas of how to add to the training/testing data to the CogoReader's understanding may belong in a different place on this community. I guess I wish I knew how I could contribute; or if and how the system is building its understanding.
Noting that discussion of incorporating the PLSS may belong in a different or separate idea or spot on this community; Our area of Colorado references the New Mexico Principal Meridian; Other areas of Colorado, seemingly reference the 6th Prinicipal Meridian.
I have found that adding "from the point of beginning" and reversing the bearing direction N W becomes S E in this case, helps the Cogoreader identify the Connection Line information.
In this one for me, the last Curved segment Delta Angle of 02°54'42" and radius of 1329.76 to the left; it calculates it having a distance about 4' longer than what is stated in the text which is 67.57'. The measurement it came up with was 71.41 or something.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.