New answers tagged

2

If you work with timeseries, Postgis now have a native way to handle these: trajectory (it's based on LINESTRINGM, you can see for example in the link or in the first function you should use: ST_IsValidTrajectory). It does not have a lot of function (in my opinion), but in my understanding it can answer your problem. Once you have your lines transformed ...


0

This turned out to be relatively easy to answer. In Java, you can calculate the length of an epoch like this: public class epoch { public static void main(String[] args) { java.util.Date epoch2 = new java.util.Date(119, 3, 7); /* 7 Apr 2019 */ java.util.Date epoch1 = new java.util.Date(99, 7, 22); /* 22 Aug 1999 */ System....


1

This is the UTC time format according to the official source1, source2: The time reference system in the SRAL/MWR Level-2 products is the Universal Time Coordinated (UTC).


1

It is right there in the link you provided: The file naming convention of SLSTR products (see this document for more details) is identified by the sequence of fields described below: MMM_SL_L_TTTTTT_yyyymmddThhmmss_YYYYMMDDTHHMMSS_YYYYMMDDTHHMMSS_[instance ID]GGG[class ID].SEN3 [...] yyyymmddThhmmss is the sensing start time ...


Top 50 recent answers are included