Https apis.google.com js platform.js là gì
|
Google Earth Engine combines a multi-petabyte catalog of satellite imagery and geospatial datasets with planetary-scale analysis capabilities. Scientists, researchers, and developers use Earth Engine to detect changes, map trends, and quantify differences on the Earth's surface. Earth Engine is now available for commercial use, and remains free for academic and research use. Show + + learn more Our planet is changingSee our impact on the Earth from a new perspective through 37 years of satellite imagery in Timelapse in Google Earth. Timelapse is one example of how Earth Engine can help gain insight into petabyte-scale datasets. Explore Timelapse Ready-to-use datasetsThe public data archive includes more than thirty years of historical imagery and scientific datasets, updated and expanded daily. It contains over eighty petabytes of geospatial data instantly available for analysis. explore datasets Simple, yet powerful APIThe Earth Engine API is available in Python and JavaScript, making it easy to harness the power of Google’s cloud for your own geospatial analysis. Google Earth Engine has made it possible for the first time in history to rapidly and accurately process vast amounts of satellite imagery, identifying where and when tree cover change has occurred at high resolution. Global Forest Watch would not exist without it. For those who care about the future of the planet Google Earth Engine is a great blessing! -Dr. Andrew Steer, President and CEO of the World Resources Institute. Convenient toolsUse our web-based code editor for fast, interactive algorithm development with instant access to petabytes of data. learn about the code editor Scientific and humanitarian impactScientists and non-profits use Earth Engine for remote sensing research, predicting disease outbreaks, natural resource management, and more. While the easiest way to use Cloud Firestore is to use one of the native client libraries, there are some situations when it is useful to call the REST API directly. The REST API can be helpful for the following use cases:
If you are using a , consider using the RPC API rather than the REST API. For authentication, the Cloud Firestore REST API accepts either a Firebase Authentication ID token or a Google Identity OAuth 2.0 token. The token you provide affects your request's authorization:
Working with Firebase ID tokensYou can attain a Firebase ID token in two ways:
By retrieving a user's Firebase ID token, you can make requests on behalf of the user. For requests authenticated with a Firebase ID token and for unauthenticated requests, Cloud Firestore uses your Cloud Firestore Security Rules to determine if a request is authorized. Working with Google Identity OAuth 2.0 tokensYou can generate an access token by using a service account with a Google API Client Library or by following the steps in Using OAuth 2.0 for Server to Server Applications. You can also generate a token with the This token must have the following scope to send requests to the Cloud Firestore REST API:
If you authenticate your requests with a service account and a Google Identity OAuth 2.0 token, Cloud Firestore assumes that your requests act on behalf of your application instead of an individual user. Cloud Firestore allows these requests to ignore your security rules. Instead, Cloud Firestore uses IAM to determine if a request is authorized. You can control the access permissions of service accounts by assigning . Authenticating with an access tokenAfter you obtain either a Firebase ID token or a Google Identity OAuth 2.0 token, pass it to the Cloud Firestore endpoints as an Making REST callsAll REST API endpoints exist under the base URL To create a path to a document with the ID 0 you would use the following structure. To interact with this path, combine it with the base API URL. The best way to begin experimenting with the REST API is to use the , which automatically generates Google Identity OAuth 2.0 tokens and allows you to examine the API. MethodsBelow are brief descriptions of the two most important method groups. For a complete list, see the REST API reference or use the . 1 Perform CRUD operations on documents, similar to those outlined in the add data or get data guides. 2 Perform actions on indexes such as creating new indexes, disabling an existing index, or listing all current indexes. Useful for automating data structure migrations or synchronizing indexes between projects. Also enables retrieval of document metadata, such as the list of all fields and subcollections for a given document. Error CodesWhen a Cloud Firestore request succeeds, the Cloud Firestore API returns an HTTP 3 status code and the requested data. When a request fails, the Cloud Firestore API returns an HTTP 4 or 5 status code and a response with information about the error. The following table lists recommended actions for each error code. These codes apply to the Cloud Firestore REST and RPC APIs. The Cloud Firestore SDKs and client libraries may not return these same error codes. Canonical Error Code Description Recommended Action 6The request conflicted with another request. For a non-transactional commit: Retry the request or re-structure your data model to reduce contention. For requests in a transaction: Retry the entire transaction or re-structure your data model to reduce contention. 7The request tried to create a document that already exists. Do not retry without fixing the problem. 8The Cloud Firestore server handling the request exceeded a deadline. Retry using exponential backoff. 9The request did not meet one of its preconditions. For example, a query request might require an index not yet defined. See the message field in the error response for the precondition that failed. Do not retry without fixing the problem.`gcloud`0The Cloud Firestore server returned an error. Do not retry this request more than once.`gcloud`1A request parameter includes an invalid value. See the message field in the error response for the invalid value. Do not retry without fixing the problem.`gcloud`2The request attempted to update a document that does not exist. Do not retry without fixing the problem.`gcloud`3The user is not authorized to make this request. Do not retry without fixing the problem.`gcloud`4The project exceeded either its quota or the region/multi-region capacity. . If you exceeded a project quota, do not retry without fixing the problem. Otherwise, retry with exponential backoff. `gcloud`5The request did not include valid authentication credentials. Do not retry without fixing the problem.`gcloud`6The Cloud Firestore server returned an error. Retry using exponential backoff. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates. Last updated 2024-01-04 UTC. [{ "type": "thumb-down", "id": "missingTheInformationINeed", "label":"Missing the information I need" },{ "type": "thumb-down", "id": "tooComplicatedTooManySteps", "label":"Too complicated / too many steps" },{ "type": "thumb-down", "id": "outOfDate", "label":"Out of date" },{ "type": "thumb-down", "id": "samplesCodeIssue", "label":"Samples / code issue" },{ "type": "thumb-down", "id": "otherDown", "label":"Other" }] [{ "type": "thumb-up", "id": "easyToUnderstand", "label":"Easy to understand" },{ "type": "thumb-up", "id": "solvedMyProblem", "label":"Solved my problem" },{ "type": "thumb-up", "id": "otherUp", "label":"Other" }] Need to tell us more? |
