Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Map between FTB data and VAN Data #127

Open
dedual opened this issue Feb 19, 2016 · 2 comments
Open

Map between FTB data and VAN Data #127

dedual opened this issue Feb 19, 2016 · 2 comments

Comments

@dedual
Copy link

dedual commented Feb 19, 2016

The API must be able to correlate information from VAN and output it correspondingly through Field The Bern so that the different apps can both use them and render them on their maps.

Ex: To be able to query the People API around a specific Lat Long, get current responses and map them to FTB data models.

@kyleschmolze
Copy link

This makes perfect sense, but are we also going to be then storing that information within the Field the Bern database? Or are we simply mapping it? I could see it going one of two ways:

  1. Mobile app makes API call
  2. FTB-api makes API call to NGP-VAN
  3. FTB-api saves/updates data from NGP-VAN in it's own database
  4. FTB-api returns objects from it's own database

OR

  1. Mobile app makes API call
  2. FTB-api makes API call to NGP-VAN
  3. FTB-api maps that data into proper fields for its models, but doesn't create save/update anything
  4. FTB-api renders those objects back to the mobile app

The first option would be faster on subsequent queries, and limit the number of API calls to NGP-VAN, and also not depend on their API as much. The second one doesn't require us to manage too many advanced permissioning within the FTB database, cause we're just passing data through. Thoughts @dedual?

@dedual
Copy link
Author

dedual commented Feb 25, 2016

I'd go with the first option, truth be told. Need to check the Terms and Conditions re: data to see whether that will pose a problem down the line, but go ahead with that first option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants