Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#4560 closed enhancement (invalid)

convert maps.xml (from scripts) into a new DB table / provide ability to add additional maps

Reported by: Paul Sands <usg990a@…> Owned by: ldunning
Priority: minor Milestone: unknown
Component: mythweather Version: head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

I found that the new mythweather trunk is working great! When I was setting up to use the maps (static and animated) from the scripts directory, I noticed that there is not currently a way to add additonal maps short of manually editing the maps.xml file.

Would it be possible to move the maps.xml data into the DB in a new table as well as providing a way to add new maps to the DB? For example, I live in the Dallas, TX USA area and although I can find maps that cover this area, none provide detail for Dallas. I added my own entry to the maps.xml file to get a local radar image which works great. The draw back is that the maps.xml file is overwritten with each svn update.

By adding a table that in which additional map sources can be defined would allow more user control over the process.

Change History (2)

comment:1 Changed 12 years ago by cpinkham

Resolution: invalid
Status: newclosed

Feature request without a patch.

comment:2 Changed 12 years ago by stuartm

We don't want this information, or any other script data in the database since the ultimate goal for mythweather (mythvideo etc) is for these data fetching scripts to be stored on the mythtv.org website and for mythfrontend to downloaded updated copies as they become available.

The problem with the old mythweather was that any small changes on the source websites required a new point release of MythTV. This new scheme changes that, updated/modified scripts and data files can be dropped into the scripts directory and become automatically available to MythWeather?. If you start storing this information in the database it complicates that process and IMHO makes it harder, not easier for users to run modified or custom mythweather scripts.

If the grabber currently in use (NWS) doesn't contain what you want, then write a new one, or modify the existing one but give it a new name. This will prevent updates from overwriting your changes. If you think your new grabber is an improvement, or would be useful for others then you can make it publicly available or even submit it for inclusion in SVN if it doesn't violate any terms of use or copyright.

Note: See TracTickets for help on using tickets.