Releases: RioBus/data-provider
Releases · RioBus/data-provider
4.1.1
26 Sep 17:34
Compare
Sorry, something went wrong.
No results found
Add an environment flag RIOBUS_DISABLE_DIRECTION to disable the direction algorithm, temporarily removing the OSRM dependency.
Fix a bug that caused the process to freeze
Fix a bug that didn't set a timeout for the HTTP requests
4.1.0
10 Mar 02:33
Compare
Sorry, something went wrong.
No results found
The direction detection algorithm was changed, using another approach which identifies the streets through the bus goes to use it as a main information to discover where is it coming from and where is it going to.
4.0.1
27 Nov 20:18
Compare
Sorry, something went wrong.
No results found
4.0.0
27 Nov 18:41
Compare
Sorry, something went wrong.
No results found
Full refactoring: going back to default Node.js
Updating base platform to node v5
Using generators to deal with async and promises
3.4.1
20 Oct 01:39
Compare
Sorry, something went wrong.
No results found
Hotfix to sense algorithm
3.4.0
15 Oct 01:31
Compare
Sorry, something went wrong.
No results found
Changing sense prediction algorithm
Removed gulp dependency
Added explicit dependency to ts-node module to run TypeScript source natively
Small fixes
3.3.0
22 Sep 01:50
Compare
Sorry, something went wrong.
No results found
Moving database configuration to environment variables
Adding a keyword field to Itinerary's collection documents for text search
Refactoring
Minor fixes
3.2.0
04 Sep 15:08
Compare
Sorry, something went wrong.
No results found
Fixing insertion to keep the outdated documents instead of removing all of them
Updating Docker environment configuration to io.js v3. Reason: preparing to Node v4
Many more unit tests
3.1.1
20 Aug 00:01
Compare
Sorry, something went wrong.
No results found
Turning MongoDB collection remove operation synchronous
Fixing insertion to the search collection
3.1.0
17 Aug 19:50
Compare
Sorry, something went wrong.
No results found
Batch save the bus data into the collections
Disable order and geolocation indexes due to memory issue