Good afternoon- GEDI data can be used to study different tree growth stages by providing detailed information about forest canopy height, structure, and vertical profile. A new GEDI Level 2C product at NASA's ORNL DAAC provides canopy structural complexity (CSC) and measures how leaves, branches, and stems are distributed across both horizontal and vertical spaces in a forest canopy. (see: www.earthdata.nasa.gov/news/feature-articles/new-gedi-data-product-provides-estimates-forest-canopy-complexity) for more info about this product. Please also consider adding this question to NASA's Earthdata Forum at forum.earthdata.nasa.gov. Subject matter experts from the NASA data centers can provide additional data guidance regarding your query. There are also many different phenology and vegetation data products from other platforms and instruments that could be combined with GEDI data. I hope this helps to get you started.

Hi there, you can add/turn base layers back on by clicking on the "eye" icon next to any layer. To learn more about any particular layer, click on the "i" icon for information.

Hi there, let me locate that file and get back to you. Thank you for your message.

@ thank u so much :) im doing a masters thesis using GEDI :)

@ hello any updates please? thank you so muchhh

Good afternoon Richard, yes, there is data available for Southeast Asia and the Philippines. For more information visit NASA's PO.DAAC Cookbook at: podaac.github.io/tutorials/quarto_text/SWOT.html#swot-spatial-coverage

You are welcome, we are glad that you find this tutorial useful for your work.

Excellent, we are glad to hear that you found this ArcGIS Image Service demo useful.

Thank you for providing feedback on our last webinar session. We appreciate your participation and are glad that you found this webinar content useful.

Thank you for your feedback, we are glad to hear that you found this session valuable for your work.

Absolutely!

Hi Edisca, Unfortunately, I’m unable to share my setup with you. However, I recommend starting by checking the salinity and temperature options in the Delft3D-FLOW GUI. Once selected, they will appear in the initial and boundary conditions settings. The process should be straightforward from there.

Thank you!!!

Hi, Have you successfully modeled salinity with delft3d 4?

Hi, for ENVI there is the EMIT Tool. I'm working on it too.

@@massimomorigi8575 what is the tool and Envi 5.6 version?

Thanks Mike! We appreciate the feedback.

Yes I can provide you some information on how to achieve this using EMIT methane data. Could you please email [email protected] with your query? Also, if you post your question to NASA's Earthdata Forum at: forum.earthdata.nasa.gov that query will benefit other data users as well. Thank you.

Hi there, thank you for your message. Were you trying to access the lake vector datasets, and so that I have the correct information, were you also using earthaccess for programmatic access? I will relay this message to our speakers and get back to you. Another option for assistance is to submit a query using NASA's Earthdata Forum (forum.earthdata.nasa.gov) We released an article on Earthdata about a month ago which outlines the Level 1 and Level 2 SWOT hydrology and oceanography datasets that are available. www.earthdata.nasa.gov/learn/articles/swot-data-release

Good afternoon- For the lake data download, try this notebook. It is demonstrated in section 2 of this page (link to notebook at top): podaac.github.io/tutorials/notebooks/datasets/SWOTHR_localmachine.html. I hope this helps!

Yes the Jupyter Notebooks used in the webinar can be found here: podaac.github.io/tutorials/quarto_text/SWOT.html

Hi there, I have some additional information for you. I reached out the speakers. Try these two examples with Fiona: podaac.github.io/tutorials/notebooks/DataStories/SWOTHR_Science_Application.html podaac.github.io/tutorials/notebooks/datasets/SWOTHR_s3Access.html

Hi there, the enhanced interface enables a smoother user experience with many functional enhancements. It also includes integrated climate reports. Notable improvements are expanded analysis-ready geospatial image services, interactive parameter selections, temporal charting, and an interactive swipe and comparison function for advanced data-driven needs. There also is Application Programming Interface (API)-based custom plotting, integrated climate reporting capabilities, and enhanced parameter selection with an integrated parameter dictionary. I hope this helps, however, I encourage you to reach out to the POWER team directly at: [email protected]

Hi there, thank you for your message. Has this issue been resolved? If not, we will look into it and get back to you.

​@@NASAEarthdata Hello thank you. Yes, indeed, there seems to be an issue ongoing. GNSS data haven't been receiving in realtime from the DYNG station for a while. Data source : cddis.nasa.gov/archive/gnss/products/realtime/jpl_ionosphere/2024/

@@NASAEarthdata Hello thank you. Yes, indeed, there seems to be an issue ongoing. GNSS data haven't been receiving in realtime from the DYNG station for a while.

@@elderizm I have asked the CDDIS to look into this. However, please always feel to reach out via the following options when you need assistance. Earthdata Forum: To interact with other users and NASA subject matter experts from across the DAACs on a variety of Earth science research and applications topics, including Space Geodesy, go to the Earthdata Forum.forum.earthdata.nasa.gov CDDIS User Support: [email protected]: Submit questions to this email address to log a ticket with their user support team. CDDIS GNSS real-time data castor help Email: [email protected].

@@NASAEarthdata Thank you. I will wait a bit longer for the issue to be resolved impatiently otherwise, I will send an e-mail. By the way I asked a question on the cddis forum page about a different topic two days ago but it's awaiting moderator approval. 😄 I'm glad there was faster interaction here. Thank you again and I'm grateful for what you're doing for humanity. 💙

Good morning, thank you for your comment. The best solution to receive user support for this specific issue is to reach out via our NASA Earthdata Forum at forum.earthdata.nasa.gov or send an email to NASA's Alaska Satellite Facility DAAC's User Services Office at: [email protected]

Hi! Do you solve the problem? I am new in InSAR, it would be nice if you can help me

@@paolamontenegro517 Thank you for reaching out to NASA Earthdata. What InSAR problem are you trying to solve? You can interact with SAR experts from the NASA Alaska Satellite Facility DAAC on our Earthdata Forum at: forum.earthdata.nasa.gov. Also, here are a few InSAR tutorial StoryMaps you might find useful: storymaps.arcgis.com/stories/68a8a3253900411185ae9eb6bb5283d3, storymaps.arcgis.com/stories/8be186e4125741518118d0102e6835e5 and there are InSAR tutorials at ASF DAAC here: asf.alaska.edu/how-to/data-basics/data-recipe-tutorials-2/

Hi Mohamed, you could order your data using AppEEARS at: appeears.earthdatacloud.nasa.gov/ and request the output as an .ENVI file. Also, you may reach out with this question via NASA's Earthdata Forum at: forum.earthdata.nasa.gov or by sending an email to the LP DAAC at [email protected] and they will work with you. We just held a webinar on how to use AppEEARS last week if you are interested. See: kzbin.info/www/bejne/Zp-uY3d8odGngKMsi=nQsh9aformyOTvqq

Hi there, thank you for your question. I have contacted the speaker for this webinar and she is looking into it. I should have a response for you shortly.

Hi Jose, I have a response from the speaker for you. For the Daymet files, time is defined as "days since ... " and in Daymet's case it's days since January 1st, 1950. We use Jan 1st, 1950 because in our Puerto Rico files we have data that start on Jan 1st, 1950. The North America and Hawaii files start Jan 1st, 1980, but we can have one start date for the whole dataset by starting in 1950. So that's 12,981.5 days since Jan 1, 1950. We use .5 to make it mid-day. Here's the full definition of time in a daily file: float time(time) ; time:standard_name = "time" ; time:calendar = "standard" ; time:units = "days since 1950-01-01 00:00:00" ; time:bounds = "time_bnds" ; time:long_name = "24-hour day based on local time" ; Software that understands netCDF files will usually interpret this to some calendar day that makes intuitive sense to us. I hope this helps, if not, please feel free to reach out to [email protected]

Hi there, here is a link to the Jupyter Notebooks at NASA's ORNL DAAC for working with GEDI data: github.com/ornldaac/gedi_tutorials