Re: [Geotools-devel] ECQL Irregularities

Kevin, Hmm... does the Barnes Surface process create an ad hoc, intermediate feature type? I think the issue may be here: https://github.com/geotools/geotools/blob/master/modules/library/cql/src/main/java/org/geotools/filter/text/commons/ExpressionToText.java#L215-221. PropertyNames are not

Re: [Geotools-devel] ECQL Irregularities

On 30 March 2015 at 18:04, Jim Hughes wrote: > The EBNF does reference key words/reserved words. That list includes wkt > keywords like POINT, POLYGON and predicates like INTERSECTS and DURING. > > A property name appears to get worked out as 'character string literal', > and would need to be q

Re: [Geotools-devel] ECQL Irregularities

Fair enough, just pointing out that intersecting attribute names with keywords crosses a linestring. And that might not work after that. Puns aside, I'm curious to see the fix when it comes. If you have a failing unit test, I'm not above playing along over here. Cheers, Jim On 03/30/2015

Re: [Geotools-devel] ECQL Irregularities

In this case "point' was the name of an attribute in the data - so not much we could do about it. -- Jody Garnett On 30 March 2015 at 18:04, Jim Hughes wrote: > The EBNF does reference key words/reserved words. That list includes wkt > keywords like POINT, POLYGON and predicates like INTERSEC

Re: [Geotools-devel] ECQL Irregularities

The EBNF does reference key words/reserved words. That list includes wkt keywords like POINT, POLYGON and predicates like INTERSECTS and DURING. A property name appears to get worked out as 'character string literal', and would need to be quoted. I think that would do the trick. Since the l

Re: [Geotools-devel] ECQL Irregularities

So what is needed here ... list of reserved words that must be escaped when encoded? I think the square brackets are just to introduce precedence, isolating point won't help since it will start trying to treat it as geometry. For reference the grammar is here: http://old.geotools.org/ECQL-Parser-

[Geotools-devel] ECQL Irregularities

I've noticed that ECQL.toCQL doesn't escape WKT keywords. So point is encoded to just point rather than "point" or [point]. When this is parsed in turn, it is interpreted as a WKT literal, although it's lacking the rest of the expression and so fails. The bracket notation also fails to resolve th

[Geotools-devel] Jenkins build is back to normal : geotools-master #634

See -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hu

[Geotools-devel] Reminder: GeoTools / GeoServer Meeting at 17:30 UTC on Tuesday

GeoTools / GeoServer committee meeting on Skype at 17:30 UTC on Tuesday: http://www.timeanddate.com/worldclock/fixedtime.html?msg=GeoTools+%2F+GeoServer+Meeting&year=2015&month=3&day=31&hour=17&min=30&sec=0&ah=1 -- Ben Caradoc-Davies Director Transient Software Limited New

[Geotools-devel] osgeo jira is usable

Got an update about the conversion, got slowed down over codehaus performance over the weekend. The good news is that placeholder issues have been created at http://osgeo-org.atlassian.net (the contents will be copied over this evening). New issues can be added to osgeo-org.atlassian.net at this

[Geotools-devel] Build failed in Jenkins: geotools-master #633

See Changes: [tbarsballe] Updated Oracle JDBC version -- Started by an SCM change Started by an SCM change Started by an SCM change Started by an SCM change Building in workspace

Re: [Geotools-devel] CSV module breaking the build on windows

Given the failure I expect this will be a line feed issue -- Jody Garnett On 30 March 2015 at 09:47, Travis Brundage wrote: > Hi Andrea, > > I will check this when I get back on my Windows machine, which will be > this evening. I'll see if I can diagnose from there. > > Regards, > Travis > > On

[Geotools-devel] jira create/edit turned off

I have turned off the jira-users and geot-developers roles in Jira. Please use geotools-devel to coordinate this week. -- Jody Garnett -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by In

Re: [Geotools-devel] CSV module breaking the build on windows

Hi Andrea, I will check this when I get back on my Windows machine, which will be this evening. I'll see if I can diagnose from there. Regards, Travis On Mon, Mar 30, 2015 at 2:45 AM, Andrea Aime wrote: > Hi, > not sure if you noticed, but the CSV module is breaking the build on the > windows

Re: [Geotools-devel] Online build green

I have updated SQL Server to use the latest microsoft driver, and it is running tests now. We are getting one test failure: Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.926 sec <<< FAILURE! - in org.geotools.data.sqlserver.SQLServerDataStoreFactoryOnlineTest testCreateDataStor

Re: [Geotools-devel] Cylindrical Equal Area Projection

I will do a pull request as you suggest. However, I want to add a couple more projections (providers) before I do (e.g. "EPSG:3410" NSIDC EASE-Grid Global). As for testing, I generated an equal area grid using the Berhmann projection. Then, I converted the grid cells (polygons) to USA_Contiguou

[Geotools-devel] [jira] (GEOT-5063) Crop operation fails to render ROI correctly in openJDK7

Title: Message Title Nicola Lagomarsini created an issue

[Geotools-devel] CSV module breaking the build on windows

Hi, not sure if you noticed, but the CSV module is breaking the build on the windows build server: http://winbuild.geo-solutions.it/jenkins/job/GeoTools-Master/org.geotools$gt-csv/531/testReport/ Not sure why we did not get a mail, going to check, but in the meantime, can the last people working

Re: [Geotools-devel] bounds of empty shape file

On Mon, Mar 30, 2015 at 10:30 AM, Peilke, Hendrik wrote: > Hi Andrea, > > > > that was, what I wanted to suggest (I probably did not explain it that > good), although I would have read the number of features directly out of > the header already available inside getBoundsInternal(…). Or is this

Re: [Geotools-devel] bounds of empty shape file

Hi Andrea, that was, what I wanted to suggest (I probably did not explain it that good), although I would have read the number of features directly out of the header already available inside getBoundsInternal(…). Or is this bad practice? Your worry sounds reasonable, but IMHO the current retur