xordspar0 / data61-capstone-2016 Goto Github PK

Social media posts should be visualized differently from reviews, etc.

Due at the end of the week of March 7.

First we can use bounding boxes, but eventually we should additionally use geometry to calculate the distance from each point to the route. Points more than a certain distance from the displayed route should not be displayed.

A route can be rated based on:

• time
• distance
• convenience
• toll price
• ratings of tourist attractions
• etc.

We need to find out how to represent each of these best. Which ones should be the same/similar/different?

This panel should have a list of map features with check boxes next to each one. This allows the user to show or hide items.

It should get the coordinates, title, and text of each social media item. They should be represented by points on the map. The function should call a KMLExporter method to add the points to the KML document.

Our demo should ideally:

1. be able to export routes as KML.
2. style routes based on a predefined rating of "good" or "bad".
3. show mockup tweets in the placemark of some cities (click on the pin on the map to bring up the title, Tweet text, and image URL).
4. get mockup tweet data and route rating from a CSV file that we make.

They are hard to figure out. I'm going to just merge the functionality into one button.

The button in our app should send the user straight to NationalMap instead of giving a KML file to download.

If you look at the resulting KML file after adding the Flickr photos, only 1 or 2 of the 250 or so photos have latitude and longitude coordinates. I think there is a problem with the way I am doing the location API calls in dataSources.js. It might need to be paralellized somehow.

The Google API for importing KML into a map only supports actual files that are accessible from the Web. Our code currently just makes the KML file in memory in the user's browser. We might have to write some server side code that could generate the KML file and serve it to Google.

Now that we won't be implementing our interface directly in NationalMap, we need our visualizations and styles to show up in our app. We will still have an export button that will allow the user to download a KML file that works with NationalMap and other map services.

For example, put the weekly reports all on one page.

We are going to put the project specification, weekly report, and other project documents here on Github. We should put a link to the Github wiki on our Trac page so that the professor and TAs can find it. I asked Dr. Knudson and this is what he recommended.

There should be a KML module for d3, otherwise we'll have to find another library or write plain strings to a file.

This will allow us to import routes generated by any API (Google or Data61) into a variety of map services, including National Map.

The plan is to use the native DOM of Javascript to write a KML file that can be saved to disk and uploaded to the map service.

The functionality behind the panel isn't implemented yet. The check boxes should be able to toggle the visibility of certain elements in the map.

Rachelle and Sean are working on this and hope to have it done by Thursday. We believe the JSON from Flickr containing the photo data is not running through the loop to obtain the photo URL. The loop also adds the marker that will contain the photo.

We could use a downloaded data set from data.gov, data.gov.au, the sample data from Iman's project, etc.

This is the first step to getting data from social media.

Either hide the link until it's ready, or make the delay time more dynamic (currently it is hard-coded to wait a few seconds to make sure the API calls come back).

Probably both of those would be good things to do.