HiGood to hear after so long. I am familiar with working in beautiful soup,XML,RSS feeds, mapping so would love to contribute in that.Let me know how and when to start.
RegardsKonark.K.Modi+91-9888211816On Wed, Aug 25, 2010 at 7:33 PM, Ajay Kumar <ajuo...@gmail.com> wrote:
Hi Guys,
Some of us have been working on the Flood Alert portal and we need some help now :)
The details are here:
http://ictd.asia/wiki/CWC_Flood_Forecast_-_India
We primarily need help with the "presentation" of the information/data we are sourcing from the CWC which posts daily updates on River Water Level, Rainfall & Flood Alert Situation(if any) for each of the flood forecasting sites in India that are publically listed.
So if you have any of the listed skills and have time to help, please respond and feel free to ask questions :)
Our next task is:
1) Publishing Feeds
2) the UI and Mapping the information and displaying it on our portal
Apart from the skills, your comments, suggestions and advice are welcome as well!~
More soon!
--
Best Regards,
Ajay Kumar
http://www.ajuonline.net
iwscraper.py worked fine for me, though.
This is a snapshot of what I'm doing.
http://ictd.asia/code/ictdasia-cwc.tar.gz
I'm sure you'll find a lot of bugs. So, go right ahead
Ravi,I looked at the data being saved in the DB.On 25 August 2010 22:37, Ravi chandra padmala <neenao...@gmail.com> wrote:
This is a snapshot of what I'm doing.
http://ictd.asia/code/ictdasia-cwc.tar.gz
I'm sure you'll find a lot of bugs. So, go right ahead
Table: site_profile , field: site_type. Values: "level forecasting site" or "inflow forecasting site"
I think there is no need to save the complete text. The flood forecast site types are: Inflow/Level.
And in the DB only site IDs from 1-79 and 148 are saved in site_profile ?
Looks like the source is missing the .py with the definition of
FloodData (in alertscraper.py)?
cwc-script.py should get everything we need and store it in the database specified in settings.py
While I work on the server side issue of identifying the problem and solving it, I have updated the wiki page with more tasks and next steps.
Ok. the code seems to be crashing after some iterations on the server. Possible memory issue.
I dont have capable servers to run the scripts so I wrote a scraperCheck
I just noticed this as well that you put up: http://media.thejeshgn.com/visualizations/india-flood-alert.html
I dont have capable servers to run the scripts so I wrote a scraperCheck
On Fri, Sep 10, 2010 at 12:32 AM, Thejesh GN <i...@thejeshgn.com> wrote:I dont have capable servers to run the scripts so I wrote a scraperCheckNice,
If you're interested in helping develop the UI, I could give you access to the server on which we're running the scraper. Though, a standard desktop should be capable enough to run the scripts.
I could use some help with the UI development.
Sure. Can I access the data in JSON format?Which gets automatically updated everyday.
For now we just run the scraper daily 4 times since they update data at multiple instances on a day. The data is stored in pgsql. If you want I can send SSH access details to the server?On 11 September 2010 14:43, Thejesh GN <i...@thejeshgn.com> wrote:
Sure. Can I access the data in JSON format?Which gets automatically updated everyday.
We are sharing resources right now, i.e. running the scraper on another VPS while we will publish it on the vps that ictd.asia is hosted on, so a little load sharing happening there :)
For now the priorities are:
1) To enable anyone to sign up to recieve these updates for their region(or a set of sites) over Email at those intervals in a day. I.e. we run the script 4 times a day, an email sent 4 times a day instantly.
2) Publish it online as a nice info display.
3) We could link the RSS feed to third party provider like identi.ca/twitter for people to subscribe? As I am not sure how much extra load will opening up the API/RSS etc add to the server.
Sure. How about Google App Engine to pull that data from your sever and serving the world through AppEngine. That way we will reduce load on your server and we can give access to others.
For now the priorities are:
1) To enable anyone to sign up to recieve these updates for their region(or a set of sites) over Email at those intervals in a day. I.e. we run the script 4 times a day, an email sent 4 times a day instantly.
This is difficult to do with limited resources.
2) Publish it online as a nice info display.We could do this. I can work on this.
Sure. Can I access the data in JSON format?Which gets automatically updated everyday.