osoc17/lopeningent_backend

Backend for the #LopenInGent project

lopeningent_backend's Issues

Add water tags to watersportlaan.

It's in the name.

Add documentation

Currently more than 200 items are undocumented, according to clippy.

Ironing out redundancies in the existing algorithm

Incorporating weighting factor into edges

Integrate rating system

Implementing POI into the algorithm

Hackathon: Request Infrastructure for Points of Interest

Trying to implement a API scheme for the Point of Interest algorithm.
I'll add more details to this issue as I go.

Cleaning up the JSON file for the POI's

https://datatank.stad.gent/4/toerisme/visitgentspots

Adapt the route algorithm

Given the new graph datastructure, rework the way the algorithm handles the way it chooses edges through the graph, this will require:

• Rewriting the /route/generate route and interface to easily pass which tags a route needs to have
• Modify the way the map closure inside the routing algorithm calculates the weighting of the tags

Allow multiple routes to show up in the app at the same time

Today, the app shows one route to take or throw away. One of the facebook comments was the request to show multiple routes at the same time so she could pick one.

POI Preprocessing

We need an extensible way to load in json-files with (lat, lon) combination. Find out a way to add this information to the edges.

Make database interactions great again

Add Firebase Authentication

Hackathon: Point of Interest Algorithm

Implementing the Point of Interest Algorithm

Add dangerous roads to the database

Create a database interface

The main focus here is to provide a interface into the PostgreSQL database containing all our preprocessed data. This would more than likely entail:

• Reworking the Graph model
• Reworking the script that constructs the Graph model