Last week I posed a question about having a FeatureSource which has also some generalizations of the vector data to speed up response time and reduce data transfer.
While it is is surely not the problem to implement such a FeatureSource, I need the ScaleDenominator from the caller. I studied the source and I want to ask the specialists about the following assumptions: 1) StreamingRenderer and ShapeFileRenderer use FeatureSource>>getFeatures(queryObject) 2) The Query interface offers the possibility to pass Hints My idea would be to pass the scaleDenominater as a hint to the queryObject. This makes sense since the scaleDenominator is only usefull for some use cases and should not be part of the FeatureSource API. I am not sure here if the ScaleDenomintar is enough, perhaps a unit of measure is also required. On the other side, the Query interface offers a getter for the CRS, I think I can get the unit from the CRS, yes or no ? Anyway, if my assumptions come close to the truth, I would do such an implementation and insert one line in the mentioned renderer classes to test it. opinions ? ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
