Need lisp to write bearing as Deg Min Sec

re:
Need lisp to write bearing as Deg Min Sec


Greetings,
What I'm trying to do is find a routine that will convert the bearing of a
line to Deg Min Sec then write it as dtext
Presently I have to do this long hand and its not only inaccurate but damned
boring
I am drawing a ton of what's called lot calcs here in the surveying world
If I could simply pic the line then pic the point I would like to write it
that would be great but it has to be in Deg Min Sec format
If you can help I would be very grateful

Regards
Allan Marks

 

Just curious Roy:
Why did you call it "brush"?

 

Roy -
Thanks for the routine.
I will give a whirl shortly and let you know how it went
ajm

 

Allan, sorry to jump into your post, but
this reminded me of a routine I used to have at an old job but no longer do.
I loaded Roy's routine (thanks for posting it Roy!), but it was not exactly
what I am looking for.

Does anyone have a routine that will do what my old one did?
It would prompt for deg min sec and length (it was written in such a way
that you only had to enter the number and return, it knew what was what).
It would then draw the line on the proper layer and add the text centered on
that line, rotated parallel to the line and offset properly.
so for each property line you only had to enter four numbers. Each time it
returned to the start for the next line.
You could run as many lines as you liked to close the lot, then go back and
add arcs at the proper radius manually.
It made laying out lots very fast and easy!

Thanks,
jojo

 

Hi Roy,
When I load up the routine (using appload) it returns this
---------------------------------------
error: bad argument type: numberp: nil
---------------------------------------
I wonder what makes it do that
I read further below that one chap used it - it wasn't what her wanted
and from that I assume it must have ran

ajm

 

IINM, the error is indicating that the routine is passing the wrong type of
value
to another function. The routine is expecting a real or integer, and it
is being given something else, maybe a string or a T...

Sometimes a difference in the setting of the EXPERT variable
between the author and the unhappy user can screw
up routines, and eventually lead to this sort of thing.
There are other things, of course. I haven't looked at the code myself.

 

....or maybe a "nil" value, i.e. something never got assigned a
number value before something else tried to use it....