Hi, I'm trying to read data from this server:
https://geodata.nationaalgeoregister.nl/bag/wfs?request=GetCapabilities
but only a 1000 features (the same ones it seems) come through. I've tried switching some parameters around, like what was suggested in previous questiosn about WFS on this forum (ignoring the schema etc. ). However, nothing has worked so far.
+34
This is because the request limit is 1000 features at a time. You can find this in the GetCapabilities:
<ows:Constraint name="CountDefault">
<ows:NoValues/>
<ows:DefaultValue>1000</ows:DefaultValue>
</ows:Constraint>If the service is 2.0.0 and responsepaging is allowed you can configure the WFS reader to read the complete dataset in blocks of 1000 features. (This is recently implemented in the WFS reader, use the HTTPCaller for earlier versions.)
The reason for this limit is to prevent overloading the service / killing the server. WFS should not be used to download entire datasets, you can use other services, like the BAG Extract for that. So you should use a polygon and a spatial filter to limit the area.
This is because the request limit is 1000 features at a time. You can find this in the GetCapabilities:
<ows:Constraint name="CountDefault">
<ows:NoValues/>
<ows:DefaultValue>1000</ows:DefaultValue>
</ows:Constraint>If the service is 2.0.0 and responsepaging is allowed you can configure the WFS reader to read the complete dataset in blocks of 1000 features. (This is recently implemented in the WFS reader, use the HTTPCaller for earlier versions.)
The reason for this limit is to prevent overloading the service / killing the server. WFS should not be used to download entire datasets, you can use other services, like the BAG Extract for that. So you should use a polygon and a spatial filter to limit the area.
This is because the request limit is 1000 features at a time. You can find this in the GetCapabilities:
<ows:Constraint name="CountDefault">
<ows:NoValues/>
<ows:DefaultValue>1000</ows:DefaultValue>
</ows:Constraint>If the service is 2.0.0 and responsepaging is allowed you can configure the WFS reader to read the complete dataset in blocks of 1000 features. (This is recently implemented in the WFS reader, use the HTTPCaller for earlier versions.)
The reason for this limit is to prevent overloading the service / killing the server. WFS should not be used to download entire datasets, you can use other services, like the BAG Extract for that. So you should use a polygon and a spatial filter to limit the area.
This seems to do the trick only partially.. It does download the data that intersects with the initiator (clip polygon), but when I want to save this data to a shapefile, I don't get any results....Why is that?
+34
This seems to do the trick only partially.. It does download the data that intersects with the initiator (clip polygon), but when I want to save this data to a shapefile, I don't get any results....Why is that?
This is because the request limit is 1000 features at a time. You can find this in the GetCapabilities:
<ows:Constraint name="CountDefault">
<ows:NoValues/>
<ows:DefaultValue>1000</ows:DefaultValue>
</ows:Constraint>If the service is 2.0.0 and responsepaging is allowed you can configure the WFS reader to read the complete dataset in blocks of 1000 features. (This is recently implemented in the WFS reader, use the HTTPCaller for earlier versions.)
The reason for this limit is to prevent overloading the service / killing the server. WFS should not be used to download entire datasets, you can use other services, like the BAG Extract for that. So you should use a polygon and a spatial filter to limit the area.
Okay, but in the 1st workbench (from WfS to FFS), what parameters do you set for your writer?
Because when I add an inspector after the feature reader,I can see both geometry and attributes.
But I just can't write them to a file. I don't get output for the FFS writer either, just like I didn't when writing to a shapefile...No matter what parameters I set for attribute and geometry handling in the feature reader. At best I get the attributes of the initiator, but I don't want that.. i want the WFS data....
+34
Okay, but in the 1st workbench (from WfS to FFS), what parameters do you set for your writer?
Because when I add an inspector after the feature reader,I can see both geometry and attributes.
But I just can't write them to a file. I don't get output for the FFS writer either, just like I didn't when writing to a shapefile...No matter what parameters I set for attribute and geometry handling in the feature reader. At best I get the attributes of the initiator, but I don't want that.. i want the WFS data....
01-wfs-ffs2017.fmw
This is because the request limit is 1000 features at a time. You can find this in the GetCapabilities:
<ows:Constraint name="CountDefault">
<ows:NoValues/>
<ows:DefaultValue>1000</ows:DefaultValue>
</ows:Constraint>If the service is 2.0.0 and responsepaging is allowed you can configure the WFS reader to read the complete dataset in blocks of 1000 features. (This is recently implemented in the WFS reader, use the HTTPCaller for earlier versions.)
The reason for this limit is to prevent overloading the service / killing the server. WFS should not be used to download entire datasets, you can use other services, like the BAG Extract for that. So you should use a polygon and a spatial filter to limit the area.
Dropping heterogeneous aggregate feature for the ESRISHAPE Writer, due to feature type allowed geometries restriction
And when I tried a geometrycoercer to coerce the FFS to fme_polygon, I got the following:
Cannot coerce from Multiple Geometry to fme_polygon
+26
Dropping heterogeneous aggregate feature for the ESRISHAPE Writer, due to feature type allowed geometries restriction
And when I tried a geometrycoercer to coerce the FFS to fme_polygon, I got the following:
Cannot coerce from Multiple Geometry to fme_polygon
+17
Dropping heterogeneous aggregate feature for the ESRISHAPE Writer, due to feature type allowed geometries restriction
And when I tried a geometrycoercer to coerce the FFS to fme_polygon, I got the following:
Cannot coerce from Multiple Geometry to fme_polygon
Try adding a GeometryFilter with the option Homogenize Collections set to Yes. This will split aggregates by geometry type as well. So if you have an mixed aggregate of lines and polygons, the output will be an aggregate of lines and an aggregate of polygons, each through the respective geometry port. This is perfect for writing to Esri GDB or Shape.
@redgeographics @DaveAtSafe @nielsgerrits
Hi everyone, ..Sorry, I was really busy, so I didn't have time to respond...Yes the deaggregator helped, I was able to create a shapefile with output. I'm also going to try the GeometryFilter to see if there are differences in output. But I've also realized that I don't need a shapefile to get my ultimate output... I've just been using the FFS for my other conversions/analyses etc...:-)
Thanks again, everyone, for your input..:-)
+26
@redgeographics @DaveAtSafe @nielsgerrits
Hi everyone, ..Sorry, I was really busy, so I didn't have time to respond...Yes the deaggregator helped, I was able to create a shapefile with output. I'm also going to try the GeometryFilter to see if there are differences in output. But I've also realized that I don't need a shapefile to get my ultimate output... I've just been using the FFS for my other conversions/analyses etc...:-)
Thanks again, everyone, for your input..:-)
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
