Open jackreid opened 3 years ago
I am going to take the approach of having one field per time unit, with a standard naming format that the code will be able to translate into specific time points, this format being NAMEYYMMDD, since that fits the 10 character fieldname limit for shapefiles.
Initial take on a map slider has been added and merge with master. A working example can be seen in Weekly Mobility in the Santiago context. In general here is how it works.
A few things remain to be done:
Different options/questions here:
Controls: Just adding more options to the drop down (potentially organized into sub-dropdowns similar to the temporal graphs) vs. adding a new control method such as a slider to move through time.
Storing Data: Could pre-produce individual shapefiles for each time period (such as month) and have them referenced, could have still have one shapefile with just more fields, could also have the data stored in a csv and the UI assembles them into either a shapefile or directly into the display live. Not sure what is the best approach.