I agree completely, Alexey, and I believe processing with ITRF is superior to any other method, because the GPS satellite orbits are in ITRF. Where I disagree with the current implementation (if I understand it correctly) is that you have places in Justin that are displaying NAD83(2011) coordinates (such as the site properties screen capture above) that apparently does not use HTDP to determine those coordinates. Any place in the software that depicts NAD83(2011) coordinates should be using HTDP to determine those coordinates from the ITRF coordinates in the database. This is consistent with the work our friend, Vladimir Prasolov, is doing with J-Field right now. With J-Field, not having HTDP is less of an issue because the NAD83(2011) control coordinates are entered manually, generally speaking, or we are receiving corrections from RTN that are already in NAD83(2011), so it is seldom that we rely on the absolute accuracy of the transformation from ITRF to NAD83(2011). This will become important in the future, with new adjustments or realizations of NAD83. So it is good that Vladimir is doing this. However, with Justin, we are importing positions for CORS as ITRF, relying on Justin to make the correct transformation to NAD83(2011) for us.