geomancer
geomancer copied to clipboard
Automated feature engineering for geospatial data
Right now, SpellBook relies on a simple ordered index from the input dataframe. If that's not the case, the output dataframe will be misaligned.
We upload a dataframe into BQ (as a table) for every call. This is inefficient given larger datasets. There should be a better way to: - Check if the dataframe...
We should first validate that the input columns exist before running the actual query.