Open edwardchalstrey1 opened 2 months ago
@edwardchalstrey1 I updated this user story with some details -- make sure it reflects the original issue!
Possibly: Store the spatial data in the linked past format which may help with this: https://github.com/LinkedPasts/linked-places-format
It's an open question over whether this should be handled on the Seshat side or the Cliopatria side, but it could be both. Perhaps the key thing here is to initially have a proxy measure such as year and to visualise it, then to allow for the measure itself to be an editable value
One idea: % coded of variables
We can follow a similar approach (and disclaimers) as was done here: https://github.com/aourednik/historical-basemaps?tab=readme-ov-file#conceptual-limitations-and-disputed-territories
For now, we probably won't want to pursue this feature, since it's too much work for Seshat RAs to suggest confidence scores for all of the shapes in the dataset, and the proxy score based on the date is not good.
If we ever do come back to this issue, another way of visualising different uncertainty levels from blur could be to play around with different border colours and thickness for the polygons
Role
As a researcher,
Desired Feature
I want to be able to see an uncertainty measure for polity borders,
Benefit
So that I can avoid interpreting polity shape boundaries as hard historical borders and understand the historical data more accurately.
Acceptance Criteria
GIVEN the VideoShapefile table contains uncertainty measures WHEN a researcher views the world map and polity maps THEN the uncertainty should be visually represented using varying line styles, shades, or colours that indicate different levels of uncertainty.
GIVEN the presence of disputed borders WHEN a researcher views these borders on the maps THEN disputed borders should be visually distinguished using visual cues such as dashed lines or different colours to indicate regions under dispute.
GIVEN the new visual features for uncertainty and disputed borders WHEN a researcher interacts with the maps THEN the maps should provide tooltips or legends explaining the visual cues (e.g., what different line styles or colours represent).
GIVEN the addition of uncertainty and disputed borders information WHEN the data is displayed THEN it should be accurate, up-to-date, and reflect the latest historical research.
GIVEN the enhanced visual representation WHEN a researcher uses the feature THEN the maps should load efficiently without performance degradation, ensuring a smooth user experience.
Dependencies
Technical Notes
VideoShapefile
table to store the uncertainty measure.Definition of Done
Progress
Started working on this in #43
Remaining TODOs: