Hi @margaret_wei,
I tried using the URL in a FeartureReader in FME 2019.2 and did get the results:
Resulting in:
Could it be the attribute for the URL is changing the URL.
Have you tried using the URL instead of the attribute?
Hope this helps.
Hmmm. I too get that problem. The message in my log file is:
2019-12-19 11:43:22| 0.9| 0.0|ERROR |Shapefile reader: Failed to open file 'https://ecos.fws.gov/docs/species/shapefiles/usfws_I02T_I01_Cavaticovelia_aaa_current_range.zip' for reading. Please ensure that the file exists and you have sufficient privileges to read it
I assume that's what you get too?
I'll check into the problem.
Hi @margaret_wei,
I tried using the URL in a FeartureReader in FME 2019.2 and did get the results:
Resulting in:
Could it be the attribute for the URL is changing the URL.
Have you tried using the URL instead of the attribute?
Hope this helps.
Interesting. And yet it fails for me too. I wonder why that is?! It's not the attribute since I was using the URL directly. It's very odd.
@erik_jan Thank you.
I tried
1) to use the same transformer as yours and used the url itself instead of attribute
Since I still failed, I installed 2019.02 as I was using 2019.01 before.
2) I tried the same with 2019.02
It made progress as I can see the coordinate system from the file this time.
But I ran into the error after a while.
Failed to obtain any schemas from reader 'SHAPEFILE' from 1 datasets. This may be due to invalid datasets or format accessibility issues due to licensing, dependencies, or module loading. See logfile for more information
Did it take you long to load that file?
Interesting. And yet it fails for me too. I wonder why that is?! It's not the attribute since I was using the URL directly. It's very odd.
Could it be a version issue?
I am using build 19813 - win 64.
Interesting. And yet it fails for me too. I wonder why that is?! It's not the attribute since I was using the URL directly. It's very odd.
I was using 2019.01 Mac.
Then I tried Build 19813, Mac 64.
The web service seems very inconsistent.
I was able to retrieve the data, but the next two tries failed with the same message as you got.
Seems to be a (timeout?) issue with the web service.
The web service seems very inconsistent.
I was able to retrieve the data, but the next two tries failed with the same message as you got.
Seems to be a (timeout?) issue with the web service.
That's what I was thinking too. With Log Debug on I was getting:
HTTP info: Operation too slow. Less than 1 bytes/sec transferred the last 90 seconds
HTTP info: Closing connection 0
HTTP info: schannel: shutting down SSL/TLS connection with ecos.fws.gov port 443
HTTP/FTP transfer error: 'Timeout was reached'
and yet it was working occasionally. Glad that it wasn't just me!
