Defining Routes
Burnside Mobile can store and display user defined routes. These are not turn-by-turn driving instructions but rather simple visual representations of routes that need to be covered. There are two ways of defining a route: by segment or by layer.
Routes defined by segment are more robustly integrated with the application and as such, this is the preferred method of defining routes in Burnside Mobile.
Defining Routes By Segment
Set the Key Value in your GIS Data
This approach relies on updating the key2 field in either the BM_Road or BM_Sidewalk layer. Using ArcMap or ArcGis Pro, isolate the segments that make up a route. Each segment that is to participate in a route must have its key2 field updated to include a reference to that route. The route reference is stored as an alphanumeric lookup key. Valid lookup keys are 0-9, A-Z, and a-z.
The key2 value can be edited by Administrators using Burnside Mobile and searching for the road section by agency id, then viewing the details, and using the attribute edit tools on the details form. This is a suitable technique for modifying a few road sections, but using ArcGIS will be more efficient for establishing new routes or updating a large number of roads sections.
Multiple Routes by Segment
Sections can participate in multiple routes by specifying each of the keys in the key2 field. These values should not be separated by a comma, space or other character. For example, if a road section is on routes identified by key 1 and key A, then the key2 value would be 1A (or A1).
Route Setting Value
Displaying this type of route on the map relies on the settings table. Each lookup key found in the BM_Road or BM_Sidewalk key2 field must have a route entry in the BM_Setting table. The value field defines the route name, display name, lookup key, and color.
In the image above, each segment with a key2 field containing d will be associated to West Route 4. Each segment with a key2 field containing e will be associated to West Route 5. A segment with a key2 field containing both d and e will be associated to West Route 4 and West Route 5. The displayName is presented to the user when choosing a route from a dropdown box and the name is used by the app to sort the dropdown list. Valid colors are Blue, Brown, Gray, GrayBlue, Green, LightBlue, LightBrown, LightGray, LightGreen, LightRed, MidBlue, MidGray, MidGreen, MidYellow, Orange, Purple, and Red. '
Route Setting Template
{'name':'West Route 4','displayName':'West Route 4','key': '4', 'color':'Green'}
Multiple Routes by Segment
Sections can participate in multiple routes by specifying each of the keys in the key2 field. These values should not be separated by a comma, space or other character. For example, if a road section is on routes identified by key 1 and key A, then the key2 value would be 1A (or A1).
Defining Routes By Layer
The BM_ReferenceLine layer can be used to store routes and other linear features. New features added to this layer that are intended to be routes must have the featureType field populated with ‘Route’ and the name field populated with a route name.
If you have existing routes in a format that allows them to be appended to this layer, make sure that when the append is complete the featureType and name fields are valid.
Displaying this type of route on the map relies on the settings table. Each route in the BM_ReferenceLine layer must have a ‘route’ entry in the BM_Setting table. The value field defines the route name and a display name.
The ‘displayName’ is presented to the user when choosing a route from a dropdown box and the ‘name’ is used by the app to sort the dropdown list.