Download Arcview 3.2 Full Crack
Blossom Stemmer
netconvert is able to directly read binaryArcView databases ("shapefiles"). To convert such databases, at leastthree files are needed: a file with the extension ".dbf", one with theextension ".shp" and one with the extension ".shx". Additionally, havinga projection file with the extension ".proj" is of benefit. The optionto load a shape-file into netconvert in orderto convert it into a SUMO-network is named --shapefile-prefix . Because shape-filedescriptions use more than a single file, one has to supply the filename without extension, only. So, the following call tonetconvert should be used to import the roadnetwork stored in "my_shape_files.shp", "my_shape_files.shx","my_shape_files.proj", and "my_shape_files.dbf":
Unfortunately, shape files describe how information is storedphysically, but neither which is stored nor how the entries of theaccording database (*.dbf) are named. Due to this, one has to examinehow a given road network is stored within the database file and givethis information to netconvert; a plain callalmost always fails.
The table below shows which informationnetconvert is trying to read from the giveninput files, what the standard values are, and how they can be changed.Also, it shows whether the information is mandatory - must be given - oroptional.
Some shape file databases do not contain explicit information about theedges' attributes (number of lanes, priority, allowed speed) at all. Itis possible to use SUMO edge type fileto describe the edges' attributes. In this case, the column toretrieve an according street's type name from must be named using --shapefile.type-id and aSUMO edge type file must be given tonetconvert using --type-files . If something fails with thetypes or the explicit values, it can be catched using --shapefile.use-defaults-on-failure. In these cases,the default netconvert values are used. Besidesthis, it is possible to load own connectiondescriptions.
ArcView-networks are encoded using geocoordinates which have to beconverted to the cartesian coordinates system used by SUMO. To describehow to convert the coordinates, one should know in which UTM-zone yournetwork is located. Use projectionoptions to set the correct one.
Our main interest is of course the street network. The following filesdescribe this: strassen.dbf, strassen.shp, strassen.shx("strassen" is the german word for "streets"). When opening"strassen.dbf" we have to realize that there is only a few informationstored herein - neither the node names are given nor the streetattributes. Instead, the street attributes seem to be stored in anadditional database and are references by type names (column "strTypID"- strassen_typ_id = street_type_id). Also, the names of thisdatabase's columns have other names than expected.
The only problem with this is that we can not extract street namesproperly. Still, within FRIDA, theedges are numbered, and we may use the street id as name.The call has to be extended by: --arcview.street-id strShapeID
The possibility to describe edges using attributes was alreadyavailable in netconvert and may be used incombination with ArcView files since version 0.9.4. Still, the typeshave to be translated into XML. The generated file (frida.typ.xml)looks like this:
Looking a bit deeper at the network, we had to realise two furtherproblems. At first, highway on- and off-ramps are marked as "highway".this yields in a network where on- and offramps have the same number oflanes as the highways themselves. And it's definitely not fitting toreality, as the next picture shows:
Furthermore, all streets are unidirectional - even highways. This makesthe network not usable for traffic simulations when left in the orignalstate. Trying to convert the network with --arcview.all-bidi, that means trying to insertedges bidirectional, makes the city usable, but the highways are evenworse, now, because also the on-/off-ramps are bidirectional, then...
Using the current features we are able to parse the network from theFrida-project but we can not state it is completely usable for trafficsimulations. At least areas around highways are not realistic, becauseon-/offramps lack an explicit declaration and are due to this as wide asthe highways themselves. Furthermore, all streets within the network arecoded in just one direction. Extending them to be bidirectional solvesthe problem in inner-city areas, but yields in an unacceptable resultfor highways.
e59dfda104