Google Earth Engine ——欧洲联盟三年一次的原地土地覆盖和土地利用数据(共有106个属性)

The Land Use/Cover Area frame Survey (LUCAS) in the European Union (EU) was set up to provide statistical information. It represents a triennial in-situ landcover and land-use data-collection exercise that extends over the whole of the EU's territory. LUCAS collects information on land cover and land use, agro-environmental variables, soil, and grassland. The surveys also provide spatial information to analyse the mutual influences between agriculture, environment, and countryside, such as irrigation and land management.

The dataset presented here is the harmonized version of all yearly LUCAS surveys with a total of 106 attributes. Each point's location is using the fields 'th_lat' and 'th_lon', that is, the LUCAS theoretical location (THLOC), as prescribed by the LUCAS grid. For more information please see Citations. Note that not every field is present for every year - see the "Years" section in property descriptions.

The text "C1 (Instructions)" in the table schema descriptions refers to this document.

欧洲联盟(EU)的土地利用/覆盖面积框架调查(LUCAS)是为了提供统计信息而设立的。它是一项三年一次的原地土地覆盖和土地利用数据收集工作,涵盖了欧盟的全部领土。LUCAS收集了关于土地覆盖和土地利用、农业环境变量、土壤和草原的信息。这些调查还提供了空间信息,以分析农业、环境和农村之间的相互影响,如灌溉和土地管理。

这里介绍的数据集是LUCAS所有年度调查的统一版本,共有106个属性。每个点的位置都使用'th_lat'和'th_lon'字段,即LUCAS的理论位置(THLOC),由LUCAS网格规定。更多信息请见引文。请注意,并不是每一年都有每个字段--见属性描述中的 "年份 "部分。

表模式描述中的文字 "C1(说明)"指的是本文件。

Dataset Availability

2006-02-05T00:00:00 - 2019-03-14T00:00:00

Dataset Provider

Joint Research Center, Unit D5

Collection Snippet

ee.FeatureCollection("JRC/LUCAS_HARMO/THLOC/V1")

NameTypeDescription
idIntUnique row identifier. Source: Added by harmonization process
point_idInt8-digit unique point identifier, point ID according to the LUCAS grid. Such a point ID can either be part or not of a particular yearly LUCAS survey. Source: C1(Instructions), p.141, sec.9.1.1 Years: all
yearIntYear of survey. Source: Added by harmonization process Years: all
nuts0StringNUTS 2016 Level 0. Years: all
nuts1StringNUTS 2016 Level 1. Years: all
nuts2StringNUTS 2016 Level 2. Years: all
nuts3StringNUTS 2016 Level 3. Years: 2018
office_piStringWhether photo-interpretation has happened in the office for this LUCAS point. If true, then this point_id was not visited by an inspector for this year. Values: * true * false Source: C1(Instructions), p.141, sec.9.1.1 Years: 2015, 2018
ex_anteStringEx-ante points are points that are parts of the in-situ sample and in principle have to be visited in the field, although there are a posteriori reasons why this is impossible. If true, then this point_id was not visited by an inspector for this year. Values: * true * false Source: C1(Instructions), p.16, sec 8.1; C1(Instructions), p.141, sec.9.1.1 Years: 2018
survey_dateStringDate on which the survey was carried out in the format dd/mm/yy Years: all
car_latitudeDoubleLatitude (WGS84) on which the car was parked. Source: C1(Instructions), p.141, sec.9.1.2 Years: 2018
car_ewStringGPS Car parking East/West compass setting. Used for knowing when to add a minus to the respective coordinate. Values: * East * West * empty if not relevant Years: 2018
car_longitudeDoubleLongitude (WGS84) on which the car was parked. Source: C1(Instructions), p.142, sec.9.1.2 Years: 2018
gps_projStringGPS projection. Values: * WGS84 * No GPS signal * empty if not relevant Source: C1(Instructions), p.142, sec.9.1.2 Years: all
gps_precDoubleAverage location error as given by GPS receiver (in meters). Source: C1(Instructions), p.142, sec.9.1.2 Years: all
gps_altitudeDoubleElevation in m above sea level. Source: C1(Instructions), p.141, sec.9.1.1 Years: 2009, 2012, 2015, 2018
gps_latDoubleGPS latitude of the location from which observation is actually done (WGS84) measured in degrees. Source: C1(Instructions), p.142, sec.9.1.2 Years: all
gps_ewStringEast-west encoding setting for GPS. Values: * East * West * empty if not relevant Years: all
gps_longDoubleGPS longitude of the location from which observation is actually done (WGS84) measured in degrees. Source: C1(Instructions), p.142, sec.9.1.2 Years: all
obs_distDoubleDistance between observation location and the LUCAS point as provided by the GPS receiver (in meters). Years: all
obs_directStringDirection of the observation. Values: * On the point: Point regularly observed * Look to the North: "Look to the North" rule is applied id the point is located on a boundary/ e.g., or a small linear feature (<3 m wide) * Look to the East: "Look to the East" rule is applied if he point is located on a boundary/e.g., or a small linear feature (<3 m wide) * empty if not relevant Source: C1(Instructions), p.144, sec.9.1.4 Years: all
obs_typeStringThe method of observation for the relevant point. For the availability of LUCAS photos according to obs_type, please check C1(Instructions), sec. 8.15.3. Values: * In situ < 100 m * In situ > 100 m * In situ PI * In situ PI not possible * Out of national territory * In office PI * Marine Sea * (only 2015) Find more details check the documentation. Source: C1(Instructions), p.142-144, sec.9.1.4 Years: all
obs_radiusDoubleThe radius of observation - whether the near or the extended window of observation is applied. Values: * 1.5 * 20 * null if not relevant Source: C1(Instructions) Years: 2006, 2009, 2012, 2015
letter_groupStringWhich letter group (top tier classification) from the C3 document is the point assigned to. Source: Added by harmonization process Years: all
lc1StringCoding of land cover according to harmonized C3 classification. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document Years: all
lc1_labelStringLabel of land cover according to harmonized C3 document. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document
lc1_specStringCoding of land cover species according to harmonized C3 classification. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document Years: 2009, 2012, 2015, 2018
lc1_spec_labelStringLabel of land cover species according to harmonized C3 document. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document
lc1_percStringThe percentage that the assigned land cover type (lc1) occupies on the ground. Values: * < 10 % * 10 - 25 % * 25 - 50 % * 50 - 75 % * > 75 % * empty if not relevant This coding applies only for the years 2009–2015 . For 2018 the number represents the percentage of land-cover (0-100). The variable does not exist for 2006 Years: 2009, 2012, 2015, 2018
lc2StringCoding of land cover according to harmonized C3 classification. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document Years: all
lc2_labelStringLabel of land cover according to harmonized C3 document. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document
lc2_specStringCoding of land cover species according to harmonized C3 classification. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document Years: 2009, 2012, 2015, 2018
lc2_spec_labelStringLabel of land cover species according to harmonized C3 document. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document
lc2_percStringThe percentage that the assigned land cover type (lc2) occupies on the ground. Values: * < 10 % * 10 - 25 % * 25 - 50 % * 50 - 75 % * > 75 % * empty if not relevant This coding applies only for the years 2009–2015 . For 2018 the number represents the percentage of land-cover (0-100). The variable does not exist for 2006 Years: 2009, 2012, 2015, 2018
lu1StringCoding of the land use according to Harmonized C3 document classification. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document Years: all
lu1_labelStringLabel of the land use according to Harmonized C3 document classification. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document
lu1_typeStringCoding of the land use types according to Harmonized C3 document classification. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document Years: 2015, 2018
lu1_type_labelStringLabel of the land use types according to Harmonized C3 document classification. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document
lu1_percStringThe percentage that the assigned land use type (lu1) occupies on the ground. Values: * < 5 % * 5 - 10 % * 10 - 25 % * 25 - 50 % * 50 - 75 % * 75 - 90 % * > 90 % * Not Relevant This coding applies only for the year 2015. For 2018 the number represents the percentage of land-cover (0-100). The variable does not exist for 2006, 2009 and 2012. Years: 2015, 2018
lu2StringCoding of the land use according to Harmonized C3 document classification. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document Years: all
lu2_labelStringLabel of the land use according to Harmonized C3 document classification. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document
lu2_typeStringCoding of the land use types according to Harmonized C3 document classification. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document Years: 2015, 2018
lu2_type_labelStringLabel of the land use types according to Harmonized C3 document classification. Coding and label translation can be found in the [supporting docs](https://figshare.com/s/e6cab3bceaa9a2299237) in file *c3_legends_new.csv*. Source: Harmonized C3 document
lu2_percStringThe percentage that the assigned land use type (lu2) occupies on the ground. Values: * < 5 % * 5 - 10 % * 10 - 25 % * 25 - 50 % * 50 - 75 % * 75 - 90 % * > 90 % * Not Relevant This coding applies only for the year 2015. For 2018 the number represents the percentage of land-cover (0-100). The variable does not exist for 2006, 2009 and 2012. Years: 2015, 2018
parcel_area_haStringSize of the surveyed parcel in hectares. Values: * < 0.5 * 0.5 - 1 * 1 - 10 * > 10 * empty if not relevant Source: C1(Instructions), p.50, sec.8.4.15 Years: 2009, 2012, 2015, 2018
tree_height_maturityStringHeight of trees at maturity. Values: * < 5 m * > 5 m * Not identifiable * empty if not relevant Source: C1(Instructions), p.147, sec.9.1.6 Years: 2012, 2015, 2018
tree_height_surveyStringHeight of trees at the moment of survey. Values: * < 5 m * > 5 m * Not identifiable * empty if not relevant Source: C1(Instructions), p.147, sec.9.1.6 Years: 2009, 2012, 2015, 2018
feature_widthStringWidth of the feature. Values: * < 20 m * > 20 m * Not identifiable * empty if not relevant Source: C1(Instructions), p.147, sec.9.1.6 Years: 2009, 2012, 2015, 2018
lm_stone_wallsStringPresence of stone walls on the plot. Values: * No * Stone wall not maintained * Stone wall well maintained * empty if not relevant Source: C1(Instructions), p.148, sec.9.1.7 Years: 2018
crop_residuesStringPresence of crop residues on the plot. Values: * true * false Source: C1(Instructions), p.51, sec.8.6 Years: 2018
lm_grass_marginsStringPresence of grass margins on the plot. Values: * No * < 1 m width * > 1 m width * empty if not relevant Source: C1(Instructions), p.148, sec.9.1.7 Years: 2018
grazingStringSigns of grazing on the plot. Values: * Signs of grazing * No signs of grazing * empty if not relevant Source: C1(Instructions), p.148, sec.9.1.8 Years: 2009, 2012, 2015, 2018
special_statusStringWhether the plot is a part of any specially regulated area. Values: * Protected * Hunting * Protected and hunting * No special status * empty if not relevant Source: C1(Instructions), p.149, sec.9.1.8 Years: 2012, 2015, 2018
lc_lu_special_remarkStringAny special remarks on the land cover / land use. Values: * Harvested field * Tilled/sowed * Clear cut * Burnt area * Fire break * Nursery * Dump site * Temporary dry * Temporary flooded * No remark * empty if not relevant For more details check the documentation. Source: C1(Instructions), p.149-150, sec.9.1.8 Years: 2012, 2015, 2018
cprn_candoStringWhether a Copernicus survey can be done on this point. For more information on the Copernicus module and the data created please refer to [d'Andrimont et al, 2021](https://essd.copernicus.org/articles/13/1119/2021/ ). Values: * true * false Source: C1(Instructions), p.58, sec.8.8.1, C1(Instructions), p.150, sec.9.1.9 Years: 2018
cprn_lcStringThe land cover on the Copernicus points according to the classification scheme at level2. Source: Harmonized C3 document Years: 2018
cprn_lc_labelStringLabel of land cover on the Copernicus points according to the classification scheme at level2. Source: Harmonized C3 document
cprn_lc1nDoubleThe extent (in meters) to which the land cover of the Copernicus point stays the same in direction North. Source: C1(Instructions), p.150, sec.9.1.9 Years: 2018
cprnc_lc1eDoubleThe extent (in meters) to which the land cover of the Copernicus point stays the same in direction East. Source: C1(Instructions), p.150, sec.9.1.9 Years: 2018
cprnc_lc1sDoubleThe extent (in meters) to which the land cover of the Copernicus point stays the same in direction South. Source: C1(Instructions), p.150, sec.9.1.9 Years: 2018
cprnc_lc1wDoubleThe extent (in meters) to which the land cover of the Copernicus point stays the same in direction West. Source: C1(Instructions), p.150, sec.9.1.9 Years: 2018
cprn_lc1n_brdthDoubleThe breath (in %) to the next Copernicus land cover in direction North. Source: C1(Instructions), p.150, sec.9.1.9 Years: 2018
cprn_lc1e_brdthDoubleThe breath (in %) to the next Copernicus land cover in direction East. Source: C1(Instructions), p.150, sec.9.1.9 Years: 2018
cprn_lc1s_brdthDoubleThe breath (in %) to the next Copernicus land cover in direction South. Source: C1(Instructions), p.150, sec.9.1.9 Years: 2018
cprn_lc1w_brdthDoubleThe breath (in %) to the next Copernicus land cover in direction West. Source: C1(Instructions), p.150, sec.9.1.9 Years: 2018
cprn_lc1n_nextStringThe recorded next land cover if a land cover change (LUCAS land cover level 2) occurs within 50m in direction North, regardless of the fact that the next land cover is visible on the landscape photo or not. Any feature less than 3m wide is not taken into account and is not considered a land cover change. Source: Harmonized C3 document Years: 2018
cprn_lc1s_nextStringThe recorded next land cover if a land cover change (LUCAS land cover level 2) occurs within 50m in direction South, regardless of the fact that the next land cover is visible on the landscape photo or not. Any feature less than 3m wide is not taken into account and is not considered a land cover change. Source: Harmonized C3 document Years: 2018
cprn_lc1e_nextStringThe recorded next land cover if a land cover change (LUCAS land cover level 2) occurs within 50m in direction East, regardless of the fact that the next land cover is visible on the landscape photo or not. Any feature less than 3m wide is not taken into account and is not considered a land cover change. Source: Harmonized C3 document Years: 2018
cprn_lc1w_nextStringThe recorded next land cover if a land cover change (LUCAS land cover level 2) occurs within 50m in direction West, regardless of the fact that the next land cover is visible on the landscape photo or not. Any feature less than 3m wide is not taken into account and is not considered a land cover change. Source: Harmonized C3 document Years: 2018
cprn_urbanStringWhether the Copernicus point located in an urban area. Values: * true * false Source: C1(Instructions), p.151, sec.9.1.10.1 Years: 2018
cprn_impervious_percDoublePercentage of impervious surfaces. Source: C1(Instructions), p.151, sec.9.1.10.1 Years: 2018
inspire_plcc1DoublePercentage of coniferous trees. Source: C1(Instructions), p.151, sec.9.1.10.2 Years: 2015, 2018
inspire_plcc2DoublePercentage of broadleaved trees. Source: C1(Instructions), p.151, sec.9.1.10.2 Years: 2015, 2018
inspire_plcc3DoublePercentage of shrubs. Source: C1(Instructions), p.151, sec.9.1.10.2 Years: 2015, 2018
inspire_plcc4DoublePercentage of herbaceous plants. Source: C1(Instructions), p.151, sec.9.1.10.2 Years: 2015, 2018
inspire_plcc5DoublePercentage of lichens and mosses. Source: C1(Instructions), p.151, sec.9.1.10.2 Years: 2015, 2018
inspire_plcc6DoublePercentage of consolidated (bare) surface (e.g., rock outcrops). Source: C1(Instructions), p.151, sec.9.1.10.2 Years: 2015, 2018
inspire_plcc7DoublePercentage of unconsolidated (bare) surface (e.g., sand). Source: C1(Instructions), p.151, sec.9.1.10.2 Years: 2015, 2018
inspire_plcc8DoubleDifference between the sum of all inspire persentage classes and 100%. Source: C1(Instructions), p.151, sec.9.1.10.2 Years: 2015, 2018
eunis_complexStringEUNIS habitat classification. Values: * X06 * X09 * Other * Unknown * empty if not relevant Source: C1(Instructions), p.152, sec.9.1.11 Years: 2018
grassland_sampleStringWhether the point is a part of the grassland module. Values: * true * false Source: C1(Instructions), p.152, sec.9.1.12 Years: 2018
grass_candoStringWhether a grassland survey is possible. Values: * true * false Source: C1(Instructions), p.152, sec.9.1.12 Years: 2018
wmStringType of water management present at the point. Values: * Irrigation * Potential irrigation * Drainage * Irrigation and drainage * No visible water management * empty if not relevant Source: C1(Instructions), p.162, sec.9.1.13 Years: 2009, 2012, 2015, 2018
wm_sourceStringSource of the irrigation at the point. Values: * Combo - Other/Not Identifiable + Well * Combo - Other/Not Identifiable + Pond/Lake/Reservoir * Combo - Other/Not Identifiable + Stream/Canal/Ditch * Combo - Other/Not Identifiable + Lagoon/Wastewater * Combo - Pond/Lake/Reservoir + Stream/Canal/Ditch * Lagoon/Wastewater * Pond/Lake/Reservoir * Stream/Canal/Ditch * Well * Other/Not Identifiable * empty if not relevant Combo classes exist only for 2009 and were later discontinued. For more details check the documentation. Source: C1(Instructions), p.163, sec.9.1.13 Years: 2009
wm_typeStringThe type of irrigation present at the point. Values: * Gravity * Pressure: Sprinkle irrigation * Pressure: Micro-irrigation * Gravity/Pressure * Other/Non identifiable * Combo - Pressure: Sprinkle irrigation + Pressure: Micro-irrigation * Combo - Gravity/Pressure + Gravity * Combo - Pressure: Sprinkle irrigation + Gravity/Pressure * Combo - Pressure: Micro-irrigation + Gravity/Pressure * Other/not identifiable * Combo - Other/Non identifiable + Gravity * Combo - Other/Non identifiable + Gravity/Pressure * Combo - Other/Non identifiable + Gravity/Pressure + Pressure: Micro-irrigation * empty if not relevant Combo classes exist only for 2009 and were later discontinued. For more details check the documentation. Source: C1(Instructions), p.162-163, sec.9.1.13 Years: 2009
wm_deliveryStringThe irrigation delivery system at the point. Values: * Canal * Combo - Pipeline + Ditch * Combo - Other/Non identifiable + Ditch * Combo - Other/Non identifiable + Pipeline * Ditch * Pipeline * Other/Non identifiable * Other/Non identifiable + Canal * empty if not relevant Combo classes exist only for 2009 and were later discontinued. For more details check the documentation. Source: C1(Instructions), p.163-164, sec.9.1.13 Years: 2009
erosion_candoStringWhether a point is foreseen for assessing erosion (true) or not (false). Values: * true * false Source: C1(Instructions), p.168, sec.9.1.15 Years: 2018
soil_stones_percStringPercentage of stones on the surface (does not include stones covered by soil). Values: * < 10 % * 10 - 25 % * 25 - 50 % * > 50 % * empty if not relevant This coding applies only for the years 2009–2015 . For 2018 the number represents the percentage of stones on the surface (0-100). The variable does not exist for 2006. Source: C1(Instructions), p.164, sec.9.1.14.2 Years: 2009, 2012, 2015, 2018
bio_sampleStringWhether the point a biodiversity sample point. Values: * true * false Years: 2018
soil_bio_takenStringWhether a soil-biodiversity sample was taken. Values: * true * false Source: C1(Instructions) Years: 2018
bulk0_10_sampleStringWhether a point is foreseen for collecting the bulk density between the given range. Values: * false * true Years: 2018
soil_blk_0_10_takenStringWhether the soil sample between the given range was taken. Values: * true * false Source: C1(Instructions) Years: 2018
bulk10_20_sampleStringWhether a point is foreseen for collecting the bulk density between the given range. Values: * true * false Source: C1(Instructions) Years: 2018
soil_blk_10_20_takenStringWhether the soil sample between the given range was taken. Values: * Yes * No Source: C1(Instructions) Years: 2018
bulk20_30_sampleStringWhether a point is foreseen for collecting the bulk density between the given range. Values: * true * false Source: C1(Instructions) Years: 2018
soil_blk_20_30_takenStringWhether the soil sample between the given range was taken. Values: * true * false Source: C1(Instructions) Years: 2018
standard_sampleStringWhether the point is a standard soil point. Values: * true * false Source: C1(Instructions) Years: 2018
soil_std_takenStringWhether the standard soil sample was taken. Values: * true * false Source: C1(Instructions) Years: 2018
organic_sampleStringWhether the point is an organic sample point. Values: * true * false Source: C1(Instructions) Years: 2018
soil_org_depth_candoStringWhether depth can be evaluated. Values: * true * false Source: C1(Instructions) Years: 2018
soil_takenStringHas a soil sample been taken (before 2018). Values: * Yes * Not possible * No, already taken * No sample required * empty if not relevant Source: C1(Instructions) Years: 2009, 2012, 2015
soil_cropStringPercentage of residual crop. Values: * < 10 % * 10 - 25 % * 25 - 50 % * > 50 % * empty if not relevant Source: C1(Instructions) Years: 2009, 2012, 2015
photo_pointStringWhether a photo on the point was taken. Values: * Photo taken * Photo not taken * empty if not relevant Source: C1(Instructions) Years: all
photo_northStringWhether a photo looking north was taken. Values: * Photo taken * Photo not taken * empty if not relevant Source: C1(Instructions) Years: all
photo_southStringWhether a photo looking south was taken. Values: * Photo taken * Photo not taken * empty if not relevant Source: C1(Instructions) Years: all
photo_eastStringWhether a photo looking east was taken. Values: * Photo taken * Photo not taken * empty if not relevant Source: C1(Instructions) Years: all
photo_westStringWhether a photo looking west been taken. Values: * Photo taken * Photo not taken * empty if not relevant Source: C1(Instructions) Years: all
transectStringThe changes in land cover as recorded by the east-facing transect line. Years: 2009, 2012, 2015
revisitDoubleNumber of visits to the point throughout the survey years. Source: Added by harmonization process
th_gps_distDoubleCalculated distance between theoretical and recorded location. Source: Added by harmonization process
file_path_gisco_northStringFile path to north-facing photo as stored on ESTAT GISCO sever. Source: Added by harmonization process Years: all
file_path_gisco_southStringFile path to south-facing photo as stored on ESTAT GISCO sever. Source: Added by harmonization process Years: all
file_path_gisco_eastStringFile path to east-facing photo as stored on ESTAT GISCO sever. Source: Added by harmonization process Years: all
file_path_gisco_westStringFile path to west-facing photo as stored on ESTAT GISCO sever. Source: Added by harmonization process Years: all
file_path_gisco_pointStringFile path to point-facing photo as stored on ESTAT GISCO sever. Source: Added by harmonization process Years: all

文献引用:

d'Andrimont, R., Yordanov, M., Martinez-Sanchez, L. et al. Harmonised LUCAS in-situ land cover and use database for field surveys from 2006 to 2018 in the European Union. Sci Data 7, 352 (2020). doi:10.1038/s41597-020-00675-z

代码:

var dataset = ee.FeatureCollection("JRC/LUCAS_HARMO/THLOC/V1");

// For the Inspector
Map.addLayer(dataset, {}, "LUCAS Points (data)", false);

dataset = dataset.style({
  color: "489734",
  pointSize: 3,
});

Map.setCenter(-3.8233, 40.609, 10);

Map.addLayer(dataset, {}, "LUCAS Points (styled green)");

 

 

 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
要利用Google Earth Engine绘制2020年重庆土地覆盖数据集并统计各类土地覆盖率的面积,可以按照以下步骤操作: 1. 打开Google Earth Engine平台并登录账户。 2. 在搜索栏中输入“重庆市”,并选择适当的地理边界范围。 3. 在代码编辑器中输入以下代码,用于显示重庆市的地图: ```javascript Map.addLayer(ee.Image().paint({ 'featureCollection': ee.FeatureCollection('TIGER/2018/States'), 'color': 'black', 'width': 2}), {}, 'US States'); ``` 4. 在代码编辑器中输入以下代码,用于导入2020年重庆市的土地覆盖数据集并显示在地图上: ```javascript //选择2020年重庆市的MODIS土地覆盖数据集 var lc = ee.ImageCollection('MODIS/006/MCD12Q1') .filterDate('2020-01-01', '2020-12-31') .select('LC_Type1'); //对土地覆盖数据集进行分类 var lc_class = lc.map(function(img){ return img.clip(chongqing) .reproject('EPSG:4326', null, 500) .uint8() .rename('landcover'); }); //添加土地覆盖率图层到地图中 var lc_vis_params = { min: 0, max: 17, palette: ['05450a', '086a10', '54a708', '78d203', '009900', 'c6b044', 'dcd159', 'dade48', 'fbff13', 'b6ff05', '27ff87', 'c24f44', 'a5a5a5', 'ff6d4c', '69fff8', 'f9ffa4', '1c0dff'] }; Map.addLayer(lc_class, lc_vis_params, 'Land Cover'); ``` 5. 在代码编辑器中输入以下代码,用于统计各类土地覆盖率的面积并显示在控制台窗口: ```javascript //计算土地覆盖率各类别的面积 var lc_area = lc_class.reduceRegions({ collection: chongqing, reducer: ee.Reducer.sum().group(0), scale: 500 }); //打印结果到控制台窗口 print(lc_area); ``` 6. 运行代码并等待结果输出,可以在控制台窗口中查看各类土地覆盖率的面积统计结果。 需要注意的是,Google Earth Engine的使用需要一定的编程基础和相关知识,如JavaScript、遥感影像处理等。同时,统计土地覆盖率面积需要选择合适的面积单位和计算方法,如平方米或平方公里等。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

此星光明

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值