Currently, Oresium considers that the 2D and 3D models used in a Cesium project are located directly in the source folder.
For 2D models, Oresium needs to open and read the image files (using ImageIO.read), and the paths referenced in the generated output.czml are always pointing to the project root.
These constraints make it difficult to use Oresium in projects that rely on a separate view or a more structured resource layout.
To improve this, I suggest avoiding the use of ImageIO.read in CzmlModel.write2D to determine the model size, and instead adding an explicit parameter for this information. In addition, I suggest using relative paths (rather than just the model name) when building the URI in both write2D and generate3DModel of CzmlModel.
This would make resource management more flexible and easier to integrate into larger Cesium-based projects.