-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GSOC idea: Add Spatial Data Support to the Data Retriever #797
Comments
@ShivamNegi, The Data retriever handles tabular data from fetching it to cleaning and installing this data into the respective database systems like Postgres, Mysql, sqlite, csv and etc. The Data retriever also handles spacial data but to a limited support. The tool can fetch spacial data to your local system, however no installation of this data into any database management systems is supported. Spatial data can be inform of points, lines, polygons and based on the data producers, different data structures are used to store the data. A few GIS file formats are Raster formats Vector formats Grid formats: examples of libraries The project focus on adding support for this type of data. A good example could be Postgres using Postgis, data can be stored in to the database |
So If I understood right. Python scripts will have to be made for installing above mentioned GIS formats in Postgis. These scripts will be added under
|
Pretty much. So for Postgis we can add the scripts to the postgres engine in |
Hi @ShivamNegi - glad to hear your interested in this one. Spatial data is becoming a such a common format it would be great to actively support importing it into databases. In addition to PostgreSQL + PostGIS we'd also like to support SQLite + SpatiaLite. |
Closing for the moment, but feel free to reopen if you have more questions as you work on your proposal. |
I would like to know more about this idea. Could you help me with insight of the project goals and implementation requirements. Thanks.
The text was updated successfully, but these errors were encountered: