This is an automated email from the ASF dual-hosted git repository.

qiaojialin pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iotdb-docs.git


The following commit(s) were added to refs/heads/main by this push:
     new 8b16c02a fix pictures in en-v Navigating_Time_Series_Data (#596)
8b16c02a is described below

commit 8b16c02a915749fa22813821043e36054fd1d97f
Author: leto-b <[email protected]>
AuthorDate: Sun Feb 23 14:38:05 2025 +0800

    fix pictures in en-v Navigating_Time_Series_Data (#596)
---
 src/.vuepress/public/img/time-series-data-en-01.png    | Bin 0 -> 371214 bytes
 src/.vuepress/public/img/time-series-data-en-02.png    | Bin 0 -> 101059 bytes
 src/.vuepress/public/img/time-series-data-en-03.png    | Bin 0 -> 89683 bytes
 src/.vuepress/public/img/time-series-data-en-04.png    | Bin 0 -> 293350 bytes
 .../Navigating_Time_Series_Data.md                     |  16 ++++++++--------
 .../Tree/Basic-Concept/Navigating_Time_Series_Data.md  |   8 ++++----
 .../Navigating_Time_Series_Data.md                     |  16 ++++++++--------
 .../Navigating_Time_Series_Data.md                     |   8 ++++----
 8 files changed, 24 insertions(+), 24 deletions(-)

diff --git a/src/.vuepress/public/img/time-series-data-en-01.png 
b/src/.vuepress/public/img/time-series-data-en-01.png
new file mode 100644
index 00000000..3f94e064
Binary files /dev/null and 
b/src/.vuepress/public/img/time-series-data-en-01.png differ
diff --git a/src/.vuepress/public/img/time-series-data-en-02.png 
b/src/.vuepress/public/img/time-series-data-en-02.png
new file mode 100644
index 00000000..c55dc563
Binary files /dev/null and 
b/src/.vuepress/public/img/time-series-data-en-02.png differ
diff --git a/src/.vuepress/public/img/time-series-data-en-03.png 
b/src/.vuepress/public/img/time-series-data-en-03.png
new file mode 100644
index 00000000..1b842547
Binary files /dev/null and 
b/src/.vuepress/public/img/time-series-data-en-03.png differ
diff --git a/src/.vuepress/public/img/time-series-data-en-04.png 
b/src/.vuepress/public/img/time-series-data-en-04.png
new file mode 100644
index 00000000..054e33c2
Binary files /dev/null and 
b/src/.vuepress/public/img/time-series-data-en-04.png differ
diff --git 
a/src/UserGuide/Master/Table/Background-knowledge/Navigating_Time_Series_Data.md
 
b/src/UserGuide/Master/Table/Background-knowledge/Navigating_Time_Series_Data.md
index eed444c8..024ecef3 100644
--- 
a/src/UserGuide/Master/Table/Background-knowledge/Navigating_Time_Series_Data.md
+++ 
b/src/UserGuide/Master/Table/Background-knowledge/Navigating_Time_Series_Data.md
@@ -31,11 +31,11 @@ In today's interconnected world, industries such as the 
Internet of Things (IoT)
 
 Sensor data collection has permeated almost every industry, generating vast 
amounts of **time series data**.
 
-![](/img/20240505154735.png)
+![](/img/time-series-data-en-01.png)
 
 Each data collection point is referred to as a **measurement point** (also 
known as a physical quantity, time series, signal, metric, or measurement 
value). As time progresses, new data is continuously recorded for each 
measurement point, forming a **time series**. In tabular form, a time series 
consists of two columns: **timestamp** and **value**. When visualized, a time 
series appears as a trend chart over time, resembling an "electrocardiogram" of 
a device.
 
-![](/img/20240505154843.png)
+![](/img/time-series-data-en-02.png)
 
 Given the vast amount of time-series data generated by sensors, structuring 
this data effectively is essential for digital transformation across 
industries. Therefore, time-series data modeling is primarily centered around 
**devices** and **sensors**.
 
@@ -43,9 +43,9 @@ Given the vast amount of time-series data generated by 
sensors, structuring this
 
 Several fundamental concepts define time-series data:
 
-| **Device**              | Also known as an entity or equipment, a device is 
a real-world object that generates time-series data. In IoTDB, a device serves 
as a logical grouping of multiple time series. A device could be a physical 
machine, a measuring instrument, or a collection of sensors. Examples 
include:<br>- Energy sector: A wind turbine, identified by parameters such as 
region, power station, line, model, and instance.<br>- Manufacturing sector: A 
robotic arm, uniquely identified [...]
-| ------------------------------- | 
------------------------------------------------------------ |
-| **FIELD**   | Also referred to as a physical quantity, signal, metric, or 
status point, a field represents a specific measurable property recorded by a 
sensor. Each field corresponds to a measurement point that periodically 
captures environmental data. Examples include:<br>- Energy and power: Current, 
voltage, wind speed, rotational speed.<br>- Connected vehicles: Fuel level, 
vehicle speed, latitude, longitude.<br>- Manufacturing: Temperature, humidity.|
-| **Data Point**        | A data point consists of a timestamp and a value. 
The timestamp is typically stored as a long integer, while the value can be of 
various data types such as BOOLEAN, FLOAT, or INT32. <br>In tabular format, a 
data point corresponds to a single row in a time-series dataset, while in 
graphical representation, it is a single point on a time-series chart.<br> <img 
src="/img/20240505154843.png" alt="" style="width: 70%;"/> |
-| **Frequency**       | The sampling frequency determines how often a sensor 
records data within a given timeframe.<br>For example, if a temperature sensor 
records data once per second, its sampling frequency is 1Hz (1 sample per 
second). |
-| **TTL**  | TTL (Time-to-Live) defines the retention period of stored data. 
Once the TTL expires, the data is automatically deleted.<br>IoTDB allows 
different TTL values for different datasets, enabling automated, periodic data 
deletion. Proper TTL configuration helps:<br>- Manage disk space efficiently, 
preventing storage overflow.<br>- Maintain high query performance.<br>- Reduce 
memory resource consumption. |
\ No newline at end of file
+| **Device**              | Also known as an entity or equipment, a device is 
a real-world object that generates time-series data. In IoTDB, a device serves 
as a logical grouping of multiple time series. A device could be a physical 
machine, a measuring instrument, or a collection of sensors. Examples 
include:<br>- Energy sector: A wind turbine, identified by parameters such as 
region, power station, line, model, and instance.<br>- Manufacturing sector: A 
robotic arm, uniquely identified [...]
+| ------------------------------- 
|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 [...]
+| **FIELD**   | Also referred to as a physical quantity, signal, metric, or 
status point, a field represents a specific measurable property recorded by a 
sensor. Each field corresponds to a measurement point that periodically 
captures environmental data. Examples include:<br>- Energy and power: Current, 
voltage, wind speed, rotational speed.<br>- Connected vehicles: Fuel level, 
vehicle speed, latitude, longitude.<br>- Manufacturing: Temperature, humidity.  
                                [...]
+| **Data Point**        | A data point consists of a timestamp and a value. 
The timestamp is typically stored as a long integer, while the value can be of 
various data types such as BOOLEAN, FLOAT, or INT32. <br>In tabular format, a 
data point corresponds to a single row in a time-series dataset, while in 
graphical representation, it is a single point on a time-series chart.<br> <img 
src="/img/time-series-data-en-03.png" alt="" style="width: 70%;"/>              
                          [...]
+| **Frequency**       | The sampling frequency determines how often a sensor 
records data within a given timeframe.<br>For example, if a temperature sensor 
records data once per second, its sampling frequency is 1Hz (1 sample per 
second).                                                                        
                                                                                
                                                                                
                       [...]
+| **TTL**  | TTL (Time-to-Live) defines the retention period of stored data. 
Once the TTL expires, the data is automatically deleted.<br>IoTDB allows 
different TTL values for different datasets, enabling automated, periodic data 
deletion. Proper TTL configuration helps:<br>- Manage disk space efficiently, 
preventing storage overflow.<br>- Maintain high query performance.<br>- Reduce 
memory resource consumption.                                                    
                           [...]
\ No newline at end of file
diff --git 
a/src/UserGuide/Master/Tree/Basic-Concept/Navigating_Time_Series_Data.md 
b/src/UserGuide/Master/Tree/Basic-Concept/Navigating_Time_Series_Data.md
index 6ff81da3..e365acb3 100644
--- a/src/UserGuide/Master/Tree/Basic-Concept/Navigating_Time_Series_Data.md
+++ b/src/UserGuide/Master/Tree/Basic-Concept/Navigating_Time_Series_Data.md
@@ -24,25 +24,25 @@
 
 In today's era of the Internet of Things, various scenarios such as the 
Internet of Things and industrial scenarios are undergoing digital 
transformation. People collect various states of devices by installing sensors 
on them. If the motor collects voltage and current, the blade speed, angular 
velocity, and power generation of the fan; Vehicle collection of latitude and 
longitude, speed, and fuel consumption; The vibration frequency, deflection, 
displacement, etc. of the bridge. The data [...]
 
-![](/img/20240505154735.png)
+![](/img/time-series-data-en-01.png)
 
 Generally speaking, we refer to each collection point as a measurement point 
(also known as a physical quantity, time series, timeline, signal quantity, 
indicator, measurement value, etc.). Each measurement point continuously 
collects new data information over time, forming a time series. In the form of 
a table, each time series is a table formed by two columns: time and value; In 
a graphical way, each time series is a trend chart formed over time, which can 
also be vividly referred to a [...]
 
-![](/img/20240505154843.png)
+![](/img/time-series-data-en-02.png)
 
 The massive time series data generated by sensors is the foundation of digital 
transformation in various industries, so our modeling of time series data 
mainly focuses on equipment and sensors.
 
 ## Key Concepts of Time Series Data
 The main concepts involved in time-series data can be divided from bottom to 
top: data points, measurement points, and equipment.
 
-![](/img/20240505154513.png)
+![](/img/time-series-data-en-04.png)
 
 ### Data Point
 
 - Definition: Consists of a timestamp and a value, where the timestamp is of 
type long and the value can be of various types such as BOOLEAN, FLOAT, INT32, 
etc.
 - Example: A row of a time series in the form of a table in the above figure, 
or a point of a time series in the form of a graph, is a data point.
 
-![](/img/20240505154432.png)
+![](/img/time-series-data-en-03.png)
 
 ### Measurement Points
 
diff --git 
a/src/UserGuide/latest-Table/Background-knowledge/Navigating_Time_Series_Data.md
 
b/src/UserGuide/latest-Table/Background-knowledge/Navigating_Time_Series_Data.md
index eed444c8..024ecef3 100644
--- 
a/src/UserGuide/latest-Table/Background-knowledge/Navigating_Time_Series_Data.md
+++ 
b/src/UserGuide/latest-Table/Background-knowledge/Navigating_Time_Series_Data.md
@@ -31,11 +31,11 @@ In today's interconnected world, industries such as the 
Internet of Things (IoT)
 
 Sensor data collection has permeated almost every industry, generating vast 
amounts of **time series data**.
 
-![](/img/20240505154735.png)
+![](/img/time-series-data-en-01.png)
 
 Each data collection point is referred to as a **measurement point** (also 
known as a physical quantity, time series, signal, metric, or measurement 
value). As time progresses, new data is continuously recorded for each 
measurement point, forming a **time series**. In tabular form, a time series 
consists of two columns: **timestamp** and **value**. When visualized, a time 
series appears as a trend chart over time, resembling an "electrocardiogram" of 
a device.
 
-![](/img/20240505154843.png)
+![](/img/time-series-data-en-02.png)
 
 Given the vast amount of time-series data generated by sensors, structuring 
this data effectively is essential for digital transformation across 
industries. Therefore, time-series data modeling is primarily centered around 
**devices** and **sensors**.
 
@@ -43,9 +43,9 @@ Given the vast amount of time-series data generated by 
sensors, structuring this
 
 Several fundamental concepts define time-series data:
 
-| **Device**              | Also known as an entity or equipment, a device is 
a real-world object that generates time-series data. In IoTDB, a device serves 
as a logical grouping of multiple time series. A device could be a physical 
machine, a measuring instrument, or a collection of sensors. Examples 
include:<br>- Energy sector: A wind turbine, identified by parameters such as 
region, power station, line, model, and instance.<br>- Manufacturing sector: A 
robotic arm, uniquely identified [...]
-| ------------------------------- | 
------------------------------------------------------------ |
-| **FIELD**   | Also referred to as a physical quantity, signal, metric, or 
status point, a field represents a specific measurable property recorded by a 
sensor. Each field corresponds to a measurement point that periodically 
captures environmental data. Examples include:<br>- Energy and power: Current, 
voltage, wind speed, rotational speed.<br>- Connected vehicles: Fuel level, 
vehicle speed, latitude, longitude.<br>- Manufacturing: Temperature, humidity.|
-| **Data Point**        | A data point consists of a timestamp and a value. 
The timestamp is typically stored as a long integer, while the value can be of 
various data types such as BOOLEAN, FLOAT, or INT32. <br>In tabular format, a 
data point corresponds to a single row in a time-series dataset, while in 
graphical representation, it is a single point on a time-series chart.<br> <img 
src="/img/20240505154843.png" alt="" style="width: 70%;"/> |
-| **Frequency**       | The sampling frequency determines how often a sensor 
records data within a given timeframe.<br>For example, if a temperature sensor 
records data once per second, its sampling frequency is 1Hz (1 sample per 
second). |
-| **TTL**  | TTL (Time-to-Live) defines the retention period of stored data. 
Once the TTL expires, the data is automatically deleted.<br>IoTDB allows 
different TTL values for different datasets, enabling automated, periodic data 
deletion. Proper TTL configuration helps:<br>- Manage disk space efficiently, 
preventing storage overflow.<br>- Maintain high query performance.<br>- Reduce 
memory resource consumption. |
\ No newline at end of file
+| **Device**              | Also known as an entity or equipment, a device is 
a real-world object that generates time-series data. In IoTDB, a device serves 
as a logical grouping of multiple time series. A device could be a physical 
machine, a measuring instrument, or a collection of sensors. Examples 
include:<br>- Energy sector: A wind turbine, identified by parameters such as 
region, power station, line, model, and instance.<br>- Manufacturing sector: A 
robotic arm, uniquely identified [...]
+| ------------------------------- 
|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 [...]
+| **FIELD**   | Also referred to as a physical quantity, signal, metric, or 
status point, a field represents a specific measurable property recorded by a 
sensor. Each field corresponds to a measurement point that periodically 
captures environmental data. Examples include:<br>- Energy and power: Current, 
voltage, wind speed, rotational speed.<br>- Connected vehicles: Fuel level, 
vehicle speed, latitude, longitude.<br>- Manufacturing: Temperature, humidity.  
                                [...]
+| **Data Point**        | A data point consists of a timestamp and a value. 
The timestamp is typically stored as a long integer, while the value can be of 
various data types such as BOOLEAN, FLOAT, or INT32. <br>In tabular format, a 
data point corresponds to a single row in a time-series dataset, while in 
graphical representation, it is a single point on a time-series chart.<br> <img 
src="/img/time-series-data-en-03.png" alt="" style="width: 70%;"/>              
                          [...]
+| **Frequency**       | The sampling frequency determines how often a sensor 
records data within a given timeframe.<br>For example, if a temperature sensor 
records data once per second, its sampling frequency is 1Hz (1 sample per 
second).                                                                        
                                                                                
                                                                                
                       [...]
+| **TTL**  | TTL (Time-to-Live) defines the retention period of stored data. 
Once the TTL expires, the data is automatically deleted.<br>IoTDB allows 
different TTL values for different datasets, enabling automated, periodic data 
deletion. Proper TTL configuration helps:<br>- Manage disk space efficiently, 
preventing storage overflow.<br>- Maintain high query performance.<br>- Reduce 
memory resource consumption.                                                    
                           [...]
\ No newline at end of file
diff --git 
a/src/UserGuide/latest/Background-knowledge/Navigating_Time_Series_Data.md 
b/src/UserGuide/latest/Background-knowledge/Navigating_Time_Series_Data.md
index 6ff81da3..e365acb3 100644
--- a/src/UserGuide/latest/Background-knowledge/Navigating_Time_Series_Data.md
+++ b/src/UserGuide/latest/Background-knowledge/Navigating_Time_Series_Data.md
@@ -24,25 +24,25 @@
 
 In today's era of the Internet of Things, various scenarios such as the 
Internet of Things and industrial scenarios are undergoing digital 
transformation. People collect various states of devices by installing sensors 
on them. If the motor collects voltage and current, the blade speed, angular 
velocity, and power generation of the fan; Vehicle collection of latitude and 
longitude, speed, and fuel consumption; The vibration frequency, deflection, 
displacement, etc. of the bridge. The data [...]
 
-![](/img/20240505154735.png)
+![](/img/time-series-data-en-01.png)
 
 Generally speaking, we refer to each collection point as a measurement point 
(also known as a physical quantity, time series, timeline, signal quantity, 
indicator, measurement value, etc.). Each measurement point continuously 
collects new data information over time, forming a time series. In the form of 
a table, each time series is a table formed by two columns: time and value; In 
a graphical way, each time series is a trend chart formed over time, which can 
also be vividly referred to a [...]
 
-![](/img/20240505154843.png)
+![](/img/time-series-data-en-02.png)
 
 The massive time series data generated by sensors is the foundation of digital 
transformation in various industries, so our modeling of time series data 
mainly focuses on equipment and sensors.
 
 ## Key Concepts of Time Series Data
 The main concepts involved in time-series data can be divided from bottom to 
top: data points, measurement points, and equipment.
 
-![](/img/20240505154513.png)
+![](/img/time-series-data-en-04.png)
 
 ### Data Point
 
 - Definition: Consists of a timestamp and a value, where the timestamp is of 
type long and the value can be of various types such as BOOLEAN, FLOAT, INT32, 
etc.
 - Example: A row of a time series in the form of a table in the above figure, 
or a point of a time series in the form of a graph, is a data point.
 
-![](/img/20240505154432.png)
+![](/img/time-series-data-en-03.png)
 
 ### Measurement Points
 

Reply via email to