Hei You could be right, i.e. I have never looked at the code, just ported it from the PostGIS plugin. The SRID code was also a later add-on, not part of the original design, and is in particular needed for databases.
However, I am not sure if the SRID is a feature property. Usually the SRID is assign to a layer or dataset. Though the geometry is stored of course with a certain SRID. So I am not sure if we should allow features with different SRID in one layer - if that is something what your suggested change would allow. Because it may become messy if the SRID of the layer is changed (e.g. for on the fly re-projection?). Well.. a bit difficult to discuss without having a re-project function yet :) [although now proj4j is there, as well as the lib from deegree] just some thoughts stefan [email protected] wrote: > Hi *, > > Each instance of SRIDStyle adds one LayerListener to the LayerManager ( > and does not remove it, when its layer is removed, I guess). > > My understanding is that each Layer has it own SRIDStyle ( and exactly > one, if I read EnsureAllLayersHaveSRIDStylePlugIn.ensureHasSRIDStyle > correctly ) and that each LayerListener is called when > LayerManager.fireFeaturesChanged is called. > > So if there are 10 Layers and one Feature of Layer X is changed then 10 > LayerListener are executed and each LayerListener change the Srid of the > Geometry of the changed Feature. The Srid of the feature after that, is > the Srid of the last LayerListener of the ArrayList > LayerManager.layerListeners. > > The "easiest" change would be that the sridstyle knows its layer and > only changes the srid of FeatureEvent where the layer matches its own. > > Any opinons about that "issue"? > > regards, > > Volker > > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > > > ------------------------------------------------------------------------ > > _______________________________________________ > Jump-pilot-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Jump-pilot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
