# Arrivals with path and pierce points
**URL:** https://discourse.obspy.org/t/arrivals-with-path-and-pierce-points/1119
**Category:** Usage Questions
**Created:** [November 5, 2020, 11:42am UTC](https://discourse.obspy.org/t/arrivals-with-path-and-pierce-points/1119 "2020-11-05T11:42:34Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@adigitoleo](https://discourse.obspy.org/u/adigitoleo)
#### Post date: [November 5, 2020, 11:42am UTC](https://discourse.obspy.org/t/arrivals-with-path-and-pierce-points/1119/1 "2020-11-05T11:42:34Z")
Hi, I’m wondering if there is a way to get arrivals that have both path and pierce point info, via `.path` and `.pierce` methods respectively. For example, say I calculate the arrivals using `get_ray_paths_geo`, I will get a `.path` method, but to get pierce points I have to calculate the same arrivals again, using `get_pierce_points_geo`. The only way I found to get around this was using:
```python
# arrivals were calculated using get_ray_paths_geo
arrivals[0].phase.calc_pierce_from_arrival(arrivals[0])
```
It works I guess, but is there a better API for this that I am missing? I’m thinking of something like `arrivals.add_pierce_points(phase_list=[''])` which would add pierce point info to all phases of type `` in the `arrivals` list. Or even at the singular arrival level, an `arrivals[0].add_pierce_points(...)`. There could also be equivalent `add_path(...)` methods.
What do you think?
---
### Author:  [@adigitoleo](https://discourse.obspy.org/u/adigitoleo)
#### Post date: [November 8, 2020, 6:01am UTC](https://discourse.obspy.org/t/arrivals-with-path-and-pierce-points/1119/2 "2020-11-08T06:01:01Z")
Conversation moved to [this post](https://discourse.obspy.org/t/make-taup-arrival-api-more-modular-and-efficient/1121).