Home Data Business & Industry

265 Parts Data: Model, No. & 37 Accessories of Garden / Forest Machinery

Name	n3_lyz_echo_usa_accessories.com
Data	528K (+ 0B)
Tables	4 (+ 0)
Columns	15 (+ 0)
Table Rows	317 (+ 0)
Media	2.29M (+ 0B)
Files	240 (+ 0)
Last Commit	2023-06-19 18:12:05 (+ 169 d)

This is a parts and accessories database of garden and forest machinery. There are 265 parts with part number, description, model number and accessory in each and 37 accessories. All these accessories are classified into 15 categories, such as Bed Redefiner Accessories, Blower Accessories, Brushcutter Accessories, Power Pruner Accessories, etc. It also includes 2.29M part images in the media set. The whole garden and forest machine parts and accessories database totaly has 4 tables.

Data Samples

Main List (for Desktop / for Mobile) / JSON / XML / Excel / CSV (Download CSV) / View by Table

Data APIs

http://n3.datasn.io/data/api/v1/n3_lyz/accessory_of_garden_machine_and_forestry_machine_1/ (By Table)

Media Files

part_image ^{Bytes: 2.29M / Files: 240}

Tables + Columns
Media Files
Updates
Download

Tables & Columns

Tables	Rows	Columns	Non-empty
accessory	37	title	100%
accessory	37	category_id	100%
category	15	title	100%
part	265	part_number	100%
		description	100%
		model_number	94.72%
		accessory_id	100%

Notes:

Meta columns id and ts are not shown here, but included in columns total.
Some statistical or memo columns are not shown here, but included in columns total.
Non-empty percentage indicates the percent of values that are non-empty for that particular column.

Media Sets

part_image

Size (Bytes)	Files
2.29M	240

Commits / Updates

Time	Data	Tables	Columns	Rows	Media	Files
2023-06-19 (+ 169 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2023-01-01 (+ 95 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2022-09-27 (+ 271 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2021-12-30 (+ 115 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2021-09-05 (+ 150 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2021-04-08 (+ 68 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2021-01-29 (+ 120 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2020-10-01 (+ 38 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2020-08-23 (+ 141 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2020-04-04 (+ 196 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2019-09-21 (+ 197 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2019-03-07 (+ 43 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2019-01-23 (+ 44 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2018-12-09 (+ 29 d)	528K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2018-11-09 (+ 27 d)	528K (+ 160K)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2018-10-13 (+ 29 d)	368K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2018-09-13 (+ 34 d)	368K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2018-08-09 (+ 27 d)	368K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2018-07-12 (+ 31 d)	368K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2018-06-10 (+ 31 d)	368K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2018-05-10 (+ 28 d)	368K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2018-04-11 (+ 38 d)	368K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2018-03-03 (+ 35 d)	368K (+ 0B)	4 (+ 0)	15 (+ 0)	317 (+ 0)	2.29M (+ 0B)	240 (+ 0)
2018-01-27	368K	4	15	317	2.29M	240

Download Latest Commit

In the same time, you can also access this data set via API.

Access Now!

How to use

View the page for data details.
Sign up for an account and log in.
Open Online Query to build API addresses / calls.
Open the API address / call to access the data.

FAQ

How to access the data?

Select a membership plan and sign up. Return to this page, click Online Query to access the API query maker. Create and open an API call to acquire the data.
Why are data size increments not in line with those of number of rows?

The scanning and profiling of data size increments are done separately from those of the number of rows.