The overall transaction flow of customer search for providers detailed in the document states that location of the customer is requested and send to the search API. But the search API schema only has country and city fields under the context. Neither under the context or message there is provision to share the geolocation coordinates(GPS as per the schema) of the customer/buyer.
Having the geolocation coordinates of the buyer and/or buyers delivery location in the search API schema, ( may be under message > intent > descriptor or under context along with buyers country, city and other details) would help BPP fetch all the hyperlocal sellers serving that particular geolocation from the list of all the sellers it will have on its platform. This use case is not limited to hyperlocal retailers but is relevant for other domains as well; for eg. mobility.
The overall transaction flow of customer search for providers detailed in the document states that location of the customer is requested and send to the search API. But the search API schema only has country and city fields under the context. Neither under the context or message there is provision to share the geolocation coordinates(GPS as per the schema) of the customer/buyer.
Having the geolocation coordinates of the buyer and/or buyers delivery location in the search API schema, ( may be under message > intent > descriptor or under context along with buyers country, city and other details) would help BPP fetch all the hyperlocal sellers serving that particular geolocation from the list of all the sellers it will have on its platform. This use case is not limited to hyperlocal retailers but is relevant for other domains as well; for eg. mobility.