spatialdev / osmquality-web Goto Github PK

We would like to update the data processing page with the data slicing process as well as the new input enhancement.

• Two slices from OSM full history
• Fully capturing the city boundaries
• MQM processing by city boundaries

Legend colors and transparency need to be updated. The colors are: yellow #ffffb2, orange #fd8d3c, and red #bd0026. Transparency in images is set at 38% (0% on this scale means totally opaque or full color).

Needs to have an image of Madison

In order to make the data render better, it would be nice to have more breaks through data.

Can we try this: ((1/score) - 0.1)/0.0133

This will normalize the scores. The highest score should be around 93 and the lowest around 8.

Need to update the data processing as well as scoring in methodology

For Pixley, should be: "This city was named after Portland, Maine (sad) and suffers from a serious inferiority complex with Seattle."

Review Methodology Page and update other fields as needed

Create a check-box on the map. When clicking the checkout, the map will render census data with different score/values.

Update data.js for RI using Providence instead

Suggesting we need to show our "formula" even if it is in pseudo form in the methodology page.

When zooming into a certain level on the data in the slippy tile, provide the option to open in ID editor by the center point of lat/long.

Nice to have - If possible, keep the zoom level as the slippy tile.

Road Network/Geometry
BuildingRoadIntersectionCheck
EdgeCrossingEdgeCheck
RoundaboutValenceCheck
OverlappingEdgeCheck
SnakeRoadCheck

Road Tag
InvalidAccessTagCheck
SignPostCheck
SnakeRoadCheck
StreetNameIntegersOnlyCheck
UnusualLayerTagCheck
InvalidLanesTagCheck
InvalidMiniRoundaboutCheck

Road Relation - Same

Roundabout Checks -> Delete

We should create a initial beta release so we can version the data used for the ranking. This will allow us to easily compare year-to-year (or sooner) results in the future

Please see CitySatsCard.js for more detail

1. Repurpose 'Total City Area (KM2)'

• Link:

  osmquality-web/src/components/CityStatsCard.js

  Line 60 in 138eece

  <GridListTile key={data.totalArea} cols={1} style={{ height: '100px' }} classes={{

• Action:
  -- change the totalArea into 'OSM Roads'
  -- fetching data.js 'totalRoads' fields

2. Repurpose 'Atlas Check flags'

• Link:

  osmquality-web/src/components/CityStatsCard.js

  Line 5 in 138eece

  import GridList from '@material-ui/core/GridList';

• Actions:
  -- replace the area of 'Atlas Check flags' into 'Trending'
  -- remove the numbers and icons
  -- replace with the three trending icons from the react library
  -- fetching data.js 'trending' field, with flat/up/down.

If the percentage of a feature is > 0 but < 1 we want to display "< 1%" instead of 0 in the UI

Received feedback that it would be a good idea to add the ranking value to the UI.

Investigate if we can just populate the data from the .csv into data.js easily.

Also, the data.js do not have to order by ranking but can be more flexible.

Would like to replace the current map from image (static) to slippy map. This issue/task would like to re-build the same space into the slippy map that serves layers.

Base map - Mapbox grey style
Rendering layers - Geojsons (city boundary as outline + MQM layers)

We would like to re-visit fun fact once we have time.

using Providence instead of the entire state of Rhode Island

The formula is too big for the desktop version. ?

The Map can be zoom as detail as possible (zoom level 14-ish) but should be fixed the zoom out by the MQM boundary. The map should center by the center point of the city boundary

Round to whole number for City area and reduce Grid Cell size to one decimal place.

Madison and Wilmington are missing for big images. Philadelphia, madison and wilmington for thumbnails

Seeking for the new way (or keep using the pie chart) to show different categories between Road network/geometry, Road Tag, and Road Relations.

switching the orders of the check type names on the right of the piechart to be ‘Road Connections’, ‘Road Tags’, ‘Road Relations’, and ‘Roundabouts’.

Is there a way to make the piechart a little smaller so the texts in the legend are not wrapped? i.e 'Map Errors by Type' and 'Road Connections' can stay in one line respectively.

The grid visualization for San Francisco leaks outside of the city boundary

https://osmquality.io/city/San%20FranciscoCA

Put commas in numbers greater than 1,000.

Making some adjustments to incorporate 2018 to 2019, need a trending array and the changes in numbers, more design ideas needed.

Changes will be involved more in the city ranking page as well as each city page

Delete the section due to the new MQM is not creating these metrics for now

Needs to have an image of Wilmington

Make responsive design smooth!

Here is the mark-up for the format/field/values:

      'key':49,
      'cityName':'Anchorage',
      'state':'AK',
      'ranking':8,
      'flags':228,
      'features':366,
      'totalArea':846.96, --> Deleted
      'gridSize':6.62,
      'totalRoads': 5420, --> Add 
      'mapImage':'images/SOTM-10-02-18-images/UAK-300.jpeg', --> Deleted
      'headerImage':'images/headerImages/AK_Anchorage_AK.jpg',
      'thumbnail':'images/thumbnails_cities/AK_Anchorage_AK.jpg',
      'swLong':100, --> Add
      'swLat':25,   --> Add
      'neLong': 102, --> Add
      'neLat': 27,  --> Add 
      'roadConnections':0.69, --> Rename into roadGeometry
      'roadRelation':0.0,  --> Deleted
      'roadTag':0.3, --> Rename into roadAttributes 
      'roundabout':0.004366812, --> Delete 
      'score':0.01034,
      'score_2018':0.01027, --> Add to do calculation to show the proper trending sign 
      'factName':'Fun Geography Fact',
      'fact':'This city is nearly equidistant to New York City, Tokyo and Frankfurt(Germany), which makes it a major international cargo hub.'
   },```