Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [sumo-user] Adding elevation (.tif) to the network using NETCONVERT

Thanks for the suggestions, Jakob. The axes were used correctly in my case.

I was able to solve the problem. Just posting here the result of my struggles for anyone looking for it later.

The problem was that my input network already contained elevations (Z coordinates) that I wanted to update from the new elevation file. And apparently, the algorithm was trying to match all three coordinates (X, Y, Z) when searching through the elevation file and ended up not matching any of the network points:


Warning: Could not get height data for coordinate 7.15,51.24,197.23

Warning: Could not get height data for coordinate 7.15,51.24,197.47

Warning: Could not get height data for coordinate 7.15,51.24,197.71


Finally, it worked when I used the same network but without any Z coordinates. New height coordinates were added to the network.

 

From: sumo-user <sumo-user-bounces@xxxxxxxxxxx> On Behalf Of Jakob Erdmann via sumo-user
Sent: Friday, 21 February 2025 15:37
To: Sumo project User discussions <sumo-user@xxxxxxxxxxx>
Cc: Jakob Erdmann <namdre.sumo@xxxxxxxxx>
Subject: Re: [sumo-user] Adding elevation (.tif) to the network using NETCONVERT

 

It might be an axis inversion thing. Different versions of GDAL used different axis-ordering by default.

 

Am Fr., 21. Feb. 2025 um 14:56 Uhr schrieb Belikhov, Danil via sumo-user <sumo-user@xxxxxxxxxxx>:

Thank you, Jakob.

I’ve tried all the possible combinations of CRFs but no luck.

I tried the test example and it worked. So the problem is probably in my files.

I am also getting warnings like this:

Warning: Could not get height data for coordinate 7.15,51.24,197.23

Warning: Could not get height data for coordinate 7.15,51.24,197.47

Warning: Could not get height data for coordinate 7.15,51.24,197.71

Warning: Could not get height data for coordinate 7.15,51.24,197.95

Warning: Could not get height data for coordinate 7.15,51.24,198.19

Warning: 55928 total messages of type: Could not get height data for coordinate %

So apparently it can not find any height coordinates in the .tif file which is super weird. My network coordinates lie within the elevation file boundaries and looking at the .tif file in QGIS, it has all the Z coordinates.

 

From: sumo-user <sumo-user-bounces@xxxxxxxxxxx> On Behalf Of Jakob Erdmann via sumo-user
Sent: Friday, 21 February 2025 13:33
To: Sumo project User discussions <sumo-user@xxxxxxxxxxx>
Cc: Jakob Erdmann <namdre.sumo@xxxxxxxxx>
Subject: Re: [sumo-user] Adding elevation (.tif) to the network using NETCONVERT

 

It's supposed to work by loading a network with any geo-projection and elevation data as WGS84.

(The network-coordinates a converted to lon/lat internally before retrieving elevation raster data).

Possibly you did not try this combination?

 

 

Am Fr., 21. Feb. 2025 um 12:37 Uhr schrieb Belikhov, Danil via sumo-user <sumo-user@xxxxxxxxxxx>:

Hello Everyone,

I am struggling with adding supplementary elevation (.tif) to the network file I generated from OSM through Netconvert.
When I execute the following commands, “success” is shown but in the network file there is no elevation at all (even the previous default elevation from OSM is deleted).

Here is an example of my command:

netconvert --sumo-net-file osm_reserve.net.xml --heightmap.geotiff new_elev_wgs84.tif --output corrected_elev.net.xml

I tried setting different coordinate systems to match between the network and the elevation data:
- I tried the network with default WGS84 and the elevation data converted to WGS84;
- I also tried using the elevation data with its default EPSG:25832 and converting the network to the EPSG:25832;
- I also ensured that the elevation data covers the whole network.

But still doesn’t work.

This is what I get after executing the command:

pj_obj_create: C:\Program Files\PostgreSQL\16\share\contrib\postgis-3.4\proj\proj.db contains DATABASE.LAYOUT.VERSION.MINOR = 2 whereas a number >= 4 is expected. It comes from another PROJ installation.

pj_obj_create: C:\Program Files\PostgreSQL\16\share\contrib\postgis-3.4\proj\proj.db contains DATABASE.LAYOUT.VERSION.MINOR = 2 whereas a number >= 4 is expected. It comes from another PROJ installation.

Warning: Could not get height data for coordinate 7.14,51.25,168.00

Warning: Could not get height data for coordinate 7.14,51.25,168.00

Warning: Could not get height data for coordinate 7.14,51.25,168.00

Warning: Could not get height data for coordinate 7.14,51.25,168.00

Warning: Could not get height data for coordinate 7.14,51.25,167.94

pj_obj_create: C:\Program Files\PostgreSQL\16\share\contrib\postgis-3.4\proj\proj.db contains DATABASE.LAYOUT.VERSION.MINOR = 2 whereas a number >= 4 is expected. It comes from another PROJ installation.

pj_obj_create: C:\Program Files\PostgreSQL\16\share\contrib\postgis-3.4\proj\proj.db contains DATABASE.LAYOUT.VERSION.MINOR = 2 whereas a number >= 4 is expected. It comes from another PROJ installation.

Warning: Ambiguity in turnarounds computation at junction '13235'.

Warning: Ambiguity in turnarounds computation at junction '3674'.

Warning: Ambiguity in turnarounds computation at junction '4378'.

Warning: Ambiguity in turnarounds computation at junction '5108'.

Warning: Ambiguity in turnarounds computation at junction '6958'.

Warning: Found sharp turn with radius 5.97 at the end of edge '-119#1'.

Warning: Found sharp turn with radius 5.45 at the start of edge '-19#1'.

Warning: Found sharp turn with radius 3.85 at the end of edge '-218'.

Warning: Found sharp turn with radius 1.60 at the start of edge '-27#1'.

Warning: Found sharp turn with radius 2.25 at the start of edge '-27#3'.

Warning: Found angle of 179.58 degrees at edge '-43#0', segment 31.

Warning: Found angle of 163.45 degrees at edge '-43#0', segment 32.

Warning: Found angle of 173.11 degrees at edge '-54#3', segment 0.

Warning: Found angle of 162.29 degrees at edge '-54#3', segment 1.

Warning: Found angle of 135.58 degrees at edge '427', segment 9.

Warning: Lane '-100_0' is not connected from any incoming edge at junction '6585'.

Warning: Lane '-107_1' is not connected from any incoming edge at junction '5733'.

Warning: Lane '-119#0_0' is not connected from any incoming edge at junction '7963'.

Warning: Lane '-119#2_0' is not connected from any incoming edge at junction '119#2'.

Warning: Lane '-119#7_0' is not connected from any incoming edge at junction '119#7'.

Warning: Speed of straight connection '483#2_0->483#1_0' reduced by 8.85 due to turning radius of 0.93 (length=1.38, angle=180.00).

Warning: Speed of straight connection '547#4_0->547#3_0' reduced by 8.48 due to turning radius of 15.72 (length=1.53, angle=20.94).

Warning: Speed of straight connection '547#4_1->547#3_1' reduced by 5.63 due to turning radius of 26.84 (length=2.67, angle=20.94).

Warning: 8 total messages of type: Ambiguity in turnarounds computation at junction '%'.

Warning: 82049 total messages of type: Could not get height data for coordinate %

Warning: 8 total messages of type: Found angle of % degrees at edge '%', segment %.

Warning: 62 total messages of type: Found sharp turn with radius % at the % of edge '%'.

Warning: 211 total messages of type: Lane '%' is not connected from any incoming edge at junction '%'.

Success.


Thank you very much in advance.


Best regards,

---

Danil Belikhov, M.Sc.
Research Associate

 

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user


Back to the top