search

GeoEra-GIP / Project-Support-WP8

Science Project Data provider support
https://geoera-gip.github.io/support/
7 stars 2 forks source link

3DGEO-EU raster data in EGDI test environment #566

Closed caasox closed 2 years ago

caasox commented 2 years ago

Hello,

I have uploaded some raster data to the EGDI test plattform (tiff, EPSG 3034). Everything works fine, except some of the layers coupled to the map do not appear in the map. If I click on some spot where the layer should be visualized, the correct information is shown in the details window.

image

The ids of the layers are 10523, 10524, 10525.

Best regards,

Lars

nmtoken commented 2 years ago

Appears to be an issue with the platform, not your data.

Looking at https://egditest01.geus.dk/egdiadmin/dolayer.jsp?id=10525 and the error reported in the Mapserver-definition test is:

loadSymbolSet(): Unable to access file. (C:/mapserver/mapscript_inc/symbols/symbols.sym)

Full error:

<!doctype html>
<html lang="en">
    <head>
        <title>HTTP Status 500 – Internal Server Error</title>
        <style type="text/css">
            h1 {
                font-family: Tahoma, Arial, sans-serif;
                color: white;
                background-color: #525D76;
                font-size: 22px;
            }
            h2 {
                font-family: Tahoma, Arial, sans-serif;
                color: white;
                background-color: #525D76;
                font-size: 16px;
            }
            h3 {
                font-family: Tahoma, Arial, sans-serif;
                color: white;
                background-color: #525D76;
                font-size: 14px;
            }
            body {
                font-family: Tahoma, Arial, sans-serif;
                color: black;
                background-color: white;
            }
            b {
                font-family: Tahoma, Arial, sans-serif;
                color: white;
                background-color: #525D76;
            }
            p {
                font-family: Tahoma, Arial, sans-serif;
                background: white;
                color: black;
                font-size: 12px;
            }
            a {
                color: black;
            }
            a.name {
                color: black;
            }
            .line {
                height: 1px;
                background-color: #525D76;
                border: none;
            }</style>
    </head>
    <body>
        <h1>HTTP Status 500 – Internal Server Error</h1>
        <hr class="line" />
        <p><b>Type</b> Exception Report</p>
        <p><b>Message</b> loadSymbolSet(): Unable to access file.
            (C:&#47;mapserver&#47;mapscript_inc&#47;symbols&#47;symbols.sym)</p>
        <p><b>Description</b> The server encountered an unexpected condition that prevented it from
            fulfilling the request.</p>
        <p>
            <b>Exception</b>
        </p>
        <pre>java.io.IOException: loadSymbolSet(): Unable to access file. (C:&#47;mapserver&#47;mapscript_inc&#47;symbols&#47;symbols.sym)
    edu.umn.gis.mapscript.mapscriptJNI.new_mapObj(Native Method)
    edu.umn.gis.mapscript.mapObj.&lt;init&gt;(mapObj.java:280)
    org.apache.jsp.map_jsp._jspService(map_jsp.java:184)
    org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:476)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
    org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
</pre>
        <p><b>Note</b> The full stack trace of the root cause is available in the server logs.</p>
        <hr class="line" />
        <h3>Apache Tomcat (TomEE)/8.5.41 (7.1.1)</h3>
    </body>
</html>
nmtoken commented 2 years ago

@caasox as an aside, you say that the data is EPSG:3034, but the mapserver configuration has the projection as EPSG:4258

i.e.

METADATA
  "ows_title" "nls3d_near_base_rupelian_depth"
  "ows_abstract" "Auto generated data set"
  "ows_group_title" "EGDI"
  "ows_group_abstract" "EGDI"
  "ows_extent" "3742257.2230224 2797832.2998871 3864457.2230224 2991832.2998871"
  "wms_format" "image/png"
  "dataset_path" "/egdi/shared/datasets/3dgeoeu/nls3d_near_base_rupelian_depth.tif"
  "wms_srs" "EPSG:4258"
  "ows_metadataurl_format" "text/xml"
  "ows_metadataurl_href" "https://egdi.geology.cz/record/basic/60caf1f4-d25c-4971-b4d4-30f10a010833"
  "ows_metadataurl_type" "TC211"
  "wms_style_default_legendurl_href" "/egdi/get_legend.jsp?layer=10525"
  "wms_style_default_legendurl_format" "image/png"
  "wms_style_default_legendurl_height" "250"
  "wms_style_default_legendurl_width" "250"
  "ows_srs" "EPSG:4258"
  "ows_inspire_capabilities" "url"
  "ows_inspire_metadataurl_format" "application/xml"
  "ows_inspire_metadataurl_href" "https://egdi.geology.cz/record/basic/60caf1f4-d25c-4971-b4d4-30f10a010833"
END
PROJECTION
  "init=epsg:4258"
END
caasox commented 2 years ago

@nmtoken well...it seems that this was the problem. I dont't know why there was the wrong EPSG-code set in the mentioned data. However it works now, thank you for pointing this out.

nmtoken commented 2 years ago

Good that correcting the layer projection has sorted your issue, though I see the Mapserver-definition test still has an issue (not a problem for you).

You may note that the "ows_srs" and "wms_srs" can have multiple values, they just allow your data to be used at different projections in WMS/WFS/WCS services. you might have:

"wms_srs" "EPSG:3034 EPSG:3035 EPSG:3857 EPSG:4326 EPSG:4258 CRS:84"

"ows_srs" "EPSG:3034 EPSG:3035 EPSG:3857 EPSG:4326 EPSG:4258"