Landscape Area to Hardscape Object, or vice-versa

[Neil Barman]

What is the best/most efficient way to take a Landscape Area object and turn it into a Hardscape object (and vice versa)?

The scenario is that the client keeps changing their mind regarding what they would like to be hardscape and what they'd like to be planted, so I'd like to be able to switch back and forth as easily as possible. I realize there isn't a direct "convert this into that" option, so I'm curious to know what would be the best way to go back and forth?

Thanks in advance!

-Neil

[J. Wallace]

When converting objects I always keep a copy of an initial polyline that I have drawn for the given area. It's then easy to delete a hardscape or landscape area and start over. If you could continue to covert from these objects it would be great.

[Neil Barman]

I agree about keeping the initial source shape, and perhaps keeping them in a "schematic design" class, but I'm wondering what could/should one do if those source shapes are no longer available.

-Neil

[Benson Shaw]

Just an idea - Can you paste a copy of the 3d (sent to surface) shape into a new layer, Top/Plan, then Modify>Convert>Convert to Lines or other flatten technique. Then either Compose the new lines to make a new poly, or apply the Polygon Tool in Inner Boundary mode (Paint Bucket).

Or, in Top/Plan, trace the 3d object with the Polyline tool.

-B

[aage.langedrag]

Hi @Katarina Ollikainen,

How to transform my Landscape Area symbols to Hardscape symbols and keep all data inside the symbols?

 

This has become more important than ever since Hardscape now can drape to Site model surface. Before this option, we used Landscape Area as Hardscape. Now is the time to transform many of the Landscape Areas into Hardscape. A great deal of data has been added to these symbols, Records, Data Mapping and IFC. We hope we can get help to automate as much of this process as possible.

Greatly appreciates getting help to come up with a good solution. I have a colleague who is waiting for me to come up with a time-saving solution.

Edited January 11, 2024 by aage.langedrag

[Katarina Ollikainen]

Hi @aage.langedrag

Do you mainly want to convert styles or individual objects? 

Can you please send over some examples of what you would like converted? This should include all p-sets, attached records, etc., so we can understand the scope.

[aage.langedrag]

Hi @Katarina Ollikainen,
You have a good question. At first I think that I don't dare to change current project models. That's why we now talk about Style objects so that new projects start with Hardscapes. Settings shown on the image should be transferred to Hardscape automatically. Does this make sense?

It may be that you want to change the Instance objects in an ongoing project, but I'm not there now. The important thing is to get shared template files and libraries right.

Untitled 2.vwx

[Katarina Ollikainen]

@aage.langedrag, Great, that's what I thought. It wouldn't make much sense to change an ongoing project if the object is already doing its job, just because it's titled 'landscape area' instead of 'hardscape'. 

I'll have a look at the sample file.

[Poot]

I wonder if a script might not be able to accomplish this? Maybe @Pat Stanford might know if thats possible...

Here is a link to a post for with script for batch renaming, which might be able to be adapted 

 

[Pat Stanford]

Almost certainly scriptable. But very challenging to get all of the fields required mapped correctly and tedious to write. Even worse if you want to have it "automatically" handle random attached records.