Add date range to data.json

[dcjohnson24]

Description

Checklist

• I am requesting to merge into the dev branch
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

Screenshots

Before	After

Fixes #97

[netlify]

✅ Deploy Preview for creative-quokka-61f1f5 ready!

Name	Link
🔨 Latest commit	cad1fd1
🔍 Latest deploy log	https://app.netlify.com/sites/creative-quokka-61f1f5/deploys/64c98732423ae30008b5422c
😎 Deploy Preview	https://deploy-preview-98--creative-quokka-61f1f5.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for sprightly-muffin-751ffc ready!

Name	Link
🔨 Latest commit	cad1fd1
🔍 Latest deploy log	https://app.netlify.com/sites/sprightly-muffin-751ffc/deploys/64c987326a5e160008b1bb52
😎 Deploy Preview	https://deploy-preview-98--sprightly-muffin-751ffc.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[hkier]

This PR will adversely impact the changes I am working on for Issue #66 which are being worked upon in branch Decouple-data-part-1. In fact, it may actually be easier to decouple the data first and then implement this change. No matter how we do this, the changes will need to be coordinated.

[hkier]

This filename name is a PITA. It will be difficult to type with both _ and - in the name. It also is visually tough to decipher. Perhaps it should be renamed something like, data-20220520-20230702. json

[lauriemerrell]

I wonder if it might be easier to add some kind of date labeling within data.json itself, for example, adding an updated timestamp within a metadata tag in the file, or as an attribute on each row?

[hkier]

In light of Laurie's comments, I've realized putting the date in the file name itself will force us to update the code every time the file is update with a new date range. This is the opposite of our end goal to decouple the data from the code. As it stands now, I would have to vote against this solution. The date range must be in the file data itself. It can either be on each record or a different element within the data structure. [date1, date2, routedata]

[dcjohnson24]

Thanks for the comments. I'll remove the date from the filename and add another field to data.json with the start and end date.

[hkier]

Is there an associated backend update which needs to be merged before this PR is merged? How is the date information being populated in the data.json file?

There are still unanswered questions about this change.

[dcjohnson24]

There isn't a backend update yet, but I'm not sure it would affect this PR.
The date information would be taken from the beginning and end dates of the DataFrame storing the latest trip ratio information and saved to data.json, which is then passed to the frontend.

[lauriemerrell]

This feature got added elsewhere