Dear Menno,
Thank you for your answer. I think I can use this.
I now model a traffic control system with a single controlled junction (intersection), but the next step is to control multiple intersections. So I am curious about
that too. And maybe it helps to make the shapes of the controlled junctions right in this project. Could you maybe share your network (especially the native sumo-files)?
Met vriendelijke groet,
Martin Barto
Senior Verkeerskundige
Mobiliteit
Vialis is een Koninklijke
VolkerWessels onderneming.
Postbus 184, 3990 DD Houten | tel. +31648510557 mob. +31648510557
.
.
Van: sumo-user-bounces@xxxxxxxxxxx [mailto:sumo-user-bounces@xxxxxxxxxxx]
Namens Menno van der Woude
Verzonden: woensdag 11 juli 2018 08:54
Aan: sumo-user@xxxxxxxxxxx
Onderwerp: Re: [sumo-user] invalid pedestrian crossings
Hi Martin,
depending on the purpose of the simulation, you could also consider modelling the pedestrians with regular edges and links.
If the purpose, as far as the pedestrians are concerned, is solely to have someone cross the intersection every now and then (that is, you are not interested in modelling the pedestrians in detail, or measuring throughput etc.), that should do just fine.
You could model the pedestrians as vehicles, which means they will queue in line for the traffic lights, and SUMO will complain. However, it also means that pedestrians will be able to activate E2 detectors (which I believe they cannot as actual pedestrians),
and it makes building the network somewhat easier.
Below is a screenshot of a network in which I followed this approach. Note that there is a single traffic light that controls multiple junctions.
Personally I have found no other way to model pedestrians that allows me easily place the crossing correctly, and also allows a destination for pedestrians where there is no other edge.
Greets,
Menno van der Woude
CodingConnected e.U. (Wien - Österreich)
E menno@xxxxxxxxxxxxxxxxxx
W www.codingconnected.eu
On 11-7-2018 08:41, Barto, Martin wrote:
Dear Jacob,
I don’t know if you pay attention to my problem? The problem is that when I add sidewalks to the incoming edges of an intersection, the pedestrian crossings are valid, but the connections
on the incoming edges are messed up. What is the solution for this? Or maybe someone else has dealt with this problem?
Best regards,
Martin Barto
Senior Verkeerskundige
Mobiliteit
Vialis is een Koninklijke
VolkerWessels onderneming.
Postbus 184, 3990 DD Houten | tel. +31648510557 mob. +31648510557
.
.
Thank you for your answer Jacob,
I did the changes according to your advices. That worked fine. The warnings have disappeared. But this change has a nasty side-effect. All the connections with edges that have sidewalks
seems to be messed up. This is also visible in Netedit:
How can I get the connections fixed according the .con.xml without changing manually in Netedit or in the .net.xml? My goal is to make a SUMO network automatically from an an existing
standard intersection topology.
I included my files again.
Kind regards,
Martin Barto
Senior Verkeerskundige
Mobiliteit
Vialis is een Koninklijke
VolkerWessels onderneming.
Postbus 184, 3990 DD Houten | tel. +31648510557 mob. +31648510557
.
.
Van: sumo-user-bounces@xxxxxxxxxxx [mailto:sumo-user-bounces@xxxxxxxxxxx]
Namens Jakob Erdmann
Verzonden: zondag 8 juli 2018 23:41
Aan: Sumo project User discussions <sumo-user@xxxxxxxxxxx>
Onderwerp: Re: [sumo-user] invalid pedestrian crossings
netconvert rejects crossings that do not have a sidewalk or another crossing on each side.
Invalid crossings are not written to the .net.xml files and therefore you cannot find them.
To better understand the problem, it helps if you load the input files directly into netedit (use the same command with netedit instead of netconvert).
Netedit will color invalid crossings in red (requires pressing F5 once).
Also, the latest development version of netconvert and netedit give additional information in the warning message.
2018-07-07 0:17 GMT+02:00 Barto, Martin <Martin.Barto@xxxxxxxxx>:
Dear SUMO-users,
I get warnings using netconvert that says:
Warning: Invalid pedestrian topology: crossing ‘:KR27_c3’ has no target.
Warning: Invalid pedestrian topology: crossing ‘:KR27_c5’ has no target.
In .net.xml the edges don’t exist.
The strange thing is that all the other pedestrian crossings are converted into .net.xml correctly. The input-files seems logical, so I don’t know what I’m doing
wrong here.
Does anyone have suggestions?
I added all the files. The call is:
netconvert --node-files=Output/KR27.nod.xml --edge-files=Output/KR27.edg.xml --connection-files=Output/KR27.con.xml --type-files=Output/all.typ.xml --tllogic-files=Output/KR27.tll.xml
--output-file=Output/KR27.net.xml
Met vriendelijke groet,
Martin Barto
Senior Verkeerskundige
Mobiliteit
Vialis is een Koninklijke
VolkerWessels onderneming.
Postbus 184, 3990 DD Houten | tel. +31648510557 mob. +31648510557
.
.
Look here for our e-mail disclaimer:
http://cp.vialis.nl/disclaimer.html
_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/sumo-user
Look here for our e-mail disclaimer:
http://cp.vialis.nl/disclaimer.html
Look here for our e-mail disclaimer:
http://cp.vialis.nl/disclaimer.html
_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/sumo-user
