Closed (duplicate)
Project:
Yr Weatherdata
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
16 Sep 2009 at 08:16 UTC
Updated:
3 Jun 2011 at 20:23 UTC
Jump to comment: Most recent
Comments
Comment #1
tjodolv commentedI haven't used the location module myself, but I'll take a look at it.
Comment #2
pvasili commentedI think that their integration will be very useful to all
Comment #3
tjodolv commentedThis is going to take some time to figure out if, and exactly how, it can be implemented, due to how yr.no deliver their location lookup.
Postponing this to a potential 2.0 release.
Comment #4
tjodolv commentedHello again. I will get to work on this when I have the time, as the location module seems ready for D7. I will start the work on the 7.x-1.x branch, but the implemetation for 6.x-2.x will be done almost in parallell.
Comment #5
Anonymous (not verified) commentedMaybe it's easier than you think. The location module has methods to determine proximity. It's commonly used to set up location-driven Views that take coordinates as input arguments and displays the node(s) or user(s) with the closest location.
On a side note, to both the maintainer and OP, the "Weather" module does this already. Too bad it only displays current weather and no forecasts.
Comment #6
Anonymous (not verified) commented#5 of course depends on having added a bunch of weather locations to the system.
Another possibility would be to explore the api of YR. These accept arbitrary coordinate input.
http://api.yr.no/weatherapi/documentation
http://api.yr.no/weatherapi/locationforecastlts/1.0/documentation
http://api.yr.no/weatherapi/locationforecast/1.8/documentation
Comment #7
tjodolv commentedYes, I have started looking at that API now, but I am waiting for an answer from yr.no on how these data are available. The only service listed as free on their website is the one currently in use where you have to input the url of the specific location you want. There have recently been some issues with certain applications requesting far too much data from the lat/long based API, and so they are currently reviewing access to it. But I will absolutely start working on this, because so many people are asking for it.
Comment #8
arru commentedI'm taking a stab at this right now; can't find anything about restrictions in the API docs except to credit Yr.no. Look here: http://api.yr.no/lisens.html
But it's always a good idea to keep # of requests down in cases like this. The strategy I'm working the moment is to round the lat/lon to integers or 1 decimal place to produce the YID, which appears to be well within the accuracy of weather prediction. These will then be retrieved and cached the same way as current location-based data.
Comment #9
tjodolv commentedCreated a new issue where I gathered up all the feature requests.
#1178150: Feature suggestions and requests