https://bugs.kde.org/show_bug.cgi?id=515041
--- Comment #8 from Angel Parra <[email protected]> --- Created attachment 193242 --> https://bugs.kde.org/attachment.cgi?id=193242&action=edit Forecast works, but *only* the forecast. OH alright, if I do type the whole name (or only up to the á) and choose the wetter.com alt, the weather forecast works, but only the forecast; not the actual current stats such as temp, thermal sensation nor UV index, which are essential metrics where I live and especially UV index as it gets very hot in the summer. Please open the attachment. > I think it's a problem on NOAA side. Probably still a problem on both sides, or better said, the API that is being used. NOAA for Culiacán works fine if you directly open its NOAA entry: https://tgftp.nws.noaa.gov/weather/current/MMCL.html The statistics show fine for the current 24 hours, directly from NOAA. Beware this takes a bit to load, it might timeout for you. It's a pain to just skim through the files searching for API info. I have no idea how I even found this URL again. There's a search field that tries to do its job searching for more cities. Apparently, the NOAA has more APIs besides just weather.gov. This is for the string "Guamúchil", encoded as "Guam%C3%BAchil" http://www.firstgov.gov/fgsearch/index.jsp?parsed=true&rn=3&in0=domain&dom0=nws.noaa.gov%2C+weather.gov%2C+wrh.noaa.gov%2C+srh.noaa.gov%2C+crh.noaa.gov%2C+prh.noaa.gov%2C%0D%0Aarh.noaa.gov%2C+alaska.net%2F%7Enwsar%2C+erh.noaa.gov%2C+ncep.noaa.gov%2C+spc.noaa.gov%2C+nhc.noaa.gov%2C+sec.noaa.gov%2C+aviationweather.gov%2C%0D%0Aaviationweather.noaa.gov%2C+weather.noaa.gov%2C+roc.noaa.gov%2C+nohrsc.nws.gov%2C+nwstc.noaa.gov%2C+wdtb.noaa.gov%2C+npmoc.navy.mil%2C%0D%0Andbc.noaa.gov&mw0=Guam%C3%BAchil&Go2=Go Unfortunately, the GO button takes me to usa.gov but it's probably worth peeking at those URLs. --- Actually, I don't know how Culiacan (no diacritic) is even shown in Plasma's applet search results. If I go to weather.gov and type the non-diacritic graphy, the page shows: No results found. Please try a different search string. The problem might be or not the NOAA, but actually for whatever API this applet uses that pointed to a non-existent "Culiacan", then attributed to NOAA which does have it (TGFTP) and not at the same time (web search results) and there you have the "InvalidPoint" error on API. ~ $ curl -i -H "User-Agent: (KDE Plasma Weather Applet, [email protected])" \ https://api.weather.gov/points/24.8034,-107.3944 HTTP/2 404 server: nginx/1.28.3 content-type: application/problem+json x-request-id: f329a2a8-84d3-4471-816a-690747b90a00 x-correlation-id: ef5acd75 x-server-id: vm-cprk-api-ops-app3.ncep.noaa.gov access-control-allow-origin: * access-control-expose-headers: X-Correlation-Id, X-Request-Id, X-Server-Id server-timing: dtTrId;desc="3929f07cf6f28e7d5ba1d32f61b3928a", dtSInfo;desc="0" content-length: 307 cache-control: private, max-age=86400 expires: Thu, 18 Jun 2026 19:34:29 GMT date: Wed, 17 Jun 2026 19:34:29 GMT set-cookie: dtCookie1up6hiss=v_4_srv_2_sn_434E9FACCF5AAE10952751AD61A1AC34_perc_100000_ol_0_mul_1_app-3Aea7c4b59f27d43eb_1; Path=/; Domain=.weather.gov x-edge-request-id: 3f7e65f4 vary: Accept,Feature-Flags,Accept-Language strict-transport-security: max-age=31536000 ; includeSubDomains ; preload { "correlationId": "ef5acd75", "title": "Data Unavailable For Requested Point", "type": "https://api.weather.gov/problems/InvalidPoint";, "status": 404, "detail": "Unable to provide data for requested point 24.8034,-107.3944", "instance": "https://api.weather.gov/requests/ef5acd75"; }% ~ $ curl -s "https://nominatim.openstreetmap.org/search?q=Culiacan&format=json&limit=1"; [{"place_id":314403914,"licence":"Data © OpenStreetMap contributors, ODbL 1.0. http://osm.org/copyright","osm_type":"node","osm_id":273590692,"lat":"24.7978965","lon":"-107.3933950","class":"place","type":"city","place_rank":16,"importance":0.5512437698005868,"addresstype":"city","name":"Culiacán","display_name":"Culiacán, Culiacán Rosales, Culiacán, Sinaloa, 80220, México","boundingbox":["24.6378965","24.9578965","-107.5533950","-107.2333950"]}]% ~ $ curl -i -H "User-Agent: (KDE Plasma Weather Applet, [email protected])" \ https://api.weather.gov/points/24.637,-107.553 HTTP/2 404 server: nginx/1.28.3 content-type: application/problem+json x-request-id: ef277e41-8575-45e8-b3b4-5c7f1625c6a1 x-correlation-id: d93cdb48 x-server-id: vm-cprk-api-ops-app5.ncep.noaa.gov access-control-allow-origin: * access-control-expose-headers: X-Correlation-Id, X-Request-Id, X-Server-Id server-timing: dtTrId;desc="356338be673cf2630c670313a622e115", dtSInfo;desc="0" content-length: 305 cache-control: private, max-age=86400 expires: Thu, 18 Jun 2026 19:45:07 GMT date: Wed, 17 Jun 2026 19:45:07 GMT set-cookie: dtCookie1up6hiss=v_4_srv_2_sn_D5C97170C0258C511F673657BB421841_perc_100000_ol_0_mul_1_app-3Aea7c4b59f27d43eb_1; Path=/; Domain=.weather.gov x-edge-request-id: 3ed9ffa7 vary: Accept,Feature-Flags,Accept-Language strict-transport-security: max-age=31536000 ; includeSubDomains ; preload { "correlationId": "d93cdb48", "title": "Data Unavailable For Requested Point", "type": "https://api.weather.gov/problems/InvalidPoint";, "status": 404, "detail": "Unable to provide data for requested point 24.637,-107.553", "instance": "https://api.weather.gov/requests/d93cdb48"; }% In conclusion, at least the local airport's reading on TGFTP works, Gemini (sorry) said that the NOAA itself is only full-fledged in the US and in Mexico we have the web service from the Servicio Metereológico Nacional (CONAGUA) that is better suited for this than the NOAA. You may translate the page to English if you wish to lean towards national providers for different countries ~ $ curl -i -H "User-Agent: (KDE Plasma Weather Applet, [email protected])" \ https://api.weather.gov/points/24.637,-107.553 HTTP/2 404 server: nginx/1.28.3 content-type: application/problem+json x-request-id: ef277e41-8575-45e8-b3b4-5c7f1625c6a1 x-correlation-id: d93cdb48 x-server-id: vm-cprk-api-ops-app5.ncep.noaa.gov access-control-allow-origin: * access-control-expose-headers: X-Correlation-Id, X-Request-Id, X-Server-Id server-timing: dtTrId;desc="356338be673cf2630c670313a622e115", dtSInfo;desc="0" content-length: 305 cache-control: private, max-age=86400 expires: Thu, 18 Jun 2026 19:45:07 GMT date: Wed, 17 Jun 2026 19:45:07 GMT set-cookie: dtCookie1up6hiss=v_4_srv_2_sn_D5C97170C0258C511F673657BB421841_perc_100000_ol_0_mul_1_app-3Aea7c4b59f27d43eb_1; Path=/; Domain=.weather.gov x-edge-request-id: 3ed9ffa7 vary: Accept,Feature-Flags,Accept-Language strict-transport-security: max-age=31536000 ; includeSubDomains ; preload { "correlationId": "d93cdb48", "title": "Data Unavailable For Requested Point", "type": "https://api.weather.gov/problems/InvalidPoint";, "status": 404, "detail": "Unable to provide data for requested point 24.637,-107.553", "instance": "https://api.weather.gov/requests/d93cdb48"; }% So, in conclusion... > Not sure what we can do about this Using countries' local meteorological providers instead of trying to load every search to the NOAA, which seems to be the main issue here, is a very good start. Turns out each country have their own service to report their own climate. And thank you for providing track and feedback again, I'm grateful" -- You are receiving this mail because: You are watching all bug changes.
