Changes between Version 3 and Version 4 of GoogleSummerCode2022
- Timestamp:
- 02/16/22 18:12:19 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GoogleSummerCode2022
v3 v4 29 29 **Idea 1: Augment pgAdmin to support importing and exporting shapefiles** 30 30 31 ''Expected outcome'': There should be a menu option in the pgAdmin browser tree whenever you right-click a database, table, or schema that allows you to import or export shapefiles. The tool would use the shp2pgsql and pgsql2shp commandlines that are part of the PostGIS source code in much the same way the backup and restore data browse menu options 32 built into pgAdmin utilizes pg_dump / pg_restore. 31 ''Expected outcome'': 32 33 Import Feature: 33 34 34 This is to replace in newer pgAdmin the shp2pgsql-gui plugin (which still exists but is standalone) that could be hosted as a plugin in pgAdmin3. Here is a screen shot of what that looks like and what we are trying to achieve: 35 1) There should be a menu option in the pgAdmin browser tree whenever you right-click a database, table, or schema that allows you to import or export Dbase/shapefiles. 36 2) The tool would use the shp2pgsql and pgsql2shp commandlines that are part of the PostGIS source code in much the same way the backup and restore data browse menu options 37 built into pgAdmin utilizes pg_dump / pg_restore. It will look for the files in default runtime folder or user specified binary path. 35 38 36 -- IMPORT -- 39 3) If a particular table is selected, it will give option to export as a Dbase/Shapefile or import (append to) (no need to ask for table aside from export/import path) or append to 40 4) If no table is selected - it will pop up a list of tables (as show in export screenshot) and allow user to import a file as a table in currently selected schema. 41 If no schema is selected it would load in the default schema. 42 43 This is to replace in newer pgAdmin 4 6.5+ the shp2pgsql-gui plugin (which still exists but is standalone) that was hosted as a plugin in pgAdmin3. Here is a screen shot of what the old guis looks like. We want to achieve the same or similar functionality 44 45 46 ''Import'' 47 37 48 [[Image(postgis-qui-import-1.png)]] 38 49 [[Image(postgis-qui-import-2.png)]] 39 50 [[Image(postgis-qui-import-3.png)]] 40 51 41 -- EXPORT -- 52 53 54 ''Export'' 55 42 56 [[Image(postgis-qui-export-1.png)]] 43 57 [[Image(postgis-qui-export-2.png)]] … … 45 59 46 60 47 ''Skills required'': python, html, css, and javascript, ability to compile PostgreSQL code, ability to compile PostGIS code, ability to compile [https://git.postgresql.org/git/pgadmin4.git pgAdmin] 61 ''Skills required'': 62 63 python, html, css, and javascript, ability to compile PostgreSQL code, ability to compile PostGIS code, ability to compile [https://git.postgresql.org/git/pgadmin4.git pgAdmin] 48 64 some familiarity with PostGIS, PostgreSQL, and pgAdmin is preferable 49 65