gee-ntl-date-boundary-handling

You compute night-time lights statistics by defining baseline, first-night, and recovery windows around an event using VNP46A2 data, then performing region reductions over AOI buffers to extract temporal impact metrics.

End-exclusive date handling in GEE uses filterDate to define inclusive start dates while excluding the end date, preventing overlapping NTL observations between adjacent analysis windows. This ensures temporal boundaries remain strictly separated.

GEE reduceRegion computations fail when analyzing large AOI buffers due to exceeding pixel limits or scale constraints. Enforce safety parameters by explicitly setting scale, maxPixels, and tileScale to prevent run-time failures during region reduction.

Yes, you can calculate NTL statistics for multiple buffer distances such as 25, 50, and 100 kilometers around an epicenter. The analysis applies confirmed boundary geometries to ensure reliable region reductions across all buffer zones.

The best way to handle uncertain AOI boundaries is to rely on confirmed boundary geometries or generate explicit spatial buffers around a known point like an epicenter. This boundary verification ensures safe and reliable data extraction.

Yes, you need the earthengine-api to access and process VNP46A2 data and pandas to structure the resulting NTL statistics. These dependencies facilitate computing the reductions and exporting the final date-boundary analysis to CSV.