How Can You Use FME To Power Your Open Data Initiative?

792 views
645 views

Published on

Presented by Brett Lord‐Castillo, St. Louis County Police

See more FME World Tour 2014 presentations at www.safe.com/recap2014

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
792
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

How Can You Use FME To Power Your Open Data Initiative?

  1. 1. CONNECT. TRANSFORM. AUTOMATE. Use FME to power your Open Data Initiative Brett Lord-Castillo GIS Programmer, St Louis County
  2. 2. Open Data Definitions  Open Licensing  Machine Readable  Open Format  Bulk Access  Discoverable  (http://okfn.org/opendata/)  (http://opendefinition.org/od/)
  3. 3. Open Formats  Shapefile  CSV  GeoJSON  TopoJSON? (Yes, there are other options)
  4. 4. Bulk Access  Self-Host  Socrata  CKAN/DKAN  GitHub? Yes, GitHub
  5. 5. File Geodatabase to Socrata  Writing to https://communities.socrata.com/catalog/rhok-st-louis  Just a reader and a writer  Edit writer feature types  Pay attention to your geometry column
  6. 6. We get a little bit crazy  Three different datasets  Vague attribute names  Some records are in the wrong projection!
  7. 7. This is Not Alternative Universe St Louis County
  8. 8. File Geodatabase to GeoJSON Live Demo! Live Demo! Live Demo!
  9. 9. ArcSDE to GeoJSON We get more than a little bit crazy  One Writer to rule them all  Remove all sorts of attributes  Use fme_feature_type to fanout (Not crazy enough to do this live)
  10. 10. But we can do this live!  Modify ToSocrata workbench to write GeoJSON 1. Copy transformers and dynamic GeoJSON writer from last workbench 2. Remove the SubstringExtractor 3. Edit writer Advanced Properties  Destination  Fanout Attribute 4. Run?
  11. 11. So you have an error…  Remember to set your Dynamic Properties too!  This error fixed by adding Schema Sources
  12. 12. Bringing into GitHub (simple)  Go to GitHub repository online  Create a new file  It’s text! Copy-paste!  Save with .json extension  Go to your file and see the pretty!
  13. 13. Bringing into GitHub (less simple)  Use a client https://windows.github.com/ https://mac.github.com/  Or use git  Zip big files! (or post-process with TopoJSON) https://github.com/mbostock/topojson
  14. 14. Wishlist  Publish to GitHub  API  Git?  README.md writer  Write a text file in markdown  TopoJSON writer  Publish Metadata to Socrata  Might be a bit more complicated
  15. 15. Thank You!  Questions?  For more information:  Brett Lord-Castillo:blord-castillo@stlouisco.com  St Louis County Emergency Management  @blordcastillo  http://github.com/blordcastillo  http://github.com/marigolds6

×