Description
In practice geotiff lat/lng values do not conform to the standard ranges (latitude: -90 to +90; longitude: -180 to +180), and use projection values to scale these.
BR adds: typically well formed GeoTIFF should contain it’s projection and for some it is not in a good or easy to use standard/projection
An example is the following output dataframe from processing november_tests_atlasai_assetwealth_allyears_2km.tif. The latitude values are greater than 90, therefore geocoding fails to identify country/admin1 etc.
timestamp country admin1 admin2 admin3 lat lng feature value
0 1514764800000 NaN NaN NaN NaN 410.5 0.5 asset wealth 1
1 1546300800000 NaN NaN NaN NaN 410.5 0.5 asset wealth 1
2 1577836800000 NaN NaN NaN NaN 410.5 0.5 asset wealth 1
3 1609459200000 NaN NaN NaN NaN 410.5 0.5 asset wealth 1
4 1514764800000 NaN NaN NaN NaN 411.5 0.5 asset wealth 1
Potential Solutions
see WorldModelers/ModelService
see geopandas - Managing Projections
Best case may be to ask the user in SpaceTag what projection/crs they have.
Description
In practice geotiff lat/lng values do not conform to the standard ranges (latitude: -90 to +90; longitude: -180 to +180), and use projection values to scale these.
An example is the following output dataframe from processing november_tests_atlasai_assetwealth_allyears_2km.tif. The latitude values are greater than 90, therefore
geocodingfails to identifycountry/admin1etc.Potential Solutions
see WorldModelers/ModelService
see geopandas - Managing Projections
Best case may be to ask the user in SpaceTag what projection/crs they have.