Hexagon Geospatial
MENU

Developer Discussions

Discuss topics with other Hexagon Geospatial Power Portfolio developers and experts to get the most out of our products.
Showing results for 
Search instead for 
Do you mean 
Reply
Highlighted
Occasional Contributor
Posts: 5
Registered: ‎11-10-2015
Accepted Solution

ATCOR Workflow via Python script

[ Edited ]

Is it possible to use ATCOR Workflow operators within a spatial model in a standalone Python script? I am using Python 3.4 and Imagine 2016, with an active license for ATCOR Workflow. 

 

I can run the spatial model with ATCOR operators in Imagine itself via the Spatial Modeler GUI, but in a standalone Python script I receive "Could not create operator" errors.

 

Here are the errors: 

 

 ***ERROR NUMBER 381 IN FUNCTION `anonymous-namespace'::LoadImpl***
 >>>HexGeo::SpatialModeler::OperatorFactory::Create failed<<
 ***ERROR NUMBER 1267 IN FUNCTION HexGeo::SpatialModeler::OperatorFactory::Create***
 >>>Could not create Operator: ATCOR.RunATCOR2<<

 ***ERROR NUMBER 381 IN FUNCTION `anonymous-namespace'::LoadImpl***
 >>>HexGeo::SpatialModeler::OperatorFactory::Create failed<<
 ***ERROR NUMBER 1267 IN FUNCTION HexGeo::SpatialModeler::OperatorFactory::Create***
 >>>Could not create Operator: ATCOR.CreateATCORProject<<

 ***ERROR NUMBER 58 IN FUNCTION erdas::sb_spatialmodel::Utils::ReadData***
 >>>Unspecified function failed<<
 ***ERROR NUMBER 53 IN FUNCTION Unspecified function***
 >>>Unable to create data object of type ATCOR.SensorTypeData<<

 ***ERROR NUMBER 381 IN FUNCTION `anonymous-namespace'::LoadImpl***
 >>>HexGeo::SpatialModeler::OperatorFactory::Create failed<<
 ***ERROR NUMBER 1267 IN FUNCTION HexGeo::SpatialModeler::OperatorFactory::Create***
 >>>Could not create Operator: ATCOR.RunATCOR2<<

 ***ERROR NUMBER 381 IN FUNCTION `anonymous-namespace'::LoadImpl***
 >>>HexGeo::SpatialModeler::OperatorFactory::Create failed<<
 ***ERROR NUMBER 1267 IN FUNCTION HexGeo::SpatialModeler::OperatorFactory::Create***
 >>>Could not create Operator: ATCOR.CreateATCORProject<<

 ***ERROR NUMBER 58 IN FUNCTION erdas::sb_spatialmodel::Utils::ReadData***
 >>>Unspecified function failed<<
 ***ERROR NUMBER 53 IN FUNCTION Unspecified function***
 >>>Unable to create data object of type ATCOR.SensorTypeData<<
Technical Evangelist
Posts: 207
Registered: ‎10-01-2015

Re: ATCOR Workflow via Python script

Hi Evan,

 

We are liaising with GEOSYSTEMS, the folks who develop and sell the ATCOR Workflow operators, to try to figure out what's going on. We'll get back to you as soon as we can.

 

Cheers

 

Ian Anderson
Chief Product Owner, Desktop Remote Sensing
Hexagon Geospatial
Technical Evangelist
Posts: 38
Registered: ‎09-16-2015

Re: ATCOR Workflow via Python script

Evan,

 

Spatial Modeler SDK uses namespaces for disambiguation of like-named plugin objects (Operators, DataTypes, etc.).  The ATCOR plugin for Spatial Modeler uses a namespace of “ATCOR” for the objects it adds to Spatial Modeler.  Unfortunately, the currently-released SMSDK has a limitation that Operators that are not in the “IMAGINE” namespace are not accessible via Python.  We hope to eliminate this limitation in an upcoming release.

 

Occasional Contributor
Posts: 5
Registered: ‎11-10-2015

Re: ATCOR Workflow via Python script

Ah okay, disappointing for the time being but good to know that things are always improving!

Do you need immediate support?
Please submit a Ticket through our
Development Ticket Portal.