Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel

[Imported] Adding geo co-ordinates for objects by name using SQL

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.

Janeway Janeway

[Imported] Adding geo co-ordinates for objects by name using SQL

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: florian, originally posted: 2018-10-25 15:56:41 Id:229
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.


**_Geo co-ordinates are stored in an Aggregate, which is a 'tree' of tables/classes separate from the main 'CDBObject' tree. Aggregates enable the main objects to have fewer redundant fields when there are options in the configuration. Aggregates are indexed by the id (of the main CDBObject) and the name (AggrName) [the latter because more than one aggregate can be used, but that's another story!]._**

**_Here's some SQL which updates the Geo co-ordinates of an object (assuming that the location configuration has been set to Static):_**

_update CGISLocationSrcStatic set Latitude = 51.05838, Longitude = 4.09659 where id = ( select id from cdbobject where fullname = 'mygrouppath.myobjectname')_

**_In the past, users have added metadata fields to objects for Latitude and Longitude._**

**_Contributors are invited to add the SQL which would transfer this data to the aggregate!_**