Issue was with the format of the nusstops.json file: the name of the latitude and longitude properties and data type did not match what the code in travel.go expected, so latitue and longitude of all the bus stops was (0,0).
Motivation and Context
Closes #49
How Has This Been Tested?
Tried /nusbus by location with a few different places around NUS.
Printed the latitude and longitude of all the bus stops to the console while testing and verified they're no longer zero.
Screenshots (if appropriate):
Types of changes
[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Description
Issue was with the format of the nusstops.json file: the name of the latitude and longitude properties and data type did not match what the code in travel.go expected, so latitue and longitude of all the bus stops was (0,0).
Motivation and Context
Closes #49
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes