agenda - geographic information systems | hennepin county · 9/5/2017 · agencies (i.e. data that...
TRANSCRIPT
When: Tuesday, September 5th | 9:30 – 11:30am
Where: Meeting Room at the Plymouth Library - 15700 36th Ave N, Plymouth
Agenda
Introductions + Updates from group (20 min)
Hennepin County (20 min) • FTP Site
• Data Sharing • Metro Parks, Trails & Bikeways Update • Local Update of Census Addresses (LUCA)
• Stormwater Data Collection Efforts • Group Discussion
Presentations (45-60 min)
• Minnesota Geo Commons + State Projects/Initiatives Updates o Mike Dolbow Dan Ross (MN IT Services)
• Hennepin County Tree Inventory
o Dustin Ellis (Hennepin County)
Closing (5 – 10 min)
Hennepin County GIS Users Group
September 5, 2017 | Plymouth Library
Agenda:Introductions and Lightning Round (20 min)
Hennepin County (20 min)• FTP Site• Data sharing• Metro Parks, Trails & Bikeways Update• Local Update of Census Addresses (LUCA)• Stormwater Data Collection Efforts• Group Discussion
Presentations (45-60 min)• Minesota Geo Commons + State Projects/Initiatives| Mike Dolbow• Hennepin County Tree Inventory| Dustin Ellis
Closing (5-10 min)• Next meeting• General discussion
Hennepin County GIS FTP Site• FTP site now available for sharing files between the county and its partners
• Intention for site use is for both project-level data and routine sharing• One secured account per partner agency has been established, as well as a general
folder that all agencies can access• Two-way uploads are permitted
• Hennepin County’s Survey Division will continue to distribute cadastral data on a monthly basis (Tom Bushey)
• Many private and public agencies have had accounts preemptively created for them. Contact me if you’d like your login information.
Data Sharing• Hennepin County has an inventory of data layers that can be shared with interested
agencies (i.e. data that aren’t available on Open Data) on a monthly basis
• ~25 layers were being shared with city contacts via our Survey Division’s monthly distributiono The layers were based on demand after asking city GIS staff what they’d like
from the county data-wise
• Hennepin County will continue a monthly GIS data share through the general folder on the new FTP siteo Ideas for layers that would be useful to your organization are welcome
• Our shareable layers will be distributed to the group in a follow-up email
Metro Parks, Trails & Bikeways Collaborative• Initial aggregation of the data occurred earlier this summer
• Schema revisions (v1.1) are currently under review• Data requests will be sent out to park/trail agencies shortly after new schema is
approved • Cities, Three Rivers Park District, DNR, etc.
• Hosting and distribution will follow other metro datasets (i.e. MRCC)• Will eventually be accessible on the Geospatial Commons
• Release to the Public is TBD
Project Information: https://metrogis.org/projects/park-and-trail.aspx
• Parks/trails data are present for each county
• Very good geometric (feature) coverage in Hennepin County
• Data to be distributed to park/trail agencies for review
• Similar review, submittalprocess as the Hennepin County bikeway data model
• Your agency’s participationin this project is importantand appreciated!
Local Update of Census Addresses (LUCA)LUCA is an opportunity offered to tribal, state, and local governments to review the United States Census Bureau’s address list for their jurisdiction prior to the 2020 Census.• The Census Bureau sent out invitations to participate in LUCA this July
• Hennepin County recently sent out email asking cities whether they are participating in LUCA or not
• Hennepin County will maintain a page on Basecamp software for tracking the project timeline and sharing workflows, issues, and information with cities
Rough Timeline:July, 2017: Determine which cities Hennepin County will be working with
October, 2017: Census-sponsored training workshops will be held
February, 2018: Address lists will be sent from Census Bureau to jurisdictions (120 days to send updated lists)
Q4, 2019 – Q1, 2020: Materials received back from Bureau, including field canvassing results. Jurisdictions can make appeals for corrections. New construction locations should also be submitted to Census Bureau.
April 1, 2020: Census Day
Stormwater Data• Hennepin County has been collecting stormwater GIS data from cities and
watershed districts since Spring of 2017
• Data have supported assessment of Hennepin County Regional Railroad Authority (HCRRA) corridor stormwater infrastructure. i.e. where is the water coming from and where is it going in the proximity of HCRRA corridorso Stormwater Infrastructure assessmento Water quality assessment
• Aside from HCRRA project, data have been useful to our internal staff for:o general analysis and mapping: locations of assets, ownership, flow direction, etc.
• The gathering of this data is helping to build momentum and feasibility for the metro project
• Stormwater data have been collected from 18 cities within and near the county this summer
• Data schemas exist in many different formats
• However some basic, useful commonalities are present:
-Asset type (catch basin, main, apron)-Pipe material (concrete, metal, plastic)-Pipe shape (circular, box)-Pipe diameter-Invert elevations-Install date-Ownership-More..
New Web Portal• New, public-facing website• One-stop shop for accessing data, maps, applications, GIS news, and contact information• Does not replace our Open Data site• Link to Portal: https://gis.hennepin.us/home/• May start pushing HCGUG content to this site
Group DiscussionCounty & metro interests have been expressed, now…
What’s important to you and your agency?
• How can this group better serve the collective interests of all attendees? (specifically municipalities and private sector agencies)
• Ideas for HCGUG meeting topics or structure
• Ideas for successful collaboration outside of HCGUG
Presentations
Tree Inventory Data CollectionDustin Ellis, Hennepin County Environment & Energy
Hennepin County GIS Technical Users Group, August 3, 2016
Tree Inventory Data Collection
Hennepin County GIS Technical Users Group, August 3, 2016
Reasons for having an inventory:• No idea what trees we have on our
property and what condition it is in.
• Trees are infrastructure that need maintenance.
• Proactive vs. reactive approach.
• Provides a common language with external agencies.
• Data-driven decision making.
The Commons & More
Building a Frankenstein Open Data Portal with FOSS, sweat, and tears
Mike Dolbow| GIS Supervisor | @mmdolbow
History
From the headwaters of the Mississippi…
History: DataFinder – 1998-2015
History: Data Deli – 1999-2015
“Uh-oh, Mom…I’m gonna need a better browser.”
History: Clearinghouse & GeoGateway – 2000-2015
User Reaction
Path to the Commons
• 2005: Conceptual Architecture Group publishes key white paper, “State GIS Enterprise Conceptual Architecture Design”
• 2008: Committee formed to work on the Commons project
• 2010-2011: Commons test bed team formed and test bed project completed
Path to the Commons
• 2011: MnGeo (MGIO) agrees to own project as requested by CIOs of DNR, MnDOT and Met Council
• 2012-2013: Multiple partners come together forming team to work on Commons project
• 2014: Soft release
• 2015: Official release
https://gisdata.mn.gov
FOSS
Along the way we faced a decision…
Platforms Considered (final eval in 2013)
• Esri GeoPortal
• GeoNetwork
• GeoNode
• CKAN
• Also:
• Dspace
• OpenGeoPortal
Value of Open Source
Strategy
• More than enough investment in Esri
• Open data needs to be in more than one format – not all proprietary
• It can still fit into the “ecosystem” and not be exactly like all the other pieces of the puzzle
DATA
Sweat
“Full speed ahead! Uh, maybe not…”
First decision: Scope
• No budget, limited time
• Relatively rigid scope:
• Organization publishers
• Free and open
• Cover at least part of MN
• Non-spatial OK if:
• Has a mappable foreign key
• Contains coordinates or geocodable data
• Metadata = Quality
• How much is enough?
• Must be able to determine a dataset’s fitness for a given purpose
Next step: Quality
What do you mean, “Frankenstein”?
• CKAN didn’t have everything out of the box
• We already had a working data warehouse system, and didn’t want to change that
• Content Management (Drupal) & Feedback (Disqus) required bolt-ons
By Universal Studios (Dr. Macro) [Public domain], via Wikimedia Commons
GDRS
GeoBroker
Commons FTP
Frankenstein as a Service
GDRS GDRS
DRUPAL
Making things fit
• Already a hard sell to change
• Why rearrange your data warehouse when you can build a bridge from it to your portal?
Documentation – Drupal. Feedback - Disqus
• Documentation
• Needed a “news”, help, etc
• Drupal plugin made sense
• Feedback
• Significant downside of old portals
• People want to connect, give each other advice…and complain!
• But wait…that’s two authentication systems
Flexibility – normally an asset
• Obviously the flexibility of CKAN was appealing
• At some point, this might make you feel a bit stretched too thin
Tears
Not so fast…
“We need a tool to create this metadata!”
• Creating metadata for each “resource” turned out to be like floating paper clips
• The team was comfortable just hacking the .xml examples
• Who knew not everyone would be up for that?
“Wait…we need unique URLs…”
• What if more than one county wants to publish a parcel dataset?
• Naming convention? Abbreviations?
• Settled on a publisher prefix, aka:
• us-mn-co-rice-plan-parcels
• us-mn-co-dakota-plan-parcels
“Can we publish CAD data?”
• One of our first local partners
• Didn’t realize it was in demand
• Had multiple problems:
• Formats we said we’d allow but weren’t fully implemented
• New formats that clearly fit the scope
“Please…take all my DEMs”
But hey…sometimes it’s all worth it
• 28 Publishing Organizations
• 695 Resources (8.14.2017)
• Steady Growth
• https://gisdata.mn.gov/dataset/society-commons-metrics
The “RagTag” Team
MnGeo and State Projects
Proirities asked for by the GAC
Updates on MN GAC priority projects and initiativesGAC Rank Project or Initiative Description Status Project Owner Champ
1 All Data Free and Open Active Len Kne Ross2 Image Service - Sustain Active Mike Dolbow Ross3 LiDAR Committee - Move Forward Proposed Sean Vaughn?4 Image Service - HTTPS, Tiling, Etc. Active Mike Dolbow Ross5 Parcel Data Active George Meyer6 Address Points Data Active Adam Iten Ross7 Street Centerline Data Active Adam Iten Ross8 EM Damage Assess Data Standard Active Brad Anderson Lusk9 Basemap Services Active Sonia Dickerson Ross
10 Geocoding Service Active Mike Dolbow Ross11 Parks and Trails Data Standard Active Jim Bunning Ross
Address Points
Future Option
R&H MnDOT or
MnGEO
RCER&H
MnDOT(MnDOTmodel)
RCE(MnDOT)
StatewideGDB
(Statewide Standard)
MN Geospatial Commons
Public Access
File GDB(change or full
upload)
Shapefile(change or full
upload)
Authoritative Data
StandardizedAggregated
ETL Conflation
Alert
GDRSState Agencies
AlertETL
Conflation
AlertETL
Provide:• Common method for
accepting data• Common standards • Common methods,
tools for validating, standardizing, aggregating data
• Consistent communications about status
ETL Conflation
Statewide Centerline Initiative
Parcels
• Standard on hold until Address Standard approved
• Collecting, standardizing, and aggregating
86 counties collected
Working on aggregating and routine collections
• Full aggregate available to government agencies only; counties have asked the state not to share parcels obtained for their counties.
• This approach hinders efforts to achieve a statewide, shared parcel layer.
Boundary Update Project
• Background – MN boundary data layers are out of date and need to be updated. More current and accurate authoritative information is available.
• MnGeo will lead an effort to identify stakeholders, authoritative data stewards, and resources required to develop, document and evaluate a process for updating, aligning and maintaining statewide geospatial boundary data layers going forward.
• Outcomes – stakeholders and authoritative data identified, process, updated PLSS, process for other related layers
• Discussion - What role can the GAC play? User Groups? • Committee or Workgroup?
NG9-1-1 GIS Project Update
• GIS Data Collection, Assessment, and Preparation• Data Readiness Profiles• Data Preparation Projects
• GIS Data Workflow and Repository• Data uploads and portal• Normalization and Validation• Aggregation
• MN NG9-1-1 GIS Data Standards• Next stakeholder review• Approval of Version 1
• Newsletters: http://tinyurl.com/mngis911news
Other large projects
• Website for DNR Parks & Trails
• Geocoding & Map Services for DHS
• Hosting & Business Intelligence for DOT
• Address Points Editor