![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
8.2 |
|
Assignee:
|
Andrea Aime
|
|
Components:
|
render |
|
Created:
|
10/Oct/12 11:53 AM
|
|
Description:
|
The method prepFeatureCollection in StreamingRenderer is apparently intended to force the source CRS onto data which is missing a CRS. However, the situation where the data already has a CRS equal to the dest CRS is not correctly handled (the source CRS is forced in this case). This causes the features to be ignored by the rendering, since they no longer lie in the output extent.
This can occur when a RenderingTransformation produces an output feature collection which already has the dest CRS. An example is chaining the Contour RT to the Heatmap RT. The Heatmap RT produces a raster output in the dest CRS, and the Contour RT preserves this for the output features. The output features are not displayed, because they are forced to be in the wrong CRS.
The fix may be to check if the feature collection is in the dest CRS, and if so do not change the CRS.
|
|
Project:
|
GeoTools
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Martin Davis
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
