You are probably out of date with the correct geotools version.
The SVN version we are using is called exactly "2.1.x". It changes regularly, especially with the renderer. It should be sync'd up with RC7 (as of tonight).

I would check out the source code, it is reasonably easy and most up to date:
1) check out: http://svn.geotools.org/geotools/branches/2.1.x
2) Navigate to the appropriate module: module/main
3 a) (for maven v1) Go to the command prompt and type: maven java:compile
3 b) (for maven v2) Go to the command prompt and type: mvn compile
4) Import the project into Eclipse (from the directory you navigated to: module/main) 5) Have the geoserver project point to the source code instead of the gt2-main jar

Refer to this page (http://www.geotools.org/display/GEOTOOLS/Using+Maven) for more help with maven and geotools.


Brent Owens
(The Open Planning Project)



Davis Ford wrote:

Hi, just a follow up to this. I'm trying to step-debug this problem. Using GeoServer from trunk, when I hit GeoTools StreamingRenderer the
debugger steps out of place.  The revision of StreamingRenderer says:

version $Id: StreamingRenderer.java 17289 2005-12-12 15:11:54Z dblasby $

It is from GeoTools 2.1.x checkout:

Revision: 17289
Author: dblasby
Date: 10:11:54 AM, Monday, December 12, 2005
Message:
fixes so the buggy test cases work. (from trunk)
----
Modified : 
/geotools/branches/2.1.x/module/main/src/org/geotools/renderer/lite/StreamingRenderer.java

Can someone on the list verify what revision of GeoTools 2.1.x I
should check out (that is in the main jar) - so the debugger steps in
the right place?

Would it be better to just build and install the latest 2.1.x trunk
myself for GeoTools?

Regards,
Davis

On 12/14/05, Davis Ford <[EMAIL PROTECTED]> wrote:
Chris / Justin -- thank you for the helpful advice.  What Chris
suggested is exactly where I was thinking the problem lies.  I do not
believe we have correctly implemented the methods.

CoordinateReferenceSystem sourceCrs =
currLayer.getFeatureSource().getSchema()
               .getDefaultGeometry().getCoordinateSystem();
I do not know what getCoordinateSystem returns, but I suspect we have
not properly set this up in the default geometry for the feature...I
just have not had adequate time to check it, and it is on my list to
do very soon.

The version I currently have is a trunk checkout:

Revision: 4023
Author: bowens
Date: 12:54:40 PM, Monday, December 12, 2005
Message:
uses the cached lat long bounding box, to be quicker. Still needs to
reproject it
----
Modified : /trunk/geoserver/src/org/vfny/geoserver/action/MapPreviewAction.java

I am hoping once I fix this, we'll be happily displaying via WMS, but
I haven't gotten there yet.

Regards,
Davis


On 12/14/05, Justin Deoliveira <[EMAIL PROTECTED]> wrote:
This is the 3rd time I have seen this exact error come up in two days. I
am starting to think that this might not be a coincidence.

Davis, Rob, Lena: can you tells us what version of geoserver you are
using? Thanks.

-Justin

Davis Ford wrote:
Hi,

We implemented our own test datastore in geotools, and are trying to
make it work via WMS using GeoServer.  WFS seems to work without a
hitch using GeoServer.

Using WMS -- however..the following query:

http://localhost:8080/geoserver/wms?version=1.3.0&request=GetMap&layers=teleatlas:RoadElement&BBOX=5.7,49.4,6.5,50.1&srs=EPSG:4326&width=300&height=300&format=image/gif&STYLES=simple_road

produces a blank map image, and eclipse debugger reports the following:

[SEVERE] org.geotools.renderer.lite.StreamingRenderer$DefaultRenderListener
- Error transforming bbox
[SEVERE] org.geotools.renderer.lite.StreamingRenderer$DefaultRenderListener
- Exception rendering layer [EMAIL PROTECTED]

Tracing the debugger in eclipse,
org.vfny.geoserver.wms.responses.produceMap() calls:
renderer.paint(graphic, paintArea, at); at line 244 in produceMap()

I did an SVN co on the 2.1.x branch of GeoTools and imported into
eclipse, but my debugger's execution pointer is not correct when I
step into org.geotools.renderer.lite.StreamingRenderer so I'm having
some trouble finding the problem.

It does seem this problem has been experienced by other users before.
Is it possible that someone on the list might help explain what may be
going wrong?

The try block where the exception is caught reads:

// Then create the geometry filters. We have to create one for each
               // geometric
               // attribute used during the rendering as the feature
may have more
               // than one
               // and the styles could use non default geometric ones
               CoordinateReferenceSystem sourceCrs =
currLayer.getFeatureSource().getSchema()
               .getDefaultGeometry().getCoordinateSystem();

               if (sourceCrs != null && !sourceCrs.equals(destinationCrs)) {
                   // get an unprojected envelope since the feature
source is operating on
                   // unprojected geometries
                   transform =
operationFactory.createOperation(destinationCrs,sourceCrs).getMathTransform();
                   if (transform != null && !transform.isIdentity()) {
                       // Envelope eee=  JTS.transform(envelope,
transform);// this is the old way
                       //10 = make 10 points on each side of the bbox
& transform the polygon
                       envelope = JTS.transform(envelope,
transform,10); // this will usually be a "bigger" bbox
                   } else
                       transform = null; //reset transform
               }

               Filter filter = null;
               if (!isMemoryPreloadingEnabled()) {
                   BBoxExpression rightBBox =
filterFactory.createBBoxExpression(envelope);
                   filter = createBBoxFilters(schema, attributes, rightBBox);
               } else {
                   filter = Filter.NONE;
               }

               // now build the query using only the attributes and
the bounding
               // box needed
               DefaultQuery q = new DefaultQuery(schema.getTypeName());
               q.setFilter(filter);
               q.setPropertyNames(attributes);
               query = q;

I'm just looking for some helpful pointers on what to try next from
any veterans familiar with this area of the code --

Thx...

Davis


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Geotools-gt2-users mailing list
Geotools-gt2-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Geoserver-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/geoserver-users



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Geotools-gt2-users mailing list
Geotools-gt2-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Reply via email to