Thanks. It sounds like the input is raw satellite photos and output might be cleaned-up maps based on the data. The page on "location embeddings" [1] seems int

Thanks. It sounds like the input is raw satellite photos and output might be cleaned-up maps based on the data. The page on "location embeddings" [1] seems interesting: > In CLAY, the encoder receives unmasked patches, latitude-longitude data, and timestep information. Notably, the last 2 embeddings from the encoder specifically represent the latitude-longitude and timestep embeddings. Perhaps it could figure out the latitude, longitude, and orientation from a satellite photo (geolocation). [1] https://clay-foundation.github.io/model/clay-v0-location-embeddings.html https://clay-foundation.github.io/model/clay-v0-location-emb...