Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Leveraging ArcGIS Online for Public Utility Data

905 Aufrufe

Veröffentlicht am

Presented at the 2013 Esri Southeast User Conference. User case story showing how ArcGIS Online was used to publish a public-facing outage map for an electric utility. Presented at the 2013 Esri Southeast User Conference in Jacksonville, FL.

Veröffentlicht in: Technologie
  • Loggen Sie sich ein, um Kommentare anzuzeigen.

  • Gehören Sie zu den Ersten, denen das gefällt!

Leveraging ArcGIS Online for Public Utility Data

  1. 1. Leveraging ArcGIS Onlinefor Public Utility InformationDavid SpeightTrue North Geographic Technologies, LLCwww.tngeo.comwww.facebook.com/tngeowww.twitter.com/tngeo
  2. 2. • User Story• Business Problem• Technical Challenges• Solution in Action• Why is this relevant?
  3. 3. Business ProblemWeNeed aMap!
  4. 4. Business Problem• Outage Data• Telvent OMS• SQL Server• ArcGIS forServer Standard• SQL Server• ArcGIS forDesktop
  5. 5. Initial IdeaWe use the FlexViewerinternally….…let’s use it forthe public.
  6. 6. Technical Problems / Concerns• Opening the firewall• Server capacity• Server performance….do we need to buy more licensing?
  7. 7. Usability Problems / Concerns• Keep users on the corporate website• Mobile device compatibility• Needs to work like the rest of the web• What information / level of detail do weexpose?
  8. 8. Alternative ApproachCEMCOMSArcGISOnlineOnline Outage Map• Feature services• Web maps• Templates / apps /embed codeDesktopGP
  9. 9. Data Prep• Geoprocessing• Convert tabular data to feature class• Limit attribute output• Aggregate data by grid• Publish to Server or AGOL (new at 10.1)• Ready to publish?
  10. 10. Wait….….we’re still at 10.0(I don’t have a Server Publishing toolbox)
  11. 11. for field in fieldnames:element = str(field)value = str(row.getValue(field))attributeDict[element] = value# Create the geometry object featfeat = row.getValue(shapefieldname)poly = feat.getPart()for allRings in poly:for coordPair in allRings:xyPair =[coordPair.X,coordPair.Y]allPairs.append(xyPair)replaceRingsList = allPairsgeometrySyntax[geometry][rings][0]= copy.deepcopy(replaceRingsList)# place the geometrySyntax dictionarythat was created above into the cumulativeinputGeometries listgeometrySyntax[attributes] =attributeDictgeometrySyntaxDeepCopy =copy.deepcopy(geometrySyntax)Workaround
  12. 12. Final Solution• Python GP scripts• ETL script exported from ModelBuilder• Load data to AGOL via featureservices• Executed as scheduled task• 24 x 7 every 10 minutes• Web Map• Symbology• Generalized data• Popups• Embedded to corporate website
  13. 13. Final Solution• Feature Service Updates vs. Republishing• FS approach was faster (< 5s)• Lose the overhead of republishing servicedefinition, resharing, etc.• ArcGIS Online Organizational Account• Level 1 (5 users / 2500 credits)• In production since November 2012• Almost no credit consumption• Free to use AGO for other uses
  14. 14. Solution in Action
  15. 15. Summary• Publishing data to ArcGIS Online• Eliminated security concerns• Eliminated server capacity concerns• Purchase AGOL Organizational subscriptioninstead of more hardware/software• Kept users on the corporate website• Maintained compatibility with mobile devices• Easy to modify & add content
  16. 16. Thank you…David SpeightTrue North Geographic Technologies, LLCdspeight@tngeo.com615-890-7728www.tngeo.com