You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am finding problems with the variable OSSequenceNumber.
I thougth this variable needed to be unique in each strata, reflecting the order os selection. In our case this order is not so relevant, as the selection methods is "NPQSRSWOR". But anyway, the upload is giving problems due to duplicates in this variable, but they are not real duplicates as the belong to different strata
You can find an exampe in the table below
Thanks!
The text was updated successfully, but these errors were encountered:
It has been agreed that each Onshore Event under a Design record should be uniquely by having a different OSsequenceNumber. At this point it will not be changed, but it can be taken up for discussion. Right now it is suggested to increase the OSsequenceNumber by one for each new Onshore Event.
The Core Group will go through the sequenseNumber for the Onshore Event, but more tables will be included in this task, we will return at a later date.
I am finding problems with the variable OSSequenceNumber.
I thougth this variable needed to be unique in each strata, reflecting the order os selection. In our case this order is not so relevant, as the selection methods is "NPQSRSWOR". But anyway, the upload is giving problems due to duplicates in this variable, but they are not real duplicates as the belong to different strata
You can find an exampe in the table below
Thanks!
The text was updated successfully, but these errors were encountered: