RASOR database and catalog

From Rasor Wiki
Jump to: navigation, search

Contents

RASOR database and catalog

The Rasor platform uses different repositories to store data. The database and catalog is based on open source components that accomplish with the user requirements, such as web-based ingestion, metadata, preview, description, OGC®/INSPIRE compliancy.

GeoServer is used as a data store and publisher of geographic data, whether static or dynamic. Spatial data infrastructure relies on the Geoserver for the publication in OGC web service standards (wms, wfs, wcs). Geonode facilitates data ingestion into the system and the publication on the geoserver and provide the possibility to compile metadata in Inspire and OGC standard format.

(thumbnail)
Main page of the Rasor catalog based on Geonode interface.

The catalog, available at http://www.rasor.eu/catalog, provides search services and metadata publication. Features include:

1. Powerful spatial search engine

2. Federated OGC services


3. Metadata catalogue

GeoNode is in practice able to encapsulate and combine GeoServer, extending it with indexing functionality and metadating. The user has two to explore the repository: through the catalog (Geonode) and through the Rasor application itself (see the "Monitor" section). While in the general catalog the user can explore all the layers, in the Rasor application layers are filtered and visualized by categories in order to ease their use in further elaborations.

(thumbnail)
Mosaic of the TanDEM-X digital elevation model over Haiti (Geonode interface)

RASOR nomenclature

In order to facilitate the file browsing, all RASOR files should comply with the simple nomenclature schema shown below. This is not a compulsory rule, but it is strongly recommended.

There are some generic recommendations, valuable for any kind of layer:

-avoid the use of capital letters
-in case of a layer valid only for didactic purposes (e.g. workshops, exercises, learning activities), please add the word 'didactic' at the end of the layer name

Exposure files

The template for exposure layer names is:

location_exposuretype_source_(date)_(opt)

where:

location is name of the exposure location

exposuretype can be :

• “agri” (agricultural site)
• “nat” (area of natural interest)
• “build” (buildings)
• “block” (building blocks)
• “facil” (facilities and high potential loss facilities)
• “lu” (land use)
• “ll” (lifelines)
• “pop” (population)
• “rail” (railways and light railways)
• “road” (roads)
• “levee" (levees)

source is data source (eg. existing database such as OSM, name of the author, name of the satellite images use for feature extraction, etc. )

date is optional date of source (e.g. satellite image acquisition)

opt is other optional reference parameters

Example: bandung_build_osm_sertit_2015

Hazard files

The template for exposure layer names is:

location_hazardtype_forcing_(source)_(date)_(opt)

where:

location is the name of the hazard location

hazardtype can be:

• “eq” (Earthquake)
• “flo” (Flood)
• “hu” (Hurricane)
• “ls” (Landslide)
• “subs” (Subsidence)
• “tsu” (Tsunami)
• “vol” (Volcano)
• “wind” (Wind)


forcing can be:

• wd (Water depth)
• vel (Velocity)
• pga (Peak ground acceleration)
• pgv (Peak ground velocity)
• disp (Co-seismic displacement)
• windvel (Wind velocity)
• md (Mean deformation rate)
• td (Total deformation rate)
• day (Number of days from 1st January)

source is data source (ex. models used or configuration user, etc.)

date = event to be modeled

opt is other optional reference parameters

Example: bandung_flo_wd_wet_2007

Impact files

The template for exposure layer names is:

location_xx_exposuretype_hazardtype_(date)_(opt)

where xx can be:

• di = Direct Impact
• si = Systemic Impact

hazardtype (see above)

exposuretype (see above)

date (see above)

opt (see above)

Example: bandung_di_build_flo_2007

Personal tools
Namespaces

Variants
Actions
Navigation
Tools