Recent Posts

Pages: [1] 2 3 ... 10
1
Yes, you answered that you are NOT converting from WLK, you are using another download method.  Case closed on that one.

I almost missed this, he's not talking about converting or saving, but downloading?  I don't upload my data, so the only downloading I did was from the datalogger to WL.  As I mentioned previously, I didn't share my data for various reasons, I didn't maintain a full time internet connection for one.  I simply saved the data locally to the computer which, again, was easily saved in CSV as well as WLK.  Still don't see the big problem.
2
Yes very easy to export "spreadsheet" compatible files from WL, .txt export file behaves exactly the same way as a .csv would, both being ASCII files anyway. No software system of any worth would store "raw" download type data in any for of ASCII file so being able to export a binary format to and ASCII/export type file is very standard stuff.

This comment, like several others misses the point:  there is no easy connection to .WLK files.  Heck, ODBC was available before WLK was the Davis storage format.

Now you have changed tack down a connectivity path  #-o Honestly you appear a little lost and wandering around in circles with this one!

You're correct, he is lost and wandering around in circles.  I explained how I save WLK files as CSV, then he asked me how I'm converting WLK to CSV.  I was stupid enough to assume he was being serious, and not just trying to cause trouble, and that he just didn't know that they could be converted, or saved in a different format, or whatever if it's semantics he's attempting to play games with now. I should have known he wasn't worth dealing with when his question had been effectively answered before he asked it.

Actually, I still think he was dense enough to not understand, and now rather than admit that, he's running around in his little circles trying to make like we're the ones who are too dense to understand that WL really doesn't meet our requirements even if we think it does.  :roll:  It doesn't appear to me that he is really serious or adding anything of substance to the discussion, if so he would have done so without chasing his tail and yapping at people's heels.
3
Hi,
I just noticed on Toxic's UK version (pity about naming of site) for "Westerhope, Tyne & Wear".

The '&' throws an XHTMl error. https://validator.w3.org/check?uri=https%3A%2F%2Fwww.conligwx.org%2Fwxmesonetmap.php;accept=text%2Fhtml%2Capplication%2Fxhtml%2Bxml%2Capplication%2Fxml%3Bq%3D0.9%2Cimage%2Fwebp%2Cimage%2Fapng%2C%2A%2F%2A%3Bq%3D0.8;accept-language=en-GB%2Cen%3Bq%3D0.9%2Cen-US%3Bq%3D0.8%2Ces%3Bq%3D0.7
Was obviously always there, just never checked before.
Regards,
That's an easy fix.. in mesonet-map-json.php to change '&' to '&' for the town/state/county names.  Included in the update above.
4
We're really loving this warm sunny weather of late spring in the UK.

If you have a Davis Vantage Pro2 or Pro weather station we'd love to share a unique promotion.

We have a number of Solar Radiation Sensors with the mounting shelf which retail at over £300 and have them at less than half price £129 This promotion will run either until stocks last or it starts raining (just kidding on that last one). 

https://www.weatherspares.co.uk/davis-solar-radiation-sensor-6450--mounting-shelf-125-p.asp
5
The stations shown are all members of the Midwestern Regional network ( https://midwesternweather.net/ ) -- the mesonet.unl.edu stations are a different network and not displayed by the script.

The mesonet-map script set only displays stations that are members of the regional networks, not other mesonets.

Thanks! Maybe they will eventually get on same network like NeRain and Cocorahs did.   
6
Weather Website PHP/AJAX scripting / Re: advforecast2.php
« Last post by saratogaWX on Today at 01:33:04 PM »
The newer versions of forecast.weather.gov (and the api.weather.gov site) are somewhat twitchy about having more than 4 decimal places on lat/long.  The api.weather.gov insists on exactly 4 places (with trailing zeroes).  Go figure.
7
Weather Website PHP/AJAX scripting / Re: advforecast2.php
« Last post by ValentineWeather on Today at 01:31:00 PM »
Thanks for catching that Ken. I took the force off and changed the coordinates, will see if that clears it up. 
8
Based on some feedback from Wim and others, I've added a few tweaks to the script set.  The updated scripts (only) are attached.

Now a right-click on the map will bring up a context menu that allows you to:
1) see the lat/long of the point
2) show what settings need to be to reproduce this map as a default
3) center map to that point
4) zoom out or zoom in

The links all now follow the $doLinkTarget setting to create a target="_blank" (default is to do that).

The markers no longer display a rotating conditions label for Offlline stations.

Using ?cluster=nn  (nn = 5 to 80) allows adjustment of the clustering algorithm.  Higher numbers for more clustering.  The right-click context menu "Show Map Settings" will display the current rmClusterRadius value.

Town/county/state names with '&' will use '&' instead for HTML validation.

9
The stations shown are all members of the Midwestern Regional network ( https://midwesternweather.net/ ) -- the mesonet.unl.edu stations are a different network and not displayed by the script.

The mesonet-map script set only displays stations that are members of the regional networks, not other mesonets.
10
Weather Website PHP/AJAX scripting / Re: advforecast2.php
« Last post by saratogaWX on Today at 01:19:07 PM »
Version 4.05 doesn't use api.weather.gov -- it 'scrapes' the point-printable forecast page.  Activating a force-a-fetch-on-every-load is NOT a good idea -- it slows down your site and unnecessarily loads the forecast.weather.gov site (which can get your server's IP address blocked by them).

It's better to find exactly what the root cause of the issues are and address that.

One thing to try changing is the forecast URL in Settings.php.
You have
Code: [Select]
http://forecast.weather.gov/MapClick.php?lat=42.87049&lon=-100.55677633445953&unit=0&lg=english&FcstType=text&TextType=2 -- doing a lookup on Valentine, NE makes the current printable forecast as
Code: [Select]
https://forecast.weather.gov/MapClick.php?lat=42.8738&lon=-100.5506&unit=0&lg=english&FcstType=text&TextType=2It may be the unnecessarily long lat/long specs are causing intermittent issues.

Pages: [1] 2 3 ... 10
anything