{"id":949,"date":"2023-10-20T14:43:13","date_gmt":"2023-10-20T18:43:13","guid":{"rendered":"https:\/\/pressbooks.bccampus.ca\/eweguide\/?post_type=chapter&p=949"},"modified":"2024-05-15T14:23:55","modified_gmt":"2024-05-15T18:23:55","slug":"sharing-external-spatial-datasets","status":"publish","type":"chapter","link":"https:\/\/pressbooks.bccampus.ca\/eweguide\/chapter\/sharing-external-spatial-datasets\/","title":{"raw":"Sharing External Spatial Datasets","rendered":"Sharing External Spatial Datasets"},"content":{"raw":"The Ecospace module of EwE has gained capabilities to be driven by external spatial-temporal datasets. These external data sets cannot be embedded within a EwE model database because they tend to be model-derived datasets that frequently update, and that are of prohibitive file size. The process of connecting to these data is detailed in Steenbeek et al. [footnote]Steenbeek, J., Coll, M., Gurney, L., M\u00e9lin, F., Hoepffner, N., Buszowski, J., Christensen, V., 2013. Bridging the gap between ecosystem modeling tools and geographic information systems: Driving a food web model with external spatial\u2013temporal data. Ecological Modelling 263, 139\u2013151. https:\/\/doi.org\/10.1016\/j.ecolmodel.2013.04.027<\/a>[\/footnote](2013), see chapter<\/a>.\r\n\r\nTo enable sharing of temporal spatial data by, e.g., scientists at different institutes in different locations, this system has been extended to offer support for shared use of the same model with accompanying external spatial data via cloud-based transfer media.\r\n

Changes to EwE<\/h1>\r\nThe Ecospace model stores definitions of available spatial-temporal data series in a local configuration file [footnote]Steenbeek et al. 2013, op. cit.[\/footnote]. Sharing this configuration file is impractical when a local system contains dataset definitions for a suite of Ecospace models: support was needed to only selectively share relevant data for a given modeling exercise. To enable this, the following changes have been made to the EwE6 software,\r\n
    \r\n \t
  1. An export function was added to EwE6 that make it possible to copy a selection of dataset definitions to a local folder with a local configuration file. Whereas datasets on a local system are indicated by absolute file paths, the exported datasets refer to their files via local paths, making this export folder highly suitable for transfer to another computer.<\/li>\r\n \t
  2. An option has been added to allow for switching to a different configuration file \u2013 either locally created configuration files particular to a given modeling exercise, or shared configuration files obtained via a cloud-based file transfer system - which provides Ecospace with access to the external spatial-temporal data connections described in the configuration file.<\/li>\r\n<\/ol>\r\nEwE6 model databases already carried all information needed to connect an Ecospace layer to external data sets [footnote]Steenbeek et al. 2013, op. cit.[\/footnote]. However, this information just contained technical details internal to the model, and was too sparse to assist troubleshooting when expected data sets could not be located. The following changes were therefore made to the EwE6 software:\r\n
      \r\n \t
    1. EwE6 model databases now also store the configuration of data sets, but not the actual data due to its prohibitive size.<\/li>\r\n \t
    2. When Ecospace loads this information it tries to resolve these data sets. If a local computer does not know these data sets, the data sets are instantiated from the data stored in the model, and the user is warned that the data set may be incomplete. Having access to the complete configuration information, a user can figure out what external data is needed to reassemble the model configuration by requesting a data set export from the original model author, and then linking to these data.<\/li>\r\n<\/ol>\r\n

      Using these Developments<\/h2>\r\nIt is possible to export data sets from several locations in EwE, such as the main Ecospace menu and the interface where external datasets are defined (Figure 1).\r\n\r\n[caption id=\"attachment_952\" align=\"aligncenter\" width=\"560\"]\"\" Figure 1 <\/strong>- Where to find the Export data sets option.[\/caption]\r\n\r\nWhen this option is selected a dedicated interface is displayed. Here users can decide which data sets to export for transfer to another computer, such as all data sets or only those used by the current model (Figure 2). Note that this interface is still in its infancy and may need further work to allow for selection of an export directory, to display export progress, and to display export result information.\r\n\r\n[caption id=\"attachment_954\" align=\"aligncenter\" width=\"283\"]\"\" Figure 2 <\/strong>- Data set export interface.[\/caption]\r\n\r\nThe EwE6 status panel notifies about where where the data sets have been exported to. When clicking this link, you are brought to the export directory, which in its entirety can be transferred to another computer, or can be shared via a cloud-based service such as Dropbox. The Export folder contains directories with file content for individual data sets where applicable, and a \u201cewe_datasets.xml\u201d configuration file for these files (Figure 3).\r\n\r\n[caption id=\"attachment_956\" align=\"aligncenter\" width=\"641\"]\"\" Figure 3 - <\/strong>Example contents of a data set export folder.[\/caption]\r\n

      Once the exported data sets are transferred to another computer they can used by EwE. For this, a user switches the local configuration to the exported data sets via the spatial temporal data page in the main EwE options interface (Figure 4). Ecospace now shows the data sets as usable for the model (Figure 5).<\/p>\r\n\r\n\r\n[caption id=\"attachment_958\" align=\"aligncenter\" width=\"633\"]\"\" Figure 4 <\/strong>- Linking to a set of exported data sets that has been received from another user.[\/caption]\r\n\r\n[caption id=\"attachment_959\" align=\"aligncenter\" width=\"708\"]\"\" Figure 5<\/strong> - The imported data sets displayed in Ecospace, ready to be used.[\/caption]","rendered":"

      The Ecospace module of EwE has gained capabilities to be driven by external spatial-temporal datasets. These external data sets cannot be embedded within a EwE model database because they tend to be model-derived datasets that frequently update, and that are of prohibitive file size. The process of connecting to these data is detailed in Steenbeek et al. [1]<\/sup><\/a>(2013), see chapter<\/a>.<\/p>\n

      To enable sharing of temporal spatial data by, e.g., scientists at different institutes in different locations, this system has been extended to offer support for shared use of the same model with accompanying external spatial data via cloud-based transfer media.<\/p>\n

      Changes to EwE<\/h1>\n

      The Ecospace model stores definitions of available spatial-temporal data series in a local configuration file [2]<\/sup><\/a>. Sharing this configuration file is impractical when a local system contains dataset definitions for a suite of Ecospace models: support was needed to only selectively share relevant data for a given modeling exercise. To enable this, the following changes have been made to the EwE6 software,<\/p>\n

        \n
      1. An export function was added to EwE6 that make it possible to copy a selection of dataset definitions to a local folder with a local configuration file. Whereas datasets on a local system are indicated by absolute file paths, the exported datasets refer to their files via local paths, making this export folder highly suitable for transfer to another computer.<\/li>\n
      2. An option has been added to allow for switching to a different configuration file \u2013 either locally created configuration files particular to a given modeling exercise, or shared configuration files obtained via a cloud-based file transfer system – which provides Ecospace with access to the external spatial-temporal data connections described in the configuration file.<\/li>\n<\/ol>\n

        EwE6 model databases already carried all information needed to connect an Ecospace layer to external data sets [3]<\/sup><\/a>. However, this information just contained technical details internal to the model, and was too sparse to assist troubleshooting when expected data sets could not be located. The following changes were therefore made to the EwE6 software:<\/p>\n

          \n
        1. EwE6 model databases now also store the configuration of data sets, but not the actual data due to its prohibitive size.<\/li>\n
        2. When Ecospace loads this information it tries to resolve these data sets. If a local computer does not know these data sets, the data sets are instantiated from the data stored in the model, and the user is warned that the data set may be incomplete. Having access to the complete configuration information, a user can figure out what external data is needed to reassemble the model configuration by requesting a data set export from the original model author, and then linking to these data.<\/li>\n<\/ol>\n

          Using these Developments<\/h2>\n

          It is possible to export data sets from several locations in EwE, such as the main Ecospace menu and the interface where external datasets are defined (Figure 1).<\/p>\n

          \"\"
          Figure 1 <\/strong>– Where to find the Export data sets option.<\/figcaption><\/figure>\n

          When this option is selected a dedicated interface is displayed. Here users can decide which data sets to export for transfer to another computer, such as all data sets or only those used by the current model (Figure 2). Note that this interface is still in its infancy and may need further work to allow for selection of an export directory, to display export progress, and to display export result information.<\/p>\n

          \"\"
          Figure 2 <\/strong>– Data set export interface.<\/figcaption><\/figure>\n

          The EwE6 status panel notifies about where where the data sets have been exported to. When clicking this link, you are brought to the export directory, which in its entirety can be transferred to another computer, or can be shared via a cloud-based service such as Dropbox. The Export folder contains directories with file content for individual data sets where applicable, and a \u201cewe_datasets.xml\u201d configuration file for these files (Figure 3).<\/p>\n

          \"\"
          Figure 3 – <\/strong>Example contents of a data set export folder.<\/figcaption><\/figure>\n

          Once the exported data sets are transferred to another computer they can used by EwE. For this, a user switches the local configuration to the exported data sets via the spatial temporal data page in the main EwE options interface (Figure 4). Ecospace now shows the data sets as usable for the model (Figure 5).<\/p>\n

          \"\"
          Figure 4 <\/strong>– Linking to a set of exported data sets that has been received from another user.<\/figcaption><\/figure>\n
          \"\"
          Figure 5<\/strong> – The imported data sets displayed in Ecospace, ready to be used.<\/figcaption><\/figure>\n
          1. Steenbeek, J., Coll, M., Gurney, L., M\u00e9lin, F., Hoepffner, N., Buszowski, J., Christensen, V., 2013. Bridging the gap between ecosystem modeling tools and geographic information systems: Driving a food web model with external spatial\u2013temporal data. Ecological Modelling 263, 139\u2013151. https:\/\/doi.org\/10.1016\/j.ecolmodel.2013.04.027<\/a> ↵<\/a><\/li>
          2. Steenbeek et al. 2013, op. cit. ↵<\/a><\/li>
          3. Steenbeek et al. 2013, op. cit. ↵<\/a><\/li><\/ol><\/div>","protected":false},"author":1909,"menu_order":11,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":["jeroensteenbeek"],"pb_section_license":""},"chapter-type":[],"contributor":[62],"license":[],"class_list":["post-949","chapter","type-chapter","status-publish","hentry","contributor-jeroensteenbeek"],"part":803,"_links":{"self":[{"href":"https:\/\/pressbooks.bccampus.ca\/eweguide\/wp-json\/pressbooks\/v2\/chapters\/949","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.bccampus.ca\/eweguide\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.bccampus.ca\/eweguide\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/eweguide\/wp-json\/wp\/v2\/users\/1909"}],"version-history":[{"count":8,"href":"https:\/\/pressbooks.bccampus.ca\/eweguide\/wp-json\/pressbooks\/v2\/chapters\/949\/revisions"}],"predecessor-version":[{"id":1694,"href":"https:\/\/pressbooks.bccampus.ca\/eweguide\/wp-json\/pressbooks\/v2\/chapters\/949\/revisions\/1694"}],"part":[{"href":"https:\/\/pressbooks.bccampus.ca\/eweguide\/wp-json\/pressbooks\/v2\/parts\/803"}],"metadata":[{"href":"https:\/\/pressbooks.bccampus.ca\/eweguide\/wp-json\/pressbooks\/v2\/chapters\/949\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.bccampus.ca\/eweguide\/wp-json\/wp\/v2\/media?parent=949"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/eweguide\/wp-json\/pressbooks\/v2\/chapter-type?post=949"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/eweguide\/wp-json\/wp\/v2\/contributor?post=949"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/eweguide\/wp-json\/wp\/v2\/license?post=949"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}