Thanks so much for your help. This makes sense - I will
make it "type1", "type2", "type3" and so on for vType ids.
However, in the end, I simply used the csv2xml() converter in
tools/, based on the following .csv file (snippet).
And the rou.xml file snippet above is what the csv2xml()
conversion produced. Why is the converter doing this
incorrectly then? And how would I go about doing this
following part using csv2xml()? `Please define vTypes without
enclosed vehicles, like you have done afterwards. Also enclose
route elements in vehicle elements or define them on the same
level as vtypes and give them IDs` I'll change vType_id to
type1, type2, type3, etc., but is there another part of the
.csv that I need to be changing for csv2xml() to work?
The first definition of your vType "type1" encloses a
vehicle definition which references it. However it
cannot find type1 as the closing tag of vtype has not
been reached yet. Please define vTypes without enclosed
vehicles, like you have done afterwards. Also enclose
route elements in vehicle elements or define them on the
same level as vtypes and give them IDs.
Do use unique IDs (strings) for vTypes. Do not define
"type1" a second time.
Maybe you have a look at the relevant documentation
page.
Regards
Mirko
Am 24.04.2020 um 16:14 schrieb Pavan Yedavalli:
Hi,
I'm a new user to SUMO, and I was wondering about
the following (very basic) error:
"Error: The vehicle type 'type1' for vehicle 'veh0'
is not known." from my rou.xml file. I generated that
using csv2xml in tools/, just FYI.
Here is a snippet of the first few vehicles in
rou.xml file:
I'm not sure what I'm doing incorrectly, but it
does not like "type1" for the vType id or for
<vehicle> type, it seems - it looks like it's
the latter given the error message. Any help would be
appreciated. Thank you.