Create Line Type entering the two lines instead of a .lin name
None that I can think of. It won't be any simpler, but you could do it with involving another kind of file in a couple of ways: 1) have a little drawing that has that Linetype [even with nothing drawn in it], INSERT that drawing into the current one, and it will bring the Linetype with it. Or 2) get into another drawing that has something drawn in that Linetype, and Copy/Paste that into the target drawing. But in either case, that other source drawing, or another that it got it from in the same way, is going to need to have gotten the linetype from a .LIN file.
@CADaSchtroumpfNice work.
This method generates elevation tags at distance along elevation curve. It generates good result when elevation curves (isohypses) are long and relatively straight. If you have complex terrain result is not so well since marking can be placed at weird position.
Better option is to avoid full automation and place elevation marks along a intersection with temporary line with some step value along z coordinates. This can be either at 1 meter, at every even z or odd z (very rare), or at z that is divisible with 5 or 10.
From my 20 years of practice, there are situations that contours are not elevated to its true z elevation, so in algorithm one can add a code that counts intersections and rises contours in regard to step from some starting value.
In attachment is my result using your code on one some real terrain data.
Miljenko Hatlak
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Hello Sea.Heaven.
Thank you very much for your help.
I've been allready solved the whole problem.
First,
Using delphi i made a code auto - constructing 99 .lin arcives containing (each one) 100 Line Type definitions.
For example 56.lin contains
*H_5600 ....
*H_5601 ....
....................
*H_5699 ....
Those 99 goups of 100 LT definitions support all earth heights
manually i inserted the 99 .lin LT groups to 99 .dwg .
I did it manually because -Linetype unfortunatelly has problems.
OK, i did it.
When i need a height LT (for example 1245) , if no H_1245 is member of Doc Linetypes , my pascal code inserts the 12.dwg in my document as exploded and purged block.
After insert, my document has 100+ line LT (H_1201,H_1202...H1255).
After using some of them ( 1245,1246...) , purgeAll will hold only the used ones and noone block added.
That's a good solution.
About polylines, the isometric and isobath lines are smooth lines and splineis the type of line representing the drwing.
But the real solution is THE AUTOCAD SUPPORT ADDING LT USING STRING.
You are a very clever person and you undestand what i say.
And sure i believe that in the future will be an update.
And the same will occure about the badly designed -LineType.
AUTODESK made a so brilliant software, the top drawing software.
But after Autocad 14 wich was fully functional and an earhquake in CAD environment, the folowing updates were (it's my opinion) in a wrong direction. If Autocad 14 sould work ob 32 bit platforms, i sould work with it until i die.
Thank you very much sea.heaven.
Regards,
Gery.
I send you screenshots
In my own opinion generating linetype for each contour elevation is bad idea. First thing that crosses my mind is that you (or users after you) will have linetype selection drop-down menu polluted with hundreds entities.
There are many lisp codes available for placing contour elevations.
Miljenko Hatlak
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
@GeryKnee wrote:
......
------ 5642 ------------- 5642 ------------- 5642 -------------
------ 5643 ------------- 5643 ------------- 5643 -------------
......
You may be able to use LabelElevMask.lsp with its LEM command, available >here<. It reads the Z coordinate of the path object [any kind with linearity] where you pick, and puts in Text with a wipeout [does not Break the path], middle-centered at the selection point over the path object, and aligned with it in the more plan-readable direction. That has the benefit, in my mind, that you can label contour lines, etc., where you want to put labels, and not have them forced to every fixed distance along the paths, which you would have no control over with a linetype, and which I would usually find looks too cluttered. Also, you can label a path object that's too short for a linetype to include the text element [assuming the linetype definition cycle is long enough that the text elements are not ridiculously close together].
@Kent1Cooper wrote:
.... you can label contour lines, etc., where you want to put labels, and not have them forced to every fixed distance along the paths, which you would have no control over with a linetype....
An example: If the white at the top is the continuous-linetype path of a contour line [not an unusual kind of shape], you might hope that a text-containing linetype would end up with the text elements "landing" something like the way they do in the red one. But depending on the extent of the contour, at the mercy of things that could be far away, it could come out like any of the others, which can obscure the information.
That's why I prefer to place labels where I want them, not at fixed spacings, clear of this kind of interference and clear of any other drawn objects, and with their locations remaining where they are even if I Trim or Extend or Stretch the remote end(s) of the contour somehow.
But, of course, as independent objects, labels such as I prefer don't adjust automatically if I alter the route of the contour, as the text elements in a linetype would -- I would need to re-label. [But in the case of existing contours specifically, I don't think I ever alter them in that way -- it would apply only to proposed new contours, and possibly to non-contour situations, whatever they might be.]
