Can anyone load this hurricane track service into Essentials?
I am trying to use the url for the following rest service that is available (hurricane cone)...
Description:
http://www.arcgis.com/home/item.html?id=10dc113cdf7f46f5878ebae4a7c5d708
The rest service I am trying to load as a map service in Essentials:
(shown on bottom right of above link)
https://nowcoast.noaa.gov/arcgis/rest/services/nowcoast/wwa_meteocean_tropicalcyclones_trackintensityfcsts_time/MapServer
But Essentials keeps showing "No Results found" or "forbidden error". I can view the rest service directly without issue.
Thanks,
Carmen
0
-
Access Denied
You don't have permission to access "http://nowcoast.noaa.gov/arcgis/rest/services/nowcoast/wwa_meteocean_tropicalcyclones_trackintensityfcsts_time/MapServer" on this server.
This is likely some sort of CORS issue to prevent use of the services in unauthorized web viewers.0 -
We are having the same issue. We were using Nowcoast services until May of this year. That's when NOAA secured their site.
You can use this services for Hurricane data for the interim: https://idpgis.ncep.noaa.gov/arcgis/rest/services/NWS_Forecasts_Guidance_Warnings/NHC_Atl_trop_cyclones_active/MapServer
A developer in our organization was able to connect to some NOAA data but he had to contact NOAA's IT staff to get granted access. I'm still actively pursiung getting our Geocortex/Nowcoast site connection "reconected". I'll post if I find a solution.
Rick0 -
Thank you! 0 -
I have run into the same issue with the Nowcoast lightning density map service, and I can't find an alternative source for that information. Please let me know if you find a solution to connecting to these services! 0 -
Hi,
What address are you using for this service? I was able to load all services from the link below.
https://nowcoast.noaa.gov/arcgis/rest/services
Thanks,
Mike Ketler0 -
Mike,
Are you accessing the NowCoast service from a Geocortex installation within a DMZ? My sites are within an organization Intranet. We are thinking that the NowCoast service is requesting a servername back and our firewall is not permitting this traffic?
Rick0 -
Hi,
I just tested the address in Essentials and it won't work. I used Fiddler to figure out that they are blocking any requests that don't contain the User-Agent HTTP header. Manager is an IIS process and doesn't send this header when you try and add a map service to your site. Unfortunately, there's no work around in Essentials. You could contact NOAA and suggest they remove this restritction.
Thanks,
Mike Ketler0 -
Mike,
I just sent an email to nowcoast.team@noaa.gov (To: nowcoast.team@noaa.gov) mailto:nowcoast.team@noaa.gov with your comments to see if they can help us out. If anyone is interested, here are additional contacts:
John Kelley
John.Kelley@noaa.gov
nowCOAST™ Project Manager
Coastal Marine Modeling Branch
NOAA/NOS/CSDL
Jason Greenlaw
Jason.Greenlaw@noaa.gov
Primary Developer
Coastal Marine Modeling Branch
NOAA/NOS/CSDL
John Evans
John.G.Evans@noaa.gov
Assistant Developer
Integrated Dissemination Program
NOAA/NWS/Office of Dissemination
Regards, Rick0 -
Watching to see what you find out! Add me to the list of interested parties who would like to add this to an intranet application that is used by City of Greenville employees. Mostly Fire and Police and weather nerds like me. Although Public Works and Parks would be interested as well.
Carmen0 -
Here was the response from the NOAA Nowcoast team:
"Hello Richard,
Unfortunately, the User-Agent header requirement was implemented as a security control and it is unlikely that the restriction will be removed.
I am not familiar with 'Geocortex', but I suggest contacting the software vendor to encourage them to include an application-identifying User-Agent header in all requests.
Another option would be to configure your own HTTP/HTTPS proxy that does include a User-Agent header and routes traffic between nowCOAST and your Geocortex installation.
Jason"
I need to get with our IT security team to see if we can implement the last option.
Rick0 -
I'm watching, too! I just ran into an error trying to use one of the nowcoast services in a webrequest activity. I received the 403 Forbidden error.
If anyone finds a good work around, please share.
Thanks!
Stephanie0 -
If you are sending your request through the Essentials proxy ([webroot]/proxy.ashx ), you can add the following line to the proxy.ashx file at approximately line 110 (above bolded text below) which should send the necessary user agent header. req.UserAgent ="Geocortex"; // add this line <b>req.Method = context.Request.HttpMethod; //existing code</b>0 -
Hm... the bold on my text got removed when I posted but you get the idea based on the comments, I hope. 0 -
Hey Peter, can you elaborate a little more on your fix? I only know of the ESRI resource proxy. Do you know of a help article about this? Thanks! 0 -
I know it's been a couple years, but...Did anyone ever get a resolution to the (403) Forbidden error?
We switched over to the https://idpgis.ncep.noaa.gov services that Rick had suggested back when we lost access to the Nowcast services. Unfortunately, we are now getting that same 403 error on the https://idpgis.ncep.noaa.gov services.
The map services draw fine in the map viewer - - we only get the error when trying to run a query via a workflow.
Is there something I can change in the proxy to fix it?
Thank you,
Stephanie0 -
Richard - were you ever able to get the nowcoast data working? We took your suggestion a couple years and switched to idpgis.ncep.nooa.gov, but now we are having the same problem with those services.
Thank you,
Stephanie0 -
Peter - Can you provide any more details on your fix? I added the req.UserAgent="Geocortex" to the proxy.ashx, but I think I might be missing a step somewhere as I'm still not able to access the noaa services.
Thank you again!0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
18 Kommentare