No announcement yet.

Tiled Image Layer from EPSG:3857 tiles

  • Filter
  • Time
  • Show
Clear All
new posts

  • Tiled Image Layer from EPSG:3857 tiles

    i would like to display a tiled Image layer from tiles, which come in an EPSG:900913 (probably better known as EPSG:3857) projection.
    The WMS is with the openaip_basemap as layer.

    I can either use a WMSTiledImageLayer, but the only projection the server supports, is EPSG:900913.

    Or i can also use a BasicMercatorTiledImageLayer and use the tile URL directly (with a custom TileUrlBuilder)/

    I use the latter approach already to display tiles from , and it seems to work well.

    I manage to see the tiles on my map, however the projection is wrong and the tiles don't show up where they are supposed to be.

    Could someone provide me a solution or a hint of how to achieve this?

    Best regards,

  • #2
    Please what do you mean by 'projection is wrong' ? Are there just slight shifts on the coasts or on the poles (all ok at the equator?). There might be a problem of "datum-shift" at high zoom.
    Or are tiles completely messed up ? A screenshot would help.


    • #3
      i mean, that the tiles are completely messed up. in the second screenshot you can see slightly above center LIRE and LIRA, which are Airports of Rome. The tiles are actually placed in the middle of the Atlantic ocean also don't even seem to be consistent (hard edges). When i zoom in to this specific area, the tiles also change slightly, e.g. LIRE jumps. The first screenshots also shows that everything is clearly out of place.
      Those tiles are loaded by using the tile url directly (I know its not very good style).

      Using WMS and a modified Version of WMSTiledImageLayer (I have to set the SRS parameter in the URL manually to EPSG:3857) I see only black (transparent) tiles are loaded, but never any content on the map. If I used the standard WMSTiledImageLayer class, then i get a server error ( it does not accept the provided standard SRS).


      • #4
        According to your screenshots, it seems you changed the display projection, no ? It looks like it is not the standard globe display. If you change/mix projections of basemap AND data, you must be in big trouble. WWJ works well with 4326 (geographic). If you want to use directly the 900913 (GooGle) or Mercator, you may find in this forum some experimental code that processes the tiles on-the-fly.


        • #5
          Thank you for your reply.
          This is definitely the standard globe, we also display live aircraft tracks and so on, so from this side I am good.

          wwd = new WorldWindowGLCanvas();
          wwd.setModel( new BasicModel() );
          The problem is surely the different projection of the additional tiles i want to display.
          Which is exactly my question: How could I transform them on-the-fly?, or at least which method would I need to modify to transform the Mercator tiles to standard geographic tiles


          • #6
            Try the BasicMercatorTiledImageLayer It should work with the EPSG:3857. The OSMMapnikLayer extends it for properly displaying OSMs mercator projection.
            World Wind Team


            • #7
              It has been sorted out support for full WMS-layers by combining the map boundingbox with top level events. However it would be really nice with more top-level events, like 'PanFinished', 'ZoomFinished', etc. as the current events are raised before the map is finished with zooming/panning (an alternative could be access to map state). For example a WMS request triggered by 'ZoomChanged', would offset the image if the zoompoint is not center of previous zoomlevel.

              This might actually be a bug, as it seems that the new calculated boundingbox does not take into account the mouse offset from center coordinate when zooming to mousepointer.


              • #8
                Did you finally get to display the OpenAIP correctly, extending BasicMercatorTiledImageLayer ? I tried to, and did not succeed, cause the tiling numbering seems to be different, and leads to the very same shifts that you observed, chris. With the very standard globe, sorry for that.
                I think it has to deal with the TMS/WMTS standards that are implemented so far in the web version, but not in the java one.
                I discovered recently that some other famous navigation systems had their own tiling calculations... But this one is not the default ("(1 << (tile.getLevelNumber()) + 3) - 1 - tile.getRow())" is the key point)
                Last edited by frenchy; 07-15-2017, 11:17 AM.


                • #9
                  Or are tiles completely messed up ? A screenshot would help.