|
1. Call to Order
Chair Rick Person called the meeting to order at 1:08 p.m. at the Metropolitan Council Offices in St. Paul.
Members present: Chair Rick Person (City of St. Paul); Jane Harper, (Washington County); Will Craig (UM CURA);
Bart Richardson (DNR IS); Roger Carlson (City of Minneapolis); Don Yaeger (LMIC); Tim Zimmerman (Hennepin County); John
Lunde (Sufficient Systems)
Members absent: Judie Erickson (City of St. Louis Park); Kathy Johnson (Metropolitan Council) Marcel Jouseau
(Metropolitan Council), Marcia Broman, (Metropolitan 911 Board), Nancy Pollock, (Metropolitan 911 Board); Dale Nikkola
(Anoka Electric Cooperative); and Michael Munson (Metropolitan Council); Dennis Carlson (Anoka-Hennepin IDS #11); John
Connelly (St. Paul & Ramsey County Charter Commissions); Kent Treichel (Wilder Foundation)
Visitors: Jim Maxwell, The Lawrence Group; Randall Johnson, MetroGIS Staff Coordinator Metropolitan Council
Support Staff: David Vessel; Theresa Foster
2. Accept Agenda
The agenda was accepted, as submitted, except Item 5e was moved to follow Item 5f and Item 5c was moved to
follow Item 5e.
3. Accept Meeting Summaries
The meeting summary from March 6, 1998 was accepted.
4. Introduce Theresa Foster, New Coordinator Business Information Needs Project
Randall Johnson introduced Theresa Foster. Foster will be the support staff for the Data Content Advisory Team
and will be the new coordinator of the business information needs project. Foster recently held a position as project
manager for MARIS, the state of Mississippis Geographic Information Council, similar to LMIC.
Member Lunde arrived.
5. Action/Discussion Items
5a. Direction to Team Follow-up to June 3rd MetroGIS Data Users Forum
Theresa Foster reported that the Coordinating Committee has asked the Data Content Advisory Team to form a
workgroup in order to evaluate several enhancements suggested for the Regional Street Centerline Database and to
prepare a recommendation for the next steps. A workgroup was proposed to provide direction on the timing, funding
source, and responsible party(ies) for each of the "needs more discussion" items provided in the matrix included with
the agenda packet. Johnson reported that the Coordinating Committee has directed the Team to form a workgroup to
identify appropriate cost-benefit analysis and prioritize the "needs more discussion" items. Will Craig suggested that
a scope of work needs to be developed before the Data Content Advisory Team could decide how it wants to proceed. Jim
Maxwell of The Lawrence Group reported that some of the "needs more discussion" items have been dealt with by The
Lawrence Group since the June 3rd Forum and that he would provide this information to staff to consider when developing
a proposed scope of work.
Vessel arrived.
Motion: Craig moved and Harper seconded to propose a strategy to address enhancements to the Regional Street
Centerline database suggested at the June 3rd Data Users Forum and to delay action until the next Data Content Advisory
Team Meeting. Motion carried unanimously.
5b. Proposed Technical Advisory Team
Staff summarized direction received from the Coordinating Committee on August 27th to evaluate the
concept of consolidating the Data Access, Data Content, and Standards Advisory Teams into a single Technical Advisory
Team. Craig suggested that the responsibilities of the Technical Advisory Team would be to activate and deactivate
workgroups and provide primary direction to these workgroups. It was agreed integration of the Access, Standards, and
Content Advisory Teams would decrease duplication of steps in the Business Information Needs Workgroup process and
afford staff more opportunity to develop comprehensive options for team consideration. The group concurred this
reorganization would provide a wider range of opportunities for team members and would be easier to support than the
current team structure. The group, however, agreed and cautioned that the Technical Advisory Team should be balanced
with technical members and non-technical members and that existing members of the teams should be encouraged to
continue to participate.
Motion: Craig moved and Harper seconded that the Data Content Advisory Team support consolidating the Data
Access, Data Content, and Standards Advisory Team into a single Technical Advisory Team. Motion carried unanimously.
In response to the motion, Craig suggested that individual team members should be thanked for their
participation and the new team needs to be opened up for new members to join. Person suggested that current committee
members should be invited to participate first, then extend invitations.
5d. Business Information Needs Project Update
Teams Role in Fair-Share Financial Model Project
Johnson summarized the teams role in the fair-share financial model project. Specific team
responsibilities include providing feedback on the makeup of the information needs workgroups and recommendation to the
Coordinating Committee for the deliverables from the information needs workgroup process (data specifications,
custodians, custodian responsibilities, user satisfaction, database enhancements). Harper asked about the scope of work
for the project, what does it consider? Johnson related that the project will focus on using jurisdictional boundaries,
addresses and parcel boundaries to define how MetroGISs needs converge or diverge from the NSDI framework data
and functions.
Parcels Information Needs Workgroup
Foster reported that the parcels information need workgroup is in the planning stage. Parcels boundaries and
location will be the focus. Feedback was requested on the guidelines for populating the workgroup. Foster provided the
members with background material and a draft of candidate participants for members to review. Foster will e-mail
guidelines to all members on September 30 so that they can review guidelines and e-mail back their suggestions. Johnson
asked members for specifications based upon parcel information needs. Craig suggested that the make-up of the workgroup
should be 75% user and 25% producer. Carlson suggested more emphasis should be placed on representation from producers,
they have an equal need. Vessel stated that potential users, as a group are, larger than the producers. Staff requested
members to provide feedback on guidelines and candidate participants in the next day or so, noting the workgroup
session is tentatively scheduled for November 5.
Land Use Plan Information Needs Workgroup
Foster reported to the members that organization and work planning meetings would start late October. Focus on
research will be centered on the I-35 W Land Use project. Workgroup contingently set for mid-January.
5f. Summary Document Defining Priority Business Information Needs
Foster reported to the members that a summary document on "Defining Priority Business Information Needs" has
been started to clearly define the process of MetroGISs Priority Business Information Needs Project. The
executive summary will be available on the MetroGIS WEB with information on how to download the documents.
Craig departed.
5e. Jurisdictional Boundary Data Maintenance Handbook
Harper reported on Washington Countys effort to document the findings of their jurisdiction boundary
project. The final report is intended to serve as a resource for other counties but is not envisioned to be written in
the form of a "handbook". She presented the document at the county user group and is in the process of updating the
preliminary draft. It should be available for distribution later this Fall.
5c. Update on "Framework Data" Project
Johnson summarized the progress of the framework data project. Person noted that the federal government has
bought into the need that the framework data should be free and widely available to all people. Johnson asked would
this be realistic for a local government unit. Person noted that some states actually do make geographic data readily
available for all people to access.
6. Next Meeting
The next meeting set for December 9 from 2 4 p.m. at Metropolitan Council.
7. Adjournment
The meeting was adjourned at 3:07 p.m.
Submitted by Theresa Foster, MetroGIS Technical Coordinator
|