Re: [GRASS-dev] PostGIS manager for GRASS GIS
Hi all, Shall I go with this PostGIS manager proposal and apply on melange website? Any further suggestions are welcome Only one day is left to appply. Thanks and regards, Mohit On Wed, 04 Apr 2012 01:56:17 +0530, Mohit Kumar wrote: Hello Martin, Sorry couldn't reply earlier as I was stuck with some college work. On Mon, 2 Apr 2012 21:00:51 +0200, Martin Landa wrote: Hi, 2012/4/2 Mohit Kumar mohit.kumaru...@students.iiit.ac.in: I am interested in making a PostGIS manager in GRASS as a GSoc 2012 task. PyGreSQL is a python module that allows easy use of database operation API from a pyhton script. So it will be like a wrapper over the database. This can be done using wxPython and will be OS independent. Sorry to bug you all, but I am very much interested in developing for GRASS. [...] there is new development ongoing for this in GRASS 7, perhaps a good moment to integrate a manager. Maybe Martin has some insights for us over the next days. Its good to know that development is ongoing for this in GRASS, I sincerely want to work on this as my GSoc task. the current PostGIS-related development in G7 is not much related to this idea. The vector engine in G7 is currently able to read PostGIS geometry data natively without any abstract level (like OGR-PostgreSQL driver). Also write support has been recently implemented. The current implementation is focused on simple feature access, GRASS builds a pseudo-like topology as for OGR links (see v.external). At this moment I am working on PostGIS topology support in GRASS. I have made a brief idea for the manager. The following are the various modules of the manager 1. Setup connection : This module will set up the connection with the remote database. It will take the input parameters from user and pass them to a connection string. After the connection has been established, the user will be shown the various tables(maps) that are stored and other information about the database and the connection This is already available in wxGUI [1]. Of course there is always a space for any kind of improvements. But basically it's already there, to add widgets for entering username and password is quite easy task. 2. View and edit data : This will display the data of the table in a window frame. One can view the map and modify the table values or the attributes. Also possible in current wxGUI [2]. You just create a link using `v.external` and display the map in the map canvas as normal GRASS vector map. Also direct OGR access [3] is possible (no links, pseudo-topology built on the fly) 3. Import to GRASS Data : This gives the user an option to save the data in Grass format for further processing/analysis of the data. This also gives user an option to discard the data which is of no use. Possible with `v.in.ogr`. Simple wrapper based `v.in.ogr` for importing PostGIS is already there [4]. 4. Execute PostGis functions (geometry processing)on database and save output in grass data format. This could be improvement. 5. SQL interface : This provides the advanced user to modify the database by use of direct SQL commands on the database. 6. Export GRASS data to PostGIS data : Convert the Grass Data to SQL database. First convert the Grass data to Esri Shapefile(.shp) using OGR and then converting that data to SQL database (shape2sql). Why?? You can export data directly using `v.out.ogr` [5]. No need for Shapefiles, that's bad idea. 7. Projection support : I was also thinking of adding projection support to the manager. In which sense, do you mean on-the fly re-projection (ST_transform)? Martin [1] http://grass.osgeo.org/wiki/Working_with_external_data_in_GRASS_7#Using_wxGUI [2] http://grass.osgeo.org/wiki/Working_with_external_data_in_GRASS_7#Digitize_OGR_layer_using_wxGUI [3] http://grass.osgeo.org/wiki/Working_with_external_data_in_GRASS_7#Direct_access_to_external_data [4] http://grass.osgeo.org/wiki/PostGIS#Import_into_GRASS [5] http://grass.osgeo.org/wiki/PostGIS#Export_to_PostGIS Thanks for your feedback. I know that various modules are possible in GRASS wxGUI. I want to integrate them all and provide a direct interface for them. Regarding data Export I was thinking about 'v.out.ogr' only. And I was talking about on-the fly re-projection. The projection tables can be stored in which ever way the user wants. What more would you like to add to the current idea to make it worth for a GSOC proposal? Looking forward to your support. Regards, Mohit Kumar (mohitkharb on irc) Lab For Spatial Informatics International Institute of Information and Technology Hyderabad, India +91-970-3840-175 ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev Mohit Kumar (mohitkharb on irc) Lab For Spatial Informatics International Institute of Information and Technology Hyderabad, India +91-970-3840-175
Re: [GRASS-dev] PostGIS manager for GRASS GIS
Hello Martin, Sorry couldn't reply earlier as I was stuck with some college work. On Mon, 2 Apr 2012 21:00:51 +0200, Martin Landa wrote: Hi, 2012/4/2 Mohit Kumar mohit.kumaru...@students.iiit.ac.in: I am interested in making a PostGIS manager in GRASS as a GSoc 2012 task. PyGreSQL is a python module that allows easy use of database operation API from a pyhton script. So it will be like a wrapper over the database. This can be done using wxPython and will be OS independent. Sorry to bug you all, but I am very much interested in developing for GRASS. [...] there is new development ongoing for this in GRASS 7, perhaps a good moment to integrate a manager. Maybe Martin has some insights for us over the next days. Its good to know that development is ongoing for this in GRASS, I sincerely want to work on this as my GSoc task. the current PostGIS-related development in G7 is not much related to this idea. The vector engine in G7 is currently able to read PostGIS geometry data natively without any abstract level (like OGR-PostgreSQL driver). Also write support has been recently implemented. The current implementation is focused on simple feature access, GRASS builds a pseudo-like topology as for OGR links (see v.external). At this moment I am working on PostGIS topology support in GRASS. I have made a brief idea for the manager. The following are the various modules of the manager 1. Setup connection : This module will set up the connection with the remote database. It will take the input parameters from user and pass them to a connection string. After the connection has been established, the user will be shown the various tables(maps) that are stored and other information about the database and the connection This is already available in wxGUI [1]. Of course there is always a space for any kind of improvements. But basically it's already there, to add widgets for entering username and password is quite easy task. 2. View and edit data : This will display the data of the table in a window frame. One can view the map and modify the table values or the attributes. Also possible in current wxGUI [2]. You just create a link using `v.external` and display the map in the map canvas as normal GRASS vector map. Also direct OGR access [3] is possible (no links, pseudo-topology built on the fly) 3. Import to GRASS Data : This gives the user an option to save the data in Grass format for further processing/analysis of the data. This also gives user an option to discard the data which is of no use. Possible with `v.in.ogr`. Simple wrapper based `v.in.ogr` for importing PostGIS is already there [4]. 4. Execute PostGis functions (geometry processing)on database and save output in grass data format. This could be improvement. 5. SQL interface : This provides the advanced user to modify the database by use of direct SQL commands on the database. 6. Export GRASS data to PostGIS data : Convert the Grass Data to SQL database. First convert the Grass data to Esri Shapefile(.shp) using OGR and then converting that data to SQL database (shape2sql). Why?? You can export data directly using `v.out.ogr` [5]. No need for Shapefiles, that's bad idea. 7. Projection support : I was also thinking of adding projection support to the manager. In which sense, do you mean on-the fly re-projection (ST_transform)? Martin [1] http://grass.osgeo.org/wiki/Working_with_external_data_in_GRASS_7#Using_wxGUI [2] http://grass.osgeo.org/wiki/Working_with_external_data_in_GRASS_7#Digitize_OGR_layer_using_wxGUI [3] http://grass.osgeo.org/wiki/Working_with_external_data_in_GRASS_7#Direct_access_to_external_data [4] http://grass.osgeo.org/wiki/PostGIS#Import_into_GRASS [5] http://grass.osgeo.org/wiki/PostGIS#Export_to_PostGIS Thanks for your feedback. I know that various modules are possible in GRASS wxGUI. I want to integrate them all and provide a direct interface for them. Regarding data Export I was thinking about 'v.out.ogr' only. And I was talking about on-the fly re-projection. The projection tables can be stored in which ever way the user wants. What more would you like to add to the current idea to make it worth for a GSOC proposal? Looking forward to your support. Regards, Mohit Kumar (mohitkharb on irc) Lab For Spatial Informatics International Institute of Information and Technology Hyderabad, India +91-970-3840-175 ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] PostGIS manager for GRASS GIS
Hello sir, On Sat, 31 Mar 2012 23:11:04 +0200, Markus Neteler wrote: Hello Mohit Kumar, On Tue, Mar 27, 2012 at 2:25 PM, Mohit Kumar mohit.kumaru...@students.iiit.ac.in wrote: Hello all, I am interested in making a PostGIS manager in GRASS as a GSoc 2012 task. PyGreSQL is a python module that allows easy use of database operation API from a pyhton script. So it will be like a wrapper over the database. This can be done using wxPython and will be OS independent. Sorry to bug you all, but I am very much interested in developing for GRASS. Is anybody willing to mentor ? there is new development ongoing for this in GRASS 7, perhaps a good moment to integrate a manager. Maybe Martin has some insights for us over the next days. Markus Thanks for your reply. Its good to know that development is ongoing for this in GRASS, I sincerely want to work on this as my GSoc task. I have made a brief idea for the manager. The following are the various modules of the manager 1. Setup connection : This module will set up the connection with the remote database. It will take the input parameters from user and pass them to a connection string. After the connection has been established, the user will be shown the various tables(maps) that are stored and other information about the database and the connection 2. View and edit data : This will display the data of the table in a window frame. One can view the map and modify the table values or the attributes. 3. Import to GRASS Data : This gives the user an option to save the data in Grass format for further processing/analysis of the data. This also gives user an option to discard the data which is of no use. 4. Execute PostGis functions (geometry processing)on database and save output in grass data format. 5. SQL interface : This provides the advanced user to modify the database by use of direct SQL commands on the database. 6. Export GRASS data to PostGIS data : Convert the Grass Data to SQL database. First convert the Grass data to Esri Shapefile(.shp) using OGR and then converting that data to SQL database (shape2sql). 7. Projection support : I was also thinking of adding projection support to the manager. These are the various major points for a spatial database manager I can think of. Can you please provide me your suggestions. Looking forward to your support as the time left to apply is very less. Regards, -- Mohit Kumar(mohitkharb on irc) Lab For Spatial Informatics International Institute of Information and Technology Hyderabad, India +91-970-3840-175 ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] PostGIS manager for GRASS GIS
Hello all, I am interested in making a PostGIS manager in GRASS as a GSoc 2012 task. PyGreSQL is a python module that allows easy use of database operation API from a pyhton script. So it will be like a wrapper over the database. This can be done using wxPython and will be OS independent. Sorry to bug you all, but I am very much interested in developing for GRASS. Is anybody willing to mentor ? Looking forward to your support. Thanks and Regards, Mohit Kumar Lab For Spatial Informatics International Institute of Information and Technology Hyderabad, India +9.1-9.7.0.3.8.4.0.1.7.5. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Applying in GSOC 2012
Sir, I have just given some suggestions from the view of a user of GRASS on how to improve it GUI further. My response is below: On Sun, 25 Mar 2012 20:32:19 -0600, Michael Barton wrote: Mohit, Can you explain what you mean a little more clearly. I just gave the suggestions that came in my mind. What is window flooding? If you mean that there are a lot of windows, this is a consequence of each GRASS module launching its own independent GUI dialog. This is done because a significant number of people like to launch modules from the command line rather than from the integrated GUI. It might be nice to have an option that windows would close automatically when a module is run unless a 'run and stay open' box was checked, or something like that. This would have the biggest impact on reducing window clutter. By window flooding I meant exactly the same, for every module there is a separate GUI dialog which becomes very untidy and then every dialog has to be closed manually. What I thought about it is we can make a single gui which has a fixed widget to display the image, and every image will be in a different tab. Even if one launches a module from command line it will open as a tab in the integrated GUI. We will also give an option to the user if he wants to open the module in new window. This was the idea of an integrated GUI. What do you mean by an integrated GUI? GRASS has an integrated GUI. How would you change this? Redoing the GUI in something other than wxPython would take a LOT of time, and would probably present a problem in being maintainable by the development team. Swipe features could be very nice. How would you create these in wxPython so that they would operate across all OS platforms? Emulating ArcGIS is not necessarily an improvement to the user experience. A PostGIS manager could be quite nice. Again, how would you implement this in wxPython across all OS platforms? Swipe feature will be a new dialog that will have to widgets lying one on another having an image each. The width of the upper widget will be resizable from zero to length of bottom widget, the bar adjusting the width will act as a slider. This feature will be very useful in comparing any two layers(pictures at different timestamp). To implement this in wxPyhton is not very tough according to me. You can see it implemented here http://www.nytimes.com/interactive/2011/03/13/world/asia/satellite-photos-japan-before-and-after-tsunami.html. PostGIS manager was yet another idea, like a PostGIS manager in Quantum GIS. PyGreSQL is a python module that allows easy use of database operation API from a pyhton script. So it will be like a wrapper over the database. This can be done using wxPython and will be OS independent. This all sounds like several SOC projects instead of one. It would probably be better if you picked one and sketched it out in more detail. All these were the basic ideas, for deciding the one to propose for SOC, I will need a mentor and feedback to guide me and make a proposal from the ideas. Michael _ C. Michael Barton Visiting Scientist, Integrated Science Program National Center for Atmospheric Research University Consortium for Atmospheric Research 303-497-2889 (voice) Director, Center for Social Dynamics Complexity Professor of Anthropology, School of Human Evolution Social Change Arizona State University www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu Regards, Mohit Kumar Lab For Spatial Informatics International Institute of Information and Technology Hyderabad, India +9.1-9.7.0.3.8.4.0.1.7.5. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Applying in GSOC 2012
On Sat, 24 Mar 2012 02:23:38 +0530, Mohit Kumar wrote: Hello , I am a M.S. research student from Lab for Spatial Informatics, International Institute of Information and Technology, Hyderabad, India. I have been developing in C++/Python from past two years, I also know jsp, java, qt,applets, mapServer, google maps API. I am very much interested in GUI development and want to get involved in GRASS, I have used ILWIS and ArcGIS. As a user of GRASS I have found window flooding in wxGUI. I would like to work on wxGUI idea on the ideas page. Apart from adding an integrated GUI I will add swipe feature. I will also like to add PostGIS manager like in QGis. I also developed web based Optical remote sensing virtual lab for DRDO, India . Is there anybody willing to mentor me? Regards, Mohit Kumar Undergraduate Computer Science Lab for Spatial Informatics International Institute of Information and Technology Hyderabad, India +9.1-9.7.0.3.8.4.0.1.7.5. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev Hello, I would really appreciate some quick response since I have been trying to get in touch but haven't been successful. I am really interested in being a part of GRASS development and look forward to your support. Regards, Mohit Kumar Lab For Spatial Informatics International Institute of Information and Technology Hyderabad, India +9.1-9.7.0.3.8.4.0.1.7.5. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Applying in GSOC 2012
Hello , I am a M.S. research student from Lab for Spatial Informatics, International Institute of Information and Technology, Hyderabad, India. I have been developing in C++/Python from past two years, I also know jsp, java, qt,applets, mapServer, google maps API. I am very much interested in GUI development and want to get involved in GRASS, I have used ELVIS and ArcGIS. As a user of GRASS I have found window flooding in wxGUI. I would like to work on wxGUI idea on the ideas page. Apart from adding an integrated GUI I will add swipe feature. I will also like to add PostGIS manager like in QGis. I also developed web based Optical remote sensing virtual lab for DRDO, India and . Is there anybody willing to mentor me? Regards, Mohit Kumar Undergraduate Computer Science Lab for Spatial Informatics International Institute of Information and Technology Hyderabad, India +9.1-9.7.0.3.8.4.0.1.7.5. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
