Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OGC Spatial filters fail if GEOS support not enabled #4431

Closed
tbonfort opened this issue Aug 22, 2012 · 8 comments
Closed

OGC Spatial filters fail if GEOS support not enabled #4431

tbonfort opened this issue Aug 22, 2012 · 8 comments

Comments

@tbonfort
Copy link
Member

If geos support is not enabled, FLTGetSpatialComparisonCommonExpression will silently create an invalid expression as the GEOS calls it's doing will return empty strings/geometries.

@ghost ghost assigned sdlime Aug 22, 2012
@sdlime
Copy link
Member

sdlime commented Aug 22, 2012

Sounds like an #ifdef is needed someplace.

@tbonfort
Copy link
Member Author

@sdlime should all calls to FLTGetSpatialComparisonCommonExpression be ifdef'd out when GEOS is not present? The problem is that FLTGetSpatialComparisonCommonExpression and FLTGetCommonExpression return a char*, so they can't explicitely return an error code in that case.

@sdlime
Copy link
Member

sdlime commented Aug 23, 2012

In theory the WFS capabilities should not offer certain spatial operators if GEOS is not enabled and we should throw an exception if one of those are used. We have fall backs (native MapServer) for some operators though (intersect is one example) so I don't think we can simply if-def the whole function. Wonder if we could pop something onto the error stack and return NULL? Otherwise we'd need to refactor the expressions.

@sdlime
Copy link
Member

sdlime commented Jul 24, 2013

Pushing to 7.0... This should get cleaned up with RFC 91 since the WFS code should just author token sequences. --Steve

@msmitherdc
Copy link
Contributor

these functions would still need geos is there is no spatial backend. So the if-def would have to check for the layer connection and disable if no geos for a non spatial backend.

@sdlime
Copy link
Member

sdlime commented Sep 8, 2014

Which if-def are you referring to?

From: Michael D. Smith [mailto:notifications@github.com]
Sent: Monday, September 08, 2014 1:46 PM
To: mapserver/mapserver
Cc: Lime, Steve D (MNIT)
Subject: Re: [mapserver] OGC Spatial filters fail if GEOS support not enabled (#4431)

these functions would still need geos is there is no spatial backend. So the if-def would have to check for the layer connection and disable if no geos for a non spatial backend.


Reply to this email directly or view it on GitHubhttps://github.com//issues/4431#issuecomment-54867816.

@msmitherdc
Copy link
Contributor

Around FLTGetSpatialComparisonCommonExpression, which this ticket was referring to. Or is this no longer an issue?

@mapserver-bot
Copy link

This is an automated comment

This issue has been closed due to lack of activity. This doesn't mean the issue is invalid, it simply got no attention within the last year. Please reopen with missing/relevant information if still valid.

Typically, issues fall in this state for one of the following reasons:

  • Hard, impossible or not enough information to reproduce
  • Missing test case
  • Lack of a champion with interest and/or funding to address the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants