This isn't really intended to be merged - I've basically taken a stab at what was discussed here https://github.com/pelicanmapping/rocky/discussions/33 and would like a general idea of how horrifying the implementation is from someone who has a better idea of how things are supposed to work.
I used the class name suggested in the discussion, but it's probably not a good choice as it might get confusing with there also being an ECS that also has entities.
It should probably automatically dirty itself when new LOD is streamed in or out as otherwise a feature that is only represented at certain LOD levels may lead to a node ending up underground or floating. I've not implemented this yet, though.
This isn't really intended to be merged - I've basically taken a stab at what was discussed here https://github.com/pelicanmapping/rocky/discussions/33 and would like a general idea of how horrifying the implementation is from someone who has a better idea of how things are supposed to work.
I used the class name suggested in the discussion, but it's probably not a good choice as it might get confusing with there also being an ECS that also has entities.
It should probably automatically dirty itself when new LOD is streamed in or out as otherwise a feature that is only represented at certain LOD levels may lead to a node ending up underground or floating. I've not implemented this yet, though.