It’s currently not possible to update the version of Proj that is used because all binaries are statically linked for compatibility reasons. We currently use proj 9.0.0.
I’m looking into the timeline for our next release to include 9.2. We are also considering shipping the full proj dataset with the tilers as well so you won’t need to manually install it in the future.
Respectfully, as a enterprise paying customer, this cant really be considered acceptable. A geospatial product that incorrectly places geospatial assets due to a known bug should really be high on the priority list or at least allow us as a client to be able to upgrade this version to remedy as an immediate/interim solution. Thanks
@Josh_Gardner I apologize for the lack of reply here and I understand your frustration.
As I mentioned previously, It’s not possible to update the version of Proj that is used because all binaries are statically linked for compatibility reasons. (I’m not even sure it’s feasible to drop in Proj 9.2 on top of 9.0 even if we were dynamically linked).
As 9.2.0 only came out on March 1st, it takes time for the ecosystem to adopt the new versions and for us to have full compatibility throughout our tool chain. We’ve internally updated to 9.1.1, but are still waiting to be able to use 9.2.0 (and in reality 9.2.1 came out today but being a patch version usually leads to faster adoption).
That being said, the team is actively looking into it and is hoping to evaluate ways we can take upstream dependencies, like proj, at a much faster cadence than we have in the past.
As soon as I have an update to share, I’ll post back here.
@Matt_Amato thank you for giving an update. We understand that this change has complexity and can take time, all we’re looking for is some indication (a date) of when you plan to have this resolved. We need to know if this is going to take weeks/months/years so we can plan around it. Please come back to us with something more concrete.