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
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
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
> 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,
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
