200 likes | 214 Views
Learn how to streamline data publishing with a systematic 1-2-3-4 workflow, maximize ROI, and embrace ODP for wider data dissemination. Explore tips on geodatabase editing, metadata management, map services, and ODP styling.
E N D
Publishing to Open Data Portal (ODP): Our 1-2-3-4 Workflow Matt Fancher Software Engineer Department of Technology, City of Columbus Jaclyn Cardillo Software Engineer Department of Technology, City of Columbus Ohio GIS Conference September 25 – 27, 2017 Hyatt Regency Columbus Columbus, Ohio
Presentation Agenda • Publishing data to ODP • Overview of our 1-2-3-4 workflow • Writing metadata for ODP • Publishing map services for ODP • Registering layers with AGO • Styling ODP
Publishing Data to ODP • City has made a big investment in GIS data • Need to maximize return on that investment • ODP is a low cost, COTS solution to get data to larger audience, increasing return
Columbus GIS at a Glance • 300+ desktop users • 100+ dependent maps and apps • 8 production map servers • 14 enterprise geodatabases
1-2-3-4 Workflow • Can’t publish/update one layer at a time • Need systematic approach in order to be sustainable • Decided to implement 1-2-3-4 workflow 1 2 3 4 EditGeodatabases Publication Geodatabase On-Premise Map Services ArcGIS Online & Open Data Portal
(1) Edit Geodatabase • Alias your feature classes and attribute fields in the geodatabase • Use editor tracking with default field names • Write metadata! FGDC-complaint metadata isn’t needed for ODP (though it wouldn’t hurt). This info can carry through to ODP.
(2) Publication Geodatabase • Automate replica sync • Remember metadata updates don’t sync • Disable editor tracking • Consider replicating to Web Mercator
(3) Map Services • Feature class and attribute aliasing should be automatic • Hide fields that aren’t useful; use def. queries to filter unwanted features • Symbology and scale dependency doesn’t matter • Enable WMS if you want to expose that API via ODP • Slice and dice layers into services as you please
(4) ArcGIS Online & ODP • Hard work is done; just register your map service layers in AGO and share item with OPD group • Enable metadata for your organization (Settings > Item Details) • Create and AGO account specifically for publishing data (we use ColumbusOhioGIS) • Don’t waste time entering item description info; import your structured metadata as XML
The Trouble with Metdata… • Metadata updates don’t move thru workflow like data updates • Need to update publication date of AGO item when data is updated (Python) • Need to update metadata doc of AGO item when the description, contact info, domain values, etc change (second Python script).
Legacy vs New ODP - Embed JavaScript - Enhanced API Explorer - Esri Recommends Upgrading - Update View Data
Styling Tips • Chose • Screen Sizes • Comment • Curate: stealing • = time consuming • Modern, but • simple
Miscellaneous Stuff • Don’t spend much time or effort on thumbnails • Don’t try to get too clever with tags • Understand ODP download caching • ODP isn’t designed for cached map services
Questions Matt Fancher Software Engineer Department of Technology, City of Columbus Jaclyn Cardillo Software Engineer Department of Technology, City of Columbus Ohio GIS Conference September 25 – 27, 2017 Hyatt Regency Columbus Columbus, Ohio