Re: [Geotools-devel] Unchecked branch: completed and green build

2020-11-18 Thread Emilio Lahr-Vivaz
One option for multiple authors on a commit is to use the 'Co-authored-by:' git commit hook, which github will respect and display:

Re: [Geotools-devel] SLD property extraction and xpath

2020-10-01 Thread Emilio Lahr-Vivaz
rendering code. The use of full xpath expressions is a bit uncommon, so you will find and fix glitches like this as you are one of the few groups to make use of the functionality. -- Jody Garnett On Tue, 29 Sep 2020 at 07:48, Emilio Lahr-Vivaz <mailto:elahrvi...@ccri.com>> wrote:

[Geotools-devel] SLD property extraction and xpath

2020-09-29 Thread Emilio Lahr-Vivaz
Hello, We at GeoMesa recently ran into an issue with SLD and property accessors; I'm hoping for some feedback on whether this is a bug in geotools or something wrong in our implementation. We've supported JSON extensions for string-type fields for a while now. We allow querying into the

Re: [Geotools-devel] Counting in GeoTools: going beyond the integer range

2020-09-04 Thread Emilio Lahr-Vivaz
I think the tension in the int vs long and size() method is that feature collection is often viewed as a java collection (an in-memory structure which has an inherent size limit of Int.MaxValue), but a feature collection can also be an iterator over remote content. I'd suggest size() be

Re: [Geotools-devel] Counting in GeoTools: going beyond the integer range

2020-09-02 Thread Emilio Lahr-Vivaz
Or, have a separate method, such as in java.util.Spliterator#estimateSize() Thanks, Emilio On 9/2/20 3:44 PM, Emilio Lahr-Vivaz wrote: In regards to returning -1, I believe the relevant count methods are detailed below. It may make sense, if the API is changing anyway, to allow for an 'exact

Re: [Geotools-devel] Counting in GeoTools: going beyond the integer range

2020-09-02 Thread Emilio Lahr-Vivaz
In regards to returning -1, I believe the relevant count methods are detailed below. It may make sense, if the API is changing anyway, to allow for an 'exact' (or equivalent) parameter to force the count evaluation, and remove the somewhat un-intuitive (to me at least) differentiation between

Re: [Geotools-devel] GeoTools 23-RC ready for testing - part II the return of testing

2020-03-18 Thread Emilio Lahr-Vivaz
and write features out that way as with any other datastore? But anyway glad that it seems to work for you. Ian On Wed, 18 Mar 2020 at 14:00, Emilio Lahr-Vivaz <mailto:elahrvi...@ccri.com>> wrote: Actually the GeoJSONWriter looks like it would work perfectly. Our workflow

Re: [Geotools-devel] GeoTools 23-RC ready for testing - part II the return of testing

2020-03-18 Thread Emilio Lahr-Vivaz
in gt-geojsondatastore I'm happy to consider them. Ian On Wed, 18 Mar 2020 at 13:06, Emilio Lahr-Vivaz <mailto:elahrvi...@ccri.com>> wrote: If that module is unsupported, are there any supported methods for writing a feature as geojson? For our use case, we need to write eac

Re: [Geotools-devel] GeoTools 23-RC ready for testing - part II the return of testing

2020-03-18 Thread Emilio Lahr-Vivaz
If that module is unsupported, are there any supported methods for writing a feature as geojson? For our use case, we need to write each feature individually, and not as a feature collection. Thanks, Emilio On 3/18/20 4:00 AM, Andrea Aime wrote: On Wed, Mar 18, 2020 at 12:03 AM Jody Garnett

Re: [Geotools-devel] filter function ECQL round-trip bug

2019-02-20 Thread Emilio Lahr-Vivaz
representation of the full range of geotools filter api). Are you sure you should not be changing that to be an expression? (just doing attribute or function does not fully cover all the kinds of expressions that ECQL could allow here). -- Jody Garnett On Mon, 18 Feb 2019 at 14:56, Emilio Lahr-Vivaz

[Geotools-devel] filter function ECQL round-trip bug

2019-02-18 Thread Emilio Lahr-Vivaz
Hello, I've hit a bug in the GeoTools ECQL parsing. I've got a fix, but wanted to raise the issue here before opening a pull request. We've got a custom filter function named 'proxyId', which just hashes the feature ID into an int. We use it for reach-back queries, so we can save bandwidth

[Geotools-devel] Polygon wrapping direction

2019-02-15 Thread Emilio Lahr-Vivaz
Hello, I was wondering if GeoTools has any conventions around handling ambiguous polygon filters in EPSG:4326. GeoMesa has always had some code that interprets polygons with unbroken x spans of more than 180 degrees as wrapping the anti-meridian, instead of spanning the entire globe. We

Re: [Geotools-devel] Filter-CQL issues

2019-02-05 Thread Emilio Lahr-Vivaz
Yeah, I think the main concern in GeoMesa is not the CQL formatting per-say, but that for any given Filter, the following test holds: Assert.assertEquals(filter, ECQL.toFilter(ECQL.toCQL(filter (or at least that they are equivalent, if not strictly equals) Thanks, Emilio On 2/4/19 4:49

Re: [Geotools-devel] Filter function to extract bits from json

2019-01-24 Thread Emilio Lahr-Vivaz
attributes with some possibly well maintained dependency. Or did I miss something? Cheers Andrea On Thu, Jan 24, 2019 at 4:24 PM Emilio Lahr-Vivaz <mailto:elahrvi...@ccri.com>> wrote: Hi Andrea, Jim, (resending after subscribing with the correct email) For some more

Re: [Geotools-devel] Filter function to extract bits from json

2019-01-24 Thread Emilio Lahr-Vivaz
Hi Andrea, Jim, (resending after subscribing with the correct email) For some more reference - we use jayway with gson as a provider, but only as a fallback. The filter functions we have are optimized for reading kryo-serialized json. In GeoMesa, you can indicate that a string field is json

[Geotools-devel] proposed changes to make heatmap process more extensible

2017-05-26 Thread Emilio Lahr-Vivaz
a PR. Thanks, Emilio Lahr-Vivaz -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ GeoTools-Devel

[Geotools-devel] [JIRA] (GEOT-5733) ECQL.toCQL doesn't properly encode Boolean literals

2017-05-22 Thread Emilio Lahr-Vivaz (JIRA)
Title: Message Title Emilio Lahr-Vivaz