X, Y, and Z accuracies are in that order typically. Your X component is generally the best, Z is the worst. There are many reasons for this, but most stem from the fact that Positioning relies on the principle of trilateration.
When you think about the orientation of satellites (birds) flying around overhead, the Z component is the most sensitive to errors in the trilateration calculations. The best birds for calculating a single distance are directly overhead, and the worst are low on the horizon. Geometry would point us to adding the birds low on the horizon to better “fix” a point in 3D space - but those signals must travel through more atmosphere than the rest. Low angles are also much more susceptible to Multi-Path interference at the receiver.
Now consider that the bird has traveled a couple hundred miles [Correction: meters] through space during the time it takes the RF signal to reach Earth. Plus the Earth is spinning and the Y coordinate has moved ~100’ during that time.
Thankfully, we have many birds to produce an overdetermined calculation.
Sorry to geek-out. After 30 years in the industry I’m still amazed we can get cm solutions.
I’d look for Multi-Path at your receiver first. This is a problem for everyone and the easiest thing to mitigate.
Next, I’d suspect your Correction Source. No person or receiver can outperform their correction source. PointOneNav has OSR and SSR service plans. SSR is a computer model, and is “generally” less accurate than OSR. However, your baseline length gets critical in OSR.
Cheers to you for actually testing ! That’s the only way to truly know what you’re getting.
Note: The Facet is capable of reproducing points inside of 2cm over weeks of time with the proper correction source and field procedure.
P.S. @Eric_S has mentioned an interesting aspect that I’ve never really considered…because I live in flat country. I’d have to drive 12+ hours away to see a 300m “Mountain” 