I did a world map in Geoserver, showing in Leaflet in the default projection, which is EPSG:900913 (aka GOOGLE Mercator) but I would like to use the Mollweide projection instead.

I successfully added this grid in Geoserver:

Name: moll - EPSG:54009 - Extents: -19,844,105 / -9,922,053 / 19,844,105 / 9,922,053 - Tiles : 256x256 - Resolutions: 65,536 - 32,768 - 16,384 - 8,192 - 4,096 - 2,048 - 1,024 - 512 - 256 - 128

I applied the gridset to my layer collection in its settings, and I have a result that I accept, inside Geoserver pointing to the 54009 epsg:


enter image description here

And though I could load a json data in a Leaflet window, that wms layer won't work. I have working script links to "proj4js-compressed.js" and "proj4leaflet.js" and an exemple world countries layer "countries-110m.js"

map crs is set to

var crs = new L.Proj.CRS('EPSG:54009', '+proj=moll +lon_0=0 +x_0=0 +y_0=0 +datum=WGS84 +units=m +no_defs', {
    resolutions: [65536, 32768, 16384, 8192, 4096, 2048, 1024, 512, 256, 128] 

var map = L.map('map', {
    crs: crs,
    maxZoom: 8

The Geojson is loading :

L.geoJson(countries, {
    style: {
        color: '#000',
        weight: 0.5,
        opacity: 0.2,
        fillColor: '#fff',
        fillOpacity: 0.2

enter image description here

the WMS tilelayer is not:

var mapbase = L.tileLayer.wms('http://mappingforyou.eu/geoserver/wms?', { 
       layers: 'pays.monde', 
          maxZoom: 20, 
           crs: crs,
        format: 'image/png', 
                attribution: '↖Menu . Categories↗)' 

The browser console is not showing any error. Can you help me please?

  • You need to turn up the logging level to developer in the global settings page, and then make the request again. Then edit your question with the relevant part of the log file.
    – Ian Turton
    Jan 13, 2022 at 12:00
  • @IanTurton If I understand question correctly, problem is not in GeoServer part, but in WMS tile layer from mappingforyou.eu/geoserver/wms.
    – TomazicM
    Jan 13, 2022 at 16:08
  • @TomazicM - that's hard to tell with out the log file
    – Ian Turton
    Jan 13, 2022 at 16:49
  • This is a webserver setup problem. Geoserver is running on port 8080, not on the default 80/443. Combine that with browsers nowadays aggressively switching to HTTPS. BTW your browser console might not be showing any errors, but I betcha that the network tab of the browser's developer tools sure is. Jan 13, 2022 at 22:16

1 Answer 1


I think the issue might be that Mollweide projection is defined as ESRI:54009 , and not EPSG:54009 (see: https://epsg.io/54009). If you've still got this issue, perhaps give that a go?

  • GeoServer is at present stuck on EPSG, it cannot use any other authority (funding to unlock this welcomed). Oct 18, 2022 at 8:16
  • Ahh... thanks for clarifying. I wonder if that's what's causing the problem, because Mollweide (as far as I understand) is not part of the EPSG standard. It might be something else, but I ran into some issues recently so posted this suggestion as an obvious one to check, since it hasn't been mentioned.
    – Carl Higgs
    Oct 21, 2022 at 10:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.