Hi there, I use tiled terrain data because of large size of region. Every height map tile is a 16-bit png texture. So, almost in each texture minimal level is not deep black and maximal level is not deep white. But when I try to import these textures as terrain height map, City Engine adjusts minimal level of every image as deep black and maximal level as deep white. Because of this every terrain has wrong heights. How can I solve it? I think computing of min and max levels of every tile by third-party software is not convenient solution.
Height maps are refined processed png images of geodata without any additional geo information. In attachment you can see an example of one tile. Full tileset has a range of height from 0 to 1000m. This particular tile has a range from 8 to 300 m. But when I set the range (0,1000) in CE it tries to do auto-level of the height map and adjust the particular height range to the full height range. You can see that this image looks more contrast in preview mode than it is.
Hi Matt, All is perfect when you download maps from geodata sources and directly use it in City Engine. But these data usually have low resolution and should be refined. For example I use World-Machina software for refining data. When you work with images with third-party editors all geo-information will be lost. So, I think it would be better and more clear for users that height range is not adapted if there are not any geo-information.
Yes, it's a bad thing those third-party editors kill that metadata. Maybe esri tech support (email@example.com) can help you with getting those edits done by maintaining the metadata in ArcGIS. ( I'm not a GIS expert ).
On the import side, when the georef metadata is not available, CE just falls back to interpreting the imagery as 'standard' images.
Hi, Yes, it's a bad thing those third-party editors kill that metadata. Matt
That's ok, because those software change heights and height range. For example, I create ocean bottom there, so there are "negative" heights in my height map.
On the import side, when the georef metadata is not available, CE just falls back to interpreting the imagery as 'standard' images. Matt
It's correct behavior, that CE interpret the imagery as "standard". I just think that additional automatic in this process is not necessary and confuse users. May be is it possible to do this feature as optional?
Otherwise I need create additional script which defines height range in every tile.