Open alpha-beta-soup opened 9 years ago
I can make this happen. Give me a list of them.
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.
Good progress on this
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.
pretty happy with these now. before finishing happy to do a final revision.
We could also consider icons for the following parameters that we currently ignore:
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.
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.
Probably quite easy to show.
This is distinct from the weather, but would often repeat the information.
I think this is an important one. Split by natural and artificial.
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.
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 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.
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?
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.
So you are keen for all objects struck? I'll do this secondary to trying to find a good solution to query issue
Yeah, this shouldn't be a priority. I'm keen for objects struck; and I'm willing to sketch them up.
All good. Working on curves at the moment. Low fruit etc
Curves done and merged.
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 .
Just did the "control" section, and changed some existing ones that easily mapped to real road signs.
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.
For some reason I just added phases of the moon icons
The icons used at present I really consider placeholders, because:
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
innztacrash.__vehicle_icons__()
,nztacrash.get_injury_icons()
, andnztacrash.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.