Closed jonselling closed 2 years ago
It kind of looks like the same issue that was raised here:
You are correct from looking at the issue, but I feel like the resolution could easily be to change the order of the code in the Transformer's Initialize()
function. There is really no reason to print an error for something that could be / is initialized shortly afterward.
@agyoungs have you ran into this?
I believe this will get fixed once #666 gets merged (due to re-ordering of the Transformer::Initialize()
function)
Resolved via: https://github.com/swri-robotics/marti_common/pull/666
When initializing the transform manager, the Wgs84Transformer and UTMTransformer seem to fail when initializing:
I believe it is because each of them check that the
local_xy_util_
pointer is not null and that check fails. Here is the UTM transformer check.The
Initialize()
function is called from the Transformer parent class's Initialize function here.The
local_xy_util_
pointer isn't set until after that function is called.As a side note, those transformers do accept a
local_xy_util
pointer in their constructor, but they are set to null