It sounds if you're mixing two concepts: - vType id: can be anything, id is referenced in <vehicle> attribute 'type' - vClass : attribute of vType, fixed list of access classes (corresponds to allow/disallow of roads): example: passenger, truck, bicycle, evehicle
Am Di., 20. Apr. 2021 um 08:32 Uhr schrieb jlange <jla...@psi.de>: > Hello, > > I want to implement new vehicle types (e.g. "passengerRain"). The > parameters > of those new vehicle types should contain the parameters as it's influenced > by weather conditions (rain, snow). > > When I define those vtypes and add "Rain" or "Snow" to the name, I get an > error message (while generating routes) that the vehicle type > "passengerRain" is not known. When I change "passengerRain" to "evehicle" > for example, it suddenly works. Is there a way to solve this problem - so I > can add "Rain"/"Snow" to the name, or do I have to stick with the names in > the link below and can only change the parameters? > > https://sumo.dlr.de/docs/Definition_of_Vehicles%2C_Vehicle_Types%2C_and_Routes.html#vehicle_length > > Kind regards, > Jens > > > > -- > Sent from: http://sumo-user-mailing-list.90755.n8.nabble.com/ > _______________________________________________ > sumo-user mailing list > sumo-user@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user >
_______________________________________________ sumo-user mailing list sumo-user@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
