Donald Winiecki

Forum Replies Created

Viewing 3 posts - 76 through 78 (of 78 total)
  • Author
    Posts
  • in reply to: Labeling values on cartesian graphs using UEB code #34581
    Donald Winiecki
    Moderator

    Glad to help Susan!

    It looks like the URL to the Guidelines & Standards for Tactile Graphics (GSTG) on BANA's website didn't survive the upload process when I added my previous message. I am including that link again below.

    http://www.brailleauthority.org/tg/

    in reply to: Labeling values on cartesian graphs using UEB code #34578
    Donald Winiecki
    Moderator

    Thanks for the question Susan!

    The following responses reference <i>Guidelines & Standard for Tactile Graphics, 2010</i> (i.e., GSTG). If you're curious, you can find GSTG at the following URL: http://www.brailleauthority.

    First off, GSTG (2010) specifies that we should omit the number sign on Cartesian graphs (see GSTG, Unit 6, pages 6-1 through 6-2, and section 6.6.2.1). No transcriber's note or other accounting is required for this. However, GSTG indicates that if the labels allow for confusion in cases where braille might be interpreted as either a number or alphabetic character, the numeric indicator (dots 3456) should be used to clarify what is meant. That said, since you indicate that the teacher wants an <u>empty</u> Cartesian graph (i.e., a graph without braille labels for what each axis represents) for students' use, there may be no such confusion and a numeric indicator will likely not be necessary anywhere on your TG.

    If you are faced with crowding on the coordinate number lines, GSTG 6.6.2.3 allows us to omit some of the numbers. For example, while including all tick marks from -10 to 10 across the coordinate regions you could choose to omit odd numbers to save space.

    For more space saving, it is also allowable to omit the dot 5 from negative number signs. This follows from the way GSTG correlates information on number lines with the way we should represent the axes on a Cartesian graph -- see GSTG 6.5.1.11 (page 6-21) and the example in GSTG on pages 6-23 through 6-25.

    In general, all of the advice in GSTG 6.6.2 is useful when converting Cartesian graphs to TGs.

    Additionally, it may be important to find out what methods students will be using to plot information into the empty Cartesian graphs you provide. This is because the plotted lines students add should be the most distinctive lines on the graph (GSTG 6.6.2.2). This means that you should choose a method for reproducing your TGs so that whatever method students use to plot data on the Cartesian plane, those lines will be bolder and more distinct than your grid lines and axis lines.

    While we are on the topic of the tactile "vocabulary" of lines on a Cartesian graph, GSTG 6.6.2.2 indicates that the grid lines should be the least distinctive of all lines on the graph, and the axis lines should be tactually distinct from the grid lines. However, as above, the actual data plot lines should be the most distinctive on a completed graph.

    Finally, our resident expert in the use of CorelDraw on the <i>NBA TG Skills Group</i> provides the attached screenshot for setting up and using CorelDraw's "TM Macro" to accomplish the above. Please note that the "TM Macro" in CorelDraw will automatically insert numeric passage indicators and terminators above and below the Cartesian graph, and insert dot-5 before the minus sign on negative numbers -- you will have to remove those features manually after the "TM Macro" in CorelDraw does it's thing.

    Please let us know if this answers your questions!

    Attachments:
    You must be logged in to view attached files.
    in reply to: double number lines #31421
    Donald Winiecki
    Moderator

    I don’t have access to the handbook at present, but I wonder if it is allowable to use the DOT LOCATOR FOR USE and numeric passage indicator and terminator on the lines preceding and following this double number line?

    This would alleviate need for individual numeric indicators at each digit, and save space on each line.

    Doing this would end up saving space overall by avoiding run overs. The result might even be easier to decode.

Viewing 3 posts - 76 through 78 (of 78 total)