Project Plan

[abhineet97]

This is my project plan. Each section below represents a Milestone/Deliverable. Under each section is a list of tasks that must be completed for the milestone/deliverable to be considered achieved/delivered.

This is a living document and hence will be updated continuously as the project goes along. The list of changes can be viewed using the "edited" drop-down menu that's available above.

Community Bonding (May 4 - June 1)

• [x] Study the existing internal tool and understand its working.
• [x] Identify elements from the internal tool that can be reused.
• [x] Understand how to use spatial data in the browser.
• [x] Evaluate different frameworks and select the best one.
• [x] Learn more about the selected frameworks.
• [x] Setup coding environment (code editor, linting and styling tools, Python, etc)

Terracotta Back-End (June 1 - July 3)

• [x] Setup the code repository, ensuring that it conforms with moja global's standards.
• [x] Add Terracotta and add associated documentation for setting up development environment.
• [x] Create an ingestion script that loads GCBM data into Terracotta.
• [x] Implement a command line interface for the tool.
• [x] Add tests for checking the implementation of the above features.
• [x] Test and verify the integration (using Terracotta's inbuilt exploration interface).

Dash Integration (July 3 - July 31)

• [x] Pitch a plan for describing how Dash integration would work.
• [x] Implement overlaying raster files onto Leaflet.js Maps.
• [x] Identify the different controls that can be used for interacting with data.
• [x] Implement the interaction controls.
• [x] Setup continuous integration.

Final Touches (August 1 - August 24)

• [x] Test tool using different data sets and then fix any encountered bugs.
• [x] Identify potential features and enhancements for post-GSoC development.
• [x] Dockerize the environment to aid easy installation and development.
• [x] Update documentation and add installation instructions. ~Publish tool on PyPI and then setup continuous deployment.~ (see #31 for an explanation of why this was not possible)

A buffer of 2 weeks has been taken to account for any unforeseeable absence on my end (about which I'll inform as early as possible).

[gmajan]

Abhineet, This is a good beginning but I hope you agree it needs work. Please discuss with @kaskou and you need to connect to @mfellows to get more details on what needs doing. It is very important to get clear deliverables so we can celebrate when you reach your milestones. Good luck!

[abhineet97]

Thank you so much for your feedback @gmajan.

Yes, I agree that it need works. I'll keep on discussing with my mentors and will clarify the plan with the deliverables ASAP.

[abhineet97]

Hello, @kaskou and @gmajan

I've updated the project plan and have now highlighted the deliverables more clearly. Please, let me know how I can improve it furture.

[gmajan]

Hi Abhineet, Looks good. I think you will be able to do more in August but let's revise that when we get to that point. Well done. Guy

[kaskou]

Hi abhineet, Good work and Looks good to me. But can you also add

• Database data to view graphically as deliverable. Will let you know soon with samples, what needed and relationships of the data.

Thanks

[kaskou]

Hi @abhineet97 , can you please add this as well to the plan

• Installation instructions

• Scripts [Bash scripts, Dockerizing] to help get everything up and running as easily as possible on a new machine

Thanks