Ok, let me see if I can gather my thoughts clearly. Yes, that post you answered in Question 1 is what I tried. However, it appears the step:
Is based on knowing the size of the storage tank object. What I seek is to scale automatically the storage tank to match the OSM polygon size, which for me is an unknown. This way, I don't need to know the object's size or even the polygon footprint size. scenProc would do a comparison of the object's size against the polygon footprint and scale accordingly... a perfect fit! And then to add to that, I would have tanks in various sizes (Large, Medium, Small), all based on different GUIDs to give a better looking fit to start and then scales those a tad to match footprint. That way the objects would not be stretched, skewed or sized looking strange.
You said above:
"Yes, there is a sample in that same thread. But it only refers to placing XML objects, AGN library objects can't be scaled"
I see, I thought there was a step to create autogen objects from an xml or I can only create a librayy object from that? My end goal is to create autogen objects on their own or from default or our own custom made library objects. Or so long as I scale in "xml" mode first and then convert to an autogen object?
You also said:
"If the features have attributes that define they are tanks it is easy indeed. I thought you also wanted to detect those that do not have such an attribute."
So I did discover the osm data file does indeed have storage tank attributes (discovered different OSM file types have different attributes). But it could be nice to also detect if there are no attributes?
Also, can you tell me what these stand for:
FLENGTH = fixed length?
FAREARAT = ?
Starting to ramble on here so I will get back to testing and create more concise questions.