CalTrap Enhancements – Milestones Complete

Milestone 1:

1. Change trap type for Mexican Fruit Fly from MX to MP

When trappers place traps in the field, the trap IDs can use the proposed identification code in the ID generation process. The example provided is for Mexican Fruit Fly traps which use McPhail traps. When placed in the field now, the traps get an ID of MG343-S-MX. This enhancement will allow the Trap ID to be MG343-S-MP. The developer can create pests and define an optional override value to be used when generating Trap IDs in the field.

2. Routes can overlap

This enhancement will provide solution support for overlapping routes. The user can use the Route management tools to create routes that overlap.

3. Survey Creation Enhancement (workflow and being able to create another survey afterwards)

Add an additional step to the Survey creation tools to assist the user with re-using Survey area options. The form will ask if the user would like to create another Survey with the last user parameters and show the form.

4. Workload balancing

Workload balancing allows some Surveys to be split up into different weeks. For example, Los Angeles County services Jackson traps every second week but wants to service McPhail traps every week. With this enhancement, Jackson Surveys can be marked as requiring Workload Balancing. When creating a Route, the areas that fall into week 1 and week 2 balancing can be selected in a similar fashion to how the Books are selected in the administrator application.

Milestone 2:

1. Subgrid visualization tool

Introduce a new tool to handle visualizations of the subgrid systems on the map. This will allow the users to turn on or off any specific subgrids they want or turn them all off together.

  • View Survey by Route (new and accepted scope)

2. Display Trap location Heatmap tool

Allow users to filter traps and show heatmap to visualize distribution of traps over an area for a given period.

3. Data Recovery Tool

When an inspector ends their workday via the End Work tool, it has been observed that errors may occur during this time. Those errors may or may not be related to the underlying services being unavailable. If any errors occur at this time, it is possible that work data may be lost. This enhancement will backup data in the case of errors so it can be added manually at a layer point. The tool needs to backup the data securely and then enable supervisor users to see a list of backups and pick which data to restore.

4. Manage Surveys (ability to edit surveys)

Allows for surveys to be archived which is a way to nondestructively delete. The proposed tool will allow for administrators to unarchive a survey also.

5. Disjointed Surveys (selection of disjointed grids)

Allow the administrative users to create surveys using the point tool. The create surveys tool will have a point selection tool. The tool should work in a seamless way so that areas can be selected using a combination of geometry selection methods when picking the ‘Grid’ option.

6. Trapper Analytics Dashboard & Report

Create a simple dashboard and report to show analytics by route and by station. The user can launch a tool to make selections and see analytics about the state of a route or all routes in a station. When the user is happy with their selection, they can print a report that contains the details of the dashboard.

7. Work Synchronization (this happens in the background on the trapper app when they end work to confirm whether there’s a duplication of traps)

Milestone 3:

1. Update Trapper Bulletin Tool

Allows the administrator to update the trapper bulletin (the notes that are associated with a route) without opening up the manage routes tool.

2. Doodle Layer

Create a layer that allows users to add point graphics to the map to symbolize different points of interest to the trappers in the field. Along with a point symbol, the user should be able to enter a short string of text that can display on the map alongside the point. Trappers can also archive doodles using a feature action after clicking on one.

3. Re-using Trapping Sites (gray to green with lines)

When all traps are removed from a site, the site becomes ‘used’. It is visualized to assist trappers in placing traps in dispersed locations to improve trapping efficiency. If there are no suitable locations, trappers may reuse a site early but must override and log a warning. Used trapping sites will change between the two visualizations (grey and green with lines).

4. Assigning multiple trappers to a vehicle

Ability to assign multiple trappers to a vehicle, including all trappers in a county.

5. Persistent User Base Setting

Will allow user to edit the following features in the admin viewer and their selection will be saved – Layer visibility, Layer Opacity, Toggle Labels and Label Customization.

Milestone 4:

1. Switch Offline Maps

Allows the ability to change map context without the need to go back online after already having start work.

2. Offline Data Optimization

Ability to take a subset of relevant data offline (versus all) before going into the field.  This was done by implementing MMPKs over TPKs for base maps and parcel data for the CalTrap application.

3. Manage User’s Tool / Bad Data Handling

Allow for an interface that can repair User Roles and their portal group associations.  Update the “Adding and Modifying Users” to handle the “out-of-sync” User Groups.

4. Switching vehicles while offline

Before ending work, Users can log miles for multiple vehicles for their work session.  These vehicles must be assigned to the User before going offline.  If multiple users were to log on to use the same vehicle, the last one to sync work will have their miles recorded on the vehicle.  This will require the below workflows to be updated so that one work log can be associated with multiple vehicles:

  • ‘Manage Work’ workflow
  • ‘Manage Vehicles’ workflow
  • ‘Assign Vehicles’ workflow
  • All Reporting workflows

5. Sorting Order of Grids (Routing Conceptualized)

Originally, the functionality was to define the ideal path for offline users to route and share with other users.  However, this has now been updated to be able to sort the order in which to service trapping sites on both the desktop admin version and the mobile application.

6. Trapping Data Editor

Build an interface in CalTrap that allows for editing trapping data.  This will allow users to fix tables to make updates/corrections (i.e. Service dates, reported pests, etc.)