Re: [Geotools-devel] Filter clean up pull request 434

As per the meeting minuets I need to ask for a volunteer to review this pull request. Ideally before the weekend as I do not want to see this (extensive) patch undergo bit rot :) There are two options for review: a) As it stands the commits form a clear progression of cleaning up interfaces, delet

Re: [Geotools-devel] Pluggable SimpleFeature Serialization

On Wed, Apr 30, 2014 at 5:21 AM, Andrew Hulbert wrote: > Forgot to ask...since you mentioned it...is there anything that you > thought should be a candidate for replacing the feature type representation? > Not sure I understand the question. If I was doing a tutorial to day I would probably do

Re: [Geotools-devel] Pluggable SimpleFeature Serialization

Forgot to ask...since you mentioned it...is there anything that you thought should be a candidate for replacing the feature type representation? On 04/29/2014 03:20 PM, Andrew Hulbert wrote: I like the WKT name...I do remember now seeing that in your tutorial (thanks for those by the way). By

Re: [Geotools-devel] Pluggable SimpleFeature Serialization

I like the WKT name...I do remember now seeing that in your tutorial (thanks for those by the way). By feature type representation do you mean the "name1:Integer,name2:Float" syntax? One thing that we run into with some of the cloud toolkits is that they don't allow spaces or dashes for field

[Geotools-devel] Issues with System.loadlibrary

Hi list, I recently proposed a pull-request on geotools[1] and imageio-ext[2], which aims to limit the number of System.loadLibrary() concerning the GDAL native lib, and maybe I should have asked here before posting them, so excuse me if do things in the wrong order ;-) The main motivation about

Re: [Geotools-devel] Pluggable SimpleFeature Serialization

> We're interested in creating pluggable serialization framework that > allows developers to choose between avro, text, and other formats of > interest (e.g. json) so that we can share the AvroSimpleFeature with > others and register serializers via SPI similar to DataSources. > > On another note,

Re: [Geotools-devel] Type conversion in SimpleFeature implementations

It is more important that the expression implementations used for access do type conversion. Especially in this case the property name expression is expected to do type conversion. As for setAttribute being forgiving, this is an example of the old computer science rule of thumb: be strict it what

[Geotools-devel] Pluggable SimpleFeature Serialization

Hi all, I've implemented a new method of serializing SimpleFeatures using Apache Avro (http://avro.apache.org/) that utilizes dynamic Avro schema generation and a binary serialization. This results in smaller data size but, more importantly, faster feature serialization and deserialization tha

[Geotools-devel] Type conversion in SimpleFeature implementations

Hi all, I noticed that in SimpleFeatureImpl the setAttribute() methods attempt to convert an Object into the correct type based on the AttributeDescriptor but the setAttributes() method takes an entire list of values and does NOT do conversion. The ResultSetFeature implementation does not atte

[Geotools-devel] GeoTools / GeoServer Meeting 2014-04-29

GeoTools / GeoServer Meeting 2014-04-29 === Attending - Ben Caradoc-Davies Jukka Rahkonen Jody Garnett Andrea Aime Agenda -- - previous meeting - fonts and testing - cite tests and build server - Java 7 - Next Release - filter/expression cleanup

Re: [Geotools-devel] Pull request of interest to wfs-ng people

Asked Niels about this and I don't think it is there in the ng implementation. Which brings up a good point about how we should treat changes to the new store while we are working on moving the ng store to supported. We have a limited budget of hours for Niels to spend on pushing the ng store to s

[Geotools-devel] Jenkins build is back to normal : geotools-11.x #51

See -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalle

[Geotools-devel] Build failed in Jenkins: geotools-11.x #50

See -- [...truncated 2056 lines...] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ gt-epsg-oracle --- [INFO] Installing

[Geotools-devel] Build failed in Jenkins: geotools-11.x #49

See Changes: [lago.88] [GEOT-4677]: added logging and workaround for invalid unit string in time axis -- [...truncated 2112 lines...] POLYGON ((-123.47009555832284 48.543261561072285, -123.469

[Geotools-devel] Jenkins build is back to normal : geotools-11.x #48

See -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalle

[Geotools-devel] Jenkins build is back to normal : GeoTools-11.x #42

See -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get

[Geotools-devel] Build failed in Jenkins: geotools-11.x #47

See Changes: [daniele.romagnoli] GEOT-4763: improve scalability on rendering/rasterSymbolizer -- [...truncated 14790 lines...] baseMaps earthCover BIL Vanda Lima en 14.05 46.46