fkh / map-score Goto Github PK

Eg N/a would apply be for time related questions on maps where there's no time data. Yes still = 1; n/a reduces the total possible score.

and also be open to weighting other criteria that the community cares about.

The thing with having a weight of 1 for every criteria, is that it will mask certain important criteria and it doesn't incentivize compliance with criteria that is harder to achieve.

HTML5Test is quite instructive in how they score and give different weights .

We just built one for Newark to visualize their snowplows during the Nov 26 snowstorm event.

http://data.ci.newark.nj.us/base/maps/snowplows.html

I then did a self-assessment using Map-Score:

Design: 5/6

• sticky-map standards: 1
• pinch & zoom on mobile: 1
• deep links: 1
• comments: 0
• time filter: 1

Data truthiness: 3/5

• different geographic roundups: 0 (N/A?)
• normalized: 0 (N/A?)
• legend: 1
• available as the original location:1 (we even used the https://github.com/BetaNYC/getDataButton)
• time of individual dots: 1

Accessibility: 3/6

• available in all significant language groups: 0
• fall-back for screen-readers: 0
• no plugin: 1
• desktop browsers: 1
• works in IOS, Android, cell, & tablet: 1
• color-blind friendly: 0 (we tried, but according to http://color-brewer2.org, there was no color-blind palette for 12 trucks for qualitative data)

For a total of 11.

I thought I'd score higher. It does bring up some issues:

• what about N/A criteria?
• I still think we need to adjust weights, not just 1 for each criterion
• animation, though not addressed by the score, will impact future accessibility criteria. We think animation for this map was not just gratuitous eye-candy, but was the primary way it communicated snow plow coverage. We even thought of shading the polygons differently based on how much snowplow coverage each neighborhood gets by changing the opacity of each polygon as each snowplow passes through, but then decided not too (animated choropleth). If we did, that would have introduced more accessibility issues.

So this map scores 9/21. Want to try scoring it, @talos @jqnatividad @chriswhong ?

How open is the map data? 1/4 pts

• underlying data is accessible for bulk download yes - 1 pt
• data is accessible in a non-proprietary data format (csv/geojson, not ArcGIS GDB or Shapefile) no
• data powering the map is directly pulled from an open data site via API (ideal) no
• a complete history of all data that ever appeared on the map is kept (even if some data eventually disappears, it is still accessible in the original data source.) no

Design 2 / 6 pts, maybe 3

• conforms to sticky-map standards (click-and-drag pans, double-click zooms, scroll wheel zooms in/out) scroll wheel doesn't zoom, pans instead
• pinch & zoom works on mobile yes - 1 pt
• can functionally jump to addresses or regions via search bar sort of -- can't search for streets, only addresses. And you have to pick the boro first
• provides "deep links" so that map views are shareable from the URL bar no
• comments or other input can be provided to report bad data, and responses are tracked & accountable no
• it is possible to filter any layer with time data by time yes -- the time slider allows you to pick a year

Data truthiness 3/5 pts

• available at different geographic roundups/aggregations (e.g. district) police, community, council -- but no totals displayed so it's hard to make sense of the results. 0 points
• normalized by area in meaningful fashion, taking into account possible statistical hiccups (like a park district with no population) yes, normalized by area but no, not taking Central Park into account in Council Districts. This item probably needs to be split in two.
• legend is labeled yes
• available as the original location dots (e.g. geocoded location of 311 reports) yes, crash locations
• the time of individual dots/locations is reported when available no, no time info given

Accessibility 3/6

• available in all (?) significant local language groups English only
• fall-back for screen readers (?) not sure -- maybe this is a bad question, maps aren't going to work well on screen readers
• works in all modern browsers without a plugin (no Flash or Silverlight) I think so
• works on both iOS and Android, cell & tablet looks ok on iOS
• works on all desktop browsers (Firefox, Chrome, Safari, latest IE) works in Firefox
• color-blind friendly (reds/greens) yes