Need better and more icons

alpha-beta-soup commented 9 years ago

The icons used at present I really consider placeholders, because:

They're inconsistent in style
They're inconsistent in size
The injury ones should (IMO) be colour coded to match the colours we use to signify injury type with the circle markers
Some of them are just shit

The icons themselves are stored in ./icons/ (weather and lighting), ./icons/injuries/ (injuries) and .icons/transport/ (vehicle types).

If the icons are changed or new ones are added, this'll need to be reflected in nzta2geojson.py in nztacrash.__vehicle_icons__(), nztacrash.get_injury_icons(), and nztacrash.weatherIcon() by specifying the new filenames in the appropriate places. This should be reasonably straightforward once new icons are prepared.

I think icons could also be used to represent lighting conditions better, such as through the use of an icon to indicate the presence (or absence) and (mal-)function of street lights at an accident location.

parnelandr commented 9 years ago

I can make this happen. Give me a list of them.

alpha-beta-soup commented 9 years ago

I'll leave it up to you to make the changes you think we need. You can browse all the current icons in the ./icons/ directory. You can replace as many or as few as you want. To see what ones get used, just search for .png in nzta2geojson.py and you will see them.

alpha-beta-soup commented 9 years ago

Good progress on this

alpha-beta-soup commented 9 years ago

I'm going to run the icons past my (designer) girlfriend. She's not really into iconography but she'll probably have some good tips and knows her way around the software. Once I've done that I'll consider this closed; we've made great progress on this.

parnelandr commented 9 years ago

pretty happy with these now. before finishing happy to do a final revision.

alpha-beta-soup commented 9 years ago

We could also consider icons for the following parameters that we currently ignore:

Movement code

Identifies the principal movements of the vehicle(s) involved. Probably quite tricky to show, but the PDF includes a chart showing these as icons already. They're pretty expressive, summarising a lot of information concisely. I'd be keen to trial these.

Objects struck

The first three objects struck (including the same object more than once if multiple parties hit it). In cases with a single crash party, this often explains why there was an injury.

Driven or accompanied animals, i.e. under control.
Bridge abutment, handrail or approach, includes tunnels.
Upright cliff or bank, retaining walls.
Debris, boulder or object dropped from vehicle.
Over edge of bank.
Fence, letterbox, hoarding etc.
House or building.
Traffic island or median strip.
Public furniture, e.g. phone boxes, bus shelters, signal controllers, etc.
Kerb, when directly contributing to incident.
Landslide, washout or floodwater.
Parked motor vehicle.
Train.
Utility pole, includes lighting columns.
Broken down vehicle, workmen’s vehicle, taxis picking up, etc.
Roadwork signs or drums, holes and excavations, etc.
Traffic signs or signal bollards.
Trees, shrubbery of a substantial nature.
Ditch.
Wild animal, strays, or out of control animals.
Other.
Objects thrown at or dropped onto vehicles.
Into water, river or sea.

Curve

~~Probably quite easy to show.~~

~~Straight~~
~~Easy curve~~
~~Moderate curve~~
~~Severe curve~~

Wetness

This is distinct from the weather, but would often repeat the information.

Wet
Dry
Ice or snow

Light

I think this is an important one. Split by natural and artificial.

Natural

Bright sun
Overcast
Twilight
Dark

Artificial

Street lights on
Street lights off
No street lights present

Control

~~Traffic controls at the crash site. These could actually make good filters; I'd be interested in seeing stop sign accidents, given how often I see people roll through them.~~

~~Traffic signals~~
~~Stop signs~~
~~Give way sign~~
~~School patrol or warden~~
~~None~~

Markings

What kind of road markings are present at the crash location (only one is recorded: there is an order or significance). Pedestrian crossing could make a useful filter, IMO.

pedestrian crossing
raised island
painted island
no passing line
centre line
none

~~## Pedestrian age~~

Tricky, because it records the oldest pedestrian injured, unless there is a pedestrian aged under 20, in which case the age of the youngest injured pedestrian is recorded. There could be a "child pedestrian" icon, perhaps.

~~## Cyclist age~~

~~Same as the pedestrian age.~~

parnelandr commented 9 years ago

OK I'm going to add these in.

1 Curves 2 Light conditions 3 Control 4 Wetness (will figure out what to do for this)

The pedestrian and cyclist age something could be done. Like a child walking/cycling.

Why would a road marking be included? just because it is close like the rule for junctions?

The objects struck it might be worth having a think what would be the most interesting. If we can filter by things like train/wild animals/things thrown at vehicle/into river or sea, they would be most useful to Police/NZTA/interested orgs.

The movement could be an idea but maybe an icon for each row rather than 72 separate or we could do selected. What do you think?

alpha-beta-soup commented 9 years ago

Objects struck: I think we could have a catch-all icon (was anything hit?), and then include a line (well, up to three lines) in the explanation text. There could be special icons that trigger in place of the default, too. I'm thinking those that have pretty special significance: train; utility pole (risk of electrocution); ...

Wow, did not realise there were 72 of those movement icons. It looks like 30 until I counted them. I'm OK working on them slowly. I'd probably only revise a few of them, so it's basically sketching.

parnelandr commented 9 years ago

So you are keen for all objects struck? I'll do this secondary to trying to find a good solution to query issue

alpha-beta-soup commented 9 years ago

Yeah, this shouldn't be a priority. I'm keen for objects struck; and I'm willing to sketch them up.

parnelandr commented 9 years ago

All good. Working on curves at the moment. Low fruit etc

alpha-beta-soup commented 9 years ago

Curves done and merged.

parnelandr commented 9 years ago

Sweet thanks

Andrew Parnell

Postgraduate GIS Student - Victoria University of Wellington LinkedIn Profile http://www.linkedin.com/in/ajparnell

On 28 December 2014 at 12:06, Richard Law notifications@github.com wrote:

Curves done and merged.

— Reply to this email directly or view it on GitHub https://github.com/alpha-beta-soup/national-crash-statistics/issues/1#issuecomment-68192986 .

alpha-beta-soup commented 9 years ago

Just did the "control" section, and changed some existing ones that easily mapped to real road signs.

alpha-beta-soup commented 9 years ago

Added an icon for crashes where a child has been injured. The definition of "child" is a parameter that can be adjusted in the Python script (it is currently 15 years and under). I have treated child injuries on foot and on bike the same, although they can be separated.

alpha-beta-soup commented 8 years ago

For some reason I just added phases of the moon icons

alpha-beta-soup / national-crash-statistics