Hey Jakob,
maybe it would be possible (and maybe relatively easy?) to implement a
dedicated pedestrian detector that reports true if any pedestrians are
inside its area that have not moved the timestep before (or the number
of those pedestrians). That would be much like an E2 detector. Similar
There is no strong technical reason that prevents E2-detectors from
handling pedestrians. It might also be useful to configure it for detecting
pedestrians either in forward, backward or both directions. However, that
still would not solve the use case of a pedestrian push-button.
This is because p
Hello Jakob,
thanks for your reply.
Is detection of pedestrians by E2 detectors a planned feature? Or is it
just not meant to function that way. Anyway I noticed that if I use
--persontrips true with od2trips, SUMO does not find connections for
pedestrians the way I modeled my network now (wi
Hello,
E2-detectors currently cannot detect pedestrians. and the only way to
implement a pedestrian-pushbutton is by checking the walking direction of
the pedestrians explicitly. This is demonstrated in
https://sumo.dlr.de/wiki/Tutorials/TraCIPedCrossing
Sidewalks should be modelled with a single
Dear all,
currently, when modelling pedestrians, I always use 'regular' edges and
connections. This results in warnings (such as "Warning: Vehicle type
'7' with vClass=pedestrian should only be used for persons and not for
vehicle 'ped26'."), and sometimes pedestrians accidentally end up on th
