From: Roy B. <roy...@b3...> - 2010-05-26 09:32:26
|
Hello List, For a project we need to use WFS on a ESRI ArcGIS 9.3 server...... :( I think the server is configured quite basic, we have no control over the ArcGIS server (lucky us). A few things we came across are: 1) If i sent a wfs getFeature request with content-type= "text/xml" i get a error back ( 501 not implemented). If i sent a xml but with content-type= "text/html" , "image/png" etc or empty, i get a correct response from the server...... This is ofcourse for both wfs 1.0.0 and wfs 1.1.0 and a bug in the ArcGIS installation. For wfs 1.0.0: This can be easily solved by creating a new class that extends the DefaultConnectionFactory(deprecated) for ArcGIS and overwrite the getConnection function. Agree? For wfs 1.1.0: i'm not quite sure what's the neatest way to solve this yet. 2) When doing a wfs 1.1.0 request: The server only has a 'output-format'= "text/xml; subType=gml/3.1.1/profiles/gmlsf/1.0.0/0". This gives some problems but they can also easily be solved: - Create a new wfs 1.1.0 Strategy (ArcGISServerStrategy) - Add a supported_output_format to the Gml31GetFeatureResponseParserFactory or Create a new Gml31GetFeatureResponseParserFactory that extends Gml31GetFeatureResponseParserFactory and overwrite the isSupportedOutputFormat Does anyone has to say something about this? Do you agree with the proposed solution? Otherwise i'll create a patch like explained above and add it to JIRA. Met vriendelijke groet, Roy Braam B3partners BV 030 214 2082 |
From: Jody G. <jod...@gm...> - 2010-05-26 12:44:12
|
I seem to recall one actual problem with the wfs connection and arcgis sever. I don't think the wfs 1.0.0 implementation can handle the errors schema it imports or something. Please check jira for known issues; and if you can provide patches for review it would be a great help. Jody On 26/05/2010, at 7:32 PM, Roy Braam wrote: > Hello List, > > For a project we need to use WFS on a ESRI ArcGIS 9.3 server...... :( > I think the server is configured quite basic, we have no control over the ArcGIS server (lucky us). > A few things we came across are: > 1) If i sent a wfs getFeature request with content-type= "text/xml" i get a error back ( 501 not implemented). If i sent a xml but with content-type= "text/html" , "image/png" etc or empty, i get a correct response from the server...... > This is ofcourse for both wfs 1.0.0 and wfs 1.1.0 and a bug in the ArcGIS installation. > For wfs 1.0.0: This can be easily solved by creating a new class that extends the DefaultConnectionFactory(deprecated) for ArcGIS and overwrite the getConnection function. Agree? > For wfs 1.1.0: i'm not quite sure what's the neatest way to solve this yet. > > > 2) When doing a wfs 1.1.0 request: The server only has a 'output-format'= "text/xml; subType=gml/3.1.1/profiles/gmlsf/1.0.0/0". This gives some problems but they can also easily be solved: > - Create a new wfs 1.1.0 Strategy (ArcGISServerStrategy) > - Add a supported_output_format to the Gml31GetFeatureResponseParserFactory > or > Create a new Gml31GetFeatureResponseParserFactory that extends Gml31GetFeatureResponseParserFactory and overwrite the isSupportedOutputFormat > > Does anyone has to say something about this? Do you agree with the proposed solution? Otherwise i'll create a patch like explained above and add it to JIRA. > > > Met vriendelijke groet, > > Roy Braam > B3partners BV > 030 214 2082------------------------------------------------------------------------------ > > _______________________________________________ > Geotools-devel mailing list > Geo...@li... > https://lists.sourceforge.net/lists/listinfo/geotools-devel |