A couple quick comments, sounds like you are down into the weeds/details...
which regardless it's a complex feature type (based on GML3) ) looks OK.
>
> Now we are close to the place where WFS service fails to handle GetFeature
> requests. GeoTools doesn't use namespace for properties in
> Sim
Hello.
I have some questions to WFS/GML specialists if there are at this
list.
My environment is GeoTools 10.x (I am quite confident that the case
is still relevant for newer versions of GT), WFSDataStore (gt-wfs)
being connection to WFS service running
Hi everybody,
my list of pull requests regarding WFSDataStore has grown with
https://github.com/geotools/geotools/pull/203
This one adds support for custom outputFormat for WFS 1.1.0 DataStore using
a new connection datastore parameter.
This can be used to force GetFeature requests to ask for a GM
Hi,
this is the second patch to the WFSDataStore (gt-wfs) module.
This is about axis order in server output and request filters.
To handle behaviours of different wfs implementations we added a couple of
parameters to choose axis order handling (for output and input filter)
between:
- compliant
-
On Thu, May 9, 2013 at 11:14 AM, Andrea Aime
wrote:
> On Thu, May 9, 2013 at 5:32 PM, Justin Deoliveira wrote:
>
>> Hi Mauro,
>>
>> Great to hear that the wfs-ng module is going to be getting some love.
>> The trick with a good wfs client has always been to deal with the
>> idiosyncrasies of speci
On Thu, May 9, 2013 at 5:32 PM, Justin Deoliveira wrote:
> Hi Mauro,
>
> Great to hear that the wfs-ng module is going to be getting some love. The
> trick with a good wfs client has always been to deal with the
> idiosyncrasies of specific servers, so handling more corner cases will be
> awesome.
Hi Mauro,
Great to hear that the wfs-ng module is going to be getting some love. The
trick with a good wfs client has always been to deal with the
idiosyncrasies of specific servers, so handling more corner cases will be
awesome.
I am not the maintainer of the module but the patch looks good to m
Hi everybody,
recently I did some work on the gt-wfs unsupported module to fix or improve
the interactions with some kind of wfs servers.
I would like to contribute some of the patches done so far.
The first one is about the CRS used in requests to the WFS server.
Currently the module tries to use
Morning Justin / Gabriel:
You guys are listed as module maintainer for gt-wfs; I got a couple of hours at
work to look at cleaning up the FeatureID handling story. As part of that I
have taken http://jira.codehaus.org/browse/GEOT-878 (Remove Duplicated Code)
out for a dance.
I have kicked out
Andrea Aime wrote:
> Jody Garnett ha scritto:
>> I have been sending Gabriel a bunch of messages; but since he seems
>> to be away right now I may as well share with the list... I went to
>> fix what appears to be an important uDig bug and found that
>> GeoServerOnlineTest no longer passes - any
Jody Garnett ha scritto:
> I have been sending Gabriel a bunch of messages; but since he seems to
> be away right now I may as well share with the list... I went to fix
> what appears to be an important uDig bug and found that
> GeoServerOnlineTest no longer passes - anything -. Changing the req
I have been sending Gabriel a bunch of messages; but since he seems to
be away right now I may as well share with the list... I went to fix
what appears to be an important uDig bug and found that
GeoServerOnlineTest no longer passes - anything -. Changing the request
to request VERSION=1.0.0 fi
Jesse Eichar wrote:
> The readers also have a couple different strategies associated with
> them you can create your own strategy there as well.
That is the approach taken for the WMS client code as well; given a
choice I would like to have several specific datastore classes to test,
rather than
The readers also have a couple different strategies associated with
them you can create your own strategy there as well.
Jesse
On 10-Jan-08, at 9:41 AM, Gabriel Roldán wrote:
> On Thursday 10 January 2008 06:15:39 pm Jody Garnett wrote:
>> Gabriel Roldán wrote:
>>> If this seems ok, it'd impl
On Thursday 10 January 2008 06:15:39 pm Jody Garnett wrote:
> Gabriel Roldán wrote:
> > If this seems ok, it'd imply moving some stuff around on the wfs plugin,
> > mostly some package refactoring to isolate version specific code from
> > general one. In my opinion it shouldn't be a problem as its
Gabriel Roldán wrote:
> If this seems ok, it'd imply moving some stuff around on the wfs plugin,
> mostly some package refactoring to isolate version specific code from general
> one. In my opinion it shouldn't be a problem as its the DataStore nature not
> to be API, and the only public class s
Hi All,
This is a request for comments as I'm working on a WFS DataStore 1.1.0
capable.
The short term goal is to have a read-only WFS 1.1.0 datastore that can be
used on uDig. Less than two weeks from now.
So, by one side, the current WFS datastore is:
- only 1.0.0
- fairly unmaintained, and
Andrea Aime wrote:
> Jody Garnett ha scritto:
>> I kind of view answer user email and having user documentation as on
>> the same level. But we
>> have considerable work to be done before I worry about this For
>> GeoTools 2.4 I am asking
>> for a *single* page of user documentation and conf
Jody Garnett ha scritto:
> I kind of view answer user email and having user documentation as on the
> same level. But we
> have considerable work to be done before I worry about this For
> GeoTools 2.4 I am asking
> for a *single* page of user documentation and conformance (if a test can
>
I kind of view answer user email and having user documentation as on the
same level. But we
have considerable work to be done before I worry about this For
GeoTools 2.4 I am asking
for a *single* page of user documentation and conformance (if a test can
be provided).
The fact that the WFS
Hi,
hard question. When is it that a supported module drops down in
unsupported land? Given that we do have rules for a module
being marked as supported, it seems a module should decay
when one (or maybe more than one, not sure) of those decays.
What made me think is the WFS module. It's clearly u
21 matches
Mail list logo
