Re: [sumo-user] incorrect street directions from shp to sumo.net

[Mirko Barthauer <m.barthauer@xxxxxxxxxxx>]

Dear Feresteh,

 

that depends on how the shape file was drawn. The SUMO edges are drawn from the start node to the end node as defined in the shape file (see docs). For bidirectional edges, another SUMO edge is added in the opposite direction. If you want to generate a lefthand network, you need to tell netconvert so by setting --lefthand true.

 

Best regards

Mirko

 

 

 

 

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

Betreff: Re: [sumo-user] incorrect street directions from shp to sumo.net

Datum: 2024-03-05T14:02:36+0100

Von: "fereshte jafari" <j.fereshte1993@xxxxxxxxx>

An: "Mirko Barthauer" <m.barthauer@xxxxxxxxxxx>

 

 

 

Dear Mirko,

 

Many thanks for your help. 

One more question. In the created network the bidirectional edges seem strange. Several of them are created like the picture below  


I mean the directions of the upper edge and the lower edge in the bidirectional should not be conversed?🤔 In the shp file, the DIR_TRAVEL of this link is B without any arrows while in the sumo it is like this picture. You can see a screenshot below. Any ideas on fixing this?

 

Thanks in advance.

On Tue, Mar 5, 2024 at 7:50 AM Mirko Barthauer <m.barthauer@xxxxxxxxxxx> wrote:

Dear Feresteh,

 

edge type files set _oneway_="true" as default if no other value is given. Unfortunately, this hadn't been documented until now. So please update your type file with _oneway_="false" attributes. The shape file DIR_TRAVEL attribute will still be considered and define whether you have both directions or not.

 

Best regards

Mirko

 

 

 

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

Betreff: Re: [sumo-user] incorrect street directions from shp to sumo.net

Datum: 2024-03-04T16:16:05+0100

Von: "fereshte jafari" <j.fereshte1993@xxxxxxxxx>

An: "Mirko Barthauer" <m.barthauer@xxxxxxxxxxx>

 

 

 

You are right. Without  --speed-in-kmh t --type-files osmNetconvert4.typ options the generated network is well constructed. Therefore, the problem is caused by the typefile. Could you please try it with my type file too which is attached here and let me know the problem of the typefile?

 

Regards,

Fereshteh

On Mon, Mar 4, 2024 at 2:45 PM Mirko Barthauer <m.barthauer@xxxxxxxxxxx> wrote:

Can you tell me a specific edge where you miss the opposite direction? I used netconvert --shapefile-prefix roads4 -o roads4.net.xml --shapefile.use-defaults-on-failure to convert the shape and it seems to work (example: link 4597796)...

 

Best regards

Mirko

 

 

 

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

Betreff: Re: [sumo-user] incorrect street directions from shp to sumo.net

Datum: 2024-03-04T13:29:56+0100

Von: "fereshte jafari" <j.fereshte1993@xxxxxxxxx>

An: "Mirko Barthauer" <m.barthauer@xxxxxxxxxxx>

 

 

 

Dear Mirko,

 

Please find enclosed my network shp file.

 

Regards,

Fereshteh

On Thu, Feb 29, 2024 at 1:53 PM Mirko Barthauer <m.barthauer@xxxxxxxxxxx> wrote:

Dear Fereshteh,

 

can you provide your test shape file? When you first load a network in netedit, the junctions are not fully computed. Press F5 to compute all links.

 

Best regards

Mirko

 

 

 

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

Betreff: Re: [sumo-user] incorrect street directions from shp to sumo.net

Datum: 2024-02-29T14:08:57+0100

Von: "fereshte jafari" <j.fereshte1993@xxxxxxxxx>

An: "Mirko Barthauer" <m.barthauer@xxxxxxxxxxx>

 

 

 

Dear Mirko,

 

Please see attached my typefile which does not include the oneway option. Also, I attached three pictures of a specific link in my network in 1-shp, 2-sumo, 3-netedit. As you can see in the pictures in shp the DIR_TRAVEL=B while in sumo and netedit it shows just one direction on the link.
Besides that, I have one more question. My links in netedit are not connected completely as you can see in the attached screenshot while in the sumo they are well connected and there is no warning. I am wondering if this situation would be ok or problematic in next steps of simulation runnings? Because my network is very large and fixing these issues one by one is really timetaking. I prefer to skip it 😬

Thanks in advance for your help.

On Thu, Feb 29, 2024 at 7:26 AM Mirko Barthauer <m.barthauer@xxxxxxxxxxx> wrote:

Dear Feresteh,

 

the only case this may happen when looking at the code is related to the type definitions you added. If the type has the attribute _oneway_="true", this overrides the value from the shape file. If this does not explain your problems, please provide a test file.

 

Best regards

Mirko

 

 

 

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

Betreff: [sumo-user] incorrect street directions from shp to sumo.net

Datum: 2024-02-28T17:41:24+0100

Von: "fereshte jafari via sumo-user" <sumo-user@xxxxxxxxxxx>

An: "Sumo project User discussions" <sumo-user@xxxxxxxxxxx>

 

 

 

Hello!

I converted my shapefile to a sumo network using the below command

netconvert --shapefile-prefix roads4 --shapefile.use-defaults-on-failure --speed-in-kmh t --type-files osmNetconvert4.typ -v

the generated network does not contain the road directions properly although this attribute already exists in my shapefile with the name DIR_TRAVEL which is given in the table of this documentation (Direction of travel ("B": both, "F": forward, "T": backward)).  https://sumo.dlr.de/docs/Networks/Import/ArcView.html

 

In most cases, the directions are correct but bidirectional roads only work in one direction!

 

Your guidance and help would be greatly appreciated.

 

--

Sincerely,

Fereshteh Jafari Shahdani

PhD candidate, Dep. of Civil Engineering

ISISE - University of Minho

--

Sincerely,

Fereshteh Jafari Shahdani

PhD candidate, Dep. of Civil Engineering

ISISE - University of Minho

--

Sincerely,

Fereshteh Jafari Shahdani

PhD candidate, Dep. of Civil Engineering

ISISE - University of Minho

 

--

Sincerely,

Fereshteh Jafari Shahdani

PhD candidate, Dep. of Civil Engineering

ISISE - University of Minho

 

--

Sincerely,

Fereshteh Jafari Shahdani

PhD candidate, Dep. of Civil Engineering

ISISE - University of Minho