[#UDIG-377] Error transforming bbox

uDIG

Error transforming bbox

Created: 27/Mar/05 08:03 PM Updated: 06/Mar/09 05:56 AM

Component/s:

file format, webservices

Affects Version/s:

UDIG 0.9

Fix Version/s:

UDIG 1.0.RC1

File Attachments:

None

Image Attachments:

1. error transforming bbox.jpg
(95 kB)

Environment:

uding 0.9.2.SC1, with shapefiles included with the release and dms solutions park layer and digital eath coastlines

Description

« Hide

The shapefiles displayed until the wms layers were added.

add swamps
add streams
add rivers
add lakes
add parks
add COASTLINES

See attached screensnap and stack trace.

!ENTRY net.refractions.udig.project 2 0 2005-03-27 16:54:58.331
!MESSAGE java.lang.Exception: Error transforming bbox
!STACK 0
net.refractions.udig.project.render.RenderException: java.lang.Exception: Error transforming bbox
at net.refractions.udig.render.internal.feature.basic.BasicFeatureRenderer.render(BasicFeatureRenderer.java:91)
at net.refractions.udig.render.internal.feature.basic.BasicFeatureRenderer.renderAll(BasicFeatureRenderer.java:167)
at net.refractions.udig.render.internal.feature.basic.BasicFeatureRenderer.render(BasicFeatureRenderer.java:214)
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)
Caused by: java.lang.Exception: Error transforming bbox
at org.geotools.renderer.lite.LiteRenderer2.queryLayer(LiteRenderer2.java:508)
at org.geotools.renderer.lite.LiteRenderer2.paint(LiteRenderer2.java:402)
at net.refractions.udig.render.internal.feature.basic.BasicFeatureRenderer.render(BasicFeatureRenderer.java:89)
... 5 more
Caused by: org.geotools.referencing.operation.projection.PointOutsideEnvelopeException: Latitude 102°52.9'N is out of range (±90°).
at org.geotools.referencing.operation.projection.MapProjection.transform(MapProjection.java:606)
at org.geotools.referencing.operation.projection.MapProjection.transform(MapProjection.java:659)
at org.geotools.geometry.JTS.transform(JTS.java:85)
at org.geotools.renderer.lite.LiteRenderer2.queryLayer(LiteRenderer2.java:490)
... 7 more

All

Comments

Change History

Sort Order:

[ Permalink | « Hide ]

Jody Garnett added a comment - 27/Mar/05 08:04 PM

canot renderer wms and shapefile

[ Permalink | « Hide ]

Richard Gould added a comment - 27/Mar/05 09:49 PM

I am getting this while attempting to render layers 'popplace' on
http://www2.dmsolutions.ca/cgi-bin/mswfs_gmap?version=1.0.0&request=getcapabilities&service=wfs

if I zoom into BC, it displays properly.

[ Permalink | « Hide ]

Jesse Eichar added a comment - 28/Mar/05 06:07 PM

This is expected and desired behaviour. The swamps, streams, etc... are in UTM 10 and since currently there is no good way to check the valid area of a crs so when we are beyond the valid are for the data we are required to report an error and give up. The CRS API has the interfaces to do this but currently the CRS objects do not have the data so it is not useful as yet. In the future we can do better.

[ Permalink | « Hide ]

Jody Garnett added a comment - 29/Mar/05 01:59 AM

How can a stack trace be expected and desired behavior? It this actually fixed, or is it a won't fix?

How can I explain to users why there data disapears?

[ Permalink | « Hide ]

Jesse Eichar added a comment - 29/Mar/05 12:25 PM

The stack trace is not to standard out or standard err rather it goes to the log. I want errors to go to the log so that we can determine what is going wrong in other cases where something really is wrong.