You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
Mobile app makes API call
FTB-api makes API call to NGP-VAN
FTB-api saves/updates data from NGP-VAN in it's own database
FTB-api returns objects from it's own database
OR
Mobile app makes API call
FTB-api makes API call to NGP-VAN
FTB-api maps that data into proper fields for its models, but doesn't create save/update anything
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?
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.
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.
The text was updated successfully, but these errors were encountered: