Andrea and the Geoserver PSC,
I think you've written very diplomatic and pragmatic solution to address
a tough problem. As I've moved away from my full-time employment in
support of a live geoserver instance, I've found that I'm definitely not
able to keep up with the weekly meetings or with t
Hey all,
I ran into an issue when trying CQL filters against the ArcSDE module
today. The issue is described in some depth here:
http://jira.codehaus.org/browse/GEOS-1979
along with the patch that attempted to fix it for me.
I'm not sure what the right answer is for this, or if it affects onl
: Saul Farber
Assignee: Andrea Aime
Fix For: 1.6.5, 1.6.x
Attachments: getmapresponse_propnames-1.6.x.patch
Consider the following scenario:
Geoserver 1.6.x latest revision: WMS GetMap on a bbox with a CQL filter like
(PROP1 = 'value2')
1. In GetMapRespon
Project: GeoServer
Issue Type: Bug
Components: ArcSDE
Affects Versions: 1.6.4
Reporter: Saul Farber
Assignee: Gabriel Roldán
Priority: Critical
Fix For: 1.6.5
Lines 131-171 of DataDataStoresEditorAction.java grab a
I agree with Luca on this one. I think "eating our own dog-food" is the
surest and best way to properly develop and constantly test the REST
api. Plus it puts all gui's on a level playing field.
FlexJSON + the config back-end + REST for configuration would seem to
allow everyone to just get on w
down. I think this should be enough
> > time for busy people.
> >
> > If you have any questions, please let me know. This is just one of the
> > pieces of the puzzle that is getting our documentation in better working
> > order.
> >
> > Thanks,
> &g
e what is still relevant to move
> > (aside from the RnD info), I can do the legwork on the moving.
> >
> > Thanks,
> > Mike
> >
> >
> > Saul Farber wrote:
> >> Mike,
> >>
> >> Once, long long ago, I tried to straighten up GEOSDE
Mike,
Once, long long ago, I tried to straighten up GEOSDEV a little bit,
clean out the old stuff and see if anyone wanted to use it as a "Not
GEOSDOC and also not GEOS" space. Geotools has the following spaces:
GEOTOOLS -- the main geotools front-page site
GEOT -- the "developers/developers gui
Just to chime in on this specific point:
My personal opinion is to have geoserver be "headless" in the sense that
a configuration/UI program is required but completely seperate from the
"server" portion of geoserver. They could be distributed together (err,
a "web UI" could be distributed along w
http://jira.codehaus.org/browse/GEOS-1823
Project: GeoServer
Issue Type: Bug
Components: WCS
Affects Versions: 1.7.x
Reporter: Saul Farber
Assignee: Andrea Aime
When you call GetFeatureInfo on a coverage layer, line 263 in
AbstractF
I actually think namespaces are a very cool idea in geoserver. They
allow a common back-end data "structuring" that allows different blocks
of data to have the same type name without conflicting.
Also, the wmsPath (as I understand it) doesn't really have much to do
with namespaces. It's about ma
11 matches
Mail list logo
