With Conserv Cloud, you can bring in data from your existing data loggers! Here are a few things to note when importing.
The Import Process
We've tried to give you a completely hassle-free import process, but sometimes issues come up.
To get your import working, it's important to understand the overall import process and to identify which step is causing a problem.
The Conserv import proces has five steps.
- Choosing a sensor type
- Selecting file(s) to be imported
- Mapping your data fields to Conserv
- Importing the data
- Mapping your import to new/existing sensors
This article will walk through these five steps to help you identify the source of your problem.
Before Getting Started - Prepare Your Files for Import
If you're using PEM2 or HOBO data loggers, we have specific articles walking you through getting your files setup for import.
📝 Import Data from PEM2 and eClimateNotebook
📝 Import Data from HOBO UX & HOBOware
📝 Import Data from HOBO MX Bluetooth and HOBOlink
If you're using any other type of logger, the best way to ensure a successful upload is to use our Import Template.
You don't have to use the import template, but if you're having issues (in Step Two in particular) the template is a good place to start.
💾 Download our Import Template
A Note about Time Zones
In some cases, data exported by loggers may include a timezone specified in the header but lack a timestamp in the date/time fields. When this happens, the import process will set the timezone to Universal Time Coordinated (UTC). This can cause issues with analytics, as the time data may appear off by several hours.
For example, you may have a file with a header that includes "CDT" in the name. However, if the date/time value looks similar to "2023-03-19T05:47:00Z", the file will be imported in UTC meaning that you analytics will appear to be 5 hours off. To correctly import the data in CDT, the date/time value should include the timezone offset, for example, "2023-03-19 05:47:00.000 -0500". The "-0500" is the indicator that the time is represented in a timezone that is five hours behind UTC.
If your data does not include the timezone offset (such as "-0500"), you can also convert the dates to UTC. This will ensure that when you look at your data in analytics, you see the values at the expected times. (Note: Data is presented to you in your specified timezone within the app.) To help with this conversion, we have a sample Excel file that uses a formula to convert a date/time that doesn't include the timezone offset into UTC.
Please make sure to set the timezone offset to the correct value for your timezone! For example, for EDT, you would set the value to "+TIME(4,0,0)".
Nathan's Tips for Cleaning Up Your Data Logger File
1. Try to avoid empty columns.
Step One - Choosing a sensor type
If you're using data from HOBO sensors, select "Onset".
If you're using data from PEM2s or eClimateNotebook select "IPI".
For all other csv files select the "Other Loggers" option. We've designed our import to work well with any csv files, assuming you've prepared the files correctly in Step One.
💡 Good news. This step is very straightforward.
💻 Here's what Step One "Choosing a Sensor Type" looks like in Conserv
Step Two - Selecting file(s) to be imported
Users on the free version of Conserv can import as much data as they want, but the import is limited to one file at a time.
💻 Here's what Step Two "Selecting file(s) to be imported" looks like in Conserv
💡 Users on the Conserv Essentials subscription can use multi-file import to import up to 20 files at once.
⚠️ If you're uploading multiple files, be sure that your formatting is the same across all of the files, otherwise the import will not proceed
- Conserv has a limit of 20 files at once for data import. If you have more files than that, you'll have to do multiple imports.
Step Three - Mapping Your Data Fields to Conserv
The fields on the right come from the data you're importing. The fields on the left are where you're data will land in Conserv.
The software tries to automatically map your fields to Conserv. You can manually change a mapping by dragging and dropping the fields.
📺 Here's a quick video showing the drag and drop feature
- Sometimes the mappings are completely wrong. Unusual file structures or languages can cause issues. The easiest way to ensure success is to move the data into the template that Conserv provides.
Step Four - Importing the data
Once you click "Next Step" on the mapping screen, your import process will begin.
💻 Here's what Step Four "Importing the data" looks like in Conserv.
- Conserv has a limit of 50mb for data import files. Depending on the specific file format, this can be millions of readings and should be enough for most use cases. If you are trying to import more data than that, you can split the file into multiple parts.
- Disable pop up blockers or whitelist the Conserv.io domain. In some cases, ad blocker or popup blockers have blocked people from importing. Handling specific ad or popup blocker products is beyond the scope of this article. Please consult the instructions for your browser or security products for specific details on how to whitelist Conserv.io.
Step Five - Mapping your import to new/existing sensors
To complete the import you'll need to associate your imported data with a new or existing sensor in Conserv.
💻 Here's what Step Five "Mapping your import to new/existing sensors" looks like in Conserv
Deleting an import file
Sometimes you need to back out an import after it's completed, and that's something we can do!
From your list of imports, find the import you want to delete and click the "..." on the right side of the screen. From there you'll be presented the option to "delete import?
Create a Support Ticket
Hopefully this article solves your import problem, but if you're having import issues and feel like you need more support just let us know.