Add support for a data vintage date
- Dominant language
- No language data
- Stars
- 27
- Forks
- 20
- Avg merge
- 22h 33m
- Merged PRs (30d)
- 1
Description
Having a data vintage date that is shown in api responses will allow users to know the vintage of the data the current geocoder/router is using.
Graeme suggests the data prep process generate an additional file with vintage data information in it which will be read in by geocoder and route planner nodes on startup.
Options
1. Single or multiple vintage dates:
- data_vintage
- data_vintage + dra_vintage, addressbc_vintage, bca_vintage, opendata_vintage, statscanrnf_vintage
2. How is vintage represented in API?
- as new HTTP headers of existing resources
- in response metadata of existing resources with code version and execution time, etc.
- in a response to a new dataVintage resource request
Contributor guide
Assessment
This issue has not been assessed yet.