The Dissolver has the option to generate a list, do that, then use a ListSorter to sort that list on the height and then you can access that list value in an AttributeManager (or use a ListIndexer). Don't forget to remove the list afterwards with an AttributeRemover.
The Dissolver has the option to generate a list, do that, then use a ListSorter to sort that list on the height and then you can access that list value in an AttributeManager (or use a ListIndexer). Don't forget to remove the list afterwards with an AttributeRemover.
@Hans van der Maarel Thanks for your answer! I realized that a few polygones were cutted in 6, 5, 4 or 3, I didn't realized before, sorry but there is about 50.000 polygones. For those where there is just two attributs height_0 et height 1, I can easily choose the second one, but for the others i can't. I will look in the forum.
@Hans van der Maarel Thanks for your answer! I realized that a few polygones were cutted in 6, 5, 4 or 3, I didn't realized before, sorry but there is about 50.000 polygones. For those where there is just two attributs height_0 et height 1, I can easily choose the second one, but for the others i can't. I will look in the forum.
If you reverse the sort order in the ListSorter, height{0}._max should always be the highest value.