uDIG
  1. uDIG
  2. UDIG-373

WMS renderer does not render layers that have a fixed size

    Details

    • Type: Bug Bug
    • Status: Analysis Analysis
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: UDIG 1.0.RC1
    • Fix Version/s: UDIG 1.4.1
    • Component/s: webservices
    • Labels:
      None

      Description

      Unable to render a layer of a fixed size:

      http://aes.gsfc.nasa.gov/cgi-bin/wms?%20SERVICE=WMS#3112_223

      <Layer opaque="1" noSubsets="1" fixedWidth="1024" fixedHeight="1024">
      <Name>3112_223</Name>
      <Title>Aral Sea Evaporation (1024x1024 Animation)</Title>

      org.geotools.ows.ServiceException: WIDTH=387 is invalid for 3112_223. Should be 1024.
      at org.geotools.data.wms.xml.WMSComplexTypes$_ServiceException.getValue(WMSComplexTypes.java:4715)
      at org.geotools.xml.handlers.ComplexElementHandler.endElement(ComplexElementHandler.java:155)
      at org.geotools.xml.XMLSAXHandler.endElement(XMLSAXHandler.java:210)
      at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.dtd.XMLNSDTDValidator.endNamespaceScope(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
      at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
      at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
      at javax.xml.parsers.SAXParser.parse(Unknown Source)
      at javax.xml.parsers.SAXParser.parse(Unknown Source)
      at org.geotools.xml.DocumentFactory.getInstance(DocumentFactory.java:139)
      at org.geotools.data.wms.response.AbstractResponse.parseException(AbstractResponse.java:65)
      at org.geotools.data.wms.response.AbstractResponse.<init>(AbstractResponse.java:48)
      at org.geotools.data.wms.response.GetMapResponse.<init>(GetMapResponse.java:39)
      at org.geotools.data.wms.WebMapServer.internalIssueRequest(WebMapServer.java:351)
      at org.geotools.data.wms.WebMapServer.issueRequest(WebMapServer.java:370)
      at net.refractions.udig.render.internal.wms.basic.BasicWMSRenderer.issueRequest(BasicWMSRenderer.java:459)
      at net.refractions.udig.render.internal.wms.basic.BasicWMSRenderer.render(BasicWMSRenderer.java:184)
      at net.refractions.udig.render.internal.wms.basic.BasicWMSRenderer.render(BasicWMSRenderer.java:740)
      at net.refractions.udig.project.internal.render.impl.RenderExecutorImpl$RenderJob.startRendering(RenderExecutorImpl.java:196)
      at net.refractions.udig.project.internal.render.impl.RenderExecutorImpl$RenderJob.run(RenderExecutorImpl.java:223)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

        Issue Links

          Activity

          Hide
          Jody Garnett added a comment -
          This has been shuffled off to the uDig 1.1.1 release as we think it is fixed; but if not it is not worth holding the release up for.
          Show
          Jody Garnett added a comment - This has been shuffled off to the uDig 1.1.1 release as we think it is fixed; but if not it is not worth holding the release up for.
          Hide
          Jody Garnett added a comment -
          I am not sure where to check if this has been fixed or not? Is there a sample service to check against?

          The origional way to handle this was with a second WMS Renderer that would deal with fixed sized wms servers (by making several requests and tiling them all together).
          Show
          Jody Garnett added a comment - I am not sure where to check if this has been fixed or not? Is there a sample service to check against? The origional way to handle this was with a second WMS Renderer that would deal with fixed sized wms servers (by making several requests and tiling them all together).

            People

            • Assignee:
              Unassigned
              Reporter:
              Richard Gould
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: