If I use the vertical scroll bar, while zoomed and rays showing, I can make the rays dissapear once the upper left corner of the drawing is fully within the viewing window. These ray lines seem to appear once the drawing is zoomed in to a point where some of the upper leftmost portion of the drawing is out of the viewing window. Projection Rays are generated originating at the upper left hand corner of the zoomed window and terminating on various points of the drawing. But If looking at the entire sheet, or looking at a print preview, the dashed lines are quite poorly rendered - they aren't uniformly dashed.įurthermore, there's a very strange artifact when zooming in and out, from time to time. If I zoom in on the part, the dashed lines, 'dashed (small)', look great. The issue I'm seeing is that dashed lines, i.e., hidden lines, are poorly rendered in both screen display and print. Basically I took the a3 template and scaled it to 1:1 for inches such that it would represent an 8.5" x 11" drawing. The part is embedded within a 8.5" x 11" drawing - title block, border etc., as shown in a3.dxf.
The drawing is of a small part, about one inch max dimension. We never did anything in 3d but we would take topography shots that had elevations on them and the drafter would make couture lines to show the slopes.I'm working on a drawing with the 'Current Drawing Preferences' set to inches with scale at 1:1. We needed to be able to make points on a drawing, and import them into the data collector so we can go out in the field and start with a known control point. Also i remember having to convert points from raw to ascii and I cant remember the name of the OS our data collectors used. Then we can gps some shots and rotate it in the drawing to match the bearings.īeen a long time since I have been in the field. Because when you open it in autocad, you don't want to be in the negative good grid. There is also something like a grid where if you start surveying a small piece of land and create a new job in the data collector, I would make my northing 5000 and my easting 5000. Instead of inches, he needs tenths since surveyors don't use inches. I know for my uncle, he needs to be able to draw by bearing ie N60:25:32W distance 500 feet. I will be putting a lot of time into it and would share my experience of anyone is interested. LazyBat if you have time to look into it. Thank you for your time if you read this. Not good at closing a sales, or apparently a project, I have the habit of constantly expanding it which I always need to avoid. I have tested it out and seems to work well, No errors in the provided examples that I compiled and execute (except for my own error).ģ) I will use LazyBat in a plug-in that I will develop as I go on.Ĥ) Been working on this project and need to set myself a deadline. Has it own 'Grammar Language' that I have review and will be quite powerful for me. It assists in creating a command line shell. Here is the copyright Institute of TechnologyĢ) I will secondly integrate a open source program called LazyBat. The ICES I would think stands for "Integrated Civil Engineering Systems". Its a very very old program for Surveyors and Civil Engineers, but was very popular at one point in time. The original geometry project I am trying to emulate is called 'Engineers_Guide_to_ICES_COGO_1_Aug67.pdf.' However, I am working on other projects as well.ġ) I will be submitting one main function (that is way to big) to validate input and it will determine the functions needed to generate additional 'control points'. I just read my post of 2 months ago!! This is taking more time then I thought. We always need a paper trail for what we do.)Īny opinions or ideas for item one, or an answer to item two? (All ascii files - for legal purposes as well as efficiency. I would like these functions to be able to accept input from a ascii files, and output to a file. Could I create a Survey Command Function, that runs from the LibraCAD command line, and redirects input from and output to a file? A need with todays data collectors in the field, all generating some kind of electronic outout to files.Īdditionally, Survey data entry can be extensive, at times, till this day. Except for a particular job-order, where numbering could be itemized to that job-order, which would be unique and perhaps very useful.Ģ) Another question I have is regarding input/output. Surveyors are most concerned about 'control points', and 90 percent of the points in a CAD dxf file would be just unnecessary. 1) Hoping to make these survey routines more functional for libreCAD, and simpler for me at this point, I am going to dump the 'survey control points' into an ascii point file, for librecad to import.
0 kommentar(er)
