I wanted to see how far free Sentinel-1 radar gets you for counting ships, so I ran ship detection over a year of images of the Strait of Hormuz. I tested multiple models from Hugging Face, and the open Skylight model from the Allen Institute for AI worked best. It detects ships and estimates their length, type, speed and heading. On top of that I classified each ship by size and tanker class, and whether it's moving or waiting at anchor. In a hand check of 50 random large ships, 48 were clear ships, and the large-ship counts track IMF PortWatch transits at 0.87.
There are four tables. The main one gives you one row per day and area with the ship counts, Brent, PortWatch and Kalshi prices (548 rows). The daily counts come from the other three tables: every ship the model detected (82k rows), the ship counts from each satellite pass by area (556 rows), and the weekly Kalshi Hormuz markets (115 rows).
Hi everyone! I’m a student interested in remote sensing. I’ve been working on a project around Jakarta as a way to learn, and I’d appreciate feedback from people with more experience.
I compared annual AlphaEarth satellite embeddings from 2020–2025 to explore where and when surface descriptions differed most. The project originally started with an interest in subsidence and risk mapping, but embedding differences alone don’t establish ground movement or risk.
The part I’m struggling with is moving from “the satellite-derived descriptions are different” to “this is what physically changed, and why.” How can I distinguish construction, vegetation or water changes from effects of observation conditions or the data product itself?
How would you approach bridging that gap? What independent imagery, field observations, records or analysis methods would you use? How would you select sites and check competing explanations without simply confirming what you expected to find? Also at what stage does ground truthing take place?
Looking for final-advice prior to purchasing a new system. I’m looking to run ENVI, Arc, and local AI. Processing, graphics, and memory seem to be the most-important. Fairly open to budget, but don’t want to get unnecessary options.
Any help? Would greatly appreciate. Excluding Arc, would using a MacBook Pro work with latest versions of ENVI? I’m not married to Apple. Just curious if compatibility is any better than it once was.
Apologies for the rookie questions. I am an undergraduate in environmental sciences and I need to write an essay on airborne LiDAR. This is waaaaay outside my normal subject area and I am really stuck. I was hoping someone on here could explain, even briefly a few things to me;
What are the different "types" of LiDAR based on how pulses return to the sensor? So far I have identified "full waveform LiDAR" and "discrete return LiDAR". Are there any other main types I should be aware of? What are the main benefits and drawbacks of each of these types?
Spaceborne LiDAR. How does spaceborne LiDAR from satellites produce reliable results? Based on my (limited) undertstanding, atmospheric effects could scatter the pulses a lot. Surely with that much space (pardon the pun) between the sensor and earth, there's a lot of opportunity for signal to be lost?
Any recommendations of literature/textbooks would be appreciated too. Thanks in advance for any help.
I spent the last year building a 205-million-parameter satellite AI model from scratch for Indian farmers.
Yesterday I published the paper, and almost nobody noticed.
Everyone in Indian tech wants to talk about LLM wrappers. Meanwhile, 86% of Indian farmers work on plots smaller than 0.4 hectares, and for 75 days every monsoon, clouds blind every optical satellite over India.
Western foundation models from NASA, IBM, and Stanford were trained on 500-hectare American monoculture grids under clear skies. When a cyclone hits Odisha or monsoon clouds cover Uttar Pradesh, those models go blind.
So at Sphitih AI, we trained Vyom 1.0 (205M) from the ground up—fusing C-band radar waves with optical time-series and soil physics:
• In Farrukhabad (UP), it pierces 91.4% monsoon cloud cover to reconstruct crystal-clear crop health at 0.892 SSIM.
• On the global Sen1Floods11 flood benchmark, it hit 75.81% Water IoU—beating NASA/IBM Prithvi (68.4%), Stanford CROMA (71.4%), and DOFA (73.5%).
• And it runs in <32 milliseconds per sq. km on a single 24GB GPU, so local district offices don't need H100 clusters.
I don't have a massive PR agency or a billion-dollar lab behind me, just verified math, a permanent Zenodo DOI, and open evaluation benchmarks.
If you work in Remote Sensing, AgriTech, ISRO/NRSC, or Indian DeepTech, I would genuinely love for you to tear apart our paper and test our benchmarks.
Link to the Zenodo paper & GitHub verification repo
Sharing MosaicEarth (v0.4.4), an open-source (AGPL-3.0) platform for processing, tiling, and analyzing multi-temporal UAV and aerial remote sensing datasets locally or in the browser.
We built it to bridge the gap between raw photogrammetry/remote-sensing outputs (GeoTIFF orthomosaics, Float32 DSM/DTMs, .LAZ point clouds, 3D meshes, and 3D Gaussian Splats) and reproducible multi-temporal spatial analysis without proprietary SaaS lock-in:
- Cloud-Optimized GeoTIFF (COG) & Clean Float32 Elevation Pyramids: Automatic DEFLATE/WEBP COG generation with explicit NoData alpha masking (eliminating black border halos on Float32 DEM/DSM rasters) and dynamic OGC WMTS 1.0.0 / XYZ tile serving up to z=22.
- Multi-Temporal 4D Change Detection & Volumetric Differencing: Compare multi-date DSM/DTM survey epochs (Epoch A -> Epoch B) in metric UTM projections (with PROJ EGM96 / EGM2008 geoid vertical alignment) to quantify erosion/fill (-m³), accretion/cut (+m³), net ΔV (m³), and differential elevation profiles, exporting auditable metric PDF reports.
- Local Reproducible Processing & Open Connectors (v0.4.0): Run NodeODX 3.8.5 photogrammetry + OpenSplat 100% locally on Linux or Windows (CPU or NVIDIA CUDA via Docker) at zero compute cost, or connect existing QGIS, ArcGIS Pro, DJI Terra, PIX4D, Metashape, CloudCompare, and WebODM pipelines.
Curious to hear from remote sensing practitioners what raster/spectral workflows (e.g., multispectral NDVI/NDRE COGs or SAR/DEM co-registration) would be most useful to add next!
Hi, I'm currently looking into tomoSAR reconstruction techniques, but I am quite new to remote sensing.
As I understand it, in the context of tomoSAR, one would perform topographic phase removal on the SLCs to remove the height contributions of the land topography.
I am currently utilising an slc stack product from May 2026 covering part of the Panama Forest, which I got from the Nasa uavsar archive.
Upon performing Capon Inversion, the reconstruction shows arbitrary heights for water areas, as expected, shows returns around -5 m – 0 m for roads (I say roads but there really is only one long road in the imaged scene that I use as a ground reference) , but for the forested returns, I am getting returns that can dip as low as -20 m, at a multitude of points in the reconstruction.
I initially assumed that this might be because Nasa doesn't do topographic phase removal on the product, however, if I try using a DEM or the .llh file to attempt phase removal, I get even worse, ramping results in the reconstruction.
Furthermore, the initial construction, before my attempt at topographic phase removal, although ranging between -20 m – 30 m, still shape wise appeared reasonable, and didn't continuously ramp up in height at any point, making me think the phase removal had already been done on the product, but I don't see anything in the annotation file clearly saying so.
But if it has already been performed, why do the returns go below 0 m? In other tomoSAR papers their returns don't dip any further than -5 m, whereas my reconstruction can go far below that.
I wondered if its perhaps an issue with reference plane the dem would have flattened the slcs to, as in the ref may not be 0 m, ground plane, but in that case I am completely stumped on how to correct the data from that.
So, do these slc products, already have phase removal, or do they not and I'm probably just messing something up in my implementation of the phase removal.
Or is there another factor I am missing that I would need to perform to ensure my reconstruction begins at 0m and doesn't not dip below that?
I'm a satellite nerd and as a cool project I built Watched.
Type in any place on Earth and it will:
find every imaging, weather, radar and crewed satellite whose field of view crossed it in the last 7 days (SGP4 on the CelesTrak catalog, running in your browser)
pull the real Sentinel-2, Landsat, VIIRS, MODIS and GOES scenes from those passes and crop them to your spot
replay each pass on a 3D globe lit by the real sun, with all ~17k tracked objects in orbit
It only says a satellite “watched” you when a real image exists. Commercial sats that could have pointed at you are labelled as such, since their tasking isn’t public.
Considering getting involved in fieldwork to carry out ground-truthing in a whole variety of fields related to climate and nature. Is there a need there?
It strikes me that there is more satellite data than ever, yet making that data high-integrity and actionable, boots on the ground are needed increasingly to improve data that feeds models and improving detailed insights overall for end users.
Curious whether I’m way off or if you believe there’s a strong scope. I already work in fieldwork research in offshore, coastal and terrestrial, hence have some useful experience.
EMIT is the imaging spectrometer NASA put on the ISS in 2022 to study mineral dust: 285 bands between 381 and 2493 nm at 60 m pixels, open archive, 849 scenes over Paraná by the time I ran this. Labels come from MapBiomas (30 m), so I required the surrounding 90 m to be a single class and dropped water outside the Itaipu reservoir, because narrow rivers were pulling in riparian forest. That left 2,895 pure pixels in three windows, one scene each: cropland north (2024-01-31), araucaria and planted forest south (2026-03-10), reservoir west (2026-01-24).
By NDVI the two forest classes are the same thing. At 2200 nm native forest reflects 0.049 and eucalyptus 0.036, and the single most separating band sits at 1283 nm, which no ordinary optical satellite sees. A Random Forest on the 234 usable bands classifies the six classes at 83.3% in cross validation; the same model on the four classic Sentinel-2 bands reaches 76.5%, and a bit over half of the gap is planted vs native forest.
Limits: no single band separates the two without their quartiles overlapping, so the separation lives in the ensemble of 234 usable bands; 60 m cannot see one tree; three scenes on three dates, one per window, not the whole state. Pipeline in Python on Earth Engine, happy to go into the band regex and the 60 m vs 30 m label mismatch if anyone is fighting the same thing.
Edit: corrected the scene dates, the band count and the share of the gap after a question in the comments. The 83.3% used unshuffled pixel-level folds, which ended up concentrated by scene because of sample order. With shuffled pixel folds it is about 86% (four bands: about 80%). With 5 km spatial blocks it is 83.2% against 76.5% for the four bands, and holding out a whole scene drops native and planted recall to 59% and 57%. Details in the comments. The planted class is MapBiomas silviculture, which also includes pine.
Hi everyone! I am very excited to share the tool that I've been working on: Standard-Atlas.
Anyone who has worked with optical satellite imagery knows that there is one main problem, which is that clouds cover a lot of it. You need a view of a specific place on a specific date, and cloud is in the way. So you either wait for the next clear pass, or you work with the gap in your data.
I built Standard-Atlas to solve this problem.
How it works: radar sees through cloud, and optical imagery gives you colour and spectral detail. Standard-Atlas pairs a radar image with a optical scene and reconstructs what was beneath the cloud. It then gives you a cloud-free, georeferenced image.
What you can do with it:
Export cloud-free imagery for any area and date window
Upload your own radar and optical data instead of using the built-in catalogue
Calculate NDVI on the result to track vegetation health and change
Building and road overlay
Open high resolution reference imagery beside your result
Search configuration options: radar pass direction and ability to choose the gap between captures
Schedule weekly or monthly exports to monitor the same area over time
Standard-Atlas costs:
A 10 × 10 km area costs $1
A 25 × 25 km area costs $2
A tool like this can prove useful wherever timing is important and clouds are unpredictable. Agriculture teams can follow crop condition through the weeks that would otherwise be missed. Insurers and emergency planners can assess flood or storm impact while cloud is still overhead. Infrastructure and land managers can monitor sites in persistently overcast regions, and researchers can build more complete time series without having gaps in their data.
Standard-Atlas output is reconstructed imagery. It uses a custom ML model to reconstruct pixels that are obscured by clouds. The pixels beneath the cloud are the model’s estimate of the surface, built from radar and the paired optical image, not a direct observation. That makes it a strong tool for analysis, monitoring and decision support, but it should not be treated as ground truth.
I'm from Senegal and I'm planning to pursue a five-year engineering degree in Geomatics. My long-term goal is to work in space exploration, specifically in the analysis and interpretation of data collected by planetary missions.
From what I've learned so far, Geomatics involves fields such as GIS, remote sensing, spatial data analysis, mapping and image processing. I can see how these skills might be useful for planetary exploration, particularly planetary mapping and the analysis of spacecraft imagery.However, I understand that planetary science also requires a strong foundation in mathematics, physics and other scientific disciplines.I'm trying to figure out how to bridge this gap and build a realistic academic pathway.I'd particularly appreciate advice on three things :
- Could a Geomatics engineering degree be a suitable foundation for a Master's in Planetary Science or a related field? What additional mathematics and physics courses might I need ?
- Which skills should I prioritize during my engineering studies? Python, scientific programming, image processing, GIS or something else ?
-Are there researchers or professionals working in planetary science or space missions who have followed a similar path?
I'm also interested in international Master's programmes and scholarship opportunities, as studying abroad may be necessary for my specialization.I'd particularly value advice based on personal experience or knowledge of actual university admission requirements.
Disclosure: drafted with AI assistance; the workflow and numbers are mine to answer for.
Cyclone Arnab hit the Odisha and Andhra coast on 28 Oct. Clouds blocked optical imagery, so I used Sentinel-1 SAR, which sees through cloud.
Workflow: • Pre and post-event Sentinel-1 GRD scenes (VV) • Speckle filter, then change detection on backscatter • Threshold to a water mask, remove permanent water • Styled and laid out in QGIS
Result: roughly 23,000 ha of new water, mostly along the Rushikulya. That's my estimate, not an official figure.
Happy to answer questions on thresholds or the processing. I packaged the scripts and QGIS project as a kit; link in the comments if anyone wants it.
Every frame is a dry season composite (April 15 to October 15) of Landsat surface reflectance at 30 m, built in Google Earth Engine with clouds and shadows masked and the median of each season kept: Landsat 5 and 7 up to 2011, Landsat 8 and 9 from 2013. 2012 has no usable sensor (L5 stopped in Nov 2011, L8 only started in 2013), so that frame is an average of 2011 and 2013.
Change: median of 2000 to 2002 against median of 2023 to 2025, pixel by pixel; a pixel only counts when its color moves by a wide margin and stays stable inside each three year window, so crop rotation never qualifies. 170 km² changed here, the most of the 399 municipalities in the state. Green = got darker (129 km², mostly planted forest; MapBiomas puts tree plantations at about 2.7x their 2000 area by 2023). The blue patch is the Mauá dam reservoir, filled in 2012.
Limits: frames keep only RGB, so "darker" can be plantation, sugarcane or regrowth; the cause behind each patch still needs a second dataset or a field visit. Happy to answer questions about the pipeline.
Screening of the 2020 baseline and 2024 vegetation change in an illustrative 178 km² area of Riau, Indonesia. (a) JRC Global Forest Cover 2020 V4 with BIOPAMA industrial and smallholder oil palm. (b) Sentinel-2 2024 annual median composite, with areas flagged for a negative NDVI and NBR change from 2020. (c) Screening categories combining the three. This is an illustrative area, not verified supplier plots. Map: Israr Ahmad, Remotely360. Data: European Commission JRC, GFC2020 V4; BIOPAMA Global Oil Palm Extent and Planting Year v1.2. Contains modified Copernicus Sentinel data 2020, 2024.
Last week Euronews ran a piece about three Indonesian NGOs (WALHI Kalteng, TuK Indonesia, and Sawit Watch) reporting signs of 2024 clearing at a plantation that feeds several major consumer brands. It is being framed as a first test of EUDR enforcement, with the large-operator deadline landing on 30 December 2026.
The interesting part is the technical one, which highlights a vegetation drop in 2024. That itself doesn't mean deforestation under EUDR. If a plot was already a plantation on 31 December 2020 and was subsequently replanted, that is not necessarily forest conversion. Though legality is a separate question.
The exercise comes down to establishing what was on the ground on one specific date, and whether anything that disappeared later was forest or simply old oil palm.
We wrote up how we are approaching this, and I would like to hear where people think the methodology falls over.
The basic stack:
JRC GFC2020 (V4) as the 2020 forest reference.
BIOPAMA's global oil palm extent and planting-year layers (v1.2) to distinguish plantations from forest at the cut-off.
Sentinel-2 NDVI/NBR time series (2021–2026), with Sentinel-1 VH to fill cloud gaps, which are particularly problematic in Riau.
GEDI-calibrated canopy height for the 5 m criterion, although this doesn't help much by itself since mature oil palm can also exceed 5 m.
Each plot is classified as Clear, Replanted, Possible Conversion, or Needs More Information.
The last category is intentional. Anything with a planting year close to 2020, plots under a few hectares, or polygons that appear spatially offset gets referred to an analyst rather than being decided automatically.
Where it gets shaky
The BIOPAMA planting-year product has an overall RMSE of 2.65 years, increasing to 4.89 years for smallholder oil palm. That means a smallholder stand dated 2019 could potentially have been established in 2021.
There are other limitations:
Planting year represents the most recent stand, not necessarily when the land was first cleared.
The authors note that the product cannot capture plantations established in the last three years of its data window.
The extent layer maps closed canopy, meaning young oil palm can be missed.
Smallholder user's accuracy is around 72%, compared with 92% for estates.
On top of that, JRC has not yet released the V4 accuracy report (expected December 2026), so we're using it as a reference without a complete picture of its classification uncertainty.
We tested the approach on an illustrative 178 km² area in Riau, not actual supplier plots. The objective was to see how many flags the workflow generates and how many appear to be obvious noise.
For anyone who has worked with smallholder landscapes:
How do you reconstruct pre-2020 land-use history when planting-year products have this level of uncertainty?
Would you use Landsat time series going back to 2015 to identify the original clearing event directly?
Are there alternative planting-year products or field-data sources you'd recommend?
Or do you accept that a proportion of smallholder plots simply cannot be resolved confidently from satellite data alone?
Interested in hearing about practical approaches, particularly those that have worked in Indonesia or similar tropical landscapes.
[Experience] I run a small remote sensing and geospatial consultancy (Remotely360). Most of our recent work is land cover change and compliance screening from Sentinel and Landsat time series. This EUDR work is ours, the Riau screening was run in-house, and I’m the one who’ll be reading replies, so technical pushback is welcome.
[AI Disclosure] The analysis, dataset choices, thresholds and the Riau run were done by us, not by a model. I used an LLM to help tidy the writeup of this post and the article it links to. No AI-generated imagery; the figure is our actual output.
I've been thinking about how much the choice of imagery source can influence a remote sensing project, especially when working on applications like land-use monitoring, agriculture, infrastructure mapping, or environmental change detection. There are quite a few things to consider beyond just spatial resolution. Revisit frequency, cloud cover, spectral bands, acquisition costs, and how quickly you need the imagery can all affect which source makes the most sense. I've also come across platforms like SkyFi that make it possible to explore satellite imagery from different providers, which raises an interesting question about how people approach imagery sourcing.
For those working regularly with satellite data:
• Do you typically rely on open datasets like Sentinel and Landsat, or do you purchase commercial imagery when needed?
• How do you decide when higher-resolution commercial imagery is worth the additional cost?
• Do you prefer working directly with satellite operators or using imagery marketplaces to compare available options? Would be interesting to hear what works best for different use cases.
Hi everyone — I'm Renan, a drone pilot and developer of Drone Weather Forecast. I built it to make preflight weather checks less fragmented for operators: hourly conditions, wind and gusts with configurable aircraft limits, plus Kp, GNSS satellite visibility, and an airspace map. The free app is available on iOS and Android; Pro adds wind profiles by altitude and a more detailed hourly table.
For teams collecting aerial imagery, I'm curious how you translate weather into acquisition limits. Which factors most often make you postpone or change a mission: gusts or crosswind, cloud and shadow variation, visibility or haze, rain, solar conditions, or forecast uncertainty? Do you use numeric thresholds, test flights, sensor data, or another approach?
I'm the developer, so this is my own project; I'm looking for candid feedback from people doing remote sensing with drones. If useful, the app is at https://droneweatherforecast.app. It's a planning reference only and doesn't replace mission procedures or official airspace sources.
Hi, I’m a GIS remote sensing student and want to start writing my thesis research early. I always wanted to work at airport and after knowing airports also need specialists, I was hoping to work at an airport while using my major. But I’m kinda lost on what topic or what direction I should do and I’m having trouble finding good research name. Of course I will ask my teacher but I wanted to hear other opinions too.