Methodology
I started the project by importing the two applicable SNF files (gsnf933r.e00 and gsnf933s.e00) using the Import71 application. The resulting coverages where in ArcInfo format, so I converted them to shape files for use with ArcView. The resulting network theme had all the streets of the lower mainland, but it also had many line features that were not streets, such as railways, powerlines, and water features.
The meta-data indicated which values for Class indicated streets. The Type field only had enteries for streets. I started by doing a null query for type ([Type] = "") to choose everything that was not a street. I then reversed the selection and added to the set with the query
([Class] = "B" ) or ([Class] = "BMN") or ([Class]="BMU") or ([Class]="BSI") or ([Class] = "E") or ([Class] = "F") or ([Class] = "FEX") or ([Class] = "FRA") or ([Class] = "H") or ([Class] = "HMU") or ([Class] = "HSI").
Upon closer inspection, I realized that there were some street features that did not have either Type or Class enteries, so I added a query
([Addr_fm_le] > 1) or ([Addr_to_le] > 1) or ([Addr_fm_rg] > 1) or ([Addr_to_rg] > 1)
to the set. This added any feature that has geocoding addresses (only streets would have this information).
I then created a new shape file with the selected features. This shape file contained only street features, and would be used for the network analysis.
I then started finding routes to and from SFU to my house and using the resulting routes to find potential problems. Naturally, overpasses presented a problem. This was solved by creating two new fields--F_elev and T_elev. These fields set the elevation of the To and From nodes of an arc. By varying these elevations, I could indicate whether a street connected to another street, or passed over it. This was very importand around the bridges--Network Analyst always wanted to jump off a bridge mid-span. I was also wanting to jump off a bridge mid-span by the time I was done inputing the From and To node elevations.
I also added a field called "ONEWAY". This field is used by Network Analyst to indicate the permitted directions of travel along an arc. The four possible values are:
I also had to connect many of the streets that are supposed to be connected--but weren't--and disconnect some streets that are not supposed to be connected (or just plain don't exist).
Because I had changed the length of several of the arcs, it became necessary to recalculate the distances of the arcs. This was a tremendous problem. Using "calculate" and using the command [Shape].ReturnLength would only return the length in decimal degrees. Using the meta-data I found that the SNF file uses the NAD27 projection. This is the State Plane 27 projection. However, the type of data was not specified. I had read that there is a Canada-Mean type for NAD27, but I could not find its particulars. ArcView doesn't have Canada-Mean, so I used Washington, North.
The command [Shape].ReturnLength in "calculate" would still only return the distance in decimal degrees. Eventually, I found an Avenue script called calcapl.ave that would return the length in meters. I used the new length data in conjuction with a Speed field that I had added (with the speed limit for streets) to calculate the time cost of the arcs. This was used by Network Analyst to calculate the fastest route.
I had recorded the position and waiting periods for many of the stop lights and stop signs along anticipated routes. Unfortunately, I was unaware of the difficulty of making use of this data. After finding out how it is done (in next semester's text book), I quickly abandoned the idea of using this data. By that point, however, it had consumed large portions of the time I had allotted for this project.