Calculating the area of multiple elements containing interior shapes

Hello! I have a map that is divided in to many different size areas. Majority of these areas contain a smaller area inside them. The areas are divided to their own layers according to their type. I would like to calculate the area of all certain layer elements but I don't want to count in those smaller elements inside.

I know that it is possible to calculate the area of an element using flood and the locate interior shapes. But is there a way to do this for multiple elements at once? Without having to click every element separately?

Thanks in advance. 

Parents
  • You could create grouped hole polygon collections and then calculate areas from these grouped holes. All interior shapes which has hole attribute set will be substituted from shape area calculation.

  • ok now it makes sense  none of your shapes were created with  regard to interior shapes this is very bad mapping  if not bad planning..

    it would have been easier if they were built as shapes or regions with interior located regions or donuts ( with holes) .. 

    As we dont  know how many shapes were dealing with its a bit mute .. but without access to gis .. microstation is not very good at bulk creation of island regions, but  if it was my job and no GIS.. I would create regions with locate interior and  use a coloured fill to help making them as I go one by one and I would tag each shape with a name or id or unique level name then I could do a report  to extract true area and names.

    Jon Summers UK Solutions  web site had a macro to tag shapes  to help get ids and areas into reports.. my  knowledge of Connect Ed and reports is pretty limited as I'm experienced v8i user .. I cant help but think of how i would do it in V8i...

    In gis this would be a very simple  5 minute sql query  provided each shape had an id or label  it could find all the islands and make them separate and  it could export it back out into microstation and  have it all as regions with interior holes as separate shapes  not part of the  larger shape hence no duplication of areas counted and true areas..

    Jon Summers also has area annotator to label all the shapes then you can search for the islands and  get the difference .. but unless all you shapes have some unique ids its not really much use for reporting...

    Lorys

    Started msnt work 1990 - Retired  Nov 2022 ( oh boy am I old )

    But was long time user V8iss10 (8.11.09.919) dabbler CE  update 16 (10.16.00.80) 

    MicroStation user since 1990 Melbourne Australia.
    click link to PM me 

Reply
  • ok now it makes sense  none of your shapes were created with  regard to interior shapes this is very bad mapping  if not bad planning..

    it would have been easier if they were built as shapes or regions with interior located regions or donuts ( with holes) .. 

    As we dont  know how many shapes were dealing with its a bit mute .. but without access to gis .. microstation is not very good at bulk creation of island regions, but  if it was my job and no GIS.. I would create regions with locate interior and  use a coloured fill to help making them as I go one by one and I would tag each shape with a name or id or unique level name then I could do a report  to extract true area and names.

    Jon Summers UK Solutions  web site had a macro to tag shapes  to help get ids and areas into reports.. my  knowledge of Connect Ed and reports is pretty limited as I'm experienced v8i user .. I cant help but think of how i would do it in V8i...

    In gis this would be a very simple  5 minute sql query  provided each shape had an id or label  it could find all the islands and make them separate and  it could export it back out into microstation and  have it all as regions with interior holes as separate shapes  not part of the  larger shape hence no duplication of areas counted and true areas..

    Jon Summers also has area annotator to label all the shapes then you can search for the islands and  get the difference .. but unless all you shapes have some unique ids its not really much use for reporting...

    Lorys

    Started msnt work 1990 - Retired  Nov 2022 ( oh boy am I old )

    But was long time user V8iss10 (8.11.09.919) dabbler CE  update 16 (10.16.00.80) 

    MicroStation user since 1990 Melbourne Australia.
    click link to PM me 

Children
  • still it would have been better to have a representative dgn sample uploaded so we could analyse your objects and levels better instead of all this second guessing.. as how your file is built is how we tackle the solution.

    Lorys

    Started msnt work 1990 - Retired  Nov 2022 ( oh boy am I old )

    But was long time user V8iss10 (8.11.09.919) dabbler CE  update 16 (10.16.00.80) 

    MicroStation user since 1990 Melbourne Australia.
    click link to PM me