CN109783473A - A kind of information processing method automatically creating Rainfall Disaster data-base recording - Google Patents
A kind of information processing method automatically creating Rainfall Disaster data-base recording Download PDFInfo
- Publication number
- CN109783473A CN109783473A CN201811602789.2A CN201811602789A CN109783473A CN 109783473 A CN109783473 A CN 109783473A CN 201811602789 A CN201811602789 A CN 201811602789A CN 109783473 A CN109783473 A CN 109783473A
- Authority
- CN
- China
- Prior art keywords
- disaster
- beginning
- straight
- disaster event
- message part
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The present invention relates to a kind of information processing methods for automatically creating Rainfall Disaster data-base recording, comprising: creation Disaster Event record: straight message part being integrated into existing Disaster Event and records or create new Disaster Event record with the end time at the beginning of according to the straight message part of the condition of a disaster；Merge Disaster Event record: the Disaster Event record of overlapping being merged with the end time at the beginning of according to each Disaster Event.Compared with prior art, the present invention passes through the xml code of the straight message part of parsing by the way of programming automation, Disaster Event record is created based on precipitation data, efficiently all straight report file resources can be put in storage automatically, the efficiency for improving comprehensive the condition of a disaster information integration, to preferably provide help for disaster management.
Description
Technical field
The present invention relates to a kind of computer technologies, more particularly, to a kind of letter for automatically creating Rainfall Disaster data-base recording
Cease processing method.
Background technique
The condition of a disaster data are the bases of Disaster Study and management, and in disaster response, assessment and management work, disaster occurs
It is government and associated mechanisms management and the action of decision disaster assistance, post-disaster rescue that the system for influencing data with disaster, which is collected with management,
Fund, post-disaster reconstruction and recovery etc. provide important evidence.
The condition of a disaster data are usually using administrative area as survey unit, in such a way that the condition of a disaster is directly reported step by step by each administrative division
Report acquisition.And disaster database is when counting disaster loss data, not using administrative area as investigation unit, but with Disaster Event
Record is unit.
History disaster database is established, for the straight message part of a large amount of history the condition of a disasters, how to quickly introduce disaster database, and
Disaster Event is integrated into be recorded as problem.Previous traditional approach be by manually creation Disaster Event record one by one, then by
Item is in all straight message part input databases of the Disaster Event, this very time consuming effort of mode, and working efficiency is extremely low.
Summary of the invention
It is an object of the present invention to overcome the above-mentioned drawbacks of the prior art and provide one kind to automatically create heavy rain
The information processing method of disaster database record.
The purpose of the present invention can be achieved through the following technical solutions:
A kind of information processing method automatically creating Rainfall Disaster data-base recording, comprising:
Creation Disaster Event record: straight message part is integrated into the end time at the beginning of according to the straight message part of the condition of a disaster
Existing Disaster Event record creates new Disaster Event record；
Merge Disaster Event record: the Disaster Event of overlapping being remembered with the end time at the beginning of according to each Disaster Event
Record merges.
The creation Disaster Event record specifically includes:
Step A1: reading straight message part, parses the xml code of straight message part, at the beginning of extracting straight message part and ties
The beam time；
Step A2: at the beginning of the straight message part based on extraction and the end time, judge whether in any created
In Disaster Event record, if it is, A3 is thened follow the steps, if it has not, thening follow the steps A4；
Step A3: the straight message part is integrated into the Disaster Event created record, and updates opening for Disaster Event
Begin time or end time；
Step A4: according to straight report document creation, new Disaster Event is recorded, and the straight message part merger to the event is remembered
In record.
Assert that foundation of the straight message part in any Disaster Event created includes: in the step A2
The straight report file start times extracted are first 1 day that any Disaster Event created records the time started, or are
1 day after any Disaster Event record end time created.
Foundation of the straight message part in any Disaster Event record created is assert in the step A2 further include:
At the beginning of the straight message part extracted at the beginning of any Disaster Event record created at the end of
Between between.
At the beginning of updating Disaster Event in the step A3 or the process of end time specifically includes:
If the straight report file start times extracted are first 1 day at the beginning of the Disaster Event created, update
At the beginning of at the beginning of Disaster Event being the straight message part extracted.
If being updated 1 day after the end time that the straight report file start times extracted are the Disaster Event created
At the beginning of the end time of Disaster Event is the straight message part extracted.
The merging Disaster Event recording process includes:
Step B1: judging in database Disaster Event record sheet, any two Disaster Event record, if there are two things
There is intersection in the beginning and the end time of part, or records at the beginning of recording with the presence or absence of a Disaster Event for another Disaster Event
End time one day after, it is for example no if it is, then follow the steps B2, then do not do and merge；
Step B2: merging two Disaster Events record, and at the beginning of two Disaster Events are recorded in make by the former
At the beginning of for new Disaster Event record, using latter in the end time of two Disaster Events record as new disaster
The end time of event traverses entire database, updates all Disaster Event records and the file information is directly reported in merger.
The step A4 is specifically included:
Step A41: the precipitation data on the straight report file start times same day is transferred；
Step A42: judging whether the meteorogical phenomena database daily precipitation data transferred are greater than predetermined threshold, if it has, then executing
Step A43, if it has not, thening follow the steps A44；
Step A43: creation Disaster Event record, and be arranged Disaster Event record at the beginning of and the end time be straight
At the beginning of message part；
Step A44: it fails to match for prompt, and the copy for creating the straight message part marks the straight message part to specified directory
There may be problems.
Compared with prior art, the invention has the following advantages:
1) system passes through the xml code for parsing straight message part by the way of programming automation, based on precipitation data
Disaster Event record is created, efficiently all straight report file resources can be put in storage automatically, improves comprehensive the condition of a disaster information integration
Efficiency, to preferably provide help for disaster management.
2) since the condition of a disaster of general Disaster Event directly reports the lag for reporting time of origin that may have 1~2 day, system background is certainly
Dynamic traverses entire database, and the corresponding same Disaster Event of category merges, and modifies the beginning and the end time of event.
3) it calls daily precipitation data as voucher, carries out the creation of Disaster Event record, can Disaster Event be recorded
Creation have foundation, avoid due to the content mistake of straight message part mistake creation Disaster Event record.
Detailed description of the invention
Fig. 1 is flow diagram of the invention.
Specific embodiment
The present invention is described in detail with specific embodiment below in conjunction with the accompanying drawings.The present embodiment is with technical solution of the present invention
Premised on implemented, the detailed implementation method and specific operation process are given, but protection scope of the present invention is not limited to
Following embodiments.
Currently, the condition of a disaster, which is collected, is based on administrative division more, county is focused on by the small towns at place, then report to city, reported step by step,
It mostly reports and acquires with the file mode of xml format since the condition of a disaster in history reports.
In the application, file warehousing and further data process&analysis are directly reported in order to facilitate the condition of a disaster, are reduced a large amount of artificial
It creates precipitation and causes Disaster Event, and manually the straight count off of the condition of a disaster that junior reports according in event where being referred to.If
A kind of software flow processing method is counted and realized, solves the automatic processing of system event record creation, without artificial dry
In advance, straight report file warehousing is read and parsed automatically and is recorded with Disaster Event and carries out merger, convenient for counting calamity by unit of event
Feelings data and analysis provide Data safeguard for crop loss rate and statistical analysis and aid decision.
A kind of information processing method automatically creating Rainfall Disaster data-base recording, as shown in Figure 1, comprising:
Creation Disaster Event record: straight message part is integrated into the end time at the beginning of according to the straight message part of the condition of a disaster
Existing Disaster Event record creates new Disaster Event record；
Merge Disaster Event record: the Disaster Event of overlapping being remembered with the end time at the beginning of according to each Disaster Event
Record merges.
Wherein, creation Disaster Event record specifically includes:
Step A1: reading straight message part, parses the xml code of straight message part, at the beginning of extracting straight message part and ties
The beam time；
Step A2: at the beginning of the straight message part based on extraction and the end time, judge whether in any created
In Disaster Event record, if it is, A3 is thened follow the steps, if it has not, thening follow the steps A4；
Specifically, assert that foundation of the straight message part in any Disaster Event created includes: extraction in step A2
It is at the beginning of straight message part first 1 day at the beginning of any Disaster Event created, or is any disaster created
1 day after the end time of event.
Preferably, foundation of the straight message part in any Disaster Event created is assert in step A2 further include: extract
Straight message part at the beginning of at the beginning of any Disaster Event created between the end time.
Step A3: the straight message part is integrated into the Disaster Event created, and at the beginning of updating Disaster Event
Between or the end time, wherein at the beginning of updating Disaster Event or the process of end time specifically includes: if the straight report extracted
For 1 day before the beginning of the Disaster Event created at the beginning of file, then at the beginning of updating the disaster time
At the beginning of straight message part for extraction, if at the beginning of the straight message part extracted being the knot of the Disaster Event created
1 after the beam time, then update the disaster time end time be extract straight message part at the beginning of.
Step A4: according to straight report document creation, new Disaster Event is recorded, and is specifically included:
Step A41: the precipitation data on the straight report file start times same day is transferred；
Step A42: judging whether the meteorogical phenomena database daily precipitation data transferred are greater than predetermined threshold, if it has, then executing
Step A43, if it has not, thening follow the steps A44；
Step A43: creation Disaster Event record, and be arranged Disaster Event record at the beginning of and the end time be straight
At the beginning of message part；
Step A44: it fails to match for prompt, and the copy for creating the straight message part marks the straight message part to specified directory
There may be problems.
In addition, merging Disaster Event recording process includes:
Step B1: judging in database Disaster Event record sheet, any two Disaster Event record, if there are two things
The beginning and the end time of part has intersection (time intersects phenomenon), or is another at the beginning of recording with the presence or absence of a Disaster Event
(the time tangent phenomenon) one day after of a Disaster Event record end time, if it is, B2 is thened follow the steps, it is for example no, then not
It does and merges；
Step B2: and two Disaster Events record, and by two Disaster Events it is forward at the beginning of as new disaster
At the beginning of event, using the end time of two Disaster Events rearward as the end time of new Disaster Event, traverse whole
A database, updates all Disaster Event records and the file information is directly reported in merger.And delete former two Disaster Events record.
Based on the software of the application method exploitation, it is straight that all history the condition of a disasters are uploaded by FTP (File Transfer Protocol) first
Message part (xml format) arrives server specified folder: such as Hunan Province, and annual April to November is flood season, and precipitation occurs
After journey event, city, district report the straight message part of the condition of a disaster once having the condition of a disaster where linchpin belongs to, and last more than 20 years, have accumulated nearly ten thousand
A file.System reads all straight message parts in this document folder automatically, parses its code, is integrated into respective Disaster Event record simultaneously
Storage.Straight message part uses XML structure file, develops program with can be convenient and is interpreted, and does not need using complicated language
Reason and good sense solution technology can be translated accurately.
The format sample of one straight message part is as follows:
<Disateraffect>according to investigations, the small towns such as city Quan Tang, mountain jujube, Mei Qiao, Li Shan, dragon's cave-stalactite cave are influenced by strong wind,
There is damage house, the condition of a disasters such as collapse big tree, industrial crops are impaired.According to Department of Civil Affairs, bureau of agriculture's rough estimates, house is damaged altogether
Between 32, between collapsed house 5.There is 23000 mu of corn area of spring sowing kind in the whole city, and 15000 mu or so of disaster area, wherein corn blows folding
Area is up to 20%, about 2950 mu, 3,500,000 yuan of direct economic loss.</Disateraffect>
<EconomyLoss>350</EconomyLoss>
<Forecastserve>on May 10th, 2014, my office forecaster according to newest meteorological data comprehensive analysis, and with
Meteorological observatory, city consultation, has been issued " in mid-May, 2015 ten days report ", and ten days domestic demand is prompted to reinforce prevention thunderstorm gale, short-time strong rainfall
Etc. disaster caused by convection weathers influence.And " thunderstorm gale orange warning signal " was issued when 11 days 04 May, ask government and phase
Pass department carries out anti-strong wind according to responsibility and works.Since 10 days, the middle ten days ten days report and pre-warning signal were passed through electronics in time by we
The multiple channels such as mailbox, phone, early warning system, MAS SMS platform, electronic display report and submit Government departments, related leader
And service unit.During flood season, office leader takes personal charge of the shift in person, and Meteorological Services personnel adhere to 24 hours double hilllocks watch systems, tight to supervise
It is comprehensive to carry out Weather-service depending on Changes in weather.
After the condition of a disaster occurs, leaders are paid much attention to, and tissue is fought calamities and provided relief.My office staff arrives Department of Civil Affairs, agriculture in time
Industry office, the spring pool, which understand, collects the condition of a disaster.</Forecastserve>
<GSUMMARIZE>is cooled air impact, and at 11 days 4 or so, the city is local strong wind occurs.According to national automatic Weather Station
Data shows, 11 separate existing 17.6 meter per second of extreme wind speed when survey station 04.It is shown according to region automatic weather station (source of agriculture), greatly
Wind speed is 18.1 meter per seconds, reaches strong wind standard.</GSUMMARIZE>
Claims (7)
1. a kind of information processing method for automatically creating Rainfall Disaster data-base recording characterized by comprising
Creation Disaster Event record: at the beginning of according to the straight message part of the condition of a disaster and the end time straight message part is integrated into it is existing
Disaster Event records or creates new Disaster Event record；
Merge Disaster Event record: at the beginning of according to each Disaster Event and the end time to the Disaster Event of overlapping record into
Row merges.
2. a kind of information processing method for automatically creating Rainfall Disaster data-base recording according to claim 1, feature
It is, the creation Disaster Event record specifically includes:
Step A1: reading straight message part, parses the xml code of straight message part, extract at the beginning of straight message part and at the end of
Between；
Step A2: at the beginning of the straight message part based on extraction and the end time, judge whether in any disaster created
In logout, if it is, A3 is thened follow the steps, if it has not, thening follow the steps A4；
Step A3: the straight message part is integrated into the Disaster Event created record, and at the beginning of updating Disaster Event
Between or the end time；
Step A4: according to straight report document creation, new Disaster Event is recorded, and by the straight message part merger into the logout.
3. a kind of information processing method for automatically creating Rainfall Disaster data-base recording according to claim 2, feature
It is, assert that foundation of the straight message part in any Disaster Event created includes: in the step A2
The straight report file start times extracted are first 1 day that any Disaster Event created records the time started, or are any
1 day after the Disaster Event record end time created.
4. a kind of information processing method for automatically creating Rainfall Disaster data-base recording according to claim 3, feature
It is, foundation of the straight message part in any Disaster Event record created is assert in the step A2 further include:
At the beginning of the Disaster Event record created at the beginning of the straight message part extracted any and the end time it
Between.
5. a kind of information processing method for automatically creating Rainfall Disaster data-base recording according to claim 3, feature
It is, at the beginning of updating Disaster Event in the step A3 or the process of end time specifically includes:
If the straight report file start times extracted are first 1 day at the beginning of the Disaster Event created, disaster is updated
At the beginning of at the beginning of event being the straight message part extracted.
If updating disaster 1 day after the end time that the straight report file start times extracted are the Disaster Event created
At the beginning of the end time of event is the straight message part extracted.
6. a kind of information processing method for automatically creating Rainfall Disaster data-base recording according to claim 1, feature
It is, the merging Disaster Event recording process includes:
Step B1: judging in database Disaster Event record sheet, any two Disaster Event record, if there are two events
There is intersection in the beginning and the end time, or is another Disaster Event record end at the beginning of recording with the presence or absence of a Disaster Event
Time one day after, it is for example no if it is, then follow the steps B2, then do not do and merge；
Step B2: merging two Disaster Events record, and at the beginning of two Disaster Events are recorded in by the former as newly
Disaster Event record at the beginning of, using two Disaster Events record end time in latter as new Disaster Event
End time, traverse entire database, update all Disaster Events record and the file information is directly reported in merger.
7. a kind of information processing method for automatically creating Rainfall Disaster data-base recording according to claim 2, feature
It is, the step A4 is specifically included:
Step A41: the precipitation data on the straight report file start times same day is transferred；
Step A42: judging whether the meteorogical phenomena database daily precipitation data transferred are greater than predetermined threshold, if it is, thening follow the steps
A43, if it has not, thening follow the steps A44；
Step A43: creation Disaster Event record, and be arranged Disaster Event record at the beginning of and the end time be straight message
At the beginning of part；
Step A44: it fails to match for prompt, and the copy for creating the straight message part marks the straight message part may to specified directory
There are problems.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811602789.2A CN109783473A (en) | 2018-12-26 | 2018-12-26 | A kind of information processing method automatically creating Rainfall Disaster data-base recording |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811602789.2A CN109783473A (en) | 2018-12-26 | 2018-12-26 | A kind of information processing method automatically creating Rainfall Disaster data-base recording |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109783473A true CN109783473A (en) | 2019-05-21 |
Family
ID=66498489
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811602789.2A Pending CN109783473A (en) | 2018-12-26 | 2018-12-26 | A kind of information processing method automatically creating Rainfall Disaster data-base recording |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109783473A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113987007A (en) * | 2021-10-12 | 2022-01-28 | 中冶南方工程技术有限公司 | Blast furnace slag skin falling and merging method, terminal equipment and storage medium |
| CN115798174A (en) * | 2022-11-01 | 2023-03-14 | 成都市美幻科技有限公司 | Fusion processing method, device, equipment and storage medium for multi-disaster early warning information |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101257421A (en) * | 2007-02-27 | 2008-09-03 | 仁荷大学教产学协力团 | Real time automatic update system and method for disaster damage investigation |
| CN105809372A (en) * | 2016-04-20 | 2016-07-27 | 国家电网公司 | Natural disaster risk monitoring system based on satellite remote sensing image |
| CN106651004A (en) * | 2016-11-18 | 2017-05-10 | 上海师范大学 | Flood forecasting method based on rainfall flood space-time database |
| CN107220279A (en) * | 2017-04-19 | 2017-09-29 | 民政部国家减灾中心 | The Dynamic Tracking and system of Disaster Event |
| CN108155928A (en) * | 2017-11-09 | 2018-06-12 | 惠州市地震局 | A kind of quick Big Dipper transmission method of earthquake disaster information |
-
2018
- 2018-12-26 CN CN201811602789.2A patent/CN109783473A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101257421A (en) * | 2007-02-27 | 2008-09-03 | 仁荷大学教产学协力团 | Real time automatic update system and method for disaster damage investigation |
| CN105809372A (en) * | 2016-04-20 | 2016-07-27 | 国家电网公司 | Natural disaster risk monitoring system based on satellite remote sensing image |
| CN106651004A (en) * | 2016-11-18 | 2017-05-10 | 上海师范大学 | Flood forecasting method based on rainfall flood space-time database |
| CN107220279A (en) * | 2017-04-19 | 2017-09-29 | 民政部国家减灾中心 | The Dynamic Tracking and system of Disaster Event |
| CN108155928A (en) * | 2017-11-09 | 2018-06-12 | 惠州市地震局 | A kind of quick Big Dipper transmission method of earthquake disaster information |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113987007A (en) * | 2021-10-12 | 2022-01-28 | 中冶南方工程技术有限公司 | Blast furnace slag skin falling and merging method, terminal equipment and storage medium |
| WO2023060662A1 (en) * | 2021-10-12 | 2023-04-20 | 中冶南方工程技术有限公司 | Blast furnace slag crust falling-off merging method and terminal device, and storage medium |
| CN113987007B (en) * | 2021-10-12 | 2023-11-21 | 中冶南方工程技术有限公司 | Blast furnace slag peel falling and merging method, terminal equipment and storage medium |
| CN115798174A (en) * | 2022-11-01 | 2023-03-14 | 成都市美幻科技有限公司 | Fusion processing method, device, equipment and storage medium for multi-disaster early warning information |
| CN115798174B (en) * | 2022-11-01 | 2023-10-27 | 成都市美幻科技有限公司 | Fusion processing method, device and equipment for multi-disaster early warning information and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Dunn et al. | HadISD: A quality-controlled global synoptic report database for selected variables at long-term stations from 1973–2011 | |
| KR100748528B1 (en) | Information update method and the real-time automatic update system for disaster damage investigation using wireless communication technology and web-gis | |
| Kiem et al. | Towards understanding hydroclimatic change in Victoria, Australia–preliminary insights into the" Big Dry" | |
| JP6300889B2 (en) | System and method for improving extraction performance of atypical text | |
| CN107679821A (en) | A kind of attendance management method and system | |
| CN109783473A (en) | A kind of information processing method automatically creating Rainfall Disaster data-base recording | |
| Thompson et al. | Modeling hurricane-caused urban forest debris in Houston, Texas | |
| CN111353380A (en) | Urban road ponding image recognition system based on machine image recognition technology | |
| CN113886596A (en) | Method for constructing flexible city knowledge graph based on city element and multi-disaster fusion | |
| Dore | Forecasting the conditional probabilities of natural disasters in Canada as a guide for disaster preparedness | |
| Zheng et al. | Avoid: Autonomous vehicle operation incident dataset across the globe | |
| Wilhite | Preparedness and coping strategies for agricultural drought risk management: recent progress and trends | |
| Ryerson et al. | Timely crop area estimates from Landsat | |
| Wu et al. | Assessment of forest damage caused by an ice storm using multi-temporal remote-sensing images: A case study from Guangdong Province | |
| Day et al. | WormBase: A data management and information system for forecasting Spodoptera exempta (Lepidoptera: Noctuidae) in eastern Africa | |
| Somers et al. | Role of trapping in detection of a small bog turtle (Glyptemys muhlenbergii) population | |
| Melby et al. | Coastal hazards system | |
| Durre et al. | White Christmas? An Application of NOAA’s 1981–2010 Daily Normals | |
| Santos | Some comments on the reliability of NOAA's Storm Events Database | |
| Gumucio et al. | Causal chains linking weather hazards to disasters in Somalia | |
| CN109800267A (en) | A kind of hydrologic monitoring data-storage system | |
| Doggett | A method to assess large-scale forest damage: A case study | |
| KR102246712B1 (en) | Disaster Monitoring System, Method Using Crowd Sourcing, and Computer Program therefor | |
| Tyson et al. | Development of Phyto-Finder’s Database Web Application | |
| CN107729462B (en) | Method and system for updating work log table |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190521 |
|
| RJ01 | Rejection of invention patent application after publication |