Hi all,
For the most part this is going smoothly, however the wms and wcs modules contain some code that I am not sure exactly how to port to geotools trunk. Could someone more knowledgeable about these parts of the code base let me know the best way to port so I don't miss anything. Thanks.
-Justin
1. In GeoTIFFCoverageResponseDelegate:
final GeoTiffWriteParams wp = new GeoTiffWriteParams();
wp.setCompressionMode(GeoTiffWriteParams.MODE_EXPLICIT);
wp.setCompressionType("LZW");
wp.setCompressionQuality(0.75F);
wp.setTilingMode(GeoToolsWriteParams.MODE_EXPLICIT);
wp.setTiling(256,256);
final ParameterValueGroup writerParams = format.getWriteParameters();
writerParams.parameter(AbstractGridFormat.GEOTOOLS_WRITE_PARAMS.getName().toString())
.setValue(wp);
2. In GetMapResponse:
layer = new DefaultMapLayer(DataUtilities.wrapGcReader(reader, CoverageUtils.getParameters(params, layers[i].getCoverage().getParameters())), style);
3. In GIFMapProducer:
new ImageWorker(image).forceIndexColorModelForGIF(true).writeGIF(
outStream, "LZW", 0.75f);
4. In JPEGMapProducer:
new ImageWorker(image).writeJPEG(outStream, "JPEG", 0.75f,
JPEGNativeAcc.booleanValue());
5. In PNGMapProducer:
new ImageWorker(image).writePNG(outStream, "FILTERED", 0.75f,
PNGNativeAcc.booleanValue(), false);
--
Justin Deoliveira
jdeolive@anonymised.com
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira ha scritto:
Hi all,
For the most part this is going smoothly, however the wms and wcs modules contain some code that I am not sure exactly how to port to geotools trunk. Could someone more knowledgeable about these parts of the code base let me know the best way to port so I don't miss anything. Thanks.
Ouch... did not think about that! Simone never ported to trunk a lot of the changes performed on 2.3.x, so you're going to have a really hard
time trying to make code work against geotools trunk.
Simone, do you know from what revision we need to start merging changes?
(and we need to merge only Simone and Alessio ones, since I think me and Jesse did port every change on all branches).
Cheers
Andrea
I just love branch development :).
Well since my immediate target is the dispatcher and working on the wfs module ( the wms and wcs modules will remain unchanged ), I may just take them out of the build for now.
Do we have a timeline for when these things are supposed to come back to trunk?
-Justin
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi all,
For the most part this is going smoothly, however the wms and wcs modules contain some code that I am not sure exactly how to port to geotools trunk. Could someone more knowledgeable about these parts of the code base let me know the best way to port so I don't miss anything. Thanks.
Ouch... did not think about that! Simone never ported to trunk a lot of the changes performed on 2.3.x, so you're going to have a really hard
time trying to make code work against geotools trunk.
Simone, do you know from what revision we need to start merging changes?
(and we need to merge only Simone and Alessio ones, since I think me and Jesse did port every change on all branches).
Cheers
Andrea
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:1004,45b7a9b7190802223018498!
--
Justin Deoliveira
jdeolive@anonymised.com
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira wrote:
I just love branch development :).
Yeh I'm starting to feel the pain now in geoserver. One change to 1.5 branch requires to back-ports (1.4 and trunk). This slows down development almost 3-fold. And sometimes changes are forgotten.
More motivation for me to push out 1.5 so we can retire 1.4 asap.
Well since my immediate target is the dispatcher and working on the wfs module ( the wms and wcs modules will remain unchanged ), I may just take them out of the build for now.
Do we have a timeline for when these things are supposed to come back to trunk?
-Justin
Brent Owens
(The Open Planning Project)
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi all,
For the most part this is going smoothly, however the wms and wcs modules contain some code that I am not sure exactly how to port to geotools trunk. Could someone more knowledgeable about these parts of the code base let me know the best way to port so I don't miss anything. Thanks.
Ouch... did not think about that! Simone never ported to trunk a lot of the changes performed on 2.3.x, so you're going to have a really hard
time trying to make code work against geotools trunk.
Simone, do you know from what revision we need to start merging changes?
(and we need to merge only Simone and Alessio ones, since I think me and Jesse did port every change on all branches).
Cheers
Andrea
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:1004,45b7a9b7190802223018498!
Brent Owens ha scritto:
Justin Deoliveira wrote:
I just love branch development :).
Yeh I'm starting to feel the pain now in geoserver. One change to 1.5 branch requires to back-ports (1.4 and trunk). This slows down development almost 3-fold. And sometimes changes are forgotten.
More motivation for me to push out 1.5 so we can retire 1.4 asap.
Agreed. Yet, we shipped with a few nasty issues so I'd really like to
push out a 1.4.1 before declaring it "end of life".
Cheers
Andrea