MetroGIS Logo: A Common Ground. MetroGIS Logo: Sharing Information Across Boundaries.
   Serving the Minneapolis/St. Paul Metropolitan Area Home   |   Search   |   Contact Us    
 
What is MetroGIS? 
Deliverables & Outcomes 
Business Planning 
What's New 
Major Accomplishments 
Annual Reports 
Affiliations 
Awards 
Grants 
History 

Overview 
Short Quotes 
Testimonials 
Studies 
Performance Measurement 

Overview
Looking for GIS Data or Web Map Services? 
Looking for GIS Applications? 
Looking for GIS Standards/Best Practices? 

Meeting Calendar 
Policy Board 
Coordinating Committee 
Technical Advisory Team 
Special Purpose Workgroups 
Organizational Structure 
Operating Guidelines 
Dissolved Teams 

Presentations 
Major Reports 
Articles & Publications 
Glossary

 

Dissolved Teams > Data Standards Team

April 1, 1998 Minutes

The meeting began at 8:30 AM in at the Land Management Information Center (LMIC) in the Centennial Building.

Members Present: David Windle, City of Roseville; Chris Cialek, LMIC; Jay Krafthefer, Washington County; Jim Maxwell, The Lawrence Group; Ron Wencl, U.S. Geological Survey; Jay Wittstock, Dakota County.

Others Present: David Arbeit, LMIC; Ed Krum, MnDOT; Sally Wakefield, Governor's Council

Support Staff: Mark Kotz, Metropolitan Council

1, 2, 3. Introductions and Modifications to Agenda and Meeting Notes

Team members made introductions. There were no modifications to the agenda or the meeting notes from the previous meeting.

4. Information Sharing & News from Other Committees and Teams

Chris Cialek (Chair of the Governor's Council Standards Committee) explained that the GC Standards Team currently has 4 active working groups. They are working on 1.) metadata clearinghouse, 2.) coordinate system standards for state agencies, 3.) positional accuracy issues (including federal standard), and 4.) communications (web site, email lists, etc).

Ron Wencl mentioned that the FGDC currently has out a proposal for a "governmental unit boundary data content standard." This is a proposal to begin creating a standard and not a proposed standard. Wencl thought it might be appropriate to respond and let them know what is going on in MetroGIS. Cialek agreed. Kotz noted that the group working on it is comprised of entirely federal people and that we might want to comment that some state and local voices would be appropriate.

Kotz and Cialek agreed to compose a brief response to the proposal that would go out from MetroGIS as a whole. Arbeit said that he could shepherd the letter through MetroGIS quickly. Comments need to be received by the FGDC on or before April 15th.

Finally Wencl noted that the Data Finder site is up and running. Work is still being done on the site, but it is usable

5. Review Items from Previous Meeting: Address Guidelines & Metadata Guidelines

Kotz explained that the address guidelines document has been approved by the Policy Board and has been distributed. It is also available on the web. The recommendation to adopt the Minnesota Geographic Metadata Guidelines has also been approved by the Policy Board.

6. Washington County jurisdictional boundaries pilot project

Jay Krafthefer gave a presentation that explained the standards related issues that resulted from the Washington County jurisdictional boundary pilot project. Krafthefer touched on the 6 issues sent to the Standards Team from the Content Team:

  • accuracy ratings
  • unique polygon issues
  • polygon link/label
  • polygon attributes
  • line attributes
  • boundary issues

Krafthefer explained that they are uncovering many other issues as well that may be standards relate in one way or another. They include:

  • Metadata required as standard
  • Maintenance of municipal data, how often and to what degree
  • Timeliness/minimum date issue (consider regional MCD layer being developed by Met. Council)
  • Level of historic perspective
  • What is being mapped (e.g. best source of legal)
  • What should be the source of legal (written by surveyor?)
  • Software and deliverable formats
  • Quality rating (positional accuracy is only a subset of this)
  • Arc/line definition
  • Arc/line label coding
  • Single description of entire MCD
  • Naming conventions for features
  • Use of particular data model
  • Map and content check / verification sources?

Team members agreed that there are many issues that have surfaces here and that our Team may not be able to take many of them. We may want to direct some or many of them to other bodies.

Finally Krafthefer noted that the Washington County Jurisdictional Boundaries project is ONGOING. He expects this list to grow as more issues are uncovered.

7. Six jurisdictional boundary issues from Data Content Team

The team, due to time constraints, did not specifically address these issues but agreed to make this the main agenda topic at the next meeting.

8. Metropolitan Council hybrid county/MCD layer development

Kotz explained that the county/MCD layer for the 7-county metro area is complete and currently includes data from 5 sources (Dakota, Scott and Washington Counties, DOT and Met. Council). Kotz explained that he completed the layer using the methodology that was presented to the Standards Team at the previous meeting in September.

The Policy Advisory Team is currently looking at two issues related to this. 1.) Met. Council's proposal to maintain a metro wide layer on an annual basis. 2.) issues of distributing this dataset comprised of multiple sources.

9 & 10. Other Items & Next Team Meeting

The next team meeting will be on Wednesday, April 22nd; 8:30 AM to 10:30 AM at LMIC.

11. The meeting was adjourned at 10:30 AM.

Action Items: Kotz & Cialek will draft a brief response to the federal proposal for a governmental unit boundary standard.

Prepared by Mark Kotz, GIS Specialist, Metropolitan Council

   
   Page last updated on April 02, 2002. Home   |   Search   |   Contact Us