Closed ChristinaTremel closed 1 year ago
Andrew's Unorganized Notes Tree plotter used for tree database Collecting tree data in tree plotter - previously using field maps Work order system built into tree plotter - DSD doesn't have another work order system Started from scratch using treeplotter work order system Future idea that perhaps this could communicate with maximo in the future Send inspection and work to be performed to contractors to trim trees Tracking of trees history through time - built into tree plotter and easily viewable Tree planted and tracked - inspected - pruned - 5 times through cycle then needs to be removed How many trees pruned over certain period of time and cost associated On the fly data visualization can be done by any user within tree plotter Alan h. is the treeplotter administrator Customization to the software can be done without tree plotter support Adding fields, add and create users, etc. Public works identified that work orders may be a useful add on This is still being figured out on the DSD side Goal is to have tree plotter as single source of tree data city wide TPW, DSD, Watershed Protection - lia g sara c, have agreed to use Parks opted out of using tree plotter - didn't see immediate need and where implementing maximo Lisa - TPW won't be getting rid of maximo because other groups rely on it Per funding vendor is supposed to be the one figuring out TreePlotter maximo integration No scoping on this has been completed on this yet PlanitGeo could provide API for Maximo developer to set up integration DSD has transition from collecting tree data in FieldMaps to TreePlotter Export trees as shapefile or csv
10/30 Meeting Notes
Attendees: Christina, Andrew, Lisa, Cody, Will, Alan, Emily
Vendor Overview
DSD Use of TreePlotter
Background Info
TreePlotter Admins
Departments that have agreed to use TreePlotter in some aspect:
Contract
Additional Details
Main Goal for TreePlotter:
Next Steps
Originally posted by @ChristinaTremel in https://github.com/cityofaustin/atd-data-tech/issues/13962#issuecomment-1785967002