The Vadodara Maps Platform supports real-time location streaming and ETA updates for delivery services using WebSockets. These real-time endpoints are managed by the Go Routing service (go-service) and proxied through Nginx at the /ws/ gateway path.

1. Endpoints

All WebSocket URLs use standard protocols (ws:// for unencrypted local dev, wss:// for production SSL).

Role	Endpoint Path	Authentication	Protocol Purpose
Rider App	/ws/track?token=<rider_token>	Query Parameter token	Streams rider GPS coordinates to the server.
Customer App	/ws/order?order_id=<id>&token=<token>	Query Parameter token	Receives real-time rider coordinates and ETA updates.

2. Rider Tracking Protocol (/ws/track)

The rider client app initiates a connection to stream coordinates.

ws://localhost/ws/track?token=rider-123

{
  "type": "location",
  "lat": 22.311000,
  "lng": 73.176000,
  "bearing": 120.5,
  "speed": 18.5
}

Field Details:

• type: Must be set exactly to "location".
• lat: Numeric latitude (WGS 84 coordinate).
• lng: Numeric longitude (WGS 84 coordinate).
• bearing: Direction of travel in degrees (0.0 to 360.0).
• speed: Instantaneous velocity in km/h.

Server-Side Behavior:

1. Validates the provided rider token.
2. Updates the rider's latest location in the Redis spatial index (GEOADD key: riders).
3. Publishes a JSON payload to the order's Redis pub/sub channel (order:<rider_token>).
4. Extends the rider's TTL in Redis by 30 seconds. If no updates are received within 30 seconds, the rider is automatically removed from the active grid.

3. Customer Order Subscription Protocol (/ws/order)

The customer client app connects to receive live updates.

ws://localhost/ws/order?order_id=rider-123&token=vmp_live_...

{
  "type": "rider_update",
  "lat": 22.311000,
  "lng": 73.176000,
  "bearing": 120.5,
  "eta_mins": 0.0
}

Connection Maintenance (Ping/Pong Keep-Alive):

• The server automatically streams control frame ping frames (opcode: 9) to the client every 25 seconds to prevent Nginx or firewall timeouts.
• The client browser or app library handles this automatically by replying with a pong frame (opcode: 10).

4. Interactive Testing in Browser

1. Open the Maps API Dashboard in your browser.
2. Scroll to the ⚡ WebSockets (Go) category in the sidebar.
3. Select Rider Location Stream:
   • Provide a rider token (e.g. rider-123).
   • Click Connect WebSocket.
   • Click Start Simulation to begin streaming automated circular path coordinates around Alkapuri, Vadodara.
4. Open a second tab to the dashboard and select Order Update Stream:
   • Set the Order ID to match your rider token (e.g. rider-123).
   • Click Connect WebSocket.
   • Watch the incoming location stream matching the simulator logs in real-time.