Multiple autogen types for a single vegetation class shapefile

[Kelvin Richardson]

Is it possible for Scenproc to add 2 or 3 different GUID's for a single shapefile rather than having to split the shapefile in multiple parts or creating a separate autogen class?

It would be good if Scenproc can allow adding multiple autogen and have some logic to mix these autogen based on a random number in percentage, i.e % of x trees and % of y trees.

 

[arno]

Hi,

Do you mean that for each feature one of the specified guids will be chosen randomly? That's a feature that's on the wishlist. I'm testing it for library objects right now.

 

[Kelvin Richardson]

Yes,

Let's say I have 4 Vegetation Shape files, all for different vegetation i.e native trees, shrubs, mangrove, scrub.

These each have their own shapefile containing the features for each one.

I would like to be able to select multiple GUID's for each shapefile but this will apply to the features inside each shapefile. This means I can have multiple autogen for each shapefile but mixed randomly for the features in the respective shapefile.

 

[arno]

As long as you still want one guid per feature it's possible. Having the same feature with multiple guids won't work.

 

[Kelvin Richardson]

Oh, I would only have a single feature in a shapefile, that feature would be a single vegetation type. From what you are saying it seems like this is not going to work for what I want.

I was hoping that for the single feature in a single shapefile I could assign a few GUID's to each one.

So it looks like I may have to split up the shapefile and assign a separate GUID to each one.

 

[arno]

I think we might not be talking about the same. With a feature I mean a single polygon here.

 

[Kelvin Richardson]

Sorry misinterpreted what you said.

So in that case I can have one GUID per polygon (feature).

This means I can achieve what I want.

Thanks for clarification.

I am looking forward to this build.

 

[arno]

Ok, once it's working for the library objects I'll add it to vegetation as well. It will probably be a few weeks before the new release is out (it's a combination of different changes I'm working on now).

 

[Kelvin Richardson]

That would be excellent.

Thanks for your responses.

 

[roland_lfor]

Sorry if I misunderstood the context, but I'm using successfully multiple vegetation GUID's for a single feature (polygon).
The following script create multiple GUID's on unique polygon:

# short vegetation
CreateAGNPolyVeg|FTYPE=POLYGON;code_12=324;FROMFILE=CENTRO_VEG_Corine.shp|{3aa3f089-5d25-43b5-8186-74173e034f32}
CreateAGNPolyVeg|FTYPE=POLYGON;code_12=324;FROMFILE=CENTRO_VEG_Corine.shp|{d7fe02de-0b21-4849-a954-b855b8b52d7b}
CreateAGNPolyVeg|FTYPE=POLYGON;code_12=324;FROMFILE=CENTRO_VEG_Corine.shp|{7639234e-11fc-44ef-bbb9-d62e319399ab}
CreateAGNPolyVeg|FTYPE=POLYGON;code_12=324;FROMFILE=CENTRO_VEG_Corine.shp|{0533d2b5-2a93-4c4a-9660-069a3f73b921}

 

[arno]

That will create multiple vegetation rectangles in the agn file. The approach suggested here was to have only one feature in the agn file but with a different guid.

For polygonal vegetation having multiple polygons with a different guid doesn't work well, all trees end up in the same place.

I can't remember if it works better for rectangular vegetation.

 

[roland_lfor]

Actually it depends on which GUIDs you choose.