What I learned a few years back about this is the official (un)obfuscating implementation was distributed to licensed companies in binary .dll/.so/.a , and not allowed to be redistributed or reverse-engineered. Licenses are only given to local companies, and foreign companies may only buy service from them. That's why if you reverse engineer Google Map or Apple Map app, they all make real time API calls to do the conversion on servers. Those contracts may also limit the end user who can consume these APIs to be in China, hence foreign users will see the shifts of roads/etc.
The open-sourced implementation one may find on the internet are probably thru sth like curve fitting by sampling many data points. It may have good enough approximations but may not work one day if the gov agency decides to change the algorithm. Changing algorithm is a backward compatibility hell but not a big problem for the industry actually, because most Map apps are owned by big corp which has resource and motivation to comply.