Hello,
For a special reason, I would like to draw a site plan in a 3D DGN instead of a 2D DGN, to be able to use the "elevation" element property.Normally we would draw this type of drawing in 2D, but in this case, I want to build this plan up in different "layers".That means, each floor on a different elevation (Z-axis height).I was very pleased when I discovered the elevation property.... and thought that would be a great help to make my work easier.Unfortunately, however, I can't handle this elevation property.
It starts with the fact that there are differences between the V8iSS4 and the Connect Edition Update14, which I both use.In the V8iSS4, the elevation is displayed for certain objects in the property window, but the elevation values cannot be changed.
The other way, in the Connect Edition, I can change the elevation values with the "Set Element Elevation" tool, but I don't know how to display this value for elements ....In the Connect Edition, the point for the element elevation is missing...., this property can not be shown.
I'm very confused about the elevation property and would be happy if you could help.
1) Why does (in MSV8iSS4) the elevation property not exist for all type of elements?For example, if I draw a shape, the "elevation" property is shown in the property windows. But if I draw a simple line, it didn´t have.
2) Why can I no longer see the elevation values in the property window in the Connect Edition?How can I display these values?
One optional question :)3) Is it possible to select elements at a specific elevation?
I add 4 screen shots, with the difference between MSV8iSS4 and Connect Edition Update 14.
Many ThanksRegardsRaphael
Modify these Z values.
sorry for repeating myself...I already know that and I don't want to change the Z values in this way!A shape for example has 4 segments and therefore also 4 Z-values....I create/edit a very extensive drawing and if there exist a elevation function, which does exactly what I actually want, namely to change all these Z values with just one entry, then I would like to do it on the smart way ;)RegardsRaphael
The following articles may help in understanding how this can achieved using the Set Element Elevation tool in MicroStation CONNECT Edition.
https://communities.bentley.com/products/building/building_analysis___design/w/building_analysis_and_design__wiki/38224/connect-edition---how-to-change-z-levels-while-moving-elements
https://communities.bentley.com/products/microstation/b/microstation_blog/posts/new-in-microstation-connect-edition-update-12---set-element-elevation-tool
RegardsAndrew BellTechnical SupportBentley Systems
Hello Andrew,
Thanks for your answer and the links.I know how I can align elements with the known alignment tools and also how I can work with the "set elevation tool".In the first linked article, I could now read that this tool is not yet compatible with all element types .....That' s the answer to one of my questions :)Unfortunately, I think it's a shame that this is limited to individual element types.In my case I have a lot of lines, curves and shapes that I have to edit and that would have been a great help.Does Bentley plan to extend this function to all elements?I also know the features shown in the video from the second linked post, but unfortunately the functionality still seems to be severely limited.
One big question remains unanswered .....In my first post I posted 4 pictures, the 2 upper ones are from MSV8iSS4 and the 2 lower ones are from Connect Edition Update 14.On these pictures I have commented on the fact that the "Elevation" is no longer displayed in the Connect Edition in the Element Property window ...Compare picture 2 with picture 4, both about the shape, and you can see the elevation property in the property window of the V8 version (picture 2) but not in the Connect Edition (picture 4) !! ??I can not understand why!Has it been completely removed ... or forgotten ... in the Connect Edition?Or can I have the elevation value displayed in a convenient way elsewhere?
I have now recognized an alternative way to read out the elevation value ...I can also read out this value in the AccuDraw window ... but then it is not enough to simply select the element, it must be a tentative snap and to be sure, you have to check all snap points separately... So it's not the great solution after all.
RegardsRaphael
Raphael :) said: I have a lot of lines, curves and shapes that I have to edit and that would have been a great help
MicroStation Help tells us...
Used to set a Z value to selected elements. This tool is helpful in positioning all vertices of a line-string, curve-string, complex string, or contours to a specified value.
If the MicroStation tool doesn't do what you want, try this VBA freeware macro: ModZ for MicroStation CONNECT. I don't think that it's element-specific. And, if it is, the macro includes the source code so you can modity it to your requirements.
Regards, Jon Summers LA Solutions
Hi Jon,
Thanks, I will give it a try.Hopely it works like a charm for all elements, since I'm still not convenient in VBA.
Do you also didn't have an idea, why the elevation property is missing in the property window or how I can display this information in a smart way?
Regards
Raphael
Hi Raphael,
Raphael :) said:Do you also didn't have an idea, why the elevation property is missing in the property window
I guess it's just a bug and should be reported to Bentley support.
Personally I do not like Elevation attribute, because when an element is not planar, the value is weird and I have not found any explanation, what Elevation really is and how is calculated for different element types.
Also, from this discussion it's clear that many people thin that Elevation is the same type of information like Z, which is not.
From this perspective, standard Move and Set Element Elevation tools are better choice.
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hi Jan,Thanks for your post.I think it's not so easy to say ...Of course, this may be a bit misleading for some peoples, but if you deal a little more with this function and, above all, recognize the benefits of this function, then I think it's justified.Otherwise such tools as the ModZ-Macro or the integretat function "set element elevation" would not have been developed .... :)I'm a bit confused in your statement, where you wrote:.
Personally I do not like Elevation attribute, because ....From this perspective, standard Move and Set Element Elevation tools are better choice.
You wrote that the set elevation tool is the better choice ...., but that's exactly my point and the "set elevation tool" sets exactly these values, which are displayed in the property window as elevation attribute ...!?RegardsRaphael
Raphael :) said:but that's exactly my point and the "set elevation tool" sets exactly these values, which are displayed in the property window as elevation attribute ...!?
No: Elevation value, displayed in Properties dialog, and Set Element Elevation tool, do different things, with potentially the same results in specific situations.
The difference can be illustrated using general 3D not planar line (no parallel with any axis or plane, not defining any plane):
The situation when results are the same is when the line is parallel with Z plane, because Elevation moves the line to the defined height (Z plane), and Set Element Elevation move the line in the same way.
Jan, yes you are right.
That falls under the point I wrote in my opening post, that there are differences between MSV8I and MSconnect regarding the elevation function.
I am still convinced of the elevation function and think that it could be helpful for certain work, but Bentley would have to change something, so that it really makes sense and is manageable in practice.One approach could be, for example, that we could choose between 2 options, when working with the "Set Element Elevation" tool.1) set elevation with "flatten"2) set elevation with "maintain offsets"
So we could specifically choose what we want to realize, either push everything down to a Z value or move elements with their origin point to a fixed Z coordinate.
Does it make sense to report this change request / bug to Bentley?What would be the best way to report?
ThanksRegardsRaphael
Raphael :) said:Does it make sense to report this change request / bug to Bentley?
You must decide whether it's a bug. If this is a bug, then submit a Service Request (SR) to Bentley Systems. They will eventually decide whether they consider this a 'defect' or Works as Designed (WAD).
Raphael :) said:What would be the best way to report?
The best way to report a bug is through a formal SR to Bentley Systems.
Service Request is done.I am curious and hope that this function will be improved.
ThanksRegards