10.46243/jst.2022.v7.i02.pp172-194 registered
FLOOD ESTIMATE USING GIS SPECIFIC TO FLOOD STUDIES FOR UPPER SARADA RIVER BASIN IN VISAKHAPATNAM DISTRICT, ANDHRA PRADESH, INDIA
Resolves to https://www.jst.org.in/index.php/pub/article/view/528
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v7.i02.pp172-194
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 e307701905237b10…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
FLOOD ESTIMATE USING GIS SPECIFIC TO FLOOD STUDIES FOR UPPER SARADA RIVER BASIN IN VISAKHAPATNAM DISTRICT, ANDHRA PRADESH, INDIA (PrincipalTitle)
Published 2022-07-03
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 7 · issue 2 · pages 172–194
Agents
- B.V.Shiva Kumar B.V.Shiva Kumar (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v7.i02.pp172-194
Abstract
Geographical Information System (GIS) techniques have been effectively used for the study of drainages and estimation of runoff of a catchment. In this paper, the flood estimate of the Upper Sarada River Basin is analyzed using GIS techniques. The Upper Sarada River Basin is analyzed by building a Drainage Elevation Model and thereby extracting the drainage map. The runoff is estimated on this catchment by assuming unit net rainfall (1cm direct runoff) and taking appropriate assumptions. For this purpose, streams in a River Basin are assigned weights with respect to slope of the area and using the same, a travel time contour map represented by isochrones is developed from the equivalent distance map. The flow accumulation map of the drainages is also developed and then this is used to determine discharge at outlet of the catchment. The entire basin area is divided into eleven parts of equal interval of travel time and the yield caused in each part is determined. Further, this is used to determine the discharge at the end of eleven-time steps and the resulting unit hydrograph (UH) is plotted. UH is prepared for the daily average run-off values. An S-hydrograph is also plotted to obtain a UH of selected time duration for the use in flood estimate due to a storm. This hydrograph is validated by taking different selected storm events from the year 1990 to 2019, recorded by Central Water Commission (CWC), Anakapalle station. Eight storm events are observed and these are validated using Thiessen polygon method
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2022.v7.i02.pp172-194 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | FLOOD ESTIMATE USING GIS SPECIFIC TO FLOOD STUDIES FOR UPPER SARADA RIVER BASIN IN VISAKHAPATNAM DISTRICT, ANDHRA PRADESH, INDIA (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: B.V.Shiva Kumar B.V.Shiva Kumar publisher: Longman Publishers published: 2022-07-03 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 7 · no. 2 · pp. 172–194 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2024-02-16 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 121 fields set · sha256 83aa4757e34a… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | agents.0.name.family: agents.0.name.given: container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
