Hi Joel
No, this is not an error in your configuration.
The renderer component does not pass a proper hint to the Data Source, the
result is the log message
"No hint for geometry distance in query, fallback to base feature"
and the original geometry is used.
@Andrea
I think this a regression. The problem is here
org.geotools.data.gen.PreGeneralizedFeatureSource.getRequestedDistance(Query)
Should Joel Open a JIRA issue.
Cheers
Christian
On Wed, Oct 8, 2014 at 6:00 PM, joel.schmitt <[email protected]>
wrote:
> Hello,
>
> I am trying to use the pregeneralized features extension for limiting the
> number of vertices drawn for a large dataset that resides in PostGIS
> (geometry type 'MultiLineString'). I've been through the tutorials and the
> help forums and adjusted my .xml config file in many different ways
> according to all the info I've found. I have also set up my Generalizing
> Data Store on geoserver in the exact manner that was specified in this
> tutorial:
>
>
> http://osgeo-org.1560.x6.nabble.com/attachment/3819796/0/pregen_tutorial.html
> <
> http://osgeo-org.1560.x6.nabble.com/attachment/3819796/0/pregen_tutorial.html
> >
>
> After zooming and panning around in OpenLayers, I am still receiving the
> following message in the geoserver logs:
> "2014-10-08 10:00:10,973 WARN [org.geotools.data.gen] - No hint for
> geometry
> distance in query, fallback to base feature"
>
> >From my understanding, this means that something in the config file is not
> right and geoserver is defaulting to the base "the_geom" column for
> rendering the pipelines.
>
> Here is my .xml file:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <GeneralizationInfos version="1.0">
> <GeneralizationInfo dataSourceNameSpace="pipelines_pregen"
> dataSourceName="pipelines"
> featureName="pipelines_general_tx_1"
> baseFeatureName="domestic_pipelines_tx_1" geomPropertyName="the_geom">
> <Generalization distance="5000" featureName="domestic_pipelines_tx_1"
> geomPropertyName="the_geom5000"/>
> </GeneralizationInfo>
> </GeneralizationInfos>
>
> I've checked and all the parameters are populated correctly in the xml file
> according to the guidelines laid out in this thread:
>
>
> http://osgeo-org.1560.x6.nabble.com/New-postgis-feature-pregeneralized-tutorial-question-tp3797025p3797026.html
> <
> http://osgeo-org.1560.x6.nabble.com/New-postgis-feature-pregeneralized-tutorial-question-tp3797025p3797026.html
> >
>
> Does anybody know of any reasons why this would be failing to generalize my
> features? Any help would be greatly appreciated!
>
> Thanks!
>
>
>
>
>
> --
> View this message in context:
> http://osgeo-org.1560.x6.nabble.com/Error-Using-the-Pregeneralized-Features-module-on-Geoserver-tp5166527.html
> Sent from the GeoServer - User mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Geoserver-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
--
DI Christian Mueller MSc (GIS), MSc (IT-Security)
OSS Open Source Solutions GmbH
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
