The GIS Engagement Strategy Workgroup intends to instantiate the foundation for resource coordination and governance, data structure, and standards/procedures to develop GIS as a viable and necessary fabric of data for administrative, academic, and community uses. Striking a balance between security and sharing of data for improvement in education, modeling, planning, campus operations, wayfinding, and response.
Align Resource Management and Planning (RMP) GIS focus with the UC San Diego Strategic Plan. Goal 5 of the Strategic Plan, Supportive Infrastructure, is an area in which RMP development, maintenance, and use of GIS can have a direct and significant impact: enabling integrated technologies and process efficiencies. The data produced by RMP GIS, and any tools can peripherally assist meeting Goal 1, providing course work content and opportunities for internships and community scientist involvement. This platform can also assist answering questions in Goal 4, Community Enrichment, measuring of service activities and impact on the community.
The following is a list of tasks this Workgroup should, at a minimum, undertake:
Provide a forum for mainly RMP staff GIS collaboration
Advocate adoption of tools, methodology, and additional resources to target identified gaps
Understand areas of redundancy and formulate a plan for engaging with one source of data
Monitor the status of existing campus-wide data layers: who maintains each, how are they stored, where are they stored, how often they are updated
Prioritize the list of development for data layers
Determine which audience has access to data, from a practical as well as a security standpoint: internal power users or viewers, consultants, and the public
Generate creative and practicable GIS recommendations and solutions
Inspire innovation and pedagogical use of data by the UC San Diego community, and peripherally by the public
Members
Members
Major intended projects, and transition to internal Administrative ArcGIS Online data dissemination platform, over the course of the next year.
The roadmap shows the sequence in which you execute on features. In addition to strategic priority, the execution order is dependent on factors such as team composition and external dependencies. Features from different broader initatives may get interleaved. If you have your roadmap set up in Jira, you can embed that below.
Feature | Initiative | Dates | Priority | Effort | Status | Notes |
---|---|---|---|---|---|---|
List feature | List initiative that feature belongs to | Type /date to add a date range |
|
|
| Link to project pages and epics |
Feature | Initiative | Dates | Priority | Effort | Status | Notes |
---|---|---|---|---|---|---|
Feature | Initiative | Dates | Priority | Effort | Status | Notes |
---|---|---|---|---|---|---|
Feature | Initiative | Dates | Priority | Effort | Status | Notes |
---|---|---|---|---|---|---|