Hello,
When generating with the numericrasterizer, it uses the altitude values to define the raster pixel values. But an essentiel point is not configurable and understandable: how this transformer chooses the pixel value when several points are located at the same XY but nut at the same Z. (easy examples : a tree, a power line, a building, any vertical things or thing above another one).
We don't know if the value taken by the raster is linked to the average of the points in the area (pixel size) or with the min, the max, randomly ...?
I have noticed twice that points above the ground are not always taken into account and therefore do not appear on the raster, which makes it wrong because not all the elements are included. This is a bit of a pity for a transformer that is supposed to make a representation according to the elevation...
It would be extremely useful (see indispensable) to be able to choose which value of z is used. Because this transformer works perfectly, it gives really nice results but it does not allow to have something reliable and rigorous.
I hope that it would be possible for you to add a parameter something like "z value dertermination" with -lowest, -average and '-highest choices :)
Regards,
Arnaud
My understanding is the numericRasterizer works by feature order. If you sort your features by Z value (ascending) do you get your highest point?
I just tested, you're right. There was nothing to suggest it. Although it does add to my treatment time, it's very good news to have a solution. Nevertheless the addition of new clear parameters would be a real plus for this transform
Or at least an update of the documentation to have no ambiguity about how it works.
thank