Is there any way we can detect an ESRI server is being used (perhaps a
common pattern in the capabilities url; or some hint in the capabilities
document?) Perhaps we can adjust our encoding of Filter as a special case
while we wait for a bug report. Good detective skills to figure out what
they will accept.
Jody
On Fri, Feb 13, 2009 at 6:34 AM, Keane, Tim <[email protected]> wrote:
> Gabriel-
>
>
>
> It claims to be WFS 1.1.0.
>
> I have also found that it fails to parse ogc elements if the namespace is
> specified (ie: <Filter> parses, but <ogc:Filter> does not).
>
>
>
> It also appears that they are not properly escaping textual values returned
> from the db as you can see if you open the attached response doc.
>
>
>
> I complained loudly to ESRI so we'll see what happens.
>
>
>
> -Tim
> ------------------------------
>
> *From:* Gabriel Roldan [mailto:[email protected]]
> *Sent:* Thursday, February 12, 2009 2:17 PM
>
> *To:* Keane, Tim
> *Cc:* [email protected];
> [email protected]
> *Subject:* Re: cascading WFS
>
>
>
> On Thursday 12 February 2009 15:32:22 Keane, Tim wrote:
>
> > Gabriel-
>
> >
>
> >
>
> >
>
> > I have been working on producing the requests and responses as you
>
> > suggested. However, I am having a no luck getting ArcGIS Server's WFS
>
> > to properly apply Filters to GetFeature requests. So for now I am going
>
> > to back burner this.
>
> I understand. Still, not everything may be lost. Do the ArcGIS WFS Server
> claim to be 1.1.0 or 1.0?
>
> In the event they don't support any filtering at all, we could still make
> use of it and apply the filtering at run time, as we do with any non
> supported part of a filter. Yes, it will be much slower than desirable,
> cause the server wouldn't be applying any filtering and hence everytime we
> access it is like a full table scan, but would at least let fetch the data.
>
> If that's acceptable we could go that way until figuring out if/what subset
> of the filter spec an ArcGIS WFS actually supports?
>
> Cheers,
>
> Gabriel
>
> >
>
> >
>
> >
>
> > Thanks for your help.
>
> >
>
> > -Tim
>
> >
>
> >
>
> >
>
> > ________________________________
>
> >
>
> > From: Gabriel Roldan [mailto:[email protected]]
>
> > Sent: Thursday, February 05, 2009 10:12 AM
>
> > To: Keane, Tim
>
> > Cc: [email protected];
>
> > [email protected]
>
> > Subject: Re: cascading WFS
>
> >
>
> >
>
> >
>
> > Hi Tim, cc'ing the list
>
> >
>
> > confirmed we lack a binding in our parser for the
>
> > ows:extendedCapabilities
>
> >
>
> > element.
>
> >
>
> > What would be good in order to make sure we support ArcGIS server is for
>
> > you
>
> >
>
> > to create a JIRA issue for it (http://jira.codehaus.org/browse/GEOT),
>
> > assign
>
> >
>
> > to the data-wfs module, me (groldan) as the responsible, and attach the
>
> >
>
> > following information:
>
> >
>
> > - A GetCapabilities document just like the one you sent me
>
> >
>
> > - The response of a couple DescribeFeatureType requests
>
> >
>
> > - The response of a couple GetFeature requests.
>
> >
>
> > for the GetFeature requests I would need the originating requests and
>
> > its
>
> >
>
> > responses. Ideally, there should be a couple of them with GET and a
>
> > couple
>
> >
>
> > with POST method. And, even more, I need to check the following:
>
> >
>
> > - whether the server respects the maxFeatures param
>
> >
>
> > - whether the server respects the resultType param
>
> >
>
> > - whether the server works with attribute based filters, geometry
>
> > filters, and
>
> >
>
> > mixed attribute/geometry filters
>
> >
>
> > - whether the server respects the sortBy param
>
> >
>
> > Despite what WFS servers declare in the capabilities, most of them have
>
> >
>
> > trouble with at least one of those parameters.
>
> >
>
> > If I had that information as separate xml files, I could set them up as
>
> > unit
>
> >
>
> > test data suite for an ArcGIS strategy in the WFS DataStore the same way
>
> > I did
>
> >
>
> > for the others, or if you feel like doing so you can go ahead with the
>
> > code,
>
> >
>
> > check out how the test data is set up for the others (you'll see
>
> > although the
>
> >
>
> > 1.0 and 1.1 datastores lives in the same module, the 1.0 one is almost
>
> >
>
> > deprecated and waiting for me to have the energy to move it to the new
>
> >
>
> > framework created for the 1.1 one).
>
> >
>
> > Best regards,
>
> >
>
> > Gabriel
>
> >
>
> > [quote]
>
> >
>
> > > > >> ...I saw that you were the last
>
> > > > >>
>
> > > > >>
>
> > > > >>
>
> > > > >> one to edit the page on WFS Datastores. I am having problems
>
> >
>
> > creating
>
> >
>
> > > > >> a
>
> > > > >>
>
> > > > >>
>
> > > > >>
>
> > > > >> datasore that connects to an ESRI ArcGIS Server WFS. Geoserver
>
> >
>
> > 1.7
>
> >
>
> > > > >> chokes on the getCapabilities document attached with the
>
> >
>
> > following:
>
> > > > >> Parsing failed for OperationsMetadata:
>
> >
>
> > java.lang.RuntimeException:
>
> > > > >> Unable to set property: ExtendedCapabilities for eobject:
>
> > > > >>
>
> > > > >>
>
> > > > >>
>
> > > > >> {http://www.opengis.net/ows}_OperationsMetadata<http://www.opengis.net/ows%7D_OperationsMetadata>
>
> > > > >>
>
> > > > >>
>
> > > > >>
>
> > > > >>
>
> > > > >>
>
> > > > >> Is the WFS Datastore a viable option for federating WFS requests
>
> >
>
> > or
>
> >
>
> > > > >> would I be better off taking a different approach. I was hoping
>
> >
>
> > that
>
> >
>
> > > > >> you might give me some insight before I start digging into the
>
> > > > >>
>
> > > > >> geoserver
>
> > > > >>
>
> > > > >>
>
> > > > >>
>
> > > > >> source to find out that this is not really a mature datstore
>
> >
>
> > option.
>
> >
>
> > > > >> Thanks
>
> > > > >>
>
> > > > >>
>
> > > > >>
>
> > > > >> -Tim
>
> >
>
> > [quote]
>
> >
>
> > --
>
> >
>
> > Gabriel Roldan
>
> >
>
> > OpenGeo - http://www.opengeo.org
>
> >
>
> > -------------------------------------------------------
>
> --
>
> Gabriel Roldan
>
> OpenGeo - http://www.opengeo.org
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
> CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the
> Enterprise
> -Strategies to boost innovation and cut costs with open source
> participation
> -Receive a $600 discount off the registration fee with the source code:
> SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
