Stay organized with collectionsSave and categorize content based on your preferences.
Retrieves the value of this object from the server.
If no callback function is provided, the request is made synchronously. If a callback is provided, the request is made asynchronously.
The asynchronous mode is preferred because the synchronous mode stops all other code (for example, the EE Code Editor UI) while waiting for the server. To make an asynchronous request, evaluate() is preferred over getInfo().
Returns the computed value of this object.
Usage
Returns
Date.getInfo(callback)
Object
Argument
Type
Details
this:computedobject
ComputedObject
The ComputedObject instance.
callback
Function, optional
An optional callback. If not supplied, the call is made synchronously.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2023-10-06 UTC."],[[["\u003cp\u003e\u003ccode\u003egetInfo()\u003c/code\u003e retrieves the value of a server-side ComputedObject (like ee.Date) and transfers it to the client.\u003c/p\u003e\n"],["\u003cp\u003eIt returns an object containing the computed value, with synchronous or asynchronous behavior depending on the presence of a callback function.\u003c/p\u003e\n"],["\u003cp\u003eAsynchronous requests, typically made with \u003ccode\u003eevaluate()\u003c/code\u003e, are preferred to avoid blocking other code execution.\u003c/p\u003e\n"],["\u003cp\u003eThe returned object, when dealing with dates, contains \u003ccode\u003etype\u003c/code\u003e and \u003ccode\u003evalue\u003c/code\u003e keys, where \u003ccode\u003evalue\u003c/code\u003e represents milliseconds since the Unix epoch.\u003c/p\u003e\n"],["\u003cp\u003eWhile \u003ccode\u003egetInfo()\u003c/code\u003e facilitates client-side data interaction, server-side operations are generally recommended for better performance and efficiency.\u003c/p\u003e\n"]]],["`getInfo()` retrieves a ComputedObject's value from the server. It can operate synchronously (no callback) or asynchronously (with a callback), the latter being preferred. It returns the object's computed value. For example a Date.getInfo() call will return an object with 'type' and 'value' keys. The value is in miliseconds since the Unix epoch. The function should be used carefully, as it transfers data from Earth Engine servers to the client.\n"],null,["# ee.Date.getInfo\n\n\u003cbr /\u003e\n\nRetrieves the value of this object from the server.\n\n\u003cbr /\u003e\n\nIf no callback function is provided, the request is made synchronously. If a callback is provided, the request is made asynchronously.\n\nThe asynchronous mode is preferred because the synchronous mode stops all other code (for example, the EE Code Editor UI) while waiting for the server. To make an asynchronous request, evaluate() is preferred over getInfo().\n\nReturns the computed value of this object.\n\n| Usage | Returns |\n|------------------------------|---------|\n| Date.getInfo`(`*callback*`)` | Object |\n\n| Argument | Type | Details |\n|------------------------|--------------------|------------------------------------------------------------------------|\n| this: `computedobject` | ComputedObject | The ComputedObject instance. |\n| `callback` | Function, optional | An optional callback. If not supplied, the call is made synchronously. |\n\nExamples\n--------\n\n### Code Editor (JavaScript)\n\n```javascript\n/**\n * WARNING: this function transfers data from Earth Engine servers to the\n * client. Doing so can negatively affect request processing and client\n * performance. Server-side options should be used whenever possible.\n * Learn more about the distinction between server and client:\n * https://developers.google.com/earth-engine/guides/client_server\n */\n\n// A server-side ee.Date object.\nvar dateServer = ee.Date('2021-4-30');\n\n// Use getInfo to transfer server-side date to the client. The result is\n// an object with keys \"type\" and \"value\" where \"value\" is milliseconds since\n// Unix epoch.\nvar dateClient = dateServer.getInfo();\nprint('Client-side date is an object', typeof dateClient);\nprint('Object keys include \"type\" and \"value\"', Object.keys(dateClient));\nprint('\"value\" is milliseconds since Unix epoch', dateClient.value);\nprint('Client-side date in JS Date constructor', new Date(dateClient.value));\n```\nPython setup\n\nSee the [Python Environment](/earth-engine/guides/python_install) page for information on the Python API and using\n`geemap` for interactive development. \n\n```python\nimport ee\nimport geemap.core as geemap\n```\n\n### Colab (Python)\n\n```python\n\"\"\"\nWARNING: this function transfers data from Earth Engine servers to the\nclient. Doing so can negatively affect request processing and client\nperformance. Server-side options should be used whenever possible.\nLearn more about the distinction between server and client:\nhttps://developers.google.com/earth-engine/guides/client_server\n\"\"\"\nfrom datetime import datetime\n\n# A server-side ee.Date object.\ndate_server = ee.Date('2021-4-30')\n\n# Use getInfo to transfer server-side date to the client. The result is\n# a dictionary with keys \"type\" and \"value\" where \"value\" is milliseconds since\n# Unix epoch.\ndate_client = date_server.getInfo()\nprint('Client-side date is a dictionary:', type(date_client))\nprint('Dictionary keys include \"type\" and \"value\":', date_client.keys())\nprint('\"value\" is milliseconds since Unix epoch:', date_client['value'])\nprint('Client-side date in Python:',\n datetime.fromtimestamp(date_client['value'] / 1000))\n```"]]
