> [!NOTE] > **Note:** If you're a Google Cloud customer with a support contract for Google Earth Engine, create an issue in the [Cloud support console](https://cloud.google.com/support/). **What do you need help with? (click link)** - I have a [**question**](https://developers.google.com/earth-engine/help#ask_a_question). - I found a [**bug**](https://developers.google.com/earth-engine/help#report_a_bug). - I need help with [**registration or access**](https://developers.google.com/earth-engine/help#registration_issues). - I have an issue with [**payments and billing**](https://developers.google.com/earth-engine/help#payments_and_billing). - I received an [**error message**](https://developers.google.com/earth-engine/help#error_messages). - I have a question about [**computational tiers**](https://developers.google.com/earth-engine/help#computational_tiers). - I want to [**request a new dataset**](https://developers.google.com/earth-engine/help#dataset_requests). - I want to [**request a new feature**](https://developers.google.com/earth-engine/help#feature_requests). - I have noticed a [**change in script behavior**](https://developers.google.com/earth-engine/help#change_in_script_behavior_or_output). - I want to report a [**missing catalog asset**](https://developers.google.com/earth-engine/help#missing_catalog_assets). - I want to [**help others**](https://developers.google.com/earth-engine/help#help_others). ## Tips for getting help *"How can I help others help me?"* Before creating a help request, **first search for similar requests that have already been made from other users.** The answer might already be there and easily findable! This is often the fastest way to get unblocked. Try the following: - Open the [Earth Engine Developer Guide](https://developers.google.com/earth-engine) and use the search box to find relevant pages. - Search posts within [GIS Stack Exchange](https://gis.stackexchange.com/questions/tagged/google-earth-engine). - Search conversations in the [Earth Engine Developers Forum](https://groups.google.com/forum/#!forum/google-earth-engine-developers). - Browse the [Code Editor](https://code.earthengine.google.com) example scripts found under **Scripts \> Examples**. If you still need help after searching, you may want to compose a help request to the Earth Engine community. To maximize the chances of having your request answered and helping to create useful information that benefits the entire community, here is a checklist for composing a request: > [!TIP] > > ### Best practices for composing a request for help: > > - > > #### **Create a meaningful title** > > > Make it easy for others to quickly identify if they can potentially help. > ("Urgent help needed!" is not a meaningful title.) > - > > #### **Provide enough information** > > > Briefly describe what you are trying to do, and why. Often others may > suggest alternative approaches if they understand what you are trying > to do. > - > > #### **Make it as simple as possible** > > > The Earth Engine community includes many people who willingly spend their > time helping others. Consider that 10s or 100s of people may read your > post, and any time that you spend improving your post will save others > from duplicating the same work. > - > > #### **Remove irrelevant code** > > > Remove any extra code that is not relevant to the question you are asking. > If you are reporting a bug/error, keep simplifying until it is the minimum > needed to trigger the bug. > - > > #### **Remove unnecessary comments** > > If the comment is not needed to explain the question or bug, remove it. > - > > #### **Add a script link** > > > If your post includes code, include a link to reproduce your code in a > development environment. If using the Code Editor, create a > [snapshot script link](https://developers.google.com/earth-engine/guides/playground#snapshot_script_links) > using the *Get Link* button at the top of the Code Editor. If > using Colab, share access to anyone with a link, and save it to Google > Drive or as a GitHub Gist. > - > > #### **Make sure your assets are publicly accessible** > > > If others cannot run your code and reproduce your results, it will be > harder for them to help. Make sure that others have access to any code > [share any private assets](https://developers.google.com/earth-engine/guides/access_control#set_asset_permissions) > that are being used. ## Ask a question **What kind of question do you have?** (click links to learn more or expand for examples) [**A technical question**](https://developers.google.com/earth-engine/help#gis_stack_exchange): API how-to and why, represented by code, reproducible - *How do I remove features with null computed values from my feature collection?* - *How do I join a feature collection to an image collection by location and date?* - *Why is my feature collection empty?* [**A discussion question**](https://developers.google.com/earth-engine/help#earth_engine_developer_forum): matters of opinion, debate, remote sensing, methodology - *What is the best way to deal with Landsat 7 SLC-off gaps?* - *How can I exclude water pixels from my analysis?* - *Why does ArcGIS analysis give a different result than Earth Engine?* - *I'm wondering if I found a bug - are others having the same issue?* ### GIS Stack Exchange Post [technical questions](https://developers.google.com/earth-engine/help#technical_question) to [Geographic Information Systems Stack Exchange](https://gis.stackexchange.com/questions/tagged/google-earth-engine) (GIS SE), a community-based question and answer site for geospatial applications. ##### See tips for composing a good question You should NOT post your complete analysis and ask the developer community to debug your code. You SHOULD isolate the problem and present it in one complete sentence and no more than a few lines of code. You SHOULD Use the Stack Exchange tag \`google-earth-engine\`. The text in your question is interpreted as Markdown (a styling syntax). Take advantage of bold, italics, and code styling to make your question easier to read and quickly skim. Use the buttons at the top of the question editor or refer to this [Markdown syntax](https://gis.stackexchange.com/editing-help) guide to apply styling. Browse GIS SE's [help page](https://gis.stackexchange.com/help/asking) for more information on asking questions. **Use this example as a guide** for how to frame and markup your question: *Title*: > Why are the results of ee.Reducer.fixedHistogram() fractional? (Earth Engine) *Body*: ### Markdown ```` I am calculating a histogram for an area of interest using `ee.Reducer.fixedHistogram()`. The pixel count per bin is often a fraction, but not always. I was expecting integer results only, why are the results fractions of a pixel? Here is my code; inspect the histogram table to see the results. ```js // Define an image. var img = ee.Image('LANDSAT/LC08/C02/T1_TOA/LC08_038029_20180810'); // Define an area of interest. var aoi = ee.Geometry.Rectangle(-110.5, 44.6, -110.1, 44.8); // Calculate a histogram for the pixels in the API. var reflHistDict = img.select('B[1-7]').multiply(1e4).reduceRegion({ reducer: ee.Reducer.fixedHistogram(0, 5000, 250), geometry: aoi, scale: 30 }); // A dictionary was returned, get the ee.Array results for SWIR1 band. var swir1HistArray = ee.Array(reflHistDict.get('B6')); print(swir1HistArray); ``` [Code Editor script](https://code.earthengine.google.com/d5c15787d1e468c5668836399fa8652f?as_external) ```` ### Rendered I am calculating a histogram for an area of interest using `ee.Reducer.fixedHistogram()`. The pixel count per bin is often a fraction, but not always. I was expecting integer results only, why are the results fractions of a pixel? Here is my code; inspect the histogram table to see the results. ```js // Define an image. var img = ee.Image('LANDSAT/LC08/C02/T1_TOA/LC08_038029_20180810'); // Define an area of interest. var aoi = ee.Geometry.Rectangle(-110.5, 44.6, -110.1, 44.8); // Calculate a histogram for the pixels in the API. var reflHistDict = img.select('B[1-7]').multiply(1e4).reduceRegion({ reducer: ee.Reducer.fixedHistogram(0, 5000, 250), geometry: aoi, scale: 30 }); // A dictionary was returned, get the ee.Array results for SWIR1 band. var swir1HistArray = ee.Array(reflHistDict.get('B6')); print(swir1HistArray); ``` [Code Editor script](https://code.earthengine.google.com/d5c15787d1e468c5668836399fa8652f?as_external) > [!CAUTION] > **Make the code in your question reproducible** . If your script includes imports, [share the > assets](https://developers.google.com/earth-engine/guides/access_control#set_asset_permissions). Always include your code as a formatted code block in the question (optionally include a [Code Editor script > link](https://developers.google.com/earth-engine/playground#script-links)). ### Earth Engine Developer Forum Post [discussion questions](https://developers.google.com/earth-engine/help#discussion_question) and general Earth Engine topics to the [Earth Engine Developer Forum](https://groups.google.com/forum/#!forum/google-earth-engine-developers), a Google Group. Keep posts focused on Earth Engine. Use other forums for more general Earth Observation, Remote Sensing, and GIS topics. You can post about job positions that require Earth Engine skills, but ask respondents to reply directly to you rather than to the list. ## Report a bug **What kind of bug did you find?** (click links to learn more or expand for examples) [**An API bug**](https://developers.google.com/earth-engine/help#api): script errors or incorrect results - *Unexpected or incorrect function result* - *Unfamiliar error* - *Internal error messages* - *Errors not resolved by common [debugging methods](https://developers.google.com/earth-engine/debugging)* - *An unchanged, working script from some time ago, now does NOT work* - *API documentation is missing critical information* - *Issues regarding Data Catalog assets* [**A Code Editor interface bug**](https://developers.google.com/earth-engine/help#code_editor): UI display and functionality issues - *Scripts not loading* - *Buttons not working* - *Strange layout* - *Missing page elements* - *Map interaction not working* - *Data Catalog search not working* [**A dataset bug**](https://developers.google.com/earth-engine/help#dataset_problem) - *Missing assets* - *Projection issues* - *Unclear dataset descriptions* > [!NOTE] > **Don't expect any response to bug reports** . If you need a response or are unsure whether the behavior you are experiencing is a bug, discuss the issue on the [Developer > Forum](https://groups.google.com/forum/#!forum/google-earth-engine-developers). ### API Follow these instructions to file a bug: 1. Search the [list of existing bugs](https://issuetracker.google.com/issues?q=componentid:184406&type:bug). 2. If you find a relevant bug issue, star the issue and optionally add a comment to describe how the bug affects your workflow. 3. If a relevant issue does not exist, add a new issue using this [bug report template](https://issuetracker.google.com/issues/new?component=184406&template=1254745). > [!NOTE] > **Note:** you can report API bugs from the Code Editor. Click the ![](https://lh6.googleusercontent.com/5yL7FgAei4y8TWvGFZ2-STmzfQwlWBySVFOg_1buYYmSzMTdyP37NwcO5_8rR-m6fwKaWhYra5kHhkXXwWH2djcMl-BUy3BS84gDx19wRm0qZy05cinqFYl164z0U4BNq1ppiyw7 "Feedback icon") button, then **Create a new issue** , then **File a bug**. ### Code Editor Report a bug related to the [Code Editor](https://developers.google.com/earth-engine/playground) interface by opening the Code Editor, clicking the ![](https://lh6.googleusercontent.com/5yL7FgAei4y8TWvGFZ2-STmzfQwlWBySVFOg_1buYYmSzMTdyP37NwcO5_8rR-m6fwKaWhYra5kHhkXXwWH2djcMl-BUy3BS84gDx19wRm0qZy05cinqFYl164z0U4BNq1ppiyw7 "Feedback icon") button, then **Send Code Editor feedback**. A window will appear allowing you to describe the issue; you are also given the opportunity to markup a screenshot to highlight the location of the problem. ### Dataset problem [Report a bug here](https://issuetracker.google.com/issues/new?component=1161653&template=1662291). If possible, provide a Code Editor link showing the problem. ## Registration issues Visit the Earth Engine [registration page](https://console.cloud.google.com/earth-engine) to configure your access. If you are having registration or access issues for Earth Engine, you may request help by creating a case in the [Private Issue Tracker](https://issuetracker.google.com/issues/new?component=2161222&template=2338951). ## Payments and billing If you have an issue with your Earth Engine payments or billing, Google provides [billing support](https://docs.cloud.google.com/support/docs/get-billing-support) for all users. This is the right place to raise issues about incorrect or unexpected charges, clarify payment questions, or request refunds. For best results, we recommend the following steps: 1. File a [billing support case](https://docs.cloud.google.com/support/docs/get-billing-support) as soon as possible. This maximizes the chances that there are relevant debugging logs and information available. Provide as much information as you can about the issue. 2. If your issue is related to ongoing charges (e.g., subscription charges, storage fees), see the documentation for [terminating commercial Earth Engine access](https://developers.google.com/earth-engine/guides/access#terminating_commercial_access). 3. Share your case number with the Earth Engine team using the [Private Issue Tracker](https://issuetracker.google.com/issues/new?component=2161222&template=2359706). Be sure to **include your Support case number**! ## Error messages There are many ways to produce an error in Earth Engine. Follow these steps to identify the source of the problem and work toward a resolution: 1. Use the [debugging guide](https://developers.google.com/earth-engine/debugging) as an initial resource to understand what type of error you are receiving and how you might resolve it. 2. Do a [Google search](https://www.google.com/) for your error message; results are often returned from [GIS Stack Exchange](https://gis.stackexchange.com/questions/tagged/google-earth-engine). 3. Search on the [Developer Forum](https://groups.google.com/forum/#!forum/google-earth-engine-developers) for your error message to see if others have had the same issue. 4. If after consulting all available resources, you are still not clear what is causing the error, [post a question](https://developers.google.com/earth-engine/help#ask_a_question). 5. Finally, if the error remains unresolved and you suspect that it is a bug, [report it](https://developers.google.com/earth-engine/help#report_a_bug). ## Computational tiers Your computational resources are set by either your [commercial plan](https://cloud.google.com/earth-engine/pricing) or [noncommercial tier](https://developers.google.com/earth-engine/guides/noncommercial_tiers). ### Commercial use If you're using Earth Engine for commercial purposes, or want to pay for more compute resources, [learn about commercial plans](https://cloud.google.com/earth-engine/pricing) or [select an Earth Engine commercial plan on the Cloud Console](https://console.cloud.google.com/earth-engine/configuration). *Note that using Earth Engine commercially can incur charges to your Cloud account*. ### Noncommercial or research use For [noncommercial or research use of Earth Engine](https://earthengine.google.com/noncommercial/), you can request a temporary increase for [asset storage](https://developers.google.com/earth-engine/guides/manage_assets) quota, which controls how much asset data you can store in the EE asset store. By switching to the [Partner Tier](https://developers.google.com/earth-engine/guides/noncommercial_tiers), you can get a temporary increase in [EECU](https://developers.google.com/earth-engine/guides/computation_overview#eecus) quota, which controls how much compute (in Earth Engine Compute Units) you can consume over time. Partner Tier requires a separate application and is intended for organizations with clear evidence of high-impact sustainability work. Applications for the Partner Tier must be submitted using your true identity and accurate organizational affiliation. We may require applicants to verify their identity using their official organizational email. Providing false information, impersonating another individual (such as a faculty member), or submitting an application on behalf of someone else without explicit authorization is strictly prohibited. Accounts found engaging in identity spoofing or fraudulent applications will have their access immediately revoked and may face permanent suspension from Google Earth Engine. See the [noncommercial tiers page](https://developers.google.com/earth-engine/guides/noncommercial_tiers) to learn more. #### Before you apply In many cases, you can modify your code to run more efficiently and avoid the need for uplift. Review the [Scaling errors](https://developers.google.com/earth-engine/guides/debugging#scaling-errors), [Debugging methods](https://developers.google.com/earth-engine/guides/debugging#debugging-methods) and [Coding Best Practices](https://developers.google.com/earth-engine/guides/best_practices) sections of the Earth Engine documentation for suggestions. You may also benefit from discussing your approach with others on the [Earth Engine Developer Forum](https://developers.google.com/earth-engine/help#earth_engine_developer_forum). There are many best practices for efficiently processing large and complex imagery using Earth Engine. Experts on the forum may be able to help. Before posting, read these [best practices for composing a request for help](https://developers.google.com/earth-engine/help#help_request_best_practices). > [!NOTE] > **Note:** Not all requests will be approved. Applications that clearly connect increased quota with demonstrable on-the-ground impact are prioritized. We'll get back to you as soon as possible, but there may be times when the process will take longer or we may ask you for additional information. **Apply for more asset storage or noncommercial partner tier** - [Application form](https://docs.google.com/forms/d/e/1FAIpQLSfK_k2-Z-jFGr2ugjDtL2EhC2Njd3DA7nmliKwndxXSjYgMfw/viewform) If you have questions about your request for uplift, submit a case using the [Private Issue Tracker](https://issuetracker.google.com/issues/new?component=2161222&template=2338667) with a description of the problem. ## Dataset requests Follow these instructions to request a new dataset or to file a bug for an existing dataset: 1. Search the [new](https://issuetracker.google.com/issues?q=componentid:1161680%2B+status:open) or [existing](https://issuetracker.google.com/issues?q=componentid:1161653%2B+status:open) dataset requests. 2. If you find a relevant dataset request, star the issue and optionally add a comment to describe how the dataset would be useful in your work. 3. If a relevant data request does not exist, submit a new request for a [new](https://issuetracker.google.com/issues/new?component=1161680&template=1662313) or [existing](https://issuetracker.google.com/issues/new?component=1161653&template=1662291) dataset. > [!NOTE] > **Note:** links to existing requests and request form can be accessed from the Code Editor by clicking the ![](https://lh6.googleusercontent.com/5yL7FgAei4y8TWvGFZ2-STmzfQwlWBySVFOg_1buYYmSzMTdyP37NwcO5_8rR-m6fwKaWhYra5kHhkXXwWH2djcMl-BUy3BS84gDx19wRm0qZy05cinqFYl164z0U4BNq1ppiyw7 "Feedback icon") button. > **Do not expect any response to new dataset requests**. ## Feature requests Follow these instructions to request a new API or Code Editor feature: 1. Search the [list of existing feature requests](https://issuetracker.google.com/issues?q=componentid:184406+type:feature_request+status:open). 2. If you find a relevant feature request, star the issue and optionally add a comment to describe how the feature would be useful in your work. 3. If a relevant feature request does not exist, submit a new request using this [template](https://issuetracker.google.com/issues/new?component=184406&template=719602). > [!NOTE] > **Note:** links to existing requests and request form can be accessed from the Code Editor by clicking the ![](https://lh6.googleusercontent.com/5yL7FgAei4y8TWvGFZ2-STmzfQwlWBySVFOg_1buYYmSzMTdyP37NwcO5_8rR-m6fwKaWhYra5kHhkXXwWH2djcMl-BUy3BS84gDx19wRm0qZy05cinqFYl164z0U4BNq1ppiyw7 "Feedback icon") button. > **Do not expect any response to feature requests**. ## Change in script behavior or output Earth Engine API code, architecture, and policies can change, resulting in different behavior or errors that appear now but did not some time ago for the same script. Submit an [API bug](https://developers.google.com/earth-engine/help#api) for these types of issues, but first verify a few things: 1. Confirm that nothing about your script has changed - check the [script history](https://developers.google.com/earth-engine/playground#script-manager-scripts-tab). 2. Confirm that nothing about your input collection has changed (e.g., are you filtering image dates to the present and now there are new images in a collection?). 3. Are you relying on [imported script modules](https://developers.google.com/earth-engine/playground#script-modules) or [shared assets](https://developers.google.com/earth-engine/guides/access_control#set_asset_permissions) that are no longer available or have changed? 4. Is it the same script but running on a different region of interest or dataset? After checking to see that a similar bug has not already been posted, submit your bug and provide information regarding these points in the bug report. ## Missing catalog assets See this [guide](https://developers.google.com/earth-engine/help_missing_images) to learn how to confirm and report a missing asset from the Earth Engine Data Catalog. ## Help others There are a number of ways you can help others: - Answer and edit questions on [GIS Stack Exchange](https://gis.stackexchange.com/questions/tagged/google-earth-engine). - Answer questions on the [Earth Engine Developer Forum](https://developers.google.com/earth-engine/help#earth_engine_developer_forum). - [Write tutorials](https://developers.google.com/earth-engine/tutorials/community/write). - Present lectures on how to use Earth Engine at your university or place of work. Here are some resources to help get you started: - [Lectures](https://developers.google.com/earth-engine/edu) - [Workshops](https://developers.google.com/earth-engine/ttt#instructor-reference-for-a-beginning-workshop) - [Tutorials](https://developers.google.com/earth-engine/tutorials) - [Script library](https://code.earthengine.google.com/?accept_repo=users/nclinton/EE101)