Error indexing WFS Service.fdl

02-03-2010 06:56 AM
Labels (1)
New Contributor III
A known bug since 9.3 SP1 (NIM045522): Data Interoperability will index all features before displaying the geometry of a WFS. This takes a long time when the WFS references a large dataset.

This behaviour is still present in 10. Or often even worse: The indexing simply finishes with an error "Error indexing <wfs name>.fdl"
The latter for instance with the "Nieuwe kaart van Nederland (New map of the Netherlands):

0 Kudos
5 Replies
New Contributor
I'm getting to think that WFS connections simply do not work in the ESRI and FME world, when they are realistic life-sized services.  I was hoping something would be  fixed for release 10, and maybe a patch for 9.3...but I don't see any significant discussion on the topic anywhere.
0 Kudos
New Contributor
In 9.3 there is a limit to the number of features indexed, and without refresh.  Is this the same in 10?

0 Kudos
Occasional Contributor
Hi everybody,

any idea if this problem got solved???
I´m working on ArcGIS 10 SP3 and get the same error message when I want to load large WFS datasets !!

Any help would be very much appreciated.

0 Kudos
New Contributor II
When a user makes a WFS connection using the Data Interoperability
extension, the connection is cached by default.  This means that when
the user views the connection features, all of the features are read and
indexed, and the cache is given a 24-hour lifespan.  Subsequent views of
the same connection features will be taken from the cache instead of
live from the WFS server.

In order to make use of the live non-cached WFS data, the user must
ensure that the "Numeric Identifier Attribute" field is entered.
(Connection Properties -> Parameters).  This is the field name of the
primary key.  When the Data Interoperability extension sees this field
populated, it turns off caching for this data and instead makes live
feature requests based on this numeric key.

The benefits of the live (dynamic) WFS requests are that changes to the
WFS data can be seen presently instead of delayed until the cache is
refreshed.  The downside is that the live requests are slower,
especially when ArcObjects requests one feature at a time (such as when
viewing the attribute table or performing a Geoprocessing task.)

0 Kudos
Occasional Contributor
Dear Jeff,

thanks for this information. It helped me a lot.

0 Kudos