Git Product home page Git Product logo

metocean's Introduction

metarelate

metarelate is a knowledge base system for managing metadata translations.

To contribute to a translation project, the static data from that project should be used to populate a local triple store which the management software may access.

Dependencies

Installation

Configuration

Local configuration files are required to set up a metarelate environment:

  • ./lib/metarelate/etc/site.cfg
  • see ./lib/metarelate/etc/sample.site.cfg
  • ./lib/metarelate/editor/settings_local.py
  • see ./lib/metarelate/editor/sample_settings_local.py
  • environment variables are used by each session to link to a local static data store and triple store:
  • METARELATE_STATIC_DIR
  • METARELATE_TDB_DIR
  • METARELATE_DATA_PROJECT

Editor

  • To run the editor application:
    1. ./run_mr_editor.py

Application Programming Interface

The API provides a Python interface to the knowledge base.

To use the API, create an instance of the metarelate.fuseki.FusekiServer class, as detailed in the API documentation.

metocean's People

Contributors

bblay avatar bjlittle avatar esc24 avatar marqh avatar pp-mo avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar

Forkers

bjlittle marqh nhsavage bblay pp-mo cpelley melissaebrooks esc24 dpeterk djkirkham

metocean's Issues

STASH Code to CF name translations: inconsistent names

Here is a copy of my upload file:
|STASH(msi)|CFName|units|force_update(y/n)|
|m01s00i023|surface_snow_amount_where_land|kg m-2|n|
|m01s00i024|sea_surface_temperature|K|n|
|m01s00i059|tendency_of_atmosphere_mass_content_of_dimethyl_sulfide_due_to_emission|kg m-2 s-1|n|
|m01s00i129|tendency_of_atmosphere_mass_content_of_black_carbon_dry_aerosol_due_to_emission|kg m-2 s-1|n|
|m01s00i211|convective_cloud_area_fraction|1|n|
|m01s00i265|cloud_area_fraction|1|n|
|m01s02i207|surface_downwelling_longwave_flux_in_air|W m-2|n|
|m01s02i208|surface_downwelling_longwave_flux_in_air_assuming_clear_sky|W m-2|n|
|m01s03i223|water_evaporation_flux|kg m-2 s-1|n|
|m01s03i293|heterotrophic_respiration_carbon_flux|kg m-2 s-1|n|
|m01s03i297|water_evaporation_flux_from_canopy|kg m-2 s-1|n|
|m01s04i204|large_scale_snowfall_flux|kg m-2 s-1|n|
|m01s05i205|convective_rainfall_flux|kg m-2 s-1|n|
|m01s08i023|surface_snow_amount_where_land|kg m-2|n|
|m01s30i451|tropopause_pressure|Pa|n|
|m02s00i137|ocean_mixed_layer_thickness_defined_by_mixing_scheme|m|n|
|m02s00i186|water_flux_correction_where_ocean|kg m-2 s-1|n|

Here is the responce:
The file failed to parse; in order to process this file you should consider:
line1: forcing replacement of m01s00i023 -> snowfall_amount(kg m-2) with m01s00i023 -> surface_snow_amount_where_land(kg m-2)
line2: forcing replacement of m01s00i024 -> surface_temperature(K) with m01s00i024 -> sea_surface_temperature(K)
line3: forcing replacement of m01s00i059 -> tendency_of_atmosphere_mass_content_of_dimethyl_sulfide_expressed_as_sulfur_due_to_emission(kg/m2/s) with m01s00i059 -> tendency_of_atmosphere_mass_content_of_dimethyl_sulfide_due_to_emission(kg m-2 s-1)
line4: forcing replacement of m01s00i129 -> tendency_of_atmosphere_mass_content_of_black_carbon_dry_aerosol_due_to_high_level_emission(kg/m2/s) with m01s00i129 -> tendency_of_atmosphere_mass_content_of_black_carbon_dry_aerosol_due_to_emission(kg m-2 s-1)
line5: forcing replacement of m01s00i211 -> Convective cloud amount with anvil(1) with m01s00i211 -> convective_cloud_area_fraction(1)
line6: forcing replacement of m01s00i265 -> cloud_area_fraction_in_atmosphere_layer(1) with m01s00i265 -> cloud_area_fraction(1)
line7: forcing replacement of m01s02i207 -> surface_downwelling_longwave_flux(W m-2) with m01s02i207 -> surface_downwelling_longwave_flux_in_air(W m-2)
line8: forcing replacement of m01s02i208 -> surface_downwelling_longwave_flux_assuming_clear_sky(W m-2) with m01s02i208 -> surface_downwelling_longwave_flux_in_air_assuming_clear_sky(W m-2)
line9: forcing replacement of m01s03i223 -> surface_upward_water_flux(kg m-2 s-1) with m01s03i223 -> water_evaporation_flux(kg m-2 s-1)
line10: forcing replacement of m01s03i293 -> soil_respiration_carbon_flux(kg/m^2/s) with m01s03i293 -> heterotrophic_respiration_carbon_flux(kg m-2 s-1)
line11: forcing replacement of m01s03i297 -> Evaporation from canopy(kg/m^2/s) with m01s03i297 -> water_evaporation_flux_from_canopy(kg m-2 s-1)
line12: forcing replacement of m01s04i204 -> stratiform_snowfall_rate(kg m-2 s-1) with m01s04i204 -> large_scale_snowfall_flux(kg m-2 s-1)
line13: forcing replacement of m01s05i205 -> convective_rainfall_rate(kg m-2 s-1) with m01s05i205 -> convective_rainfall_flux(kg m-2 s-1)
line14: forcing replacement of m01s08i023 -> surface_snow_amount(kg m-2) with m01s08i023 -> surface_snow_amount_where_land(kg m-2)
line15: forcing replacement of m01s30i451 -> tropopause_air_pressure(Pa) with m01s30i451 -> tropopause_pressure(Pa)
line16: forcing replacement of m02s00i137 -> ocean_mixed_layer_thickness(m) with m02s00i137 -> ocean_mixed_layer_thickness_defined_by_mixing_scheme(m)
line17: forcing replacement of m02s00i186 -> water_flux_correction(kg m-2 s-1) with m02s00i186 -> water_flux_correction_where_ocean(kg m-2 s-1)

The units are consistent (although there are some differences in the formatting*), but the names are inconsistent.

*I personally find kg m-2 s-1 more readble than kg/m^2/s :)

CF to GRIB2 mass_fraction_of_cloud_liquid_water_in_air and mass_fraction_of_cloud_ice_in_air

I propose these changes to Metarelate's metOcean knowledge base.
The changes are correct, to the best of my knowledge.
I agree to my username being used to label these changes.

http://www.metarelate.net/metOcean/controlpanel/?branch=c69de422800c062dff1d2b58172e0649c6ab7c28

http://www.metarelate.net/metOcean/list_mappings/True/?ref=%22c69de422800c062dff1d2b58172e0649c6ab7c28%2F%22

The added mappings are:

These changes have been discussed here: SciTools/iris-grib#160

invalid units

unit strings that do not parse in udunits exist in the translation store:

  • "Mass mixing ratio (kg/kg)" - should be "kg/kg"
  • "1e3 psu @0.035"
  • "MKS"
  • "Kg m-2 s-1" - should be "kg m-2 s-1"

STASH Code to CF name translations: look consistent but aren't accepted

Here is a copy of my upload file:
STASH(msi)|CFName|units|force_update(y/n)|
|m01s03i236|air_temperature|K|n|
|m01s03i237|specific_humidity|1|n|
|m01s03i245|relative_humidity|%|n|

Here is the responce:
The file failed to parse; in order to process this file you should consider:
line1: forcing replacement of m01s03i236 -> air_temperature(K) with m01s03i236 -> air_temperature(K)
line2: forcing replacement of m01s03i237 -> specific_humidity(1) with m01s03i237 -> specific_humidity(1)
line3: forcing replacement of m01s03i245 -> relative_humidity(%) with m01s03i245 -> relative_humidity(%)

These look identical to me, so I'm not sure why they aren't being accepted :(

STASH Code to CF name translations: inconsistent units

Here is a copy of my upload file:
|STASH(msi)|CFName|units|force_update(y/n)|
|m01s00i010|specific_humidity|1|n|
|m01s03i202|downward_heat_flux_in_soil|W m-2|n|
|m02s00i101|sea_water_potential_temperature|K|n|
|m02s00i130|ocean_barotropic_streamfunction|m3 s-1|n|
|m02s30i201|upward_sea_water_velocity|m s-1|n|
|m02s30i211|northward_ocean_heat_transport|W|n|
|m02s30i320|eastward_sea_water_velocity|m s-1|n|
|m02s30i321|northward_sea_water_velocity|m s-1|n|

Here is the responce:
The file failed to parse; in order to process this file you should consider:
line1: forcing replacement of m01s00i010 -> specific_humidity(kg kg-1) with m01s00i010 -> specific_humidity(1)
line2: forcing replacement of m01s03i202 -> downward_heat_flux_in_soil(unknown) with m01s03i202 -> downward_heat_flux_in_soil(W m-2)
line3: forcing replacement of m02s00i101 -> sea_water_potential_temperature(degC) with m02s00i101 -> sea_water_potential_temperature(K)
line4: forcing replacement of m02s00i130 -> ocean_barotropic_streamfunction(cm3 s-1) with m02s00i130 -> ocean_barotropic_streamfunction(m3 s-1)
line5: forcing replacement of m02s30i201 -> upward_sea_water_velocity(cm s-1) with m02s30i201 -> upward_sea_water_velocity(m s-1)
line6: forcing replacement of m02s30i211 -> northward_ocean_heat_transport(PW) with m02s30i211 -> northward_ocean_heat_transport(W)
line7: forcing replacement of m02s30i320 -> eastward_sea_water_velocity(cm s-1) with m02s30i320 -> eastward_sea_water_velocity(m s-1)
line8: forcing replacement of m02s30i321 -> northward_sea_water_velocity(cm s-1) with m02s30i321 -> northward_sea_water_velocity(m s-1)

The names are consistent but the units are inconsistent.

STASH code to CF name translations: photolysis and nmvoc additions

I propose these changes to Metarelate's metOcean knowledge base.
The changes are correct, to the best of my knowledge.
I agree to my username being used to label these changes.
Notify:
@jhemmings
https://www.metarelate.net/metOcean/controlpanel/?branch=ffc0a84ed952530f0a59ff04c7428fc9214473e1%2F

Copy of text in the uploaded file:

|STASH(msi)|CFName|units|force_update(y/n)|
|m01s50i228|photolysis_rate_of_ozone_to_1D_oxygen_atom|s-1|n|
|m01s50i229|photolysis_rate_of_nitrogen_dioxide|s-1|n|
|m01s50i230|mass_concentration_of_nmvoc_expressed_as_carbon_in_air|ug m-3|n|

prune unused translations

When we create a translation and then refine it in the same session,
the old translation is replaced with the new, but stays in the system.
This can be seen in #3 and #4.

Whilst this might be useful for persisting old translations that were real,
it might be worth pruning old translations that were never used.
E.g created and replaced before export, or those set as "draft".

STASH Code to CF name translations: x / eastward and y / northward

Here is a copy of my upload file:
|STASH(msi)|CFName|units|force_update(y/n)|
|m01s00i002|eastward_wind|m s-1|n|
|m01s00i003|northward_wind|m s-1|n|
|m01s03i225|eastward_wind|m s-1|n|
|m01s03i226|northward_wind|m s-1|n|
|m01s15i201|eastward_wind|m s-1|n|
|m01s15i202|northward_wind|m s-1|n|

Here is the responce:
The file failed to parse; in order to process this file you should consider:
line1: forcing replacement of m01s00i002 -> x_wind(m s-1) with m01s00i002 -> eastward_wind(m s-1)
line2: forcing replacement of m01s00i003 -> y_wind(m s-1) with m01s00i003 -> northward_wind(m s-1)
line3: forcing replacement of m01s03i225 -> x_wind(m s-1) with m01s03i225 -> eastward_wind(m s-1)
line4: forcing replacement of m01s03i226 -> y_wind(m s-1) with m01s03i226 -> northward_wind(m s-1)
line5: forcing replacement of m01s15i201 -> x_wind(m s-1) with m01s15i201 -> eastward_wind(m s-1)
line6: forcing replacement of m01s15i202 -> y_wind(m s-1) with m01s15i202 -> northward_wind(m s-1)

x or eastward? y or northward?

lbfc 56/57

a collection of uses of UM:LBFC 56 and 57 exist. These are linked to CF names of eastward/northward wind whilst the lbfc descriptions contain reference to westward and southward

this needs investigating and resolving

STASH Code to CF name translations: unrecognised STASH codes

Here is a copy of my upload file:
|STASH(msi)|CFName|units|force_update(y/n)|
|m01s17i301|mass_concentration_of_sulfate_aerosol_in_air|kg m-3|n|
|m01s17i302|mass_concentration_of_sulfur_dioxide_in_air|kg m-3|n|
|m01s17i303|mass_concentration_of_dimethyl_sulfide_in_air|kg m-3|n|
|m01s17i311|atmosphere_content_of_sulfate_aerosol|kg m-2|n|
|m01s17i312|atmosphere_mass_content_of_sulfur_dioxide|kg m-2|n|
|m01s17i313|atmosphere_mass_content_of_dimethyl_sulfide|kg m-2|n|
|m01s19i301|leaf_area_index|1|n|
|m01s30i501|concentration_of_chlorophyll_in_sea_water|kg m-3|n|

Here is the responce:
The file failed to parse; in order to process this file you should consider:
line1: unrecognised stash code: http://reference.metoffice.gov.uk/um/stash/m01s17i301
line2: unrecognised stash code: http://reference.metoffice.gov.uk/um/stash/m01s17i302
line3: unrecognised stash code: http://reference.metoffice.gov.uk/um/stash/m01s17i303
line4: unrecognised stash code: http://reference.metoffice.gov.uk/um/stash/m01s17i311
line5: unrecognised stash code: http://reference.metoffice.gov.uk/um/stash/m01s17i312
line6: unrecognised stash code: http://reference.metoffice.gov.uk/um/stash/m01s17i313
line7: unrecognised stash code: http://reference.metoffice.gov.uk/um/stash/m01s19i301
line8: unrecognised stash code: http://reference.metoffice.gov.uk/um/stash/m01s30i501

expired certificate

www.metarelate.net uses an invalid security certificate. The certificate expired on 02/12/17 23:59. The current time is 08/03/17 15:38. Error code: SEC_ERROR_EXPIRED_CERTIFICATE

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.