split repo into pre-processing function and routing functions

[carocad]

Currently this repo contains functions for pre-processing of curves/routes, parsing osm files and routing algorithms.

If we want to have an auto-scalable api (with something like lambda-functions in AWS or firebase functions) we need to split this repo into two or more repos that can be used separatedly.

The pre-processing functions would be run on demand whenever we get new input and killed afterwards. Whereas the routing functions should be kept alive to keep getting the last updates of the road-network.

My proposal (of the top of my head) is:

• 1 repo for curves estimations
• 1 repo for OSM files pre-processing
• 1 repo for graph routing algorithms (possibly including live updates in the future but doesnt need to)

[mehdisadeghi]

I have no strong opinion on this at the moment. Please proceed and create those repos then I can send PRs for them and split the code. I guess that you will stick to the backend.functions.LIB convention.

[carocad]

@mehdisadeghi you should be able to create and delete repositories by yourself. Feel free to open an issue if that is not the case ;)

As for the convention, yes I find it quite intuitive to organize the components of our organization into a structure that makes it easier for people to just jump in and start contributing. This is of course still a work in progress since many repos require refactoring but that is another topic :D

[mehdisadeghi]

@carocad I didn't know that! OK, I'll make some repos! :)