OSGeo - User contributions [en]

GSoC 2020 Data transaction implementation on pygeoapi

2020-08-31T12:12:01Z

Wiki-Alex-mathew: /* Summary */

== Introduction ==
=== Idea ===
[https://pygeoapi.io/ pygeoapi] is a python server implementation of the OGC API suite of standards. The project emerged as part of the next generation OGC API efforts in 2018 and provides the capability for organizations to deploy a RESTful OGC API endpoint using OpenAPI, GeoJSON, and HTML. pygeoapi is open source and released under an MIT license.

This GSoC project aims to add support for simple transactions in pygeoapi. This project will implement Create, Update, Delete operations in pygeoapi data providers, thereby enabling all standard CRUD transactions in pygeoapi. This will enable an application developer to perform a transaction in a pygeoapi data provider through an HTTP request containing the resource id and suitable HTTP verb (POST/PUT/DELETE/PATCH). The project proposal is based on [http://docs.opengeospatial.org/DRAFTS/20-002.html OGC API - Features - Part 4: Simple Transactions].

===Project proposal===
My proposal for GSoC 2020 can be found at [https://docs.google.com/document/d/1NaUvOVT8hJVa-jCQHatnnvblD8GQmRKWbxs8_Jrm0dw/edit?usp=sharing Proposal].

=== Advantages from this project ===
pygeoapi implements OGC WFS 3.0 (OGC Feature API) which is fully RESTful. This makes it much easier for the application developers to work with. This project idea implements 'Part 4 : Simple Transactions' of this OGC standard. It adds transactional capabilities to the pygeoapi data providers by which application developers can perform transactions via the RESTful API itself. A RESTful API supporting complete CRUD transactions will be preferred by most application developers over other non-RESTful APIs. So this will make pygeoapi a more popular choice among application developers.

'''Link to Github repository:''' [https://github.com/alex-mathew/pygeoapi Repo]

== Timeline ==

=== Community bonding period ===
=== 4th May - 31st May ===
'''What I have done during this period?'''
* Joined pygeoapi Gitter room
* Went through the current features of pygeoapi
* Went through OGC API - Features - Part 4: Simple Transactions [http://docs.opengeospatial.org/DRAFTS/20-002.html] draft
* Forked the pygeoapi GitHub repository [https://github.com/alex-mathew/pygeoapi Repository]
* Introduced myself over the channel and shared my proposal over mailing list for suggestions
* Created a wiki page for the project "Data transaction implementation on pygeoapi"
* Updated wiki user page and added my personal information [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]
* Updated links on the wiki Google_Summer_of_Code_2020_Accepted page [[https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2020_Accepted Link]]
* Had a discussion with mentors regarding the expectations and development workflow
* Discussed the openapi specification document with the mentors
* Started working on the openapi document

=== Coding Phase 1 ===
=== Week 1(1st June - 7th June) ===
'''What I have done during this period?'''
* Defined openapi document schemas for remove(DELETE), insert(POST), modify(PATCH), replace(PUT) transactions
* Pushed the proposed openapi document sample to the openapidoc branch in my [https://github.com/alex-mathew/pygeoapi forked repo]
* Shared the doc with pygeoapi community for suggestions

'''What do I plan on doing next week?'''
* Modify openapi.py file so that it generates the proposed openapi document
* Test the code for compliance

'''Blocking issues'''

None

=== Week 2(8th June - 14th June) ===
'''What I have done during this period?'''
* Corrected schemas for insert(POST) & replace(PUT) transactions as per suggestions from mentors
* Modified the code to generate the proposed openapi doc
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Test the code for compliance

'''Blocking issues'''

None

=== Week 3(15th June - 21st June) ===
'''What I have done during this period?'''
* Started writing test cases for get_oas30() function
* Started testing and made corrections to the code
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Complete writing test cases and compliance test
* Start documentation

'''Blocking issues'''

None

=== Week 4(22nd June - 28th June) ===
'''What I have done during this period?'''
* Refactored code and passed flake8 linting
* Integrated travis CI and read the docs to my branch
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Add more test cases and pass travis build
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Coding Phase 2 ===
=== Week 5(29th June - 5th July) ===
'''What I have done during this period?'''
* Refactored code to pass the community standards
* Added details about transaction functionality to the configuration section in the documentation
* Raised [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Started researching on generic implementations for routing

'''What do I plan on doing next week?'''
* Fix a generic implementation for routing
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Week 6(6th July - 12th July) ===
'''What I have done during this period?'''
* Performed suggested changes on the [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Designed a basic solution for generic flask endpoint to add support for transactions
* Successfully implemented a flask endpoint for POST and tested it with the available geojson provider implementation

'''What do I plan on doing next week?'''
* Find a better solution for the generic endpoint
* Implement rest of the flask endpoints
* Refactor code by adding exceptions and write unit tests

'''Blocking issues'''

None

=== Week 7(13th July - 19th July) ===
'''What I have done during this period?'''
* Implemented flask and starlette routings for transaction requests
* Implemented transaction support for the geojson data provider

'''What do I plan on doing next week?'''
* Add transaction unit tests for flask_app.py and starlette_app.py
* Add transaction unit tests for the geojson data provider
* Start implementing transactional support in other data providers

'''Blocking issues'''

None

=== Week 8(20th July - 26th July) ===
'''What I have done during this period?'''
* Implemented transaction support for csv data provider
* Refactored geojson data provider code
* Added new unit tests for geojson and csv data providers

'''What do I plan on doing next week?'''
* Write unit tests for transactional support in remaining data providers
* Start implementing transactional support in remaining data providers

'''Blocking issues'''

None

=== Week 9(27th July - 2nd August) ===
'''What I have done during this period?'''
* Modified schemaless providers to fully support PATCH verb
* Completed unit tests for geojson and csv providers
* Completed functional tests for flask and starlette endpoints

'''What do I plan on doing next week?'''
* Write unit tests for transactional support in remaining data providers
* Start implementing transactional support in remaining data providers

'''Blocking issues'''

None

=== Week 10(3rd August - 9th August) ===
'''What I have done during this period?'''
* Improved openapi with examples
* Improved descriptions for CRUD operations
* Created unit tests for postgresql and sqlite providers

'''What do I plan on doing next week?'''
* Implement transactional support for postgresql and sqlite providers

'''Blocking issues'''

None

=== Week 11(10th August - 16th August) ===
'''What I have done during this period?'''
* Added documentation for data transactions
* Updated id selection rule for POST transaction based on data type of id
* Updated request examples in openapidoc
* Started working on transactional support for postgresql and sqlite providers

'''What do I plan on doing next week?'''
* Complete transactional support for postgresql and sqlite providers

'''Blocking issues'''

None

=== Week 12(17th August - 23rd August) ===
'''What I have done during this period?'''
* Updated documentation for data transactions
* Updated csv provider to handle type of attributes
* Updated id selection rule in POST to generate type specific ids
* Updated request examples in openapidoc
* Started writing unit tests for postgresql and sqlite providers

'''What do I plan on doing next week?'''
* Complete transactional support for postgresql and sqlite providers

'''Blocking issues'''

None

== Student's Biography ==
My name is Alex Mathew. I am a computer science graduate now pursuing my masters in geoinformatics under the Centre of Studies in Resources Engineering, Indian Institute of Technology Bombay, Mumbai, India.
Some more information about me can be obtained by following the link: [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]

== Mentors ==
*Jorge de Jesus
*Francesco Bartoli

[[Category: Google Summer of Code]]

GSoC 2020 Data transaction implementation on pygeoapi

2020-08-26T21:07:47Z

Wiki-Alex-mathew: /* Introduction */

== Introduction ==
=== Summary ===
◦ Created OpenAPI Specification document from the OGC Features API - Simple Transactions proposal

◦ Implemented transaction operations in pygeoapi, exposed them as REST endpoints using Flask and Starlette

◦ Currently member of pygeoapi community and will be presenting the work in OGC API Features Sprint 2020

=== Idea ===
[https://pygeoapi.io/ pygeoapi] is a python server implementation of the OGC API suite of standards. The project emerged as part of the next generation OGC API efforts in 2018 and provides the capability for organizations to deploy a RESTful OGC API endpoint using OpenAPI, GeoJSON, and HTML. pygeoapi is open source and released under an MIT license.

This GSoC project aims to add support for simple transactions in pygeoapi. This project will implement Create, Update, Delete operations in pygeoapi data providers, thereby enabling all standard CRUD transactions in pygeoapi. This will enable an application developer to perform a transaction in a pygeoapi data provider through an HTTP request containing the resource id and suitable HTTP verb (POST/PUT/DELETE/PATCH). The project proposal is based on [http://docs.opengeospatial.org/DRAFTS/20-002.html OGC API - Features - Part 4: Simple Transactions].

===Project proposal===
My proposal for GSoC 2020 can be found at [https://docs.google.com/document/d/1NaUvOVT8hJVa-jCQHatnnvblD8GQmRKWbxs8_Jrm0dw/edit?usp=sharing Proposal].

=== Advantages from this project ===
pygeoapi implements OGC WFS 3.0 (OGC Feature API) which is fully RESTful. This makes it much easier for the application developers to work with. This project idea implements 'Part 4 : Simple Transactions' of this OGC standard. It adds transactional capabilities to the pygeoapi data providers by which application developers can perform transactions via the RESTful API itself. A RESTful API supporting complete CRUD transactions will be preferred by most application developers over other non-RESTful APIs. So this will make pygeoapi a more popular choice among application developers.

'''Link to Github repository:''' [https://github.com/alex-mathew/pygeoapi Repo]

== Timeline ==

=== Community bonding period ===
=== 4th May - 31st May ===
'''What I have done during this period?'''
* Joined pygeoapi Gitter room
* Went through the current features of pygeoapi
* Went through OGC API - Features - Part 4: Simple Transactions [http://docs.opengeospatial.org/DRAFTS/20-002.html] draft
* Forked the pygeoapi GitHub repository [https://github.com/alex-mathew/pygeoapi Repository]
* Introduced myself over the channel and shared my proposal over mailing list for suggestions
* Created a wiki page for the project "Data transaction implementation on pygeoapi"
* Updated wiki user page and added my personal information [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]
* Updated links on the wiki Google_Summer_of_Code_2020_Accepted page [[https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2020_Accepted Link]]
* Had a discussion with mentors regarding the expectations and development workflow
* Discussed the openapi specification document with the mentors
* Started working on the openapi document

=== Coding Phase 1 ===
=== Week 1(1st June - 7th June) ===
'''What I have done during this period?'''
* Defined openapi document schemas for remove(DELETE), insert(POST), modify(PATCH), replace(PUT) transactions
* Pushed the proposed openapi document sample to the openapidoc branch in my [https://github.com/alex-mathew/pygeoapi forked repo]
* Shared the doc with pygeoapi community for suggestions

'''What do I plan on doing next week?'''
* Modify openapi.py file so that it generates the proposed openapi document
* Test the code for compliance

'''Blocking issues'''

None

=== Week 2(8th June - 14th June) ===
'''What I have done during this period?'''
* Corrected schemas for insert(POST) & replace(PUT) transactions as per suggestions from mentors
* Modified the code to generate the proposed openapi doc
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Test the code for compliance

'''Blocking issues'''

None

=== Week 3(15th June - 21st June) ===
'''What I have done during this period?'''
* Started writing test cases for get_oas30() function
* Started testing and made corrections to the code
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Complete writing test cases and compliance test
* Start documentation

'''Blocking issues'''

None

=== Week 4(22nd June - 28th June) ===
'''What I have done during this period?'''
* Refactored code and passed flake8 linting
* Integrated travis CI and read the docs to my branch
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Add more test cases and pass travis build
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Coding Phase 2 ===
=== Week 5(29th June - 5th July) ===
'''What I have done during this period?'''
* Refactored code to pass the community standards
* Added details about transaction functionality to the configuration section in the documentation
* Raised [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Started researching on generic implementations for routing

'''What do I plan on doing next week?'''
* Fix a generic implementation for routing
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Week 6(6th July - 12th July) ===
'''What I have done during this period?'''
* Performed suggested changes on the [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Designed a basic solution for generic flask endpoint to add support for transactions
* Successfully implemented a flask endpoint for POST and tested it with the available geojson provider implementation

'''What do I plan on doing next week?'''
* Find a better solution for the generic endpoint
* Implement rest of the flask endpoints
* Refactor code by adding exceptions and write unit tests

'''Blocking issues'''

None

=== Week 7(13th July - 19th July) ===
'''What I have done during this period?'''
* Implemented flask and starlette routings for transaction requests
* Implemented transaction support for the geojson data provider

'''What do I plan on doing next week?'''
* Add transaction unit tests for flask_app.py and starlette_app.py
* Add transaction unit tests for the geojson data provider
* Start implementing transactional support in other data providers

'''Blocking issues'''

None

=== Week 8(20th July - 26th July) ===
'''What I have done during this period?'''
* Implemented transaction support for csv data provider
* Refactored geojson data provider code
* Added new unit tests for geojson and csv data providers

'''What do I plan on doing next week?'''
* Write unit tests for transactional support in remaining data providers
* Start implementing transactional support in remaining data providers

'''Blocking issues'''

None

=== Week 9(27th July - 2nd August) ===
'''What I have done during this period?'''
* Modified schemaless providers to fully support PATCH verb
* Completed unit tests for geojson and csv providers
* Completed functional tests for flask and starlette endpoints

'''What do I plan on doing next week?'''
* Write unit tests for transactional support in remaining data providers
* Start implementing transactional support in remaining data providers

'''Blocking issues'''

None

=== Week 10(3rd August - 9th August) ===
'''What I have done during this period?'''
* Improved openapi with examples
* Improved descriptions for CRUD operations
* Created unit tests for postgresql and sqlite providers

'''What do I plan on doing next week?'''
* Implement transactional support for postgresql and sqlite providers

'''Blocking issues'''

None

=== Week 11(10th August - 16th August) ===
'''What I have done during this period?'''
* Added documentation for data transactions
* Updated id selection rule for POST transaction based on data type of id
* Updated request examples in openapidoc
* Started working on transactional support for postgresql and sqlite providers

'''What do I plan on doing next week?'''
* Complete transactional support for postgresql and sqlite providers

'''Blocking issues'''

None

=== Week 12(17th August - 23rd August) ===
'''What I have done during this period?'''
* Updated documentation for data transactions
* Updated csv provider to handle type of attributes
* Updated id selection rule in POST to generate type specific ids
* Updated request examples in openapidoc
* Started writing unit tests for postgresql and sqlite providers

'''What do I plan on doing next week?'''
* Complete transactional support for postgresql and sqlite providers

'''Blocking issues'''

None

== Student's Biography ==
My name is Alex Mathew. I am a computer science graduate now pursuing my masters in geoinformatics under the Centre of Studies in Resources Engineering, Indian Institute of Technology Bombay, Mumbai, India.
Some more information about me can be obtained by following the link: [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]

== Mentors ==
*Jorge de Jesus
*Francesco Bartoli

[[Category: Google Summer of Code]]

GSoC 2020 Data transaction implementation on pygeoapi

2020-08-23T21:22:41Z

Wiki-Alex-mathew: /* Timeline */

== Introduction ==
=== Idea ===
[https://pygeoapi.io/ pygeoapi] is a python server implementation of the OGC API suite of standards. The project emerged as part of the next generation OGC API efforts in 2018 and provides the capability for organizations to deploy a RESTful OGC API endpoint using OpenAPI, GeoJSON, and HTML. pygeoapi is open source and released under an MIT license.

This GSoC project aims to add support for simple transactions in pygeoapi. This project will implement Create, Update, Delete operations in pygeoapi data providers, thereby enabling all standard CRUD transactions in pygeoapi. This will enable an application developer to perform a transaction in a pygeoapi data provider through an HTTP request containing the resource id and suitable HTTP verb (POST/PUT/DELETE/PATCH). The project proposal is based on [http://docs.opengeospatial.org/DRAFTS/20-002.html OGC API - Features - Part 4: Simple Transactions].

===Project proposal===
My proposal for GSoC 2020 can be found at [https://docs.google.com/document/d/1NaUvOVT8hJVa-jCQHatnnvblD8GQmRKWbxs8_Jrm0dw/edit?usp=sharing Proposal].

=== Advantages from this project ===
pygeoapi implements OGC WFS 3.0 (OGC Feature API) which is fully RESTful. This makes it much easier for the application developers to work with. This project idea implements 'Part 4 : Simple Transactions' of this OGC standard. It adds transactional capabilities to the pygeoapi data providers by which application developers can perform transactions via the RESTful API itself. A RESTful API supporting complete CRUD transactions will be preferred by most application developers over other non-RESTful APIs. So this will make pygeoapi a more popular choice among application developers.

'''Link to Github repository:''' [https://github.com/alex-mathew/pygeoapi Repo]
== Timeline ==

=== Community bonding period ===
=== 4th May - 31st May ===
'''What I have done during this period?'''
* Joined pygeoapi Gitter room
* Went through the current features of pygeoapi
* Went through OGC API - Features - Part 4: Simple Transactions [http://docs.opengeospatial.org/DRAFTS/20-002.html] draft
* Forked the pygeoapi GitHub repository [https://github.com/alex-mathew/pygeoapi Repository]
* Introduced myself over the channel and shared my proposal over mailing list for suggestions
* Created a wiki page for the project "Data transaction implementation on pygeoapi"
* Updated wiki user page and added my personal information [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]
* Updated links on the wiki Google_Summer_of_Code_2020_Accepted page [[https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2020_Accepted Link]]
* Had a discussion with mentors regarding the expectations and development workflow
* Discussed the openapi specification document with the mentors
* Started working on the openapi document

=== Coding Phase 1 ===
=== Week 1(1st June - 7th June) ===
'''What I have done during this period?'''
* Defined openapi document schemas for remove(DELETE), insert(POST), modify(PATCH), replace(PUT) transactions
* Pushed the proposed openapi document sample to the openapidoc branch in my [https://github.com/alex-mathew/pygeoapi forked repo]
* Shared the doc with pygeoapi community for suggestions

'''What do I plan on doing next week?'''
* Modify openapi.py file so that it generates the proposed openapi document
* Test the code for compliance

'''Blocking issues'''

None

=== Week 2(8th June - 14th June) ===
'''What I have done during this period?'''
* Corrected schemas for insert(POST) & replace(PUT) transactions as per suggestions from mentors
* Modified the code to generate the proposed openapi doc
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Test the code for compliance

'''Blocking issues'''

None

=== Week 3(15th June - 21st June) ===
'''What I have done during this period?'''
* Started writing test cases for get_oas30() function
* Started testing and made corrections to the code
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Complete writing test cases and compliance test
* Start documentation

'''Blocking issues'''

None

=== Week 4(22nd June - 28th June) ===
'''What I have done during this period?'''
* Refactored code and passed flake8 linting
* Integrated travis CI and read the docs to my branch
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Add more test cases and pass travis build
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Coding Phase 2 ===
=== Week 5(29th June - 5th July) ===
'''What I have done during this period?'''
* Refactored code to pass the community standards
* Added details about transaction functionality to the configuration section in the documentation
* Raised [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Started researching on generic implementations for routing

'''What do I plan on doing next week?'''
* Fix a generic implementation for routing
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Week 6(6th July - 12th July) ===
'''What I have done during this period?'''
* Performed suggested changes on the [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Designed a basic solution for generic flask endpoint to add support for transactions
* Successfully implemented a flask endpoint for POST and tested it with the available geojson provider implementation

'''What do I plan on doing next week?'''
* Find a better solution for the generic endpoint
* Implement rest of the flask endpoints
* Refactor code by adding exceptions and write unit tests

'''Blocking issues'''

None

=== Week 7(13th July - 19th July) ===
'''What I have done during this period?'''
* Implemented flask and starlette routings for transaction requests
* Implemented transaction support for the geojson data provider

'''What do I plan on doing next week?'''
* Add transaction unit tests for flask_app.py and starlette_app.py
* Add transaction unit tests for the geojson data provider
* Start implementing transactional support in other data providers

'''Blocking issues'''

None

=== Week 8(20th July - 26th July) ===
'''What I have done during this period?'''
* Implemented transaction support for csv data provider
* Refactored geojson data provider code
* Added new unit tests for geojson and csv data providers

'''What do I plan on doing next week?'''
* Write unit tests for transactional support in remaining data providers
* Start implementing transactional support in remaining data providers

'''Blocking issues'''

None

=== Week 9(27th July - 2nd August) ===
'''What I have done during this period?'''
* Modified schemaless providers to fully support PATCH verb
* Completed unit tests for geojson and csv providers
* Completed functional tests for flask and starlette endpoints

'''What do I plan on doing next week?'''
* Write unit tests for transactional support in remaining data providers
* Start implementing transactional support in remaining data providers

'''Blocking issues'''

None

=== Week 10(3rd August - 9th August) ===
'''What I have done during this period?'''
* Improved openapi with examples
* Improved descriptions for CRUD operations
* Created unit tests for postgresql and sqlite providers

'''What do I plan on doing next week?'''
* Implement transactional support for postgresql and sqlite providers

'''Blocking issues'''

None

=== Week 11(10th August - 16th August) ===
'''What I have done during this period?'''
* Added documentation for data transactions
* Updated id selection rule for POST transaction based on data type of id
* Updated request examples in openapidoc
* Started working on transactional support for postgresql and sqlite providers

'''What do I plan on doing next week?'''
* Complete transactional support for postgresql and sqlite providers

'''Blocking issues'''

None

=== Week 12(17th August - 23rd August) ===
'''What I have done during this period?'''
* Updated documentation for data transactions
* Updated csv provider to handle type of attributes
* Updated id selection rule in POST to generate type specific ids
* Updated request examples in openapidoc
* Started writing unit tests for postgresql and sqlite providers

'''What do I plan on doing next week?'''
* Complete transactional support for postgresql and sqlite providers

'''Blocking issues'''

None

== Student's Biography ==
My name is Alex Mathew. I am a computer science graduate now pursuing my masters in geoinformatics under the Centre of Studies in Resources Engineering, Indian Institute of Technology Bombay, Mumbai, India.
Some more information about me can be obtained by following the link: [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]

== Mentors ==
*Jorge de Jesus
*Francesco Bartoli

[[Category: Google Summer of Code]]

GSoC 2020 Data transaction implementation on pygeoapi

2020-08-16T18:35:34Z

Wiki-Alex-mathew: /* Timeline */

== Introduction ==
=== Idea ===
[https://pygeoapi.io/ pygeoapi] is a python server implementation of the OGC API suite of standards. The project emerged as part of the next generation OGC API efforts in 2018 and provides the capability for organizations to deploy a RESTful OGC API endpoint using OpenAPI, GeoJSON, and HTML. pygeoapi is open source and released under an MIT license.

This GSoC project aims to add support for simple transactions in pygeoapi. This project will implement Create, Update, Delete operations in pygeoapi data providers, thereby enabling all standard CRUD transactions in pygeoapi. This will enable an application developer to perform a transaction in a pygeoapi data provider through an HTTP request containing the resource id and suitable HTTP verb (POST/PUT/DELETE/PATCH). The project proposal is based on [http://docs.opengeospatial.org/DRAFTS/20-002.html OGC API - Features - Part 4: Simple Transactions].

===Project proposal===
My proposal for GSoC 2020 can be found at [https://docs.google.com/document/d/1NaUvOVT8hJVa-jCQHatnnvblD8GQmRKWbxs8_Jrm0dw/edit?usp=sharing Proposal].

=== Advantages from this project ===
pygeoapi implements OGC WFS 3.0 (OGC Feature API) which is fully RESTful. This makes it much easier for the application developers to work with. This project idea implements 'Part 4 : Simple Transactions' of this OGC standard. It adds transactional capabilities to the pygeoapi data providers by which application developers can perform transactions via the RESTful API itself. A RESTful API supporting complete CRUD transactions will be preferred by most application developers over other non-RESTful APIs. So this will make pygeoapi a more popular choice among application developers.

'''Link to Github repository:''' [https://github.com/alex-mathew/pygeoapi Repo]
== Timeline ==

=== Community bonding period ===
=== 4th May - 31st May ===
'''What I have done during this period?'''
* Joined pygeoapi Gitter room
* Went through the current features of pygeoapi
* Went through OGC API - Features - Part 4: Simple Transactions [http://docs.opengeospatial.org/DRAFTS/20-002.html] draft
* Forked the pygeoapi GitHub repository [https://github.com/alex-mathew/pygeoapi Repository]
* Introduced myself over the channel and shared my proposal over mailing list for suggestions
* Created a wiki page for the project "Data transaction implementation on pygeoapi"
* Updated wiki user page and added my personal information [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]
* Updated links on the wiki Google_Summer_of_Code_2020_Accepted page [[https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2020_Accepted Link]]
* Had a discussion with mentors regarding the expectations and development workflow
* Discussed the openapi specification document with the mentors
* Started working on the openapi document

=== Coding Phase 1 ===
=== Week 1(1st June - 7th June) ===
'''What I have done during this period?'''
* Defined openapi document schemas for remove(DELETE), insert(POST), modify(PATCH), replace(PUT) transactions
* Pushed the proposed openapi document sample to the openapidoc branch in my [https://github.com/alex-mathew/pygeoapi forked repo]
* Shared the doc with pygeoapi community for suggestions

'''What do I plan on doing next week?'''
* Modify openapi.py file so that it generates the proposed openapi document
* Test the code for compliance

'''Blocking issues'''

None

=== Week 2(8th June - 14th June) ===
'''What I have done during this period?'''
* Corrected schemas for insert(POST) & replace(PUT) transactions as per suggestions from mentors
* Modified the code to generate the proposed openapi doc
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Test the code for compliance

'''Blocking issues'''

None

=== Week 3(15th June - 21st June) ===
'''What I have done during this period?'''
* Started writing test cases for get_oas30() function
* Started testing and made corrections to the code
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Complete writing test cases and compliance test
* Start documentation

'''Blocking issues'''

None

=== Week 4(22nd June - 28th June) ===
'''What I have done during this period?'''
* Refactored code and passed flake8 linting
* Integrated travis CI and read the docs to my branch
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Add more test cases and pass travis build
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Coding Phase 2 ===
=== Week 5(29th June - 5th July) ===
'''What I have done during this period?'''
* Refactored code to pass the community standards
* Added details about transaction functionality to the configuration section in the documentation
* Raised [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Started researching on generic implementations for routing

'''What do I plan on doing next week?'''
* Fix a generic implementation for routing
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Week 6(6th July - 12th July) ===
'''What I have done during this period?'''
* Performed suggested changes on the [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Designed a basic solution for generic flask endpoint to add support for transactions
* Successfully implemented a flask endpoint for POST and tested it with the available geojson provider implementation

'''What do I plan on doing next week?'''
* Find a better solution for the generic endpoint
* Implement rest of the flask endpoints
* Refactor code by adding exceptions and write unit tests

'''Blocking issues'''

None

=== Week 7(13th July - 19th July) ===
'''What I have done during this period?'''
* Implemented flask and starlette routings for transaction requests
* Implemented transaction support for the geojson data provider

'''What do I plan on doing next week?'''
* Add transaction unit tests for flask_app.py and starlette_app.py
* Add transaction unit tests for the geojson data provider
* Start implementing transactional support in other data providers

'''Blocking issues'''

None

=== Week 8(20th July - 26th July) ===
'''What I have done during this period?'''
* Implemented transaction support for csv data provider
* Refactored geojson data provider code
* Added new unit tests for geojson and csv data providers

'''What do I plan on doing next week?'''
* Write unit tests for transactional support in remaining data providers
* Start implementing transactional support in remaining data providers

'''Blocking issues'''

None

=== Week 9(27th July - 2nd August) ===
'''What I have done during this period?'''
* Modified schemaless providers to fully support PATCH verb
* Completed unit tests for geojson and csv providers
* Completed functional tests for flask and starlette endpoints

'''What do I plan on doing next week?'''
* Write unit tests for transactional support in remaining data providers
* Start implementing transactional support in remaining data providers

'''Blocking issues'''

None

=== Week 10(3rd August - 9th August) ===
'''What I have done during this period?'''
* Improved openapi with examples
* Improved descriptions for CRUD operations
* Created unit tests for postgresql and sqlite providers

'''What do I plan on doing next week?'''
* Implement transactional support for postgresql and sqlite providers

'''Blocking issues'''

None

=== Week 11(10th August - 16th August) ===
'''What I have done during this period?'''
* Added documentation for data transactions
* Updated id selection rule for POST transaction based on data type of id
* Updated request examples in openapidoc
* Started working on transactional support for postgresql and sqlite providers

'''What do I plan on doing next week?'''
* Complete transactional support for postgresql and sqlite providers

'''Blocking issues'''

None

== Student's Biography ==
My name is Alex Mathew. I am a computer science graduate now pursuing my masters in geoinformatics under the Centre of Studies in Resources Engineering, Indian Institute of Technology Bombay, Mumbai, India.
Some more information about me can be obtained by following the link: [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]

== Mentors ==
*Jorge de Jesus
*Francesco Bartoli

[[Category: Google Summer of Code]]

GSoC 2020 Data transaction implementation on pygeoapi

2020-08-09T18:29:07Z

Wiki-Alex-mathew: /* Timeline */

== Introduction ==
=== Idea ===
[https://pygeoapi.io/ pygeoapi] is a python server implementation of the OGC API suite of standards. The project emerged as part of the next generation OGC API efforts in 2018 and provides the capability for organizations to deploy a RESTful OGC API endpoint using OpenAPI, GeoJSON, and HTML. pygeoapi is open source and released under an MIT license.

This GSoC project aims to add support for simple transactions in pygeoapi. This project will implement Create, Update, Delete operations in pygeoapi data providers, thereby enabling all standard CRUD transactions in pygeoapi. This will enable an application developer to perform a transaction in a pygeoapi data provider through an HTTP request containing the resource id and suitable HTTP verb (POST/PUT/DELETE/PATCH). The project proposal is based on [http://docs.opengeospatial.org/DRAFTS/20-002.html OGC API - Features - Part 4: Simple Transactions].

===Project proposal===
My proposal for GSoC 2020 can be found at [https://docs.google.com/document/d/1NaUvOVT8hJVa-jCQHatnnvblD8GQmRKWbxs8_Jrm0dw/edit?usp=sharing Proposal].

=== Advantages from this project ===
pygeoapi implements OGC WFS 3.0 (OGC Feature API) which is fully RESTful. This makes it much easier for the application developers to work with. This project idea implements 'Part 4 : Simple Transactions' of this OGC standard. It adds transactional capabilities to the pygeoapi data providers by which application developers can perform transactions via the RESTful API itself. A RESTful API supporting complete CRUD transactions will be preferred by most application developers over other non-RESTful APIs. So this will make pygeoapi a more popular choice among application developers.

'''Link to Github repository:''' [https://github.com/alex-mathew/pygeoapi Repo]
== Timeline ==

=== Community bonding period ===
=== 4th May - 31st May ===
'''What I have done during this period?'''
* Joined pygeoapi Gitter room
* Went through the current features of pygeoapi
* Went through OGC API - Features - Part 4: Simple Transactions [http://docs.opengeospatial.org/DRAFTS/20-002.html] draft
* Forked the pygeoapi GitHub repository [https://github.com/alex-mathew/pygeoapi Repository]
* Introduced myself over the channel and shared my proposal over mailing list for suggestions
* Created a wiki page for the project "Data transaction implementation on pygeoapi"
* Updated wiki user page and added my personal information [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]
* Updated links on the wiki Google_Summer_of_Code_2020_Accepted page [[https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2020_Accepted Link]]
* Had a discussion with mentors regarding the expectations and development workflow
* Discussed the openapi specification document with the mentors
* Started working on the openapi document

=== Coding Phase 1 ===
=== Week 1(1st June - 7th June) ===
'''What I have done during this period?'''
* Defined openapi document schemas for remove(DELETE), insert(POST), modify(PATCH), replace(PUT) transactions
* Pushed the proposed openapi document sample to the openapidoc branch in my [https://github.com/alex-mathew/pygeoapi forked repo]
* Shared the doc with pygeoapi community for suggestions

'''What do I plan on doing next week?'''
* Modify openapi.py file so that it generates the proposed openapi document
* Test the code for compliance

'''Blocking issues'''

None

=== Week 2(8th June - 14th June) ===
'''What I have done during this period?'''
* Corrected schemas for insert(POST) & replace(PUT) transactions as per suggestions from mentors
* Modified the code to generate the proposed openapi doc
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Test the code for compliance

'''Blocking issues'''

None

=== Week 3(15th June - 21st June) ===
'''What I have done during this period?'''
* Started writing test cases for get_oas30() function
* Started testing and made corrections to the code
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Complete writing test cases and compliance test
* Start documentation

'''Blocking issues'''

None

=== Week 4(22nd June - 28th June) ===
'''What I have done during this period?'''
* Refactored code and passed flake8 linting
* Integrated travis CI and read the docs to my branch
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Add more test cases and pass travis build
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Coding Phase 2 ===
=== Week 5(29th June - 5th July) ===
'''What I have done during this period?'''
* Refactored code to pass the community standards
* Added details about transaction functionality to the configuration section in the documentation
* Raised [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Started researching on generic implementations for routing

'''What do I plan on doing next week?'''
* Fix a generic implementation for routing
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Week 6(6th July - 12th July) ===
'''What I have done during this period?'''
* Performed suggested changes on the [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Designed a basic solution for generic flask endpoint to add support for transactions
* Successfully implemented a flask endpoint for POST and tested it with the available geojson provider implementation

'''What do I plan on doing next week?'''
* Find a better solution for the generic endpoint
* Implement rest of the flask endpoints
* Refactor code by adding exceptions and write unit tests

'''Blocking issues'''

None

=== Week 7(13th July - 19th July) ===
'''What I have done during this period?'''
* Implemented flask and starlette routings for transaction requests
* Implemented transaction support for the geojson data provider

'''What do I plan on doing next week?'''
* Add transaction unit tests for flask_app.py and starlette_app.py
* Add transaction unit tests for the geojson data provider
* Start implementing transactional support in other data providers

'''Blocking issues'''

None

=== Week 8(20th July - 26th July) ===
'''What I have done during this period?'''
* Implemented transaction support for csv data provider
* Refactored geojson data provider code
* Added new unit tests for geojson and csv data providers

'''What do I plan on doing next week?'''
* Write unit tests for transactional support in remaining data providers
* Start implementing transactional support in remaining data providers

'''Blocking issues'''

None

=== Week 9(27th July - 2nd August) ===
'''What I have done during this period?'''
* Modified schemaless providers to fully support PATCH verb
* Completed unit tests for geojson and csv providers
* Completed functional tests for flask and starlette endpoints

'''What do I plan on doing next week?'''
* Write unit tests for transactional support in remaining data providers
* Start implementing transactional support in remaining data providers

'''Blocking issues'''

None

=== Week 10(3rd August - 9th August) ===
'''What I have done during this period?'''
* Improved openapi with examples
* Improved descriptions for CRUD operations
* Created unit tests for postgresql and sqlite providers

'''What do I plan on doing next week?'''
* Implement transactional support for postgresql and sqlite providers

'''Blocking issues'''

None

== Student's Biography ==
My name is Alex Mathew. I am a computer science graduate now pursuing my masters in geoinformatics under the Centre of Studies in Resources Engineering, Indian Institute of Technology Bombay, Mumbai, India.
Some more information about me can be obtained by following the link: [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]

== Mentors ==
*Jorge de Jesus
*Francesco Bartoli

[[Category: Google Summer of Code]]

GSoC 2020 Data transaction implementation on pygeoapi

2020-08-02T16:41:57Z

Wiki-Alex-mathew: /* Timeline */

== Introduction ==
=== Idea ===
[https://pygeoapi.io/ pygeoapi] is a python server implementation of the OGC API suite of standards. The project emerged as part of the next generation OGC API efforts in 2018 and provides the capability for organizations to deploy a RESTful OGC API endpoint using OpenAPI, GeoJSON, and HTML. pygeoapi is open source and released under an MIT license.

This GSoC project aims to add support for simple transactions in pygeoapi. This project will implement Create, Update, Delete operations in pygeoapi data providers, thereby enabling all standard CRUD transactions in pygeoapi. This will enable an application developer to perform a transaction in a pygeoapi data provider through an HTTP request containing the resource id and suitable HTTP verb (POST/PUT/DELETE/PATCH). The project proposal is based on [http://docs.opengeospatial.org/DRAFTS/20-002.html OGC API - Features - Part 4: Simple Transactions].

===Project proposal===
My proposal for GSoC 2020 can be found at [https://docs.google.com/document/d/1NaUvOVT8hJVa-jCQHatnnvblD8GQmRKWbxs8_Jrm0dw/edit?usp=sharing Proposal].

=== Advantages from this project ===
pygeoapi implements OGC WFS 3.0 (OGC Feature API) which is fully RESTful. This makes it much easier for the application developers to work with. This project idea implements 'Part 4 : Simple Transactions' of this OGC standard. It adds transactional capabilities to the pygeoapi data providers by which application developers can perform transactions via the RESTful API itself. A RESTful API supporting complete CRUD transactions will be preferred by most application developers over other non-RESTful APIs. So this will make pygeoapi a more popular choice among application developers.

'''Link to Github repository:''' [https://github.com/alex-mathew/pygeoapi Repo]
== Timeline ==

=== Community bonding period ===
=== 4th May - 31st May ===
'''What I have done during this period?'''
* Joined pygeoapi Gitter room
* Went through the current features of pygeoapi
* Went through OGC API - Features - Part 4: Simple Transactions [http://docs.opengeospatial.org/DRAFTS/20-002.html] draft
* Forked the pygeoapi GitHub repository [https://github.com/alex-mathew/pygeoapi Repository]
* Introduced myself over the channel and shared my proposal over mailing list for suggestions
* Created a wiki page for the project "Data transaction implementation on pygeoapi"
* Updated wiki user page and added my personal information [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]
* Updated links on the wiki Google_Summer_of_Code_2020_Accepted page [[https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2020_Accepted Link]]
* Had a discussion with mentors regarding the expectations and development workflow
* Discussed the openapi specification document with the mentors
* Started working on the openapi document

=== Coding Phase 1 ===
=== Week 1(1st June - 7th June) ===
'''What I have done during this period?'''
* Defined openapi document schemas for remove(DELETE), insert(POST), modify(PATCH), replace(PUT) transactions
* Pushed the proposed openapi document sample to the openapidoc branch in my [https://github.com/alex-mathew/pygeoapi forked repo]
* Shared the doc with pygeoapi community for suggestions

'''What do I plan on doing next week?'''
* Modify openapi.py file so that it generates the proposed openapi document
* Test the code for compliance

'''Blocking issues'''

None

=== Week 2(8th June - 14th June) ===
'''What I have done during this period?'''
* Corrected schemas for insert(POST) & replace(PUT) transactions as per suggestions from mentors
* Modified the code to generate the proposed openapi doc
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Test the code for compliance

'''Blocking issues'''

None

=== Week 3(15th June - 21st June) ===
'''What I have done during this period?'''
* Started writing test cases for get_oas30() function
* Started testing and made corrections to the code
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Complete writing test cases and compliance test
* Start documentation

'''Blocking issues'''

None

=== Week 4(22nd June - 28th June) ===
'''What I have done during this period?'''
* Refactored code and passed flake8 linting
* Integrated travis CI and read the docs to my branch
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Add more test cases and pass travis build
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Coding Phase 2 ===
=== Week 5(29th June - 5th July) ===
'''What I have done during this period?'''
* Refactored code to pass the community standards
* Added details about transaction functionality to the configuration section in the documentation
* Raised [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Started researching on generic implementations for routing

'''What do I plan on doing next week?'''
* Fix a generic implementation for routing
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Week 6(6th July - 12th July) ===
'''What I have done during this period?'''
* Performed suggested changes on the [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Designed a basic solution for generic flask endpoint to add support for transactions
* Successfully implemented a flask endpoint for POST and tested it with the available geojson provider implementation

'''What do I plan on doing next week?'''
* Find a better solution for the generic endpoint
* Implement rest of the flask endpoints
* Refactor code by adding exceptions and write unit tests

'''Blocking issues'''

None

=== Week 7(13th July - 19th July) ===
'''What I have done during this period?'''
* Implemented flask and starlette routings for transaction requests
* Implemented transaction support for the geojson data provider

'''What do I plan on doing next week?'''
* Add transaction unit tests for flask_app.py and starlette_app.py
* Add transaction unit tests for the geojson data provider
* Start implementing transactional support in other data providers

'''Blocking issues'''

None

=== Week 8(20th July - 26th July) ===
'''What I have done during this period?'''
* Implemented transaction support for csv data provider
* Refactored geojson data provider code
* Added new unit tests for geojson and csv data providers

'''What do I plan on doing next week?'''
* Write unit tests for transactional support in remaining data providers
* Start implementing transactional support in remaining data providers

'''Blocking issues'''

None

=== Week 9(27th July - 2nd August) ===
'''What I have done during this period?'''
* Modified schemaless providers to fully support PATCH verb
* Completed unit tests for geojson and csv providers
* Completed functional tests for flask and starlette endpoints

'''What do I plan on doing next week?'''
* Write unit tests for transactional support in remaining data providers
* Start implementing transactional support in remaining data providers

'''Blocking issues'''

None

== Student's Biography ==
My name is Alex Mathew. I am a computer science graduate now pursuing my masters in geoinformatics under the Centre of Studies in Resources Engineering, Indian Institute of Technology Bombay, Mumbai, India.
Some more information about me can be obtained by following the link: [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]

== Mentors ==
*Jorge de Jesus
*Francesco Bartoli

[[Category: Google Summer of Code]]

GSoC 2020 Data transaction implementation on pygeoapi

2020-07-26T18:20:21Z

Wiki-Alex-mathew: /* Timeline */

== Introduction ==
=== Idea ===
[https://pygeoapi.io/ pygeoapi] is a python server implementation of the OGC API suite of standards. The project emerged as part of the next generation OGC API efforts in 2018 and provides the capability for organizations to deploy a RESTful OGC API endpoint using OpenAPI, GeoJSON, and HTML. pygeoapi is open source and released under an MIT license.

This GSoC project aims to add support for simple transactions in pygeoapi. This project will implement Create, Update, Delete operations in pygeoapi data providers, thereby enabling all standard CRUD transactions in pygeoapi. This will enable an application developer to perform a transaction in a pygeoapi data provider through an HTTP request containing the resource id and suitable HTTP verb (POST/PUT/DELETE/PATCH). The project proposal is based on [http://docs.opengeospatial.org/DRAFTS/20-002.html OGC API - Features - Part 4: Simple Transactions].

===Project proposal===
My proposal for GSoC 2020 can be found at [https://docs.google.com/document/d/1NaUvOVT8hJVa-jCQHatnnvblD8GQmRKWbxs8_Jrm0dw/edit?usp=sharing Proposal].

=== Advantages from this project ===
pygeoapi implements OGC WFS 3.0 (OGC Feature API) which is fully RESTful. This makes it much easier for the application developers to work with. This project idea implements 'Part 4 : Simple Transactions' of this OGC standard. It adds transactional capabilities to the pygeoapi data providers by which application developers can perform transactions via the RESTful API itself. A RESTful API supporting complete CRUD transactions will be preferred by most application developers over other non-RESTful APIs. So this will make pygeoapi a more popular choice among application developers.

'''Link to Github repository:''' [https://github.com/alex-mathew/pygeoapi Repo]
== Timeline ==

=== Community bonding period ===
=== 4th May - 31st May ===
'''What I have done during this period?'''
* Joined pygeoapi Gitter room
* Went through the current features of pygeoapi
* Went through OGC API - Features - Part 4: Simple Transactions [http://docs.opengeospatial.org/DRAFTS/20-002.html] draft
* Forked the pygeoapi GitHub repository [https://github.com/alex-mathew/pygeoapi Repository]
* Introduced myself over the channel and shared my proposal over mailing list for suggestions
* Created a wiki page for the project "Data transaction implementation on pygeoapi"
* Updated wiki user page and added my personal information [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]
* Updated links on the wiki Google_Summer_of_Code_2020_Accepted page [[https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2020_Accepted Link]]
* Had a discussion with mentors regarding the expectations and development workflow
* Discussed the openapi specification document with the mentors
* Started working on the openapi document

=== Coding Phase 1 ===
=== Week 1(1st June - 7th June) ===
'''What I have done during this period?'''
* Defined openapi document schemas for remove(DELETE), insert(POST), modify(PATCH), replace(PUT) transactions
* Pushed the proposed openapi document sample to the openapidoc branch in my [https://github.com/alex-mathew/pygeoapi forked repo]
* Shared the doc with pygeoapi community for suggestions

'''What do I plan on doing next week?'''
* Modify openapi.py file so that it generates the proposed openapi document
* Test the code for compliance

'''Blocking issues'''

None

=== Week 2(8th June - 14th June) ===
'''What I have done during this period?'''
* Corrected schemas for insert(POST) & replace(PUT) transactions as per suggestions from mentors
* Modified the code to generate the proposed openapi doc
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Test the code for compliance

'''Blocking issues'''

None

=== Week 3(15th June - 21st June) ===
'''What I have done during this period?'''
* Started writing test cases for get_oas30() function
* Started testing and made corrections to the code
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Complete writing test cases and compliance test
* Start documentation

'''Blocking issues'''

None

=== Week 4(22nd June - 28th June) ===
'''What I have done during this period?'''
* Refactored code and passed flake8 linting
* Integrated travis CI and read the docs to my branch
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Add more test cases and pass travis build
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Coding Phase 2 ===
=== Week 5(29th June - 5th July) ===
'''What I have done during this period?'''
* Refactored code to pass the community standards
* Added details about transaction functionality to the configuration section in the documentation
* Raised [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Started researching on generic implementations for routing

'''What do I plan on doing next week?'''
* Fix a generic implementation for routing
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Week 6(6th July - 12th July) ===
'''What I have done during this period?'''
* Performed suggested changes on the [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Designed a basic solution for generic flask endpoint to add support for transactions
* Successfully implemented a flask endpoint for POST and tested it with the available geojson provider implementation

'''What do I plan on doing next week?'''
* Find a better solution for the generic endpoint
* Implement rest of the flask endpoints
* Refactor code by adding exceptions and write unit tests

'''Blocking issues'''

None

=== Week 7(13th July - 19th July) ===
'''What I have done during this period?'''
* Implemented flask and starlette routings for transaction requests
* Implemented transaction support for the geojson data provider

'''What do I plan on doing next week?'''
* Add transaction unit tests for flask_app.py and starlette_app.py
* Add transaction unit tests for the geojson data provider
* Start implementing transactional support in other data providers

'''Blocking issues'''

None

=== Week 8(20th July - 26th July) ===
'''What I have done during this period?'''
* Implemented transaction support for csv data provider
* Refactored geojson data provider code
* Added new unit tests for geojson and csv data providers

'''What do I plan on doing next week?'''
* Write unit tests for transactional support in remaining data providers
* Start implementing transactional support in remaining data providers

'''Blocking issues'''

None

== Student's Biography ==
My name is Alex Mathew. I am a computer science graduate now pursuing my masters in geoinformatics under the Centre of Studies in Resources Engineering, Indian Institute of Technology Bombay, Mumbai, India.
Some more information about me can be obtained by following the link: [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]

== Mentors ==
*Jorge de Jesus
*Francesco Bartoli

[[Category: Google Summer of Code]]

GSoC 2020 Data transaction implementation on pygeoapi

2020-07-19T16:08:05Z

Wiki-Alex-mathew: /* Timeline */

== Introduction ==
=== Idea ===
[https://pygeoapi.io/ pygeoapi] is a python server implementation of the OGC API suite of standards. The project emerged as part of the next generation OGC API efforts in 2018 and provides the capability for organizations to deploy a RESTful OGC API endpoint using OpenAPI, GeoJSON, and HTML. pygeoapi is open source and released under an MIT license.

This GSoC project aims to add support for simple transactions in pygeoapi. This project will implement Create, Update, Delete operations in pygeoapi data providers, thereby enabling all standard CRUD transactions in pygeoapi. This will enable an application developer to perform a transaction in a pygeoapi data provider through an HTTP request containing the resource id and suitable HTTP verb (POST/PUT/DELETE/PATCH). The project proposal is based on [http://docs.opengeospatial.org/DRAFTS/20-002.html OGC API - Features - Part 4: Simple Transactions].

===Project proposal===
My proposal for GSoC 2020 can be found at [https://docs.google.com/document/d/1NaUvOVT8hJVa-jCQHatnnvblD8GQmRKWbxs8_Jrm0dw/edit?usp=sharing Proposal].

=== Advantages from this project ===
pygeoapi implements OGC WFS 3.0 (OGC Feature API) which is fully RESTful. This makes it much easier for the application developers to work with. This project idea implements 'Part 4 : Simple Transactions' of this OGC standard. It adds transactional capabilities to the pygeoapi data providers by which application developers can perform transactions via the RESTful API itself. A RESTful API supporting complete CRUD transactions will be preferred by most application developers over other non-RESTful APIs. So this will make pygeoapi a more popular choice among application developers.

'''Link to Github repository:''' [https://github.com/alex-mathew/pygeoapi Repo]
== Timeline ==

=== Community bonding period ===
=== 4th May - 31st May ===
'''What I have done during this period?'''
* Joined pygeoapi Gitter room
* Went through the current features of pygeoapi
* Went through OGC API - Features - Part 4: Simple Transactions [http://docs.opengeospatial.org/DRAFTS/20-002.html] draft
* Forked the pygeoapi GitHub repository [https://github.com/alex-mathew/pygeoapi Repository]
* Introduced myself over the channel and shared my proposal over mailing list for suggestions
* Created a wiki page for the project "Data transaction implementation on pygeoapi"
* Updated wiki user page and added my personal information [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]
* Updated links on the wiki Google_Summer_of_Code_2020_Accepted page [[https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2020_Accepted Link]]
* Had a discussion with mentors regarding the expectations and development workflow
* Discussed the openapi specification document with the mentors
* Started working on the openapi document

=== Coding Phase 1 ===
=== Week 1(1st June - 7th June) ===
'''What I have done during this period?'''
* Defined openapi document schemas for remove(DELETE), insert(POST), modify(PATCH), replace(PUT) transactions
* Pushed the proposed openapi document sample to the openapidoc branch in my [https://github.com/alex-mathew/pygeoapi forked repo]
* Shared the doc with pygeoapi community for suggestions

'''What do I plan on doing next week?'''
* Modify openapi.py file so that it generates the proposed openapi document
* Test the code for compliance

'''Blocking issues'''

None

=== Week 2(8th June - 14th June) ===
'''What I have done during this period?'''
* Corrected schemas for insert(POST) & replace(PUT) transactions as per suggestions from mentors
* Modified the code to generate the proposed openapi doc
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Test the code for compliance

'''Blocking issues'''

None

=== Week 3(15th June - 21st June) ===
'''What I have done during this period?'''
* Started writing test cases for get_oas30() function
* Started testing and made corrections to the code
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Complete writing test cases and compliance test
* Start documentation

'''Blocking issues'''

None

=== Week 4(22nd June - 28th June) ===
'''What I have done during this period?'''
* Refactored code and passed flake8 linting
* Integrated travis CI and read the docs to my branch
* Pushed the changes to my [https://github.com/alex-mathew/pygeoapi forked repo]

'''What do I plan on doing next week?'''
* Add more test cases and pass travis build
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Coding Phase 2 ===
=== Week 5(29th June - 5th July) ===
'''What I have done during this period?'''
* Refactored code to pass the community standards
* Added details about transaction functionality to the configuration section in the documentation
* Raised [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Started researching on generic implementations for routing

'''What do I plan on doing next week?'''
* Fix a generic implementation for routing
* Mockup REST endpoints on flask_app.py

'''Blocking issues'''

None

=== Week 6(6th July - 12th July) ===
'''What I have done during this period?'''
* Performed suggested changes on the [https://github.com/geopython/pygeoapi/pull/483 PR] for data-transaction-GSoC-1 branch
* Designed a basic solution for generic flask endpoint to add support for transactions
* Successfully implemented a flask endpoint for POST and tested it with the available geojson provider implementation

'''What do I plan on doing next week?'''
* Find a better solution for the generic endpoint
* Implement rest of the flask endpoints
* Refactor code by adding exceptions and write unit tests

'''Blocking issues'''

None

=== Week 7(13th July - 19th July) ===
'''What I have done during this period?'''
* Implemented flask and starlette routings for transaction requests
* Implemented transaction support for the geojson data provider

'''What do I plan on doing next week?'''
* Add transaction unit tests for flask_app.py and starlette_app.py
* Add transaction unit tests for the geojson data provider
* Start implementing transactional support in other data providers

'''Blocking issues'''

None

== Student's Biography ==
My name is Alex Mathew. I am a computer science graduate now pursuing my masters in geoinformatics under the Centre of Studies in Resources Engineering, Indian Institute of Technology Bombay, Mumbai, India.
Some more information about me can be obtained by following the link: [[https://wiki.osgeo.org/wiki/User:Alex-mathew Link]]

== Mentors ==
*Jorge de Jesus
*Francesco Bartoli

[[Category: Google Summer of Code]]

GSoC 2020 Data transaction implementation on pygeoapi

2020-07-12T18:27:41Z

Wiki-Alex-mathew: /* Timeline */

GSoC 2020 Data transaction implementation on pygeoapi

2020-07-05T18:31:29Z

Wiki-Alex-mathew:

GSoC 2020 Data transaction implementation on pygeoapi

2020-06-28T15:45:23Z

Wiki-Alex-mathew: /* Timeline */

GSoC 2020 Data transaction implementation on pygeoapi

2020-06-21T16:57:23Z

Wiki-Alex-mathew: /* Timeline */

GSoC 2020 Data transaction implementation on pygeoapi

2020-06-14T18:34:27Z

Wiki-Alex-mathew:

GSoC 2020 Data transaction implementation on pygeoapi

2020-06-06T16:56:25Z

Wiki-Alex-mathew:

GSoC 2020 Data transaction implementation on pygeoapi

2020-06-06T16:47:59Z

Wiki-Alex-mathew:

GSoC 2020 Data transaction implementation on pygeoapi

2020-06-06T16:47:14Z

Wiki-Alex-mathew:

GSoC 2020 Data transaction implementation on pygeoapi

2020-06-06T16:46:36Z

Wiki-Alex-mathew:

GSoC 2020 Data transaction implementation on pygeoapi

2020-05-28T20:20:53Z

Wiki-Alex-mathew:

GSoC 2020 Data transaction implementation on pygeoapi

2020-05-28T19:32:12Z

Wiki-Alex-mathew: /* 4th May - 31st May */

GSoC 2020 Data transaction implementation on pygeoapi

2020-05-20T04:10:33Z

Wiki-Alex-mathew:

User:Alex-mathew

2020-05-19T20:17:23Z

Wiki-Alex-mathew:

{{OSGeo Member
|Name=Alex Mathew
|JobTitle=Student
|Address=Indian Institute of Technology, Bombay
|Country=India
|State=Maharashtra
|City=Mumbai
|Coordinate=19.134385, 72.905793
|LocalChapter=India
|Email=pingalex94@gmail.com
|Phone=(+91)9446756867
|SocialMedia=https://www.linkedin.com/in/alex94/;
|Website=https://alex-mathew.github.io/
|Photo=Alex.jpg
|Languages=English; Malayalam;
|Info=My name is Alex Mathew. I am a Computer Science graduate, pursuing my Master's degree in Geoinformatics Engineering under the Centre of Studies in Resources Engineering, Indian Institute of Technology Bombay, Mumbai, India.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=No
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
I am working on the project "Data transaction implementation on pygeoapi" for GSoC 2020. [https://wiki.osgeo.org/wiki/GSoC_2020_Data_transaction_implementation_on_pygeoapi]

Google Summer of Code 2020 Accepted

2020-05-19T20:13:40Z

Wiki-Alex-mathew:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] <font size="+3"> @ </font>
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

* Back to the main OSGeo [[Google Summer of Code 2020]] @ OSGeo wiki page.

== Accepted Proposals ==

This year OSGeo accepted 10 students working on the following projects:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;"
|'''Project Logo'''
|'''Community'''
|'''Project'''
|'''Student'''
|'''1st mentor'''
|'''2nd mentor'''
|'''Other Mentors'''
|'''Wiki page'''
|'''Repository'''
|-
|[[Image:logo-qgis.png|40px|center]]
|QGIS
|Improving QGIS 3D
|[[User:Belgacem_nedjima|Belgacem Nedjima]]
|[[User:MartinDobias|Martin Dobias]]
|[[User:Zilolv|Peter Petrik]]
|
|https://wiki.osgeo.org/wiki/Improving_qgis_3d
|https://github.com/NEDJIMAbelgacem/QGIS
|-
|-
|[[Image:logo-grass.png|40px|center]]
|GRASS GIS
|<Fill Details Here>
|Linda Kladivova
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|-
|-
|[[Image:Mapmint-logo-small.png|40px|center]]
|MapMint
|Enhancing ARScale and CloudAnchor support to the MapMint4ME Android Application
|Aditi Sawant
|Gérald Fenoy
|Rajat Shinde
|
|https://wiki.osgeo.org/wiki/Enhancing_ARScale_and_CloudAnchor_support_to_the_MapMint4ME_Android_Application#Idea
|https://github.com/aditis1204/MapMint4ME_shapes
|-
|-
|[[Image:logo-gvSIG.png|40px|center]]
|gvSIG
|<Fill Details Here>
|Giani Carlevaro
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|-
|-
|[[Image:logo-gvSIG.png|40px|center]]
|gvSIG
|New rules for the Topology Framework in gvSIG Desktop
|José Olivas
|Oscar Martinez
|Mario Carrera
|jjdelcerror
|https://github.com/jolicar/GSoC2020/wiki/GSoC2020-New-rules-for-the-Topology-Framework-in-gvSIG-Desktop
|https://github.com/jolicar/GSoC2020
|-
|-
|[[Image:Pgrouting-logo.png|40px|center]]
|pgRouting
|Depth First Search and Sequential Vertex Coloring for pgRouting
|Ashish Kumar
|Daniel Kastl
|Cayetano Benavent
|
|https://github.com/pgRouting/pgrouting/wiki/GSoC-2020-Depth-First-Search-and-Sequential-Vertex-Coloring
|https://github.com/krashish8/GSoC-pgRouting
|-
|-
|[[Image:Pgrouting-logo.png|40px|center]]
|pgRouting
|Implementation of Edge Contraction Technique in pgRouting
|Himanshu Raj
|Vicky Vergara
|Daniel Kastl
|
|https://github.com/pgRouting/pgrouting/wiki/GSoC-2020-Implementation-of-Edge-Contraction-Technique-in-pgRouting
|https://github.com/pgRouting/GSoC-pgRouting/tree/edgeContract
|-
|-
|[[Image:Pgrouting-logo.png|40px|center]]
|pgRouting
|Lengauer Tarjan dominator tree and Two graphs common Spanning Trees for pgRouting
|Prakash Tiwari
|Vicky Vergara
|Aasheesh Tiwari
|<Fill Details Here>
|https://github.com/pgRouting/pgrouting/wiki/GSoC-2020-Lengauer-Tarjan-dominator-tree-and-Two-graphs-common-Spanning-Trees
|https://github.com/prakashupes/GSoC-pgRouting
|-
|-
|[[Image:Pygeoapi-logo.png|100px|center]]
|pygeoapi
|Data Transaction implementation on pygeoapi
|Alex Mathew
|Jorge de Jesus
|Francesco Bartoli
|
|https://wiki.osgeo.org/wiki/GSoC_2020_Data_transaction_implementation_on_pygeoapi
|https://github.com/alex-mathew/pygeoapi
|-
|-
|[[Image:Pygeoapi-logo.png|100px|center]]
|pygeoapi
|Develop CQL Filter implementation for pygeoapi
|Farheen Bano
|Francesco Bartoli
|Jorge Samuel Mendes de Jesus
|
|https://wiki.osgeo.org/wiki/GSoC_2020_Develop_CQL_Filter_implementation_for_pygeoapi
|https://github.com/FarheenB/pygeoapi
|-
|}

[[Category:Google Summer of Code]]

GSoC 2020 Data transaction implementation on pygeoapi

2020-05-19T20:09:19Z

Wiki-Alex-mathew: Created page with "== Introduction == === Idea === [https://pygeoapi.io/ pygeoapi] is a python server implementation of the OGC API suite of standards. The project emerged as part of the next ge..."

User:Alex-mathew

2020-05-19T19:54:38Z

Wiki-Alex-mathew:

{{OSGeo Member
|Name=Alex Mathew
|JobTitle=Student
|Company=-
|Address=Indian Institute of Technology, Bombay
|Country=India
|State=Maharashtra
|City=Mumbai
|Coordinate=19.134385, 72.905793
|LocalChapter=India
|Email=pingalex94@gmail.com
|Phone=(+91)9446756867
|SocialMedia=https://www.linkedin.com/in/alex94/;
|Website=https://alex-mathew.github.io/
|Photo=Alex.jpg
|Languages=English; Malayalam;
|Info=My name is Alex Mathew. I am a Computer Science graduate, pursuing my Master's degree in Geoinformatics Engineering under the Centre of Studies in Resources Engineering, Indian Institute of Technology Bombay, Mumbai, India.
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=No
|Translate=No
|PSC=No
|ExBoard=No
|Charter=No
|Chair=No
|SolKatz=No
|Committer=No
}}
I am working on the project "" for GSoC 2019. [ ]

User:Alex-mathew

2020-05-19T19:49:40Z

Wiki-Alex-mathew: Blanked the page

File:Alex.jpg

2020-05-19T19:27:58Z

Wiki-Alex-mathew:

Google Summer of Code 2020 Accepted

2020-05-19T18:14:28Z

Wiki-Alex-mathew: /* Accepted Proposals */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] <font size="+3"> @ </font>
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

* Back to the main OSGeo [[Google Summer of Code 2020]] @ OSGeo wiki page.

== Accepted Proposals ==

This year OSGeo accepted 10 students working on the following projects:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;"
|'''Project Logo'''
|'''Community'''
|'''Project'''
|'''Student'''
|'''1st mentor'''
|'''2nd mentor'''
|'''Other Mentors'''
|'''Wiki page'''
|'''Repository'''
|-
|[[Image:logo-qgis.png|40px|center]]
|QGIS
|Improving QGIS 3D
|[[User:Belgacem_nedjima|Belgacem Nedjima]]
|[[User:MartinDobias|Martin Dobias]]
|[[User:Zilolv|Peter Petrik]]
|
|https://wiki.osgeo.org/wiki/Improving_qgis_3d
|https://github.com/NEDJIMAbelgacem/QGIS
|-
|-
|[[Image:logo-grass.png|40px|center]]
|GRASS GIS
|<Fill Details Here>
|Linda Kladivova
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|-
|-
|[[Image:Mapmint-logo-small.png|40px|center]]
|MapMint
|Enhancing ARScale and CloudAnchor support to the MapMint4ME Android Application
|Aditi Sawant
|Gérald Fenoy
|Rajat Shinde
|
|https://wiki.osgeo.org/wiki/Enhancing_ARScale_and_CloudAnchor_support_to_the_MapMint4ME_Android_Application#Idea
|https://github.com/aditis1204/MapMint4ME_shapes
|-
|-
|[[Image:logo-gvSIG.png|40px|center]]
|gvSIG
|<Fill Details Here>
|Giani Carlevaro
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|-
|-
|[[Image:logo-gvSIG.png|40px|center]]
|gvSIG
|New rules for the Topology Framework in gvSIG Desktop
|José Olivas
|Oscar Martinez
|Mario Carrera
|jjdelcerror
|https://github.com/jolicar/GSoC2020/wiki/GSoC2020-New-rules-for-the-Topology-Framework-in-gvSIG-Desktop
|https://github.com/jolicar/GSoC2020
|-
|-
|[[Image:Pgrouting-logo.png|40px|center]]
|pgRouting
|Depth First Search and Sequential Vertex Coloring for pgRouting
|Ashish Kumar
|Daniel Kastl
|Cayetano Benavent
|
|https://github.com/pgRouting/pgrouting/wiki/GSoC-2020-Depth-First-Search-and-Sequential-Vertex-Coloring
|https://github.com/krashish8/GSoC-pgRouting
|-
|-
|[[Image:Pgrouting-logo.png|40px|center]]
|pgRouting
|Implementation of Edge Contraction Technique in pgRouting
|Himanshu Raj
|Vicky Vergara
|Daniel Kastl
|
|https://github.com/pgRouting/pgrouting/wiki/GSoC-2020-Implementation-of-Edge-Contraction-Technique-in-pgRouting
|https://github.com/pgRouting/GSoC-pgRouting/tree/edgeContract
|-
|-
|[[Image:Pgrouting-logo.png|40px|center]]
|pgRouting
|Lengauer Tarjan dominator tree and Two graphs common Spanning Trees for pgRouting
|Prakash Tiwari
|Vicky Vergara
|Aasheesh Tiwari
|<Fill Details Here>
|https://github.com/pgRouting/pgrouting/wiki/GSoC-2020-Lengauer-Tarjan-dominator-tree-and-Two-graphs-common-Spanning-Trees
|https://github.com/prakashupes/GSoC-pgRouting
|-
|-
|[[Image:Pygeoapi-logo.png|100px|center]]
|pygeoapi
|Data Transaction implementation on pygeoapi
|Alex Mathew
|Jorge de Jesus
|Francesco Bartoli
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|-
|-
|[[Image:Pygeoapi-logo.png|100px|center]]
|pygeoapi
|<Fill Details Here>
|Farheen Bano
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|<Fill Details Here>
|-
|}

[[Category:Google Summer of Code]]