The summary endpoint is a great way to get metadata about a page that is useful to display to users to help them decide if they would like to read an article.
Location data is increasingly being added to designs for apps. We have nearby in Android, and v2 of the feature "Places" set to be released on iOS this quarter. This update includes both search and the ability to see top read articles on a map.
Just like wikidata description and thumb, these are starting to become a basic piece of data that clients may want to display in many other contexts.
This leads to the question: Is it feasible to return location data in the summary of articles?
How would this affect caching / cache invalidation / storage / CPU?
This ticket is intentionally very similar to:
T157061
Basically the thrust of both of these in enrichment of summary data