Final Report

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Final Report

Mayank Agrawal
This is my last report of the GSoC project. I would like to thank Rashad and Massimo, my mentors.

Brief Description
My project focussed on the development of web based GUI for the Grass “WebGrass” where people can use Grass modules on their data through a web browser without actually installing GRASS. GRASS is running on a server. The user interface is built using wt web toolkit. 

The state of the project before my GSoC
Was not implemented but a proof of concept was there.

The addition that your project brought to the software
A working webapp. People can use data from their system and apply different modules and get output. A Web based UI like GRASS and modules implementation. Whole "WebGrass" is a very big project for one gsoc and we try to implement as much as possible.

Things implemented-
  • Location and Mapset wizard
  • UI of the modules
  • Modules implementation like desktop grass (command line output also)
  • Authorization of the user
  • Input/output/processing of raster data
  • display of raster data
  • Input/output/processing of vector data
From this project, a official start of "WebGrass" is done and I hope it will be useful for the people.
This has been a very interesting and learning experience. I learned a lot from my mentors. I hope this project keeps on growing and will continue to contribute to this project. 

Links-


Images-


Mayank Agrawal
Lab for Spatial Informatics
IIIT Hyderabad 
India

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev
Reply | Threaded
Open this post in threaded view
|

Re: Final Report

wenzeslaus
Hi Mayank,

thanks for the final report. It looks very promising. Can you please gather your reports and put them on the wiki page as it was done in the previous years? (Last one is from week 2.) Mailing list is a good archive but it is hard to go through all of them.

Also, I was not able to find the current instructions how to run it. Did I missed them?

Thanks,
Vaclav


On Mon, Aug 15, 2016 at 8:10 PM, Mayank Agrawal <[hidden email]> wrote:
This is my last report of the GSoC project. I would like to thank Rashad and Massimo, my mentors.

Brief Description
My project focussed on the development of web based GUI for the Grass “WebGrass” where people can use Grass modules on their data through a web browser without actually installing GRASS. GRASS is running on a server. The user interface is built using wt web toolkit. 

The state of the project before my GSoC
Was not implemented but a proof of concept was there.

The addition that your project brought to the software
A working webapp. People can use data from their system and apply different modules and get output. A Web based UI like GRASS and modules implementation. Whole "WebGrass" is a very big project for one gsoc and we try to implement as much as possible.

Things implemented-
  • Location and Mapset wizard
  • UI of the modules
  • Modules implementation like desktop grass (command line output also)
  • Authorization of the user
  • Input/output/processing of raster data
  • display of raster data
  • Input/output/processing of vector data
From this project, a official start of "WebGrass" is done and I hope it will be useful for the people.
This has been a very interesting and learning experience. I learned a lot from my mentors. I hope this project keeps on growing and will continue to contribute to this project. 

Links-


Images-


Mayank Agrawal
Lab for Spatial Informatics
IIIT Hyderabad 
India

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev


_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev
Reply | Threaded
Open this post in threaded view
|

Re: Final Report

Mayank Agrawal




On Tue, Aug 16, 2016 7:39 AM, Vaclav Petras [hidden email] wrote:
Hi Mayank,

thanks for the final report. It looks very promising. Can you please gather your reports and put them on the wiki page as it was done in the previous years? (Last one is from week 2.) Mailing list is a good archive but it is hard to go through all of them.

Also, I was not able to find the current instructions how to run it. Did I missed them?

Thanks,
Vaclav


On Mon, Aug 15, 2016 at 8:10 PM, Mayank Agrawal <[hidden email]> wrote:
This is my last report of the GSoC project. I would like to thank Rashad and Massimo, my mentors.

Brief Description
My project focussed on the development of web based GUI for the Grass “WebGrass” where people can use Grass modules on their data through a web browser without actually installing GRASS. GRASS is running on a server. The user interface is built using wt web toolkit. 

The state of the project before my GSoC
Was not implemented but a proof of concept was there.

The addition that your project brought to the software
A working webapp. People can use data from their system and apply different modules and get output. A Web based UI like GRASS and modules implementation. Whole "WebGrass" is a very big project for one gsoc and we try to implement as much as possible.

Things implemented-
  • Location and Mapset wizard
  • UI of the modules
  • Modules implementation like desktop grass (command line output also)
  • Authorization of the user
  • Input/output/processing of raster data
  • display of raster data
  • Input/output/processing of vector data
From this project, a official start of "WebGrass" is done and I hope it will be useful for the people.
This has been a very interesting and learning experience. I learned a lot from my mentors. I hope this project keeps on growing and will continue to contribute to this project. 

Links-


Images-


Mayank Agrawal
Lab for Spatial Informatics
IIIT Hyderabad 
India

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev


_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev
Reply | Threaded
Open this post in threaded view
|

Re: Final Report

wenzeslaus
Thanks!

On Tue, Aug 16, 2016 at 3:28 AM, Mayank Agrawal <[hidden email]> wrote:


I suggest merging README and README.md.

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev
Reply | Threaded
Open this post in threaded view
|

Re: Final Report

ychemin
In reply to this post by Mayank Agrawal
Hi,
I got a clean compile on Ubuntu 16.10 following readme instruction.

-------------
yann@yann-ok:~/dev/webgrass$ mkdir build
yann@yann-ok:~/dev/webgrass$ cd build
yann@yann-ok:~/dev/webgrass/build$ cmake ..
-- The C compiler identification is GNU 6.1.1
-- The CXX compiler identification is GNU 6.1.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found the Wt libraries at /usr/lib/libwthttp.so;/usr/lib/libwt.so
-- Found the Wt headers at /usr/include
-- Found the Wt debug libraries at /usr/lib/libwthttp.so;/usr/lib/libwt.so
-- Found the Wt debug headers at /usr/include
-- GRASS_DATA_DIR=/home/yann/grassdata
-- Configuring done
-- Generating done
-- Build files have been written to: /home/yann/dev/webgrass/build
yann@yann-ok:~/dev/webgrass/build$ cd ..
yann@yann-ok:~/dev/webgrass$ cd build
yann@yann-ok:~/dev/webgrass/build$ make
Scanning dependencies of target wgrass.wt
[  8%] Building CXX object CMakeFiles/wgrass.wt.dir/src/MainUI.cpp.o
[ 16%] Building CXX object CMakeFiles/wgrass.wt.dir/src/WGApplication.cpp.o
[ 25%] Building CXX object CMakeFiles/wgrass.wt.dir/src/main.cpp.o
[ 33%] Building CXX object CMakeFiles/wgrass.wt.dir/src/LayerManager.cpp.o
[ 41%] Building CXX object CMakeFiles/wgrass.wt.dir/src/Display.cpp.o
[ 50%] Building CXX object CMakeFiles/wgrass.wt.dir/src/Toolbar.cpp.o
[ 58%] Building CXX object CMakeFiles/wgrass.wt.dir/src/Startup.cpp.o
[ 66%] Building CXX object CMakeFiles/wgrass.wt.dir/src/Module.cpp.o
[ 75%] Building CXX object CMakeFiles/wgrass.wt.dir/src/Parameter_text.cpp.o
[ 83%] Building CXX object CMakeFiles/wgrass.wt.dir/src/Parameter.cpp.o
[ 91%] Building CXX object CMakeFiles/wgrass.wt.dir/src/Authentication.cpp.o
[100%] Linking CXX executable wgrass.wt
[100%] Built target wgrass.wt
yann@yann-ok:~/dev/webgrass/build$

-------------

On 16/08/2016 02:10, Mayank Agrawal wrote:

> This is my last report of the GSoC project. I would like to thank Rashad and
> Massimo, my mentors.
> Brief Description My project focussed on the development of web based GUI for the Grass
> “WebGrass” where people can use Grass modules on their data through a web
> browser without actually installing GRASS. GRASS is running on a server. The
> user interface is built using wt web toolkit.
> The state of the project before my GSoC Was not implemented but a proof of concept was there.
> The addition that your project brought to the software A working webapp. People can use data from their system and apply different
> modules and get output. A Web based UI like GRASS and modules implementation.
> Whole "WebGrass" is a very big project for one gsoc and we try to implement as
> much as possible.
> Things implemented- * Location and Mapset wizard
>   * UI of the modules
>   * Modules implementation like desktop grass (command line output also)
>   * Authorization of the user
>   * Input/output/processing of raster data
>   * display of raster data
>   * Input/output/processing of vector data
>
>  From this project, a official start of "WebGrass" is done and I hope it will be
> useful for the people. This has been a very interesting and learning experience. I learned a lot from
> my mentors. I hope this project keeps on growing and will continue to contribute to this project.
> Links - Github - https://github.com/mayank33/webgrass/commits/gsoc2016 https://github.com/mayank33/webgrass/commits/auth
> Project Page - https://trac.osgeo.org/grass/wiki/GSoC/2016/WebGrass
> Images- first page
> second page
> Module UI
>
>
> Mayank Agrawal Lab for Spatial Informatics IIIT Hyderabad India
>
>
> _______________________________________________
> grass-dev mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/grass-dev

--
-----
Yann Chemin
Address: 3 Toul Melin, 56400 Plumergat
Mobile: +33 (0)7 83 85 52 34

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev
Reply | Threaded
Open this post in threaded view
|

Re: Final Report

ychemin
In reply to this post by Mayank Agrawal
Maybe not the right place to say, but the GRASS GIS data directory is
not editable, so cannot change to another GRASSDATA directory name.

On 16/08/2016 02:10, Mayank Agrawal wrote:

> This is my last report of the GSoC project. I would like to thank Rashad and
> Massimo, my mentors.
> Brief Description My project focussed on the development of web based GUI for the Grass
> “WebGrass” where people can use Grass modules on their data through a web
> browser without actually installing GRASS. GRASS is running on a server. The
> user interface is built using wt web toolkit.
> The state of the project before my GSoC Was not implemented but a proof of concept was there.
> The addition that your project brought to the software A working webapp. People can use data from their system and apply different
> modules and get output. A Web based UI like GRASS and modules implementation.
> Whole "WebGrass" is a very big project for one gsoc and we try to implement as
> much as possible.
> Things implemented- * Location and Mapset wizard
>   * UI of the modules
>   * Modules implementation like desktop grass (command line output also)
>   * Authorization of the user
>   * Input/output/processing of raster data
>   * display of raster data
>   * Input/output/processing of vector data
>
>  From this project, a official start of "WebGrass" is done and I hope it will be
> useful for the people. This has been a very interesting and learning experience. I learned a lot from
> my mentors. I hope this project keeps on growing and will continue to contribute to this project.
> Links - Github - https://github.com/mayank33/webgrass/commits/gsoc2016 https://github.com/mayank33/webgrass/commits/auth
> Project Page - https://trac.osgeo.org/grass/wiki/GSoC/2016/WebGrass
> Images- first page
> second page
> Module UI
>
>
> Mayank Agrawal Lab for Spatial Informatics IIIT Hyderabad India
>
>
> _______________________________________________
> grass-dev mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/grass-dev

--
-----
Yann Chemin
Address: 3 Toul Melin, 56400 Plumergat
Mobile: +33 (0)7 83 85 52 34

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev
SBL
Reply | Threaded
Open this post in threaded view
|

Re: Final Report

SBL
Hi Mayank,

Thanks for WebGRASS! I am glad we can test it and thanks also for fixing the compilation issue so fast!

For me it would be absolutely OK that www-users cannot browse the whole server for GRASS DBs. And that all WebGRASS users are forced to work in one DB might be almost a pluss - from the administrators perspective ;-).

What I really like about WebGRASS is the simplicity of installing it. No long configuration and settings to be changed many places. Fast compile and It runs!

A clear drawback however is the Google based authentication, which seems to be the only available authentication method at the moment. Esp. for internal server deployment that does not feel right. Se also: https://github.com/rashadkm/webgrass/issues/19

Another question is: does WebGRASS currently only allow for a single connection at a time?
I opened one login page in one browser, and then tried to access WebGRASS in parallel from another browser, but I got a Connection Refused error...
Is that intentional or a known limitation of the chosen approach? The main aim of the web-UI is to give several users easy-access to GRASS on a server, isn`t it?

Or is the concept that each user should start his/her WebGRASS session (WebGRASS does not require root permissions to start the server process)? Would not that lead to possible issues with port conflicts?

Cheers
Stefan


-----Original Message-----
From: grass-dev [mailto:[hidden email]] On Behalf Of Yann
Sent: 16. august 2016 18:46
To: [hidden email]
Subject: Re: [GRASS-dev] Final Report

Maybe not the right place to say, but the GRASS GIS data directory is not editable, so cannot change to another GRASSDATA directory name.

On 16/08/2016 02:10, Mayank Agrawal wrote:

> This is my last report of the GSoC project. I would like to thank
> Rashad and Massimo, my mentors.
> Brief Description My project focussed on the development of web based
> GUI for the Grass “WebGrass” where people can use Grass modules on
> their data through a web browser without actually installing GRASS.
> GRASS is running on a server. The user interface is built using wt web toolkit.
> The state of the project before my GSoC Was not implemented but a proof of concept was there.
> The addition that your project brought to the software A working
> webapp. People can use data from their system and apply different modules and get output. A Web based UI like GRASS and modules implementation.
> Whole "WebGrass" is a very big project for one gsoc and we try to
> implement as much as possible.
> Things implemented- * Location and Mapset wizard
>   * UI of the modules
>   * Modules implementation like desktop grass (command line output also)
>   * Authorization of the user
>   * Input/output/processing of raster data
>   * display of raster data
>   * Input/output/processing of vector data
>
>  From this project, a official start of "WebGrass" is done and I hope
> it will be useful for the people. This has been a very interesting and
> learning experience. I learned a lot from my mentors. I hope this project keeps on growing and will continue to contribute to this project.
> Links - Github - https://github.com/mayank33/webgrass/commits/gsoc2016 
> https://github.com/mayank33/webgrass/commits/auth
> Project Page - https://trac.osgeo.org/grass/wiki/GSoC/2016/WebGrass
> Images- first page
> second page
> Module UI
>
>
> Mayank Agrawal Lab for Spatial Informatics IIIT Hyderabad India
>
>
> _______________________________________________
> grass-dev mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/grass-dev

--
-----
Yann Chemin
Address: 3 Toul Melin, 56400 Plumergat
Mobile: +33 (0)7 83 85 52 34

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev
_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev
Reply | Threaded
Open this post in threaded view
|

Re: Final Report

Mayank Agrawal
In reply to this post by ychemin
This is what was decided but can be implemented(editable option) in future

 -DGRASS_DATA_DIR can be used in the cmake for defining the directory 



On Tue, Aug 16, 2016 10:15 PM, Yann [hidden email] wrote:

Maybe not the right place to say, but the GRASS GIS data directory is

not editable, so cannot change to another GRASSDATA directory name.


On 16/08/2016 02:10, Mayank Agrawal wrote:

> This is my last report of the GSoC project. I would like to thank Rashad and

> Massimo, my mentors.

> Brief Description My project focussed on the development of web based GUI for the Grass

> “WebGrass” where people can use Grass modules on their data through a web

> browser without actually installing GRASS. GRASS is running on a server. The

> user interface is built using wt web toolkit.

> The state of the project before my GSoC Was not implemented but a proof of concept was there.

> The addition that your project brought to the software A working webapp. People can use data from their system and apply different

> modules and get output. A Web based UI like GRASS and modules implementation.

> Whole "WebGrass" is a very big project for one gsoc and we try to implement as

> much as possible.

> Things implemented- * Location and Mapset wizard

> * UI of the modules

> * Modules implementation like desktop grass (command line output also)

> * Authorization of the user

> * Input/output/processing of raster data

> * display of raster data

> * Input/output/processing of vector data

>

> From this project, a official start of "WebGrass" is done and I hope it will be

> useful for the people. This has been a very interesting and learning experience. I learned a lot from

> my mentors. I hope this project keeps on growing and will continue to contribute to this project.

> Links - Github - https://github.com/mayank33/webgrass/commits/gsoc2016 https://github.com/mayank33/webgrass/commits/auth

> Project Page - https://trac.osgeo.org/grass/wiki/GSoC/2016/WebGrass

> Images- first page

> second page

> Module UI

>

>

> Mayank Agrawal Lab for Spatial Informatics IIIT Hyderabad India

>

>

> _______________________________________________

> grass-dev mailing list

> [hidden email]

> http://lists.osgeo.org/mailman/listinfo/grass-dev


--

-----

Yann Chemin

Address: 3 Toul Melin, 56400 Plumergat

Mobile: +33 (0)7 83 85 52 34


_______________________________________________

grass-dev mailing list

[hidden email]

http://lists.osgeo.org/mailman/listinfo/grass-dev


_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev