Hi,
I want to import Sentinel 2 data but there is a problem. When i choose .SAFE data, granules part is not working. How can i fix it?
Thank you...
Date
Votes
9 comments
-
Clark Labs Official comment I am not sure why there aren't any tiles/granules showing up. If you'd like to send us the data to look at, submit a tech support ticket.
I do see one thing that looks different. Your output folder has the .SAFE extension. You might want a different output folder. But that wouldn't cause the tiles/granules to not appear, so that is not the solution.
Tammy
-
Gabriele Montesanto Hi, I have a similar error. I'm trying to import Sentinel-2 data, but I get the same message and the granules part is only showing R60, but it is not showing R20 and R10.
-
Gabriele Montesanto The weird thing is that I think that in the “Band to process” section all the bands are showing up (including the R20 and R10 ones), but if I select them all, only the R60 bands are actually processed.
Instead, if I try to select only some of the R10 or R20 bands, I get the error message: “Please select at least one granule and one tile to process.” -
Clark Labs I looked in the bug database and there is an open (unfixed) bug for it giving this error message if the full filename (path, including all subfolders, and filename) is too long. There is a 255 or 256 character limit to the filename that gets passed to the module, and Sentinel has such a long set of nested folders with long names, that this error is sometimes encountered . Unfortunately, the error message is misleading and doesn't give a clue to the problem.
The solution for now is to put the Sentinel file(s)/folder in a shorter beginning path, so that the filenames of the bands (granules) don't end up being longer than 255 characters.
-
Iris Hi,
I am still encountering this bug and have moved the .SAFE folder to my root directory to avoid the file path character limit. I have also checked the internal folder structure and made sure the metadata file is there and complete. Yet still, the import tool only recognises the R60m granule and not the R10m nor R20m. I'm using TerrSet liberaGIS version 20.0.4.
-
Clark Labs Hi Iris,
Is your root directory c: or d:? Or is it c:\users\username\?
Those extra 20 or so characters in the "users\<username<\" might be enough to push it over the 255 character limit.
How many characters are in the full path to the files inside the R10m folder (including the filename(s))?
I do acknowledge that we need to find a fix to this internally in the software, but for now, I'm trying to make sure you can use your data with the software as it is.
Tammy
-
Iris Hi Tammy,
Many thanks for your response. My folder path is as follows:
H:\S2C_MSIL2A_20250630T104041_N0511_R008_T32VNJ_20250630T161206.SAFE -
Clark Labs Hi again Iris,
I think I was wrong about the path length being the cause of your problem (and the similar problem that someone else had). It looks like there are some files that have a slightly differently formatted metadata file than what the Sentinel Import was expecting, and that is causing the R10m and R20m bands not to show up as options. I am working on fixing this, but will not get it completed by today. Hopefully on Monday.
Tammy
-
Clark Labs Hi Iris and Gabriele Montesanto,
I have a fix for this problem.
The structure of the metadata file for Sentinel data changed in 2016, and now all the resolutions are in the same granules section of the metadata, whereas formerly they were separated into granules based on resolution. This fix works for the files I have (and hopefully for all files).
I'm not quite ready for a full official patch/release (20.05 will be the next one), so I put the file impexp.dll into DropBox, which is temporary until I we publish the 20.05 release (probably in a couple of weeks). Here is the link to download impexp.dll, which you would put into your c:\program files (x86)\TerrSet liberaGIS\extensions folder. (or TerrSet2020 or TerrSet or TerrSet_liberaGIS, depending on the version you are using and where it is installed):
The important thing is that it goes into the extensions folder and overwrites the impexp.dll that is there.
Please let me know if this fixes your problem, or if you still have problems or have different problems.
Tammy
Please sign in to leave a comment.