The Get Directions module and several other mapping modules provides the ability to get directions to and from places using Google Maps. However, if you have only a few content items that need a simple way of providing directions to venues/locations, you can easily provide 'Get Directions' functionality using Views, Chaos tools Suite and, Eva modules as an alternative to the more robust and complex solutions provided by the some of the more comprehensive mapping modules.

To illustrate, we will enable Views, Views UI, Chaos tools (Ctools) and EVA modules and: 

1. Create a content type to store our address fields. We will name our content type 'Venue' and add the following fields:
   • Field label: Street Address, machine name: field_street_address, Field type: Text, Field Widget: Text Field
   • Field label: City, machine name: field_city, Field type: Text, Field Widget: Text Field;
   • Field label: State, machine name: field_state, Field type: List(text), Field Widget: Select List; (the field widget here could be text field as well, however, I want the content author to select the state from a drop-down box, so, I use a select list as the field widget here).
2. Add some content to the Venue content type (node/add/venue)
3. Create a View showing content of type 'Venue' and a display format of Unformated List of Fields.
   1. Add an EVA Field display to the View (if you do not see this display type, you need to enable the Eva module)
      • Under the Entity Content Settings section of the Eva display, configure the following:
        • Entity Type: Node
        • Bundles: Venue
        • Arguments: ID
      • Under the Contextual Filters Section of the View, select Content:Nid as the filter.
        • When the filter value is NOT available, Provide Default Value of Content ID from URL
           
   2. Add the following fields from the Venue content type to your View and select to Exclude them from display:
      • Content: Title 
      • Content: Street Address 
      • Content: City 
      • Content: State 
      • Content: ZipCode (may not be required but may improve accuracy)
      • Global Custom Text (do not Exclude from Display)
        • Uncheck Create Label 
        • In the Text box of the Global Custom Text field, add the following html codes: 

          <a href="http://maps.google.com/maps?saddr=&amp;daddr=[field_street_address]+[field_city]+[field_state]+[field_zip_code]" target="_blank">Driving Directions</a>
          

   3. Save the View
   4. 

Done.  Eva adds an additional field to your content display.  So, if you go to admin/structure/types/manage/venue/display you should see newly created Eva field in your field displays.  Now whenever you are viewing a Venue content type, you have a dynamic driving directions link attached to every single Venue node display.

In this illustration, I used a custom content type to demonstrate, however, you can use any entity that have address type fields attached to them.  For example, instead of using a custom content type to store the address fields data, you could attach address type fields to a Taxonomy entity or even Users.

This was inspired by https://www.drupal.org/node/347001#comment-2285812 and https://www.drupal.org/node/347001#comment-2581298.  Hope this helps someone.