Re: [Geotools-devel] Two bugs for parsing ArcGIS Server 10.1 WFS GetFeature response
On Sun, Feb 9, 2014 at 10:20 PM, Allen Lin wrote: > Hi Jody, > > Thanks for pointing that out, though I am having two more questions: > 1) What to be included in the test case? Says, for Parsing WFS GetFeature > response from ArcGIS Server, should I make a WFS FeatFeaturePOST request to > one ArcGIS Server and parsing that using the Patched class I wrote? > Have a look at the TinyOWS tests, they use a mock system and recorded responses as xml files that are fed to the client without the need for a running ArcGIS server (well, you need one when you write the tests, but that is all). > > 2) JIRA seems to require a membership to report any bug issue, which I > don't have. Should I get one from Geotool community or could someone file > the bug report for me. > Please register as xircles.codehaus.org Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk___ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
Re: [Geotools-devel] proposal extended release schedule
Looks like we have enough votes to proceed. Linked to the google doc. Filled in the release schedule: http://geoserver.org/display/GEOS/GeoTools+and+GeoServer+release+schedule Currently I have both individual branch schedule, and a combined schedule (thanks to text editor sort). I think I like the combined schedule better in terms of planning. Jody Garnett On Mon, Feb 10, 2014 at 2:39 PM, Ben Caradoc-Davies < ben.caradoc-dav...@csiro.au> wrote: > +1. Thanks Jody. > > And thanks to Andrea and Alessio, who IIRC originated the idea. Perhaps > add a link to Andrea's Google Doc? > > Kind regards, > Ben. > > > On 06/02/14 11:13, Jody Garnett wrote: > >> Proposal is up: >> >> http://docs.codehaus.org/display/GEOTOOLS/Extended+Release+Schedule >> >> In writing it up I ended up with a gap before the maintenance phase, in >> order to transition from RC to Release on time. The result still >> alternates between stable and maintenance, but the change to a new >> branch produces the "glitch". >> >> Jody Garnett >> >> >> >> -- >> Managing the Performance of Cloud-Based Applications >> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. >> Read the Whitepaper. >> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&; >> iu=/4140/ostg.clktrk >> >> >> >> ___ >> GeoTools-Devel mailing list >> GeoTools-Devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geotools-devel >> >> > -- > Ben Caradoc-Davies > Software Engineer > CSIRO Earth Science and Resource Engineering > Australian Resources Research Centre > -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk___ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
Re: [Geotools-devel] Two bugs for parsing ArcGIS Server 10.1 WFS GetFeature response
You should be able to copy one of the existing tests cases, many of them contain the sample output which is fed into the WFS Client code. Your test case can show that the current code fails, and then when the developer applies you patch they can verify that your fix works. You can sign up to Jira on codehaus: http://xircles.codehaus.org/signup Jody Garnett On Mon, Feb 10, 2014 at 8:20 AM, Allen Lin wrote: > Hi Jody, > > Thanks for pointing that out, though I am having two more questions: > 1) What to be included in the test case? Says, for Parsing WFS GetFeature > response from ArcGIS Server, should I make a WFS FeatFeaturePOST request to > one ArcGIS Server and parsing that using the Patched class I wrote? > > 2) JIRA seems to require a membership to report any bug issue, which I > don't have. Should I get one from Geotool community or could someone file > the bug report for me. > > Thanks, > Allen > > > On Mon, Feb 3, 2014 at 2:49 PM, Jody Garnett wrote: > >> Patches are easiest to submit via github pull request. You can also >> attach the patch to a JIRA issue. Be sure to include a test case (it makes >> the difference between your patch quickly getting reviewed vs a developer >> having to set up a test case to prove that the patch does something before >> it can be accepted). >> >> The second issue (migrating data to a shapefile) is due to limitations of >> the shapefile format. We actually just updated our tutorials to "help" >> point this out. If you need a data format that preserves a bit more detail >> for interoperability look at property datastore (which we use for many test >> cases). >> >> (And yes it would be nice to have funding to build a GML datastore for >> these purposes since that is what GML is supposed to be good at). >> >> Jody >> >> Jody Garnett >> >> >> On Tue, Feb 4, 2014 at 4:16 AM, Allen Lin wrote: >> >>> Hi all, >>> >>> (Totally new to Geotools community so sorry if I am posting at wrong >>> place and please help to move it to where it belongs to.) >>> >>> While using Geotools in our project, I found two bugs when parsing WFS >>> GetFeature response from ArcGIS Server 10.1. >>> >>> 1) attribute "gml:id" is missing. Unlike a standard WFS GetFeature >>> response, the attribute "gml:id" is missing for EACH FEATURE in ArcGIS >>> response. (see >>> http://resources.arcgis.com/en/help/main/10.1/index.html#//015404rz00, >>> search for "gml:ids") However, this is a mandatory attribute in >>> org.geotools.data.wfs.v1_1_0.parwers.XMLSimpleFeatureParser.java >>> This issue has been raised before within the community >>> http://jira.codehaus.org/browse/GEOT-2912 but it is still marked >>> unsolved. I have made a patched XMLSimpleFeatureParser.java my own. Please >>> let me know if I should submit my patch to somewhere and where to submit. >>> >>> 2) The second bugs is more trickier. I found discrepancies between >>> Geometry Attribute Name in ShapefileDataStore schema and the WFS response >>> schema. >>> While WFS response generate the geometry attribute name from >>> DescribeFeatureType request, ShapefileDataStore would generate its own >>> geometry attribute name by default value "the_geom". This triggered errors >>> when copying feature source from WFS datastore to feature source in >>> Shapefile data store, especially considering that ArcGIS Server WFS >>> GerFeature response is using "Shape" as its geometry attribute name. Is it >>> a bug or did I miss something here? >>> >>> >>> Thanks in advance! >>> >>> best, >>> Allen >>> -- >>> 林轶伦 LIN, Yilun (Allen) >>> >>> >>> >>> -- >>> Managing the Performance of Cloud-Based Applications >>> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. >>> Read the Whitepaper. >>> >>> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk >>> ___ >>> GeoTools-Devel mailing list >>> GeoTools-Devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geotools-devel >>> >>> >> > > > -- > 林轶伦 LIN, Yilun (Allen) > > -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk___ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
Re: [Geotools-devel] proposal extended release schedule
+1. Thanks Jody. And thanks to Andrea and Alessio, who IIRC originated the idea. Perhaps add a link to Andrea's Google Doc? Kind regards, Ben. On 06/02/14 11:13, Jody Garnett wrote: > Proposal is up: > > http://docs.codehaus.org/display/GEOTOOLS/Extended+Release+Schedule > > In writing it up I ended up with a gap before the maintenance phase, in > order to transition from RC to Release on time. The result still > alternates between stable and maintenance, but the change to a new > branch produces the "glitch". > > Jody Garnett > > > -- > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk > > > > ___ > GeoTools-Devel mailing list > GeoTools-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel > -- Ben Caradoc-Davies Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk ___ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
Re: [Geotools-devel] Two bugs for parsing ArcGIS Server 10.1 WFS GetFeature response
Hi Jody, Thanks for pointing that out, though I am having two more questions: 1) What to be included in the test case? Says, for Parsing WFS GetFeature response from ArcGIS Server, should I make a WFS FeatFeaturePOST request to one ArcGIS Server and parsing that using the Patched class I wrote? 2) JIRA seems to require a membership to report any bug issue, which I don't have. Should I get one from Geotool community or could someone file the bug report for me. Thanks, Allen On Mon, Feb 3, 2014 at 2:49 PM, Jody Garnett wrote: > Patches are easiest to submit via github pull request. You can also attach > the patch to a JIRA issue. Be sure to include a test case (it makes the > difference between your patch quickly getting reviewed vs a developer > having to set up a test case to prove that the patch does something before > it can be accepted). > > The second issue (migrating data to a shapefile) is due to limitations of > the shapefile format. We actually just updated our tutorials to "help" > point this out. If you need a data format that preserves a bit more detail > for interoperability look at property datastore (which we use for many test > cases). > > (And yes it would be nice to have funding to build a GML datastore for > these purposes since that is what GML is supposed to be good at). > > Jody > > Jody Garnett > > > On Tue, Feb 4, 2014 at 4:16 AM, Allen Lin wrote: > >> Hi all, >> >> (Totally new to Geotools community so sorry if I am posting at wrong >> place and please help to move it to where it belongs to.) >> >> While using Geotools in our project, I found two bugs when parsing WFS >> GetFeature response from ArcGIS Server 10.1. >> >> 1) attribute "gml:id" is missing. Unlike a standard WFS GetFeature >> response, the attribute "gml:id" is missing for EACH FEATURE in ArcGIS >> response. (see >> http://resources.arcgis.com/en/help/main/10.1/index.html#//015404rz00, >> search for "gml:ids") However, this is a mandatory attribute in >> org.geotools.data.wfs.v1_1_0.parwers.XMLSimpleFeatureParser.java >> This issue has been raised before within the community >> http://jira.codehaus.org/browse/GEOT-2912 but it is still marked >> unsolved. I have made a patched XMLSimpleFeatureParser.java my own. Please >> let me know if I should submit my patch to somewhere and where to submit. >> >> 2) The second bugs is more trickier. I found discrepancies between >> Geometry Attribute Name in ShapefileDataStore schema and the WFS response >> schema. >> While WFS response generate the geometry attribute name from >> DescribeFeatureType request, ShapefileDataStore would generate its own >> geometry attribute name by default value "the_geom". This triggered errors >> when copying feature source from WFS datastore to feature source in >> Shapefile data store, especially considering that ArcGIS Server WFS >> GerFeature response is using "Shape" as its geometry attribute name. Is it >> a bug or did I miss something here? >> >> >> Thanks in advance! >> >> best, >> Allen >> -- >> 林轶伦 LIN, Yilun (Allen) >> >> >> >> -- >> Managing the Performance of Cloud-Based Applications >> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. >> Read the Whitepaper. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk >> ___ >> GeoTools-Devel mailing list >> GeoTools-Devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geotools-devel >> >> > -- 林轶伦 LIN, Yilun (Allen) -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk___ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
[Geotools-devel] [jira] (GEOT-4696) Image mosiac jdbc cannot handle single band float images
Title: Message Title Christian Mueller created an issue GeoTools / GEOT-4696 Image mosiac jdbc cannot handle single band float images Issue Type: Bug Affects Versions: 10.4, 11-beta Assignee: Unassigned Components: imagemosaic-jdbc plugin Created: 09/Feb/14 8:41 AM Priority: Major Reporter: Christian Mueller Single band float images are causing exceptions during the rescale operation. The solution is to rescale using a planar image. Additionally, the data buffer for the result image is not created correctly. Add Comment
[Geotools-devel] [jira] (GEOT-4695) Image Reader should return null if no image data is available
Title: Message Title Christian Mueller created an issue GeoTools / GEOT-4695 Image Reader should return null if no image data is available Issue Type: Bug Affects Versions: 10.4, 11-RC1 Assignee: Unassigned Components: imagemosaic-jdbc plugin Created: 09/Feb/14 8:24 AM Priority: Major Reporter: Christian Mueller At the moment the image reader constructs an "empty" image if no image data can be found for a given envelope. This behavior is inconsistent with other readers return "null" in this situation. (e. g. ArcSDE reader) Add Comment
Re: [Geotools-devel] [Geowebcache-devel] Modification on WMSTileFuser class
So I understand what is being proposed. I suppose my questions twofold a) what is your time frame for this work and b) why 10.x ( since we are nearing the 11.0)? As for moving code between projects, everything looks okay. For the GeoServer code subject to a license change we will need a email request w/ response from GeoServer PSC (Quantizer / PNGEncoder). Cheers, Jody On Friday, February 7, 2014, Nicola Lagomarsini < nicola.lagomars...@geo-solutions.it> wrote: > Hi all, > > I would submit a proposal for changing the GeoWebCache WMSTileFuser class. > > This class presents some limitations associated to bad performances on > reading the input tiles and writing the final image. These performances are > dued to a direct call to the ImageIO methods. > > A possible improvement could be to skip the ImageIO methods by adding some > classes which internally handle image writing and reading. Also the output > image can be optimized, if it is PNG8, with an optimal colorTable. Finally > better performance and quality results could be achieved with improvements > on the image scaling phase. > > This proposal requires moving some code to avoid cyclic dependencies: > >- moving Quantizer from GeoServer to GeoTools. >- moving the new PNGEncoder from GeoServer to ImageIO-Ext and leaving >only a single facade class which calls the PNGEncoder. > > The GeoServer, GeoTools, GeoWebCache and ImageIO-Ext versions are all > taken from their master branch, but a backport will be needed: > >- for Geoserver on 2.4.x; >- for GeoWebCache on 1.5.0; >- for ImageIo-Ext on 1.1.x; >- for GeoTools 10.x. > > > The modifications on the WMSTileFuser class can be divided in 3 groups: > >- improving the reading of every tile and the final image writing by >adding few classes and avoiding to call directly the ImageIO class, which >requires a lookup of the streams and readers/writers; >- improving the PNG8 images by applying the Quantizer on them; >- improving the scaling of the final image by adding RenderingHints. > > The first improvement consist of creating 2 container classes which > internally handle the writing/reading by automatically using the > encoder/decoder for the defined MimeType. These encoders/decoders are > defined in the Spring application context as subclasses of 2 new abstract > classes called ImageDecoder and ImageEncoder. Each subclass internally > searches all the Spi classes defined in the associated bean configuration > and then stores the first Spi available. All the encoder/decoder beans are > injected into the related container when the application is launched. > > For PNG images, the new GeoServer PNGEncoder is used by default, but the > user can disable this functionality by changing a property file associated. > > > An UML diagram could help understanding these modifications. > > The second improvement consists of calculating an optimal ColorTable > associated to the image with the Quantizer class. > > The last improvement consists of using an optimal configuration for the > RenderingHints for having better quality and speed. > > The estimated time is 1/2 days. > > If there is any question I would be pleased to answer. > > Best Regards, > Nicola Lagomarsini. > > -- > == > Our support, Your Success! Visit http://opensdi.geo-solutions.it for more > information. > == > > Ing. Nicola Lagormarsini > Junior Software Engineer > > GeoSolutions S.A.S. > Via Poggio alle Viti 1187 > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > --- > -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk___ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
