I've seen this error previously when the unzipped temp file paths created were too long.
Although I'm also not sure whether you can actually use wildcards when reading from a URL either
I wonder if I have influence on the length of the unzipped temp files, but will see what I can do.
In case that I cannot use wildcards in an url, is there another way of reading sources where you as the 'end-user' do not have control over the data provided? It will be a great pain if I would have to create readers for each and every geodatabase provided, while having good chances that on the next visit the names have changed, or some data are not provided anymore...
I think from the URL you should be able to get the name of the each GDB, although it would require some looping to go through all the subfolders too. Once you have those values you can use that as the source in your reader
I think from the URL you should be able to get the name of the each GDB, although it would require some looping to go through all the subfolders too. Once you have those values you can use that as the source in your reader
Well, I do have to whole thing tumbling down the rabbit hole...
and I was thinking to read all the geodatabases in FeatureReaders dynamically in, but that's exactly where my issue was... how do I set the FeatureReader up to read all the data? Finally I managed! I tell the FeatureReader the input is of type File GDB, and point at the url + gdb_name (Value(name))
and repeat Value(name) here
Now all data are read and the correct number of schemas returned by the FeatureReader.
You should be able to do something a bit more elegant to get the urls for the files,
e.g.
You should be able to do something a bit more elegant to get the urls for the files,
e.g.
I have one more question in relation to the reading of the files @ebygomm .
I connected a FeatureReader to the loop-output and configured the way seen in the screenshot below.
Here the features to read are left at default settings: Schema and Data Features, and format is set to 'Esri Geodatabase (File Geodb)', while the output ports are set to 'One per Feature Type'. Due to the latter setting I am getting the following dialog. I tried to give it an arbitrary GDB file, since at this time also the File Geodatabase does not exist yet, and the 'Regenerate' checkbox is checked.
The FeatureReader brings 'Schemas' as output as well.
When I try to write the features read via a dynamic FeatureWriter, the writing fails because of the following warning and error:
Cannot define schema for '' as the feature does not contain schema information, and schema source is set to 'Schema from Schema Feature'. Please verify writer feature type configuration
Esri Geodatabase Writer: Feature Type Definition '' was requested, but not defined. Please visit https://www.safe.com/support
The default settings for the dynamic schema definition is 'Schema From Schema Feature' and there is nothing else to set it to. The schema definition name defaults to the name of the feature class or table name and that's also where I left it.
How do I get the features from multiple databases written into their own database tables? At the moment it seems the link to schemas is simply not there.
You should be able to do something a bit more elegant to get the urls for the files,
e.g.
Okay, it seems like my latest attempt is fruitful, but I wonder if that's really the way to go...
