# Live geolocation Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert. ### Sending live locations inputGeoPointEmpty#e4c123d6 = InputGeoPoint; inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint; inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia; ---functions--- messages.sendMedia#330e77f flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?true update_stickersets_order:flags.15?true invert_media:flags.16?true allow_paid_floodskip:flags.19?true peer:InputPeer reply_to:flags.0?InputReplyTo media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector schedule_date:flags.10?int schedule_repeat_period:flags.24?int send_as:flags.13?InputPeer quick_reply_shortcut:flags.17?InputQuickReplyShortcut effect:flags.18?long allow_paid_stars:flags.21?long suggested_post:flags.22?SuggestedPost = Updates; messages.editMessage#51e842e1 flags:# no_webpage:flags.1?true invert_media:flags.16?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector schedule_date:flags.15?int schedule_repeat_period:flags.18?int quick_reply_shortcut_id:flags.17?int = Updates; To send a live geolocation, use [messages.sendMedia](/method/messages.sendMedia.md) with an [inputMediaGeoLive](/constructor/inputMediaGeoLive.md) `media` . The [inputMediaGeoLive](/constructor/inputMediaGeoLive.md) allows sending the geolocation as an [inputGeoPoint](/constructor/inputGeoPoint.md) with floating point latitude and longitude, with an optional `accuracy_radius` in meters. Clients can also provide a `heading`, a direction in degrees (1-360) that can be used to indicate the direction of the user, a validity `period` for the current location, and a `proximity_notification_radius` . The sent geolocation should be updated periodically using [messages.editMessage](/method/messages.editMessage.md) **at most** every `period` seconds, in order to implement the "live" part of live geolocations. To stop sharing the location, pass [inputGeoPointEmpty](/constructor/inputGeoPointEmpty.md) as location and set the `stopped` flag to true in a last [messages.editMessage](/method/messages.editMessage.md) call. ### Receiving live locations geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint; messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia; updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update; ---functions--- messages.getRecentLocations#702a40e0 peer:InputPeer limit:int hash:long = messages.Messages; All recent live locations sent to a chat can be fetched using [messages.getRecentLocations](/method/messages.getRecentLocations.md): this method returns up to 1 location message ([messageMediaGeoLive](/constructor/messageMediaGeoLive.md)) per chat participant. Clients will also receive a message with a [messageMediaGeoLive](/constructor/messageMediaGeoLive.md), containing the information passed by the sender; when the geolocation message is [marked as read](/api/views.md#read-message-contents), an [updateGeoLiveViewed](/constructor/updateGeoLiveViewed.md) is generated. Periodically, the geolocation will be updated with [updateEditMessage](/constructor/updateEditMessage.md)/[updateEditChannelMessage](/constructor/updateEditChannelMessage.md) updates. #### Live location previews inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation; inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint; ---functions--- upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile; A map preview can be generated by passing the received [geoPoint](/constructor/geoPoint.md) to [upload.getWebFile](/api/files.md#downloading-webfiles), to download an image preview of the map. * `geo_point` is generated from the `lat` , `long` `accuracy_radius` parameters of the [geoPoint](/constructor/geoPoint.md) * `access_hash` is the access hash of the [geoPoint](/constructor/geoPoint.md) * `w` - Map width in pixels before applying scale; 16-1024 * `h` - Map height in pixels before applying scale; 16-1024 * `zoom` - Map zoom level; 13-20 * `scale` - Map scale; 1-3 The image is then downloaded as specified [here » ](/api/files.md) ### Proximity alert messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction; messageService#7a800e0a flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true reactions_are_possible:flags.9?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer saved_peer_id:flags.28?Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction reactions:flags.20?MessageReactions ttl_period:flags.25?int = Message; If: * A user sets a `proximity_notification_radius` when sending a location * Multiple users share their location within the same chat * One of the other users comes within `proximity_notification_radius` meters of the first user, and updates their location accordingly An [updateNewMessage](/constructor/updateNewMessage.md)/[updateNewChannelMessage](/constructor/updateNewChannelMessage.md) is generated for all chat members, containing a [messageService](/constructor/messageService.md) with action [messageActionGeoProximityReached](/constructor/messageActionGeoProximityReached.md): * `messageActionGeoProximityReached.to_id` is the peer that enabled proximity alerts * `messageActionGeoProximityReached.from_id` is the peer that is now in proximity of `messageActionGeoProximityReached.to_id` * `messageActionGeoProximityReached.distance` is the distance between them, in mete