Error: Could not build output file 'net.net.xml' (Permission denied).

[Hector A Martinez <hmartinez@xxxxxxxxx>]

Mirko,

 

Never mind this question below.

 

I identified the problem with my script.  I was running netconvert from its bin location and of course it wasn’t letting the system save the new file in that location.  I fixed it and I am up and running again.  Will let you know if I bump into any issues with the new file.

 

Thanks,

 

--H

 

From: sumo-user <sumo-user-bounces@xxxxxxxxxxx> On Behalf Of Hector A Martinez via sumo-user
Sent: Thursday, January 18, 2024 11:42 AM
To: Mirko Barthauer <m.barthauer@xxxxxxxxxxx>; Sumo project User discussions <sumo-user@xxxxxxxxxxx>
Cc: Hector A Martinez <hmartinez@xxxxxxxxx>
Subject: Re: [sumo-user] [EXT] AW: Changing rail to be bidirectional using netconvert

 

Thank you Mirko! I think this might do the trick but I am getting this error when I run it on windows command line: Error: Could not build output file 'net. net. xml' (Permission denied). Quitting (on error). How do I point the output file location

Thank you Mirko!

 

I think this might do the trick but I am getting this error when I run it on windows command line:

 

Error: Could not build output file 'net.net.xml' (Permission denied).

Quitting (on error).

 

How do I point the output file location to a user location so that I doesn’t need elevated permissions?

 

Thanks,

 

--Hector

 

From: Mirko Barthauer <m.barthauer@xxxxxxxxxxx>
Sent: Thursday, January 18, 2024 3:20 AM
To: Sumo project User discussions <sumo-user@xxxxxxxxxxx>
Cc: Hector A Martinez <hmartinez@xxxxxxxxx>
Subject: [EXT] AW: [sumo-user] Changing rail to be bidirectional using netconvert

 

Dear Hector, maybe it is not explained clearly enough in the documentation. The option --railway. topology. all-bidi. input-file can be used to restrict the set of rail edges you want to make bidirectional. This means the required file is a selection

 

Dear Hector,

 

maybe it is not explained clearly enough in the documentation. The option --railway.topology.all-bidi.input-file can be used to restrict the set of rail edges you want to make bidirectional. This means the required file is a selection file you can generate with netedit (select edges and then choose "Save" from the select frame/mode).

 

if you want to make all rail edges bidirectional, just call

 

netconvert --railway.topology.all-bidi true -s C:\pathtofile\test_osm_in.net.xml.gz

If you want only a subset of edges to be bidirectional, call

 

netconvert --railway.topology.all-bidi.input-file selection.txt  -s C:\pathtofile\test_osm_in.net.xml.gz

 

Best regards

Mirko

 

 

 

-----Original-Nachricht-----

Betreff: [sumo-user] Changing rail to be bidirectional using netconvert

Datum: 2024-01-17T20:50:48+0100

Von: "Hector A Martinez via sumo-user" <sumo-user@xxxxxxxxxxx>

An: "sumo-user@xxxxxxxxxxx" <sumo-user@xxxxxxxxxxx>

 

 

 

Sumo team,

 

I am trying to convert all of my rail network to be bidirectional using netconvert without affecting my roadway network. This is for commodity/container movement, not people movement. I am using a file I generated using OSM wizard.

 

I used this script:

netconvert --railway.topology.all-bidi.input-file C:\pathtofile\test_osm_in.net.xml.gz

 

This is the error I get.

 

Error: No nodes loaded.

Quitting (on error).

 

I recognize that the network file is a .gz file but both netedit and sumo open the network file as is and it has everything to include the nodes. Netedit crashes on me all the time while I am making changes to the file so I need to do this rail changes quicker using netconvert. I welcome any advice that will point me in the right direction.  Thanks,

 

--Hector

 

 

From: Mirko Barthauer <m.barthauer@xxxxxxxxxxx>
Sent: Friday, January 12, 2024 3:50 AM
To: Hector A Martinez <hmartinez@xxxxxxxxx>
Subject: AW: [EXT] AW: Adding Containers using TraCI

 

Hi Hector, you can try to process your network with netconvert using the PlainXML format: convert your network to PlainXML analyse your network with a script and write the missing edges in a new file in PlainXML format convert back to the normal

 

Hi Hector,

 

you can try to process your network with netconvert using the PlainXML format:

• convert your network to PlainXML
• analyse your network with a script and write the missing edges in a new file in PlainXML format
• convert back to the normal SUMO format with netconvert by supplying the PlainXML files using the respective input options (-n,-e,-x,-i)

Please write to the mailing list next time, so that everybody can answer the question (or at least learn from it).

 

Best regards

Mirko