Skip to main content
Solved

Writing to MBTILES format doesn't inherit transparency

tara_he
Contributor
Forum|alt.badge.img+4

I’m trying to upload a raster to Mapbox, but no matter what I do, the output file always turns the nodata cells to black. I have tried fixing this using RasterBandNodataSetter and RasterPaletteResolver. If I look at the feature cached output from those transformers the nodata cells are still transparent. The issue arises when I use the MBTILES writer. No matter what, it writes nodata as black. I also tried removing the nodata (RasterBandNodataRemover), doesn’t work. I have tried outputting the data both as png, png8, and jpeg. Does anyone have any other suggestions? Thank you in advance!

Best answer by evieatsafe

Hi @tara_he I got some advice from a colleague and neither PNG or JPEG are great with transparency (especially JPEG). They suggest that you might have better luck using an alpha band instead of nodata values for representing the invalid parts of the raster. However, Alpha is not supported by JPEG so you will need to use PNG. You can generate an alpha band from nodata by using a RasterInterpretationCoercer or RasterPaletteInterpretationCoercer (especially if you have paletted data, which it sounds like you do) with the following settings:

  • Destination Interpretation Type = RGBA32
  • RGB to RGBA = Create alpha band from nodata

Let us know if this has different or desired results! 

View original
Did this help you find an answer to your question?

6 replies

evieatsafe
Safer
  • evieatsafeSafer
  • Safer
  • June 18, 2024

Hi @tara_he could you send a screenshot of what your MBTILES writer parameters look like? Specifically, which compression setting do you have: PNG or JPEG? This may have an impact on how your no-data values are displayed. If you have anything else you can share with us we might be able to look into it further. There doesn’t seem to be any documentation on how no-data is displayed in the output, only that “any [values are accepted; however,] all bands on a raster must have the same value”. 

Happy to help - Evie
tara_he
Contributor
Forum|alt.badge.img+4
  • tara_heContributor
  • Author
  • Contributor
  • June 19, 2024

Thanks for the offer of help @evieatsafe. Here is what I currently have.

I have tried PNG, PNG8, and JPEG, but I haven’t changed the PNG Compression Levels. All of my nodata cells have a value of 0 as defined by a Raster BandNodataSetter. When I have tried writing to JPEG, I do need to also use a RasterPaletteResolver. That is not necessary on PNG though. Thank you again. 

evieatsafe
Safer
  • evieatsafeSafer
  • Safer
  • Best Answer
  • June 19, 2024

Hi @tara_he I got some advice from a colleague and neither PNG or JPEG are great with transparency (especially JPEG). They suggest that you might have better luck using an alpha band instead of nodata values for representing the invalid parts of the raster. However, Alpha is not supported by JPEG so you will need to use PNG. You can generate an alpha band from nodata by using a RasterInterpretationCoercer or RasterPaletteInterpretationCoercer (especially if you have paletted data, which it sounds like you do) with the following settings:

  • Destination Interpretation Type = RGBA32
  • RGB to RGBA = Create alpha band from nodata

Let us know if this has different or desired results! 

Happy to help - Evie
tara_he
Contributor
Forum|alt.badge.img+4
  • tara_heContributor
  • Author
  • Contributor
  • June 20, 2024

That was it @evieatsafe! It makes so much sense now… I can’t believe I didn’t think of that before. I truly appreciate you and your colleague’s help. Oh, and yes, my data is paletted so I did need to use the RasterPaletteInterpretationCoercer. I honestly didn’t understand what that transformer even did. I’m so excited this is figured out. Thank you again!!

evieatsafe
1 person upvoted this
  • evieatsafe
    evieatsafe
froberts
Contributor
Forum|alt.badge.img+2
  • frobertsContributor
  • Contributor
  • February 3, 2025

​@evieatsafe and ​@tara_he  I am wondering if this is the same issue I am having.  I have tiff file that I have been provided when I run it through FME Workbench 2024.2 to create a mbtiles package, I get this strange black background, I assume it is the defulat tile for the area.  The orginal tiff only occupies the extent of what you see in the map itself below.  So the conversion is tacking on this huge black boundary.  Any ideas on how I make it not do that?  I have included a screen shot of my settings below.  Thanks for any ideas!!

 

 

r_huesken
1 person upvoted this
  • r_huesken
    r_huesken
r_huesken
Contributor
Forum|alt.badge.img+5
  • r_hueskenContributor
  • Contributor
  • March 11, 2025

I have a similar issue with 2024.2. In my opinion this was working in previous versions, yet I have no way to demonstrate this anymore...

The part of the tile that is not covered with data has a black background (where the red dot is) and I do not see a way to get around that...

 


​​​​​

 

Reply


Helpful Members This Week

Community Stats

31,223
Posts
118,401
Replies
38,824
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.