ckinateder / ufo-visualization Goto Github PK

Provide a set of 'color by' options for the points on the map, which the user can activate through user interface elements:

• #20
• #19
• #18
• #17
• design explanation for documentation: describe the colors you selected for these options and why you selected them, referencing whether the data is nominal, ordinal, quantitative, etc. and whether the color scheme is monochromatic, diverging, or categorical.
• #16

The layout really needs work.
This includes:

• Map
• Timeline (sightings over time)
• Shape trends bar chart
• Year cycles histogram
• Time of day histogram
• Encounter length histogram
• Word cloud

There also must be a place that shows

• Controls (color by, reset, etc.)
• Filters applied
• Details of the current color scale

If there is a way to get this all on one page, that would be great. We don't want to have to scroll away from the map.

We need more than just "steelblue" for the colors

for the project

Add the ability to brush the map, to select points within a region on the map. This may not work with the default d3 brush and you may have to create a custom interaction- creating a custom selection rect, or capturing mouse over interactions while also holding a control key, to handle brushing data points in the map.
Create a set of design sketches for your approach.
Describe how you realized this design in your implementation.

Don't set it in the CSS

Choose one of the following additions:
Text descriptions: A visualization designed by your team showing the unstructured text description of the encounters. The goal is to summarize the body of these descriptions, to give the user an impression of these encounters as a whole. You will likely need to integrate some natural language processing techniques to create these views- remove stop words, stemming. One approach would be to find frequently used words, and create a text visualization (such as a word cloud).
As with the other charts, this should update when the user makes brushing selections
Sketch your approach, including encodings and interactions, and submit these sketches with your documentation.
Interactive search for words or phrases in the unstructured text descriptions of the encounters. How often did people report 'flashing' or 'bright' or 'airplane' in their report? Let the user search for a word in the description and highlight incidents on the map or in other views that include this word or phrase. Note- no need for a database, you can use a simple table and javascript string functions to find matches.

• #9
• #11
• #12
• #13

I want to make things look smoother.

Need to factor in padding for axis labels, etc. Use a padding variable.

Will need global vars

Add a button that allows the user to toggle between different map background- such as from aerial images to one that shows roads/boundaries/etc. Find backgrounds here:
https://leaflet-extras.github.io/leaflet-providers/preview/

Visualize the filter somewhere

When hovering over a point, provide details-on-demand about the sighting. This should include the date and time of the sighting, the shape of the UFO, the description of the encounter, and other information you wish to show.

Note- some entries may not have GPS coordinates. Don't eliminate these items altogether, because they are part of the dataset and should be featured in the other charts. You could indicate somewhere within the visualization how many sightings are not mapped.

Text descriptions:
A visualization designed by your team showing the unstructured text description of the encounters. The goal is to summarize the body of these descriptions, to give the user an impression of these encounters as a whole. You will likely need to integrate some natural language processing techniques to create these views- remove stop words, stemming. One approach would be to find frequently used words, and create a text visualization (such as a word cloud).
As with the other charts, this should update when the user makes brushing selections
Sketch your approach, including encodings and interactions, and submit these sketches with your documentation.

Details on demand: When hovering over the timeline, provide a tooltip to give the user more information about the timeframe they are hovering over.