Usually you move the computation to the location of the data and not the other way around. That's the basic premise of Hadoop/Spark and many similar big data tools.
GAIA-X self-descriptions give visibility on whether your data is (would be) in a data center that also has GPU-capacities. And if not, what you would have to pay for interconnection.
See this demo for the basic idea of the self-description graph: https://www.youtube.com/watch?v=f17c3Vpi3rA
It's more of an example really. Patching together multiple provider offerings is going to involve interconnecting them somehow.
Thanks for the vid. The app they're demonstrating seems to be publicly accessible too:
A searchable catalog of all say virtual machines across countries & providers would be pretty cool for starters.
Don't quite see how they're going to get around stuff being in different physical locations. That creates latency, cost and reliability headaches that AWS/GCP/Azure doesn't need to deal with since you normally put say DB and VM into the same data center