-
Notifications
You must be signed in to change notification settings - Fork 3
GSoC 2023 Implement SensorThings API standard in istSOS Filippo Finke
- Community Bonding Period May 4 - May 28
- Coding Period - First Week Report May 29 - June 4
- Coding Period - Second Week Report June 5 - June 11
- Coding Period - Third Week Report June 12 - June 18
- Coding Period - Fourth Week Report June 19 - June 25
- Coding Period - Fifth Week Report June 25 - Jul 2
- Coding Period ‐ Sixth Week Report Jul 3 ‐ Jul 9
- Coding Period ‐ Seventh Week Report Jul 10 ‐ Jul 16
- Coding Period ‐ Eighth Week Report Jul 17 ‐ Jul 23
- Coding Period ‐ Ninth Week Report Jul 24 ‐ Jul 30
- Coding Period ‐ Tenth Week Report Jul 31 ‐ Aug 6
- Coding Period - Eleventh Week Report Aug 7 - Aug 13
- Coding Period ‐ Twelfth Week Report Aug 14 ‐ Aug 20
- Final Report
- Name and surname: Filippo Finke
- Nickname: filippofinke
- Country: Switzerland, Ticino
- Email: [email protected]
- Personal blog: https://blog.filippofinke.ch
- LinkedIn: https://www.linkedin.com/in/filippofinke/
- GitHub: https://github.com/filippofinke
- Website: https://filippofinke.ch
Support basic SensorThings API (STA) for istSOS
istSOS currently supports the Sensor Observation Service (SOS) standard, but to enhance its interoperability, we propose implementing some of the basic APIs from the SensorThings API (STA) in a prototype version. This project aims to test new technologies that could be adopted in a future revised version of istSOS.
Currently, istSOS only supports the SOS standard, and there is no implementation of the STA API.
The project will add support for basic STA API, enabling users to access sensor observations and metadata via RESTful web services. This will improve the interoperability of istSOS with other sensor data management systems and make it easier for users to interact with istSOS.
After the GSoC project is complete, the new STA API implementation can be expanded to support more advanced features and improved documentation. The new technologies and standards that will be tested during the project can also be integrated into a future revised version of istSOS.
The project will deliver a well-tested implementation of the basic STA API.
Research on SensorThings API (STA) and its requirements (1 week) Setup of development environment and required tools (1 week) Familiarization with istSOS codebase (1 week) Communicate with mentors and get feedback (1 weeks)
Implementation of basic STA API endpoints (2 weeks) Implementation of STA API metadata endpoints (1 week)
Testing and debugging of Phase 1 code (1 week) Integration of Phase 1 code into istSOS codebase (2 weeks)
Implementation of STA API filter, orderby, and select options (2 weeks) Testing and debugging of Phase 3 code (1 week)
Implementation of STA API pagination (1 week) Integration of Phase 3 and 4 code into istSOS codebase (2 weeks)
Final testing and debugging of the entire codebase (1 week) Documentation and submission of the project
- Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
Yes, I understand that this is a serious commitment and I am willing to dedicate the time and effort required to complete the project successfully.
- Do you have any known time conflicts during the official coding period?
From June to July I will have exams, so I will not be able to work full-time on the project during this period.
I do not know the exact dates of the exams yet, but I will be able to work on the project during the weekends and evenings.
- What is your School and degree?
I am studying Computer Science at SUPSI (University of Applied Sciences and Arts of Southern Switzerland) in Viganello, and I am currently a second-year Bachelor student.
- Would your application contribute to your ongoing studies/degree? If so, how?
Yes, I believe that this application would contribute significantly to my ongoing studies and degree. By participating in the Google Summer of Code with istSOS, I would gain valuable experience working on a real-world project and collaborating with a professional team. This opportunity would allow me to apply the theoretical knowledge and programming skills I have learned in my studies to a practical setting, helping me to further develop my abilities and understanding of software development. Additionally, the mentorship and guidance provided by the project mentors would provide me with invaluable feedback and support, enhancing my learning experience and helping me to achieve my academic and career goals.
- Computing experience:
I use both macOS and Windows on a daily basis, and I also have experience with Linux, particularly in setting up and managing servers.
I have experience programming with NodeJS, JavaScript, TypeScript HTML, CSS, SQL, Java, Python, Docker, and C/C++ and using Git and GitHub for version control and collaboration on open source projects.
Overall, I am comfortable working with a wide range of tools and technologies, and I am confident in my ability to adapt to new environments quickly.
- GIS experience as a user
I have not used GIS before as a user, but I am eager to learn and have a strong interest in geospatial data and analysis.
- GIS programming and other software programming
While I have not programmed in GIS before, I am proficient in several programming languages and have experience with software development, including contributing to open source projects. I am confident in my ability to learn new programming languages and frameworks quickly and apply my existing skills to GIS programming.
- Briefly mention and link to former open source contributions
I have contributed to multiple open source projects, including Stormkit (https://github.com/stormkit-io/app-stormkit-io) and Filebrowser (https://github.com/filebrowser/filebrowser). In these projects, I worked on frontend development and adding features and bugfixes, respectively. I have also contributed to other repositories for hot fixes and bug fixes. These experiences have given me valuable experience working with codebases developed by others, collaborating with team members, and using version control tools like Git.
- Have you participated to GSoC before?
I have never participated in GSoC before.
- How many times, which year, which project?
N/A
- Have you applied but were not selected? When?
N/A
- Have you submitted/will you submit another proposal for this year's GSoC to a different org? Which one?
No, I am not planning to submit a proposal to different organizations this year.
.