My point is that it is far more important to have reasonably accurate coordinates on observations, rather than having them adjusted to conform to location boundaries which may or may not be accurate. Based on the posts above, it seems that anyone can create these place boundaries. If that’s the case, I’m not sure the admin’s can do anything about it if a particular location boundary is not considered accurate. I’m not sure why it matters whether or not your observations get “captured” within the TTP site boundary defined on iNat. What is the downside if they are not? What do you gain when they are “captured” ?
Perhaps the solution is to create your own TTP location with more accurate boundaries, though as I said, I’m not sure what your goal is by having them fall within these boundaries.
If you must make these adjustments, I hope that you are also adjusting the “coordinate accuracy” number accordingly. Moving the coordinates by a few hundred meters is no big deal (from my perspective). I’m sure that the coordinates of many observations are off by much more than that. But the accuracy figure should reflect the potential discrepancy.