[sumo-user] netedit - lane selection for neigh tag

[Richter Gerald]

Hi.

Netedit 1.7.0.... recent git

to get an overview of the successful guesswork or necessary manual
corrections
regarding opposite lane overtaking

I tried to select for all lanes/edges that have the neigh element within
their lane definition

using edge selection mode
choosing: network elements, lane

which does not allow for a selection where neigh is present.

is there a way to do this?

thanks,
Gerald
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

[Jakob Erdmann]

Hi Gerald,

the latest nightly version of netedit supports lane attribute 'opposite' which you can edit and select for.

The easiest way to select all lanes with an opposite lane is to enter "_" (underscore) in the match-attribute input field.

regards,

Jakob

Am Mo., 14. Sept. 2020 um 09:47 Uhr schrieb Richter Gerald <[hidden email]>:

Hi.

Netedit 1.7.0.... recent git

to get an overview of the successful guesswork or necessary manual
corrections
regarding opposite lane overtaking

I tried to select for all lanes/edges that have the neigh element within
their lane definition

using edge selection mode
choosing: network elements, lane

which does not allow for a selection where neigh is present.

is there a way to do this?

thanks,
Gerald
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

[Richter Gerald]

Hi Jakob,

thank you for this swift response - again.

using your selection instructions I now can see 

that most of the desired associations for opposite lanes have been found and implemented 

by the netconvert opposite guess reprocessing.

however, some stretches - often parallel routes - have been left out and I wonder how to elegantly fix this.

(see attachment - selected edges in blue are those where lanes have the opposite set)

1. can I pick lane ids and enforce a netconvert reprocessing on just those, or 
2. would the best way be to 
   1. define/select ids for stretches of edges along non-ambiguous routes and 
   2. write a separate script using sumolib which 
   3. would be following these stretches from junction-node to junction node and 
   4. pick out the equivalent closest lane from the opposite direction stretch, 
   5. set lengths to the average and 
   6. associate by setting opposite="..."

please share your best guess

thanks,
Gerald

Von: [hidden email] <[hidden email]> im Auftrag von Jakob Erdmann <[hidden email]>
Gesendet: Dienstag, 15. September 2020 15:33:31
An: Sumo project User discussions
Betreff: Re: [sumo-user] netedit - lane selection for neigh tag

 

Hi Gerald,

the latest nightly version of netedit supports lane attribute 'opposite' which you can edit and select for.

The easiest way to select all lanes with an opposite lane is to enter "_" (underscore) in the match-attribute input field.

regards,

Jakob

Am Mo., 14. Sept. 2020 um 09:47 Uhr schrieb Richter Gerald <[hidden email]>:

Hi.

Netedit 1.7.0.... recent git

to get an overview of the successful guesswork or necessary manual
corrections
regarding opposite lane overtaking

I tried to select for all lanes/edges that have the neigh element within
their lane definition

using edge selection mode
choosing: network elements, lane

which does not allow for a selection where neigh is present.

is there a way to do this?

thanks,
Gerald
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

[Jakob Erdmann]

Hello Gerald,

the stretches where guessing did not find an opposite lane are those where opposites lanes cannot currently be represented due to network topology (opposite lanes must connect reversed from- and to-nodes). Thus whenever there are in-between nodes that only apply to one road direction, opposites do not work.

So if you want to fix this programmatically you need to find edges where the opposite direction has an in-between node and define a <split>,

then reprocess the networks with these splits and re-guess opposites.

regards,

Jakob

Am Mi., 16. Sept. 2020 um 13:04 Uhr schrieb Richter Gerald <[hidden email]>:

Hi Jakob,

thank you for this swift response - again.

using your selection instructions I now can see 

that most of the desired associations for opposite lanes have been found and implemented 

by the netconvert opposite guess reprocessing.

however, some stretches - often parallel routes - have been left out and I wonder how to elegantly fix this.

(see attachment - selected edges in blue are those where lanes have the opposite set)

1. can I pick lane ids and enforce a netconvert reprocessing on just those, or 
2. would the best way be to 
   1. define/select ids for stretches of edges along non-ambiguous routes and 
   2. write a separate script using sumolib which 
   3. would be following these stretches from junction-node to junction node and 
   4. pick out the equivalent closest lane from the opposite direction stretch, 
   5. set lengths to the average and 
   6. associate by setting opposite="..."

please share your best guess

thanks,
Gerald

Von: [hidden email] <[hidden email]> im Auftrag von Jakob Erdmann <[hidden email]>
Gesendet: Dienstag, 15. September 2020 15:33:31
An: Sumo project User discussions
Betreff: Re: [sumo-user] netedit - lane selection for neigh tag

 

Hi Gerald,

the latest nightly version of netedit supports lane attribute 'opposite' which you can edit and select for.

The easiest way to select all lanes with an opposite lane is to enter "_" (underscore) in the match-attribute input field.

regards,

Jakob

Am Mo., 14. Sept. 2020 um 09:47 Uhr schrieb Richter Gerald <[hidden email]>:

Hi.

Netedit 1.7.0.... recent git

to get an overview of the successful guesswork or necessary manual
corrections
regarding opposite lane overtaking

I tried to select for all lanes/edges that have the neigh element within
their lane definition

using edge selection mode
choosing: network elements, lane

which does not allow for a selection where neigh is present.

is there a way to do this?

thanks,
Gerald
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user