In this post I will explain how PlaneView is set up and works. I will explain how the back-end is set up, how the aircraft classification works, how the front-end is set up, the image storage, and the deployment. Back-end Let's start with the back-end. For the back-end I chose to go with FastAPI , as it provides a simple and fast way to create API endpoints that the front-end can access. Let's look at an example. A user uploads an image of an aircraft. The image is sent to the API endpoint associated with the upload button. The code on the back-end now checks if the uploaded image actually is an image. If it passes the check, inference is run on the image to find the plane type shown in the image. Once that is complete, the image and associated data like the user that uploaded the image, the inference result, time of upload, the image’s unique name, and more are stored in the PostgreSQL database that is running. The image is stored in MinIO object storage . Authentication ...
PlaneView is a page where you can upload images of airplanes and find out which type it is. For example you are at the airport and take a picture of a plane. You can upload the image to PlaneView and find out what type if plane you are looking at. If you create an account you can even see all of the planes you have uploaded in the past. PlaneView is still at the start of the development process. I am working on it alone as a hobby project, so its not always that i have time to work on it. Core functionalities are already implemented and working, like the core concept of uploading and analyzing images, accounts, history page and the ability to lookup the recent flights of the aircraft you have analyzed if you have its registration number. Future Development I have multiple features i want to implement for PlaneView . Right now i am working on improving the classification model so that the page can recognize more aircraft's and the process a...