Map directions in the app just gives the gps location of the crag to google/apple maps. When the gps coordinate is not on a road (which is usually the case) the mapping software gives directions to the closest location on the road. In most cases the closest road approach to a crag is also the parking area and so the directions as currently implemented work fine. But sometimes this is not the case, and can lead to confusion. A recent example can be found in this thread. If the metadata for a crag included a second gps coordinate for the parking area, then this issue could be fixed. This field could default to the same gps as the crag itself which works in most cases, and would only need to be updated for the crags that are problematic. When giving driving directions, the app could then use this new field.
An alternative option would be to have a flag for problematic areas. So that when you ask for directions in the app, if the area is flagged, you get a pop up saying to check the written directions for correct driving directions.
Alex, your point is a reasonable one, but there are definitely cases where this isn't the sole solution. In fact, many crags have multiple places from which to approach. Which do you pick? Some have very long approaches, too. Would you want the GPS miles away from the crag? This may not be a universal fit for all areas. Also, some folks don't always manage to match the crag or parking area with the satellite imagery.
A different solution will come eventually: we're working on approach trails to crags, and you can change the map directions to start at the beginning of an approach trail. These should be in the app by next year.