OpenStreetMap Importer: Elevation Grid Rotated 90° Counterclockwise and Generated as Separate object from Flat Ground (with --enable-3D)

[aalgirdas]

Steps to Reproduce:
Run the OpenStreetMap Importer with the 3D elevation option:

python3 importer.py --enable-3D  --no-trees --no-forests  --input=myMap.osm --output=myMap.wbt

Observe the scene: The elevation grid appears rotated 90 degrees counterclockwise relative to the main scene elements (roads, buildings, etc.).

Additionally, the elevation grid is generated as a separate entity from the main scene ground, which remains completely flat. All roads and buildings are placed on this flat ground at the same elevation level, ignoring the 3D terrain.

Expected Behavior:

The elevation grid should align correctly with the main scene (no rotation).
The main scene ground should incorporate the 3D elevation data, with roads and buildings positioned accordingly on the varied terrain rather than on a separate flat layer.

[AntonioLuisGH]

The 90-degree rotation definitely looks like a bug, probably a simple X/Y vs X/Z coordinate mix-up when the script generates the ElevationGrid.

Regarding the roads and buildings staying on a flat plane, I'm pretty sure that's actually a known limitation of the current importer. From what I can tell, the script doesn't automatically project 2D map elements (like roads) onto the 3D terrain mesh yet, which is why it just spits them out as two completely separate layers.

As a quick workaround for the rotation, have you tried manually adjusting the rotation field of the ElevationGrid node directly in the generated .wbt file to line it up?