Closed pmallas closed 2 years ago
This might not be a nvector code problem, but a numpy issue. But I thought I would mention it anyway.
I have the following code:
ecef = [[ 1782029.5702637 ] [-5958967.13026865] [ 1407960.53954478]]
ell = nv.FrameE(name='WGS84') p_EB_E = ell.ECEFvector(ecef) pnt = p_EB_E.to_geo_point() lon, lat, z = pnt.latlon_deg print(lon, lat) print(type(lat))
With Windows, I get the following output: [12.83821967] [-73.35070153] <class 'numpy.ndarray'>
with linux, I get this: 12.838219667803369 -73.35070153096443 <class 'numpy.float64'>
Any idea why one returns single element array vs a floating point?
Actually, it is not a difference between windows and linux but between versions - 0.7.4 vs 0.7.7 - sorry to trouble you
This might not be a nvector code problem, but a numpy issue. But I thought I would mention it anyway.
I have the following code:
ecef = [[ 1782029.5702637 ] [-5958967.13026865] [ 1407960.53954478]]
ell = nv.FrameE(name='WGS84') p_EB_E = ell.ECEFvector(ecef) pnt = p_EB_E.to_geo_point() lon, lat, z = pnt.latlon_deg print(lon, lat) print(type(lat))
With Windows, I get the following output: [12.83821967] [-73.35070153] <class 'numpy.ndarray'>
with linux, I get this: 12.838219667803369 -73.35070153096443 <class 'numpy.float64'>
Any idea why one returns single element array vs a floating point?