I have a WFS URL that I am adding as an item to ArcGIS Online. The WFS has well over 10,000 features. The default max number of features that ArcGIS Online will import is 3000 and the most I can enter is 9999.
If I change the visibility range to capture less than 3000 features at a time, it is still only importing the first 3000 records in the table for the entire dataset, not the given extent.
Is there a workaround to retrieve all features from a WFS? I also have a SQL Server Geodatabase instance that I could use to import this WFS to and publish through ArcGIS Server for consumption if needed. If this avoids the WFS max features obstacle.
Solved! Go to Solution.
Hey @AlexMetzler, @JennyRassmus , @shaileshgavathe , @CSA , @MathesSilas here is an idea which addresses the issue with the maximal features returned. you might want to give it kudos:
I'm encountering a similar problem with ArcGIS Pro 2.4.2. It seems to do the initial WFS request by pulling in the first 3000 features queried regardless of extent. Changing the extent fails to trigger a request for additional features.
Same problem here. I have ~4500 features, and the AGOL map only loads the first 3000, even if I zoom in to view an area with only the additional features. Looks like it's just always requesting the first 3000, and not adjusting per view extents. This feels broken... it really should request based on viewport. Anyone figure out how to do that, or is there a bug in the AGOL WFS map viewer?
you can always change the limit by going into layer from 3k to 10k. But that's the max limit and was hoping to have a lot higher limit.
I could live with limited number of features if the delivery of features was chosen with regard to the map extent. Why is that not possible? This makes all OGC web feature services containing a lot of features worthless to use.
Hey @AlexMetzler, @JennyRassmus , @shaileshgavathe , @CSA , @MathesSilas here is an idea which addresses the issue with the maximal features returned. you might want to give it kudos:
Hi @AlexMetzler and @nadja I don't understand how the idea that's marked as a solution solves the problem for ArcGIS online. Unless the idea is intended for ArcGIS online aswell. Or is there something I'm missing here?
@nadja ,
Are you saying , there will be a future ESRI release that may possibly solve this issue?
or you are saying, more kudos to your ideas will make ESRI developers happy and make them expedite it so it will happen sooner?
Thanks,