Vissim Crack
Kanisha Dezarn
Although Vissim is a microscopic simulation as SUMO is, it follows acompletely different concept of modelling traffic. Due to this, theimport is quite clumsy, does not work with all networks, and manual workon the imported network is necessary. The option which forcesnetconvert to read a vissim file is --vissim-file or --vissim forshort. A usage example for netconvert's Vissimimport may look like:
Vissim-networks do possibly not contain explicit definitions of anedge's speed. We have to propagate once set velocities, but even thensome edges' speeds may not be defined. The option --vissim.default-speed may change thedefault speed used in the case an edge's speed is not defined. Thedefault value for this parameter is 13.89m/s, being around 50km/h. Thesecond parameter --vissim.speed-norm describes the factor to multiply a described flowsmaximum velocity to gain the velocity to use. The default value is 1.
Furthermore, as we have to use geometrical heuristics for joiningconnections to nodes, a further factor steers the process of convertingVissim-networks: simply spoken, --vissim.join-distance holds the information how near twonodes must be (in meters) to be joined.
As of SVN revision [18592] the import parser used by netconvertwas extended to accomodate for the new XML input file format (*.inpx)of VISSIM version >= 6 (which makes a lot of things a lot easier)...
In order to enhance the quality of the imported network, the VISSIM network structureshould follow some general guidelines. Although VISSIM has no problems with using links instead ofconnectors and the other way round, it is best to stick to the following rule for the net to be importedwith netconvert:
Please let me know if you have any questions. I have been stuck on this for quite long. It maybe that changing the georeference projection line in opendrive will help match the cooridnates in opendrive and Vissim but I am not sure what is the correct sentence needed there.
Could you confirm that this xord file is exported from VISSIM? If not, what are the origins of the file(s)? The reason I am asking is that I have explored the file in an independent FOSS online that can visualise an xord file, and I see that the issues in the CarMaker import actually exist in the file itself.
I noticed those. I also sent you a clean .xodr file that does not have these type of issues. But when I import it I find that the coordinaqtes are different that the vissim network. If you can tell me how are the bbox coordinates defined or local scale is set in IPG Road that would help me solve this.
In short, chatt_v2.xodr (original opendrive) file is imported to Vissim.
Then, Sumo netconvert command was used to convert Vissim network to opendrive format (file A - problematic junction opendrive). Thanks
I cannot find a way to import OpenDRIVE XORD and change its coordinates or translate it inside CarMaker. However, if you export it to rd5 and re-import it, the whole road network is selected at first and you can translate it:
image2235969 162 KB
I see, I will look at it.
Thanks. I did the same thing in Vissim (rotated and translated) in there as a workaround for now. I am curious to know what is the coordinate system in carmaker. What exactly is the rotation and translation needed to match coordinates when same opendrive file is imported in Vissim and CarMaker. It would be good to know that, in case there is a standard difference between vissim and carmaker import of opendrive files. Then there can be a standard rule around rotation and translation as opposed to specific for each network. Any clues on this will be helpful. Thank you very much for looking into this. Appreciate it.