Arcview Gis 3.3 Portable Free Do
You can also with any Windows 7 Pro or Ultimate,use the Windows XP mode and do not hack to make it works.It means, you have a Windows XP running in Windows 7 for free and compatibilitySee -GB/windows7/install-and-use-windows-xp-mode-in-windows-7 for more
Arcview Gis 3.3 Portable Free Do
Each extension in ArcGIS costs money beyond the base price of the software, and many school and companies save money by not purchasing extensions they do not need or only purchasing a limited amount of licenses to be shared on a network of several users. To allow everyone access to all of the licences, extensions must be enabled before tools within that particular toolbox can be launched. Enabling the extension checks it out from a central location and allows the tools associated with it to be utilized. Think about it like a public library. Instead of purchasing tons of copies of one particular best-seller, they purchase a limited number of copies, then lend them out free of charge to their registered users. While the book is checked out, no one else can read it. ArcGIS extensions work the same way - the extension will only work for the same number of computers for which the company or school has paid for until they are checked back in.
Two basic design goals are approached: the software shall be fast and it shall be portable. Due to this, the very first versions were developed to be run from the command line only - no graphical interface was supplied at first and all parameter had to be inserted by hand. This should increase the execution speed by leaving off slow visualisation. Also, due to these goals, the software was split into several parts. Each of them has a certain purpose and must be run individually. This is something that makes SUMO different to other simulation packages where the dynamical user assignment is made within the simulation itself, not via an external application like here. This split allows an easier extension of each of the applications within the package because each is smaller than a monolithic application doing everything. Also, it also allows the usage of faster data structures, each adjusted to the current purpose, instead of using complicated and ballast-loaded ones. Still, this makes the usage of SUMO a little bit uncomfortable in comparison to other simulation packages. As there are still other things to do, we are not thinking of a redesign towards an integrated approach by now.
NETCONVERT is able to directly read binary NavTech's ArcView databases. To convert such databases, you need at least three files: a file with the extension ".dbf", one with the extension ".shp" and one with the extension ".shx". Additionally, having a projection file with the extension ".proj" is of benefit. Since version 0.9.2 we do not suply the possibility to use different names for the files, so all files should have the same name besides the extension. To build your network from an ArcView-database use the option "--arcview=":
The problem is, that not all networks stored as ArcView-databases also use this naming scheme. During some further work with ArcView-networks, some further options got necessary which allow to name the fields the used database contains. The column the street name shall be read from may be specified using --arcview.street-id . You can also name the columns the names of the edges' origin and destination nodes shall be read from using --arcview.from-id and --arcview.to-id . If the no information about the starting/ending nodes is given and your database does not contain the columns "REF_IN_ID" and "NREF_IN_ID", nodes will be placed into the network at the positions the streets end.
Some databases do not contain explicite information about the edges' attributes (number of lanes, priority, allowed speed) at all. Since version 0.9.4 you can use types as described in "Types Descriptions" to describe your edges' attributes. You have to name the column to retrieve the information about a street's type from using --arcview.type-id . Of course, you have then to supply a type-file using --xml-type-files (or --types or -t ). If something fails with the types or the explicite values, you can catch it using --arcview.use-defaults-on-failure. Besides this, you can specify your own connections using --xml-connection-files (or --xml-connections or -x, see "Connection Descriptions").
ArcView-networks are (mostly?) encoded using geocoordinates which have to be converted to the cartesian coordinates system used by SUMO. Our current implementation is not yet fully developed, it works for the most cases, but you should not be surprised if it fails with a certain network. Contact us in this case, please. To describe how to convert the coordinates, you should know in which UTM-zone your network is located. Pass this to NETCONVERT using --arcview.utm . If the conversion can not be initialised, you may additionally use --arcview.guess-projection to let NETCONVERT guess the conversion by him own.
As FastLane is portable, you may encounter files generated on a Windows-machine. Those files give some strange warnings, something that should not happen if you supply the right net. To avoid them, use the --intel-cell switch to tell DUAROUTER it has to turn the byte order.