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
The availability of a lonlat file will help automate the data archiving process significantly, by creating the browse graphic automatically, etc. I wonder if we could add some instructions to the file uploading interface to alert users the importance of including a lonlat file.
For gridded data, they can simply create a lonlat file covering the four corners of the bounding box. For example something like the below:
-179.5 89.5
179.5 89.5
179.5 -89.5
-179.5 -89.5
Adding all grid points there could overcrawd our Oracle database and slow down the searching engine.
Thanks,
Liqing
The text was updated successfully, but these errors were encountered:
The availability of a lonlat file will help automate the data archiving process significantly, by creating the browse graphic automatically, etc. I wonder if we could add some instructions to the file uploading interface to alert users the importance of including a lonlat file.
For gridded data, they can simply create a lonlat file covering the four corners of the bounding box. For example something like the below:
-179.5 89.5
179.5 89.5
179.5 -89.5
-179.5 -89.5
Adding all grid points there could overcrawd our Oracle database and slow down the searching engine.
Thanks,
Liqing
The text was updated successfully, but these errors were encountered: