automated xml conversion using fme server

13
Automated XML Conversion using FME Server Sarah Wach Manitoba Hydro

Upload: safe-software

Post on 25-Jan-2017

175 views

Category:

Technology


2 download

TRANSCRIPT

Page 1: Automated XML Conversion using FME Server

Automated XML Conversion using FME Server

Sarah WachManitoba Hydro

Page 2: Automated XML Conversion using FME Server

Manitoba Hydro Electric Distribution staff and contractors are using GE FieldSmart to update GE Smallworld data in the field

Problem: Some of this data needs to be loaded into the ESRI SDE database

Page 3: Automated XML Conversion using FME Server

The Data• Road Crossing points

• Grounding Assessment Survey Poles

• XML files

Page 4: Automated XML Conversion using FME Server

- <Object id="19653" action="update" objectType="roadcrossings_edit" associatedObjectType="pole_base_location" associatedObjectId="16759520" UniverseId="0" WorldId="0">- <Attributes>  <Attribute id="OBJECTID">19653</Attribute>   <Attribute id="GlobalID">{B39F337D-884F-4432-9FDB-490E92127A01}</Attribute>   <Attribute id="INSPECTION_DATE" />   <Attribute id="USERID" />   <Attribute id="CROSSING_STATE">Existing</Attribute>   <Attribute id="POLE_A" />   <Attribute id="POLE_B" />   <Attribute id="MEASURED_CONDUCTOR_TYPE" />   <Attribute id="MEASURED_CONDUCTOR_FUNCTION">Neutral</Attribute>   <Attribute id="MEASURED_SPAN_LENGTH">0.000000</Attribute>   <Attribute id="MEASURED_CLEARANCE_M">0.000000</Attribute>   <Attribute id="MEASURED_CLEARANCE_FT">0.000000</Attribute>   <Attribute id="MEASURED_TEMP">-273.000000</Attribute>   <Attribute id="RULING_SPAN_LENGTH">0.000000</Attribute>   <Attribute id="ICING_AREA" />   <Attribute id="CROSSING_VERIFIED">No</Attribute>   <Attribute id="CROSSING_DELETED">No</Attribute>   <Attribute id="CROSSING_ID">19653</Attribute>   <Attribute id="COMMENTS" />   <Attribute id="MEASURED_CONDUCTOR_UNDER_3YRS">Unknown</Attribute>

Page 5: Automated XML Conversion using FME Server

- <Inspection>  <Status>Assigned</Status>   <CompletedDate>2016-02-17</CompletedDate>   <CompletedTime>13:21:23</CompletedTime>   <CompletedBy>veharder</CompletedBy> - <Results>- <Result id="inspection_date_time" type="inspection">  <Value>02-17-2016 13:19:47</Value>   </Result>  <Result id="pressed_ok" type="inspection" /> - <Result id="userid" type="inspection">  <Value>veharder</Value>   </Result>- <Result id="crossing_verified" type="inspection">  <Value>Yes</Value>   </Result>- <Result id="crossing_state" type="inspection">  <Value>Existing</Value>   </Result>- <Result id="crossing_state_man" type="inspection">  <Value>Existing</Value>   </Result>- <Result id="crossing_state_uman" type="inspection">  <Value>Existing</Value>   </Result>- <Result id="measured_conductor_under_3_years" type="inspection">  <Value>No</Value>   </Result>

Page 6: Automated XML Conversion using FME Server

FME Server Setup-Directory Watch-Email Topic and Subscription-Dedicated Server

Page 7: Automated XML Conversion using FME Server

Workspace Runner

Page 8: Automated XML Conversion using FME Server
Page 9: Automated XML Conversion using FME Server

XML Processing

Page 10: Automated XML Conversion using FME Server

Pole Processing

New features

Page 11: Automated XML Conversion using FME Server

Deleted and Moved Features

Page 12: Automated XML Conversion using FME Server

Challenges• -XML data model

changes• -SDE overwriting

attributes• Users entering

unexpected data

Future• -Vegetation

Management app

Page 13: Automated XML Conversion using FME Server

Thank you!Sarah WachGeospatial Data ServicesManitoba [email protected]