Changes between Version 36 and Version 37 of GSoC/2014/MetadataForGRASS
- Timestamp:
- 06/13/14 09:54:35 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GSoC/2014/MetadataForGRASS
v36 v37 37 37 = Development = 38 38 == Dependencies == 39 Current development of metadata management ha vedependence on external libraries:39 Current development of metadata management has dependence on external libraries: 40 40 * OWSLib (no additional dependence), 41 * Jinja templates (suitable to rem ake)41 * Jinja templates (suitable to remove dependence) 42 42 43 43 == Architecture == 44 The new designed metadata management in GRASS is based on external python modules without interference toGRASS core.45 * First step which is part ially successful is to create basic modules for exporting ISO based metadata for raster and vector maps. The modules are contented to implemented class which is providing parsing metadata from r.info and v.info. This metadata are unassigned to ISO attributes with using OWSLib. The OWSLib is offering to create instances of ISO element. The instances are suitable to filled in the predefined Jinja xml ISO profile. From this part are created r.info.iso and v.info.iso44 The new designed metadata management in GRASS is based on external python modules without processing of the GRASS core. 45 * First step which is partly done is to create basic modules for exporting ISO based metadata for raster and vector maps. The modules are intended to implement class that is providing parsing metadata from r.info and v.info. These metadata are assigned to ISO attributes with using OWSLib. The OWSLib is offering creation instances of ISO elements. The instances are suitable to filled predefined of Jinja xml ISO profiles. From this part of project r.info.iso and v.info.iso are created. 46 46 47 47 === r.info.iso and v.info.iso === 48 * The modules are based on the said implementation.49 * Offers converting metadata from *.info to xml file based on ISO standard 50 * Current available metadata profile for GRASS.51 52 48 * These modules are based on the mentioned implementation. 49 * Offers converting metadata from *.info to xml file based on ISO standard. 50 * Currently available metadata profile for GRASS: 51 * INSPIRE profile, 52 * GRASS BASIC profile - this profile is mainly including available metadata from GRASS. 53 53 54 54 === g.gui.metadata === 55 Current task is to design the GUI interface and the implementation. Below is the first design.56 Main aggravating factor is the fact that some attributes in ISO can be define multiple times. For the solution is necessary to crate interface for getting information from some source. Currently the easier way is to get information form predefined XML Jinja template. Interface ensure independence between editor and source of in formations. This is useful for future development.57 55 Current task is to design and the implementation of the GUI interface. Below is the first design provided. 56 Main aggravating factor is, that some attributes in ISO can be defined multiple times. For the solution, there is necessary to create interface for getting information from some source. Currently the easiest way is to get information forom predefined XML Jinja template. Interface ensures independence between editor and source of information. This is useful for future development steps. 57 The editor will support: 58 58 59 59 || version || function || … … 62 62 || || to create xml ISO file (with using v/r.info.iso) || 63 63 || || interface to get information about ISO attributes || 64 || 1.1 || editing of created xml file with using Jinja templates ||64 || 1.1 || editing of created xml files with using Jinja templates || 65 65 || 1.2 || to add multiple values for specific attributes || 66 66 || 1.3 || validator of inspire xml || 67 || || options for update r/v.support by changed valuesvalues in editor. ||68 || 1.4 || multiple metadata editing ( choos e maps, chooses attributes with are same forchosen maps. ||67 || || options for update metadata with using r/v.support by changed values in editor. || 68 || 1.4 || multiple metadata editing ( choosing maps invokes process that changes selected attributes of all chosen maps. || 69 69 70 70 scheme of a designed implementation