You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
At the moment Taswira is able to visualize only GCBM output. It has the table names, raster patterns and other things hard-coded into it for the sole purpose of visualizing GCBM output. It would exponentially increase the utility of Taswira if it were able to visualize any arbitrary combinations of spatial and non-spatial data.
Describe the solution you'd like
I think that if we are somehow able to offload the task of specifying table names, column name, raster patterns, SQL queries, etc to the user then we can solve this problem.
The text was updated successfully, but these errors were encountered:
abhineet97
changed the title
Taswira as general purpose tool for visualising arbitrary combinations of spatial and non-spatial data
Taswira as a general purpose tool for visualising arbitrary combinations of spatial and non-spatial data
Aug 27, 2020
abhineet97
changed the title
Taswira as a general purpose tool for visualising arbitrary combinations of spatial and non-spatial data
Taswira as a general purpose spatial+non-spatial visualization tool
Aug 27, 2020
this feature would be of great use and will be useful for the people who are using flint can visualise the outputs easily rather than building their own tool
Is your feature request related to a problem? Please describe.
At the moment Taswira is able to visualize only GCBM output. It has the table names, raster patterns and other things hard-coded into it for the sole purpose of visualizing GCBM output. It would exponentially increase the utility of Taswira if it were able to visualize any arbitrary combinations of spatial and non-spatial data.
Describe the solution you'd like
I think that if we are somehow able to offload the task of specifying table names, column name, raster patterns, SQL queries, etc to the user then we can solve this problem.
The text was updated successfully, but these errors were encountered: