<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>iXGIS Blog</title>
        <link>https://www.ixgis.com/fr/articles</link>
        <description>iXGIS Blog</description>
        <lastBuildDate>Tue, 21 Apr 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>fr</language>
        <item>
            <title><![CDATA[Writing Raster Calculator and Field Calculator Formulas with AI]]></title>
            <link>https://www.ixgis.com/fr/articles/ai-formula-for-raster-and-field-calculator</link>
            <guid>https://www.ixgis.com/fr/articles/ai-formula-for-raster-and-field-calculator</guid>
            <pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Learn how to use AI in iXGIS to draft Raster Calculator and Field Calculator formulas, including suitable use cases, prompt writing tips, review points, and practical examples.]]></description>
            <content:encoded><![CDATA[<p>Many users understand the calculation logic clearly when they first work with expressions, but run into problems as soon as they need to write the actual formula.</p>
<ul>
<li>Band numbers are easy to mistype.</li>
<li>Nested <code>where(...)</code> expressions make it easy to miss a parenthesis.</li>
<li>Once conditions become complex, it is hard to tell whether the logic has been reversed.</li>
<li>The desired result may be "population density", "risk level", or "elevation zone", but the business rule is clearer in your head than the formula syntax.</li>
</ul>
<p>The Raster Calculator and Field Calculator in iXGIS now support AI-assisted formula writing. In practical terms, you can describe the requirement in plain language first, then let AI turn it into an expression that can run in the current window.</p>
<p>This article focuses on three questions:</p>
<ol>
<li>Which scenarios are suitable for AI-generated formulas?</li>
<li>How can you write prompts that are more likely to produce correct results on the first try?</li>
<li>How do you use this workflow in the Raster Calculator, Field Calculator, and attribute table field calculation?</li>
</ol>
<h2 id="when-ai-formula-writing-is-useful">When AI Formula Writing Is Useful</h2>
<p>If the expression is as simple as <code>a + b</code>, writing it manually is usually faster.</p>
<p>AI saves the most time in cases like these:</p>
<ul>
<li>You know the business rule, but do not want to translate it into formula syntax by hand.</li>
<li>You need to write multi-level <code>where(...)</code> classification logic.</li>
<li>You need to handle several conditions at once and are worried about parentheses or operator precedence.</li>
<li>You already have a formula but want to rewrite it into a clearer multi-line structure.</li>
<li>You need to use area, length, bands, or null checks, which are easy to mix up.</li>
</ul>
<p>A simple rule is: once you start wondering whether you wrote something incorrectly, it is a good time to let AI draft a first version.</p>
<h2 id="how-to-use-ai-to-generate-formulas">How to Use AI to Generate Formulas</h2>
<h3 id="1-state-what-you-want-to-calculate">1. State What You Want to Calculate</h3>
<p>Do not only say "write a formula for me".</p>
<p>Better prompts include:</p>
<ul>
<li>"Calculate NDVI."</li>
<li>"Classify elevation into four classes."</li>
<li>"Calculate population density from population and area."</li>
<li>"Classify roads by length."</li>
</ul>
<h3 id="2-specify-the-fields-rasters-or-bands-to-use">2. Specify the Fields, Rasters, or Bands to Use</h3>
<p>The more specific you are, the better.</p>
<p>For example:</p>
<ul>
<li><code>image_a.tif.band4</code> and <code>image_a.tif.band3</code></li>
<li><code>Population</code> and <code>AREA</code></li>
<li><code>slope</code>, <code>rain</code></li>
</ul>
<p>If the names are vague or incorrect, the generated result is likely to be off as well.</p>
<h3 id="3-define-boundary-conditions-clearly">3. Define Boundary Conditions Clearly</h3>
<p>This is the part most likely to go wrong.</p>
<p>Instead of saying only "divide it into four classes", write something like:</p>
<pre><code class="language-text">Values less than or equal to 1610 are 1; values greater than 1610 and less than or equal to 2415 are 2; values greater than 2415 and less than or equal to 3468 are 3; all other values are 4.
</code></pre>
<p>This helps AI write complete interval boundaries and reduces overlaps or gaps.</p>
<h3 id="4-explain-how-null-values-should-be-handled">4. Explain How Null Values Should Be Handled</h3>
<p>This is important and often overlooked.</p>
<p>You can tell AI directly:</p>
<ul>
<li>"If any input is null, output null."</li>
<li>"Treat null values as 0."</li>
<li>"Output <code>nan</code> when the denominator is 0."</li>
</ul>
<p>If this is not stated clearly, the result may run successfully but have the wrong business meaning.</p>
<h2 id="using-ai-in-the-raster-calculator">Using AI in the Raster Calculator</h2>
<p>The Raster Calculator is suitable for cell-by-cell operations, such as indices, masks, reclassification, weighted overlay, and multi-band combinations.</p>
<p>Common use cases include:</p>
<ul>
<li>Remote sensing indices such as NDVI and NDBI</li>
<li>Threshold extraction from elevation, slope, rainfall, and similar rasters</li>
<li>Reclassification by value range</li>
<li>Combining multiple rasters into a weighted evaluation result</li>
</ul>
<p>You can load a template that already contains prepared data.</p>
<h3 id="example-1-ask-ai-to-write-ndvi">Example 1: Ask AI to Write NDVI</h3>
<p>You can say:</p>
<pre><code class="language-text">Use band4 and band2 from air-survey-multiband-raster-100m.tif to calculate NDVI.
</code></pre>
<p>AI will likely return a formula close to this:</p>
<pre><code class="language-python">result = (air-survey-multiband-raster-100m.tif.band4 - air-survey-multiband-raster-100m.tif.band2) / (air-survey-multiband-raster-100m.tif.band4 + air-survey-multiband-raster-100m.tif.band2)
</code></pre>
<p>With null-value handling:</p>
<pre><code class="language-python"># prompt
Use band4 and band2 from air-survey-multiband-raster-100m.tif to calculate NDVI. If the denominator is 0 or any input is null, output nan.
# formula
nir = air-survey-multiband-raster-100m.tif.band4
red = air-survey-multiband-raster-100m.tif.band2
num = nir - red
den = nir + red
result = where(logical_or(den == 0, logical_or(isnan(nir), isnan(red))), nan, num / den)
</code></pre>
<p>The advantage of this approach is that AI does not only write the formula; it also helps account for exceptional cases.</p>
<p>Note: Boolean functions cannot rely on default null handling. Null handling must be written explicitly.</p>
<h3 id="example-2-ask-ai-to-write-reclassification-logic">Example 2: Ask AI to Write Reclassification Logic</h3>
<pre><code class="language-text">Classify dem.tif into four classes: values less than or equal to 100 are 1; values greater than 100 and less than or equal to 500 are 2; values greater than 500 and less than or equal to 1500 are 3; all other values are 4. Keep null values as null.
</code></pre>
<p>Possible result:</p>
<pre><code class="language-text">result = where(isnan(dem.tif), nan, where(dem.tif &lt;= 100, 1, where(logical_and(dem.tif &gt; 100, dem.tif &lt;= 500), 2, where(logical_and(dem.tif &gt; 500, dem.tif &lt;= 1500), 3, 4))))
</code></pre>
<p>This is especially suitable for AI because nested <code>where</code> formulas are where people most often miss a parenthesis in the second or third layer.</p>
<h3 id="example-3-ask-ai-to-write-a-risk-mask">Example 3: Ask AI to Write a Risk Mask</h3>
<pre><code class="language-text">Generate a risk mask from slope.tif and rain.tif: cells with slope greater than 15 and rainfall greater than 500 should be 1; all other cells should be 0. If either input is null, output null.
</code></pre>
<p>Possible result:</p>
<pre><code class="language-text">result = where(logical_or(isnan(slope.tif), isnan(rain.tif)), nan, where(logical_and(slope.tif &gt; 15, rain.tif &gt; 500), 1, 0))
</code></pre>
<h2 id="using-ai-in-the-field-calculator">Using AI in the Field Calculator</h2>
<p>The Field Calculator focuses on attribute calculation. It is suitable for generating or updating field values in batches for vector features.</p>
<p>Common scenarios include:</p>
<ul>
<li>Calculating indicators such as population density, output density, and coverage rate</li>
<li>Generating level fields based on rules</li>
<li>Converting values with geometry keywords such as <code>AREA</code> and <code>LENGTH_GEODESIC</code></li>
<li>Calculating an intermediate field first, then deriving a second field from it</li>
</ul>
<h3 id="example-1-generate-a-population-density-field">Example 1: Generate a Population Density Field</h3>
<pre><code class="language-text">Add a density field and calculate population density as population divided by area.
</code></pre>
<p>Possible result:</p>
<pre><code class="language-text">density = Population / AREA_GEODESIC
</code></pre>
<p>Note: For vector data in a geographic coordinate system, use the geodesic area keyword <code>AREA_GEODESIC</code> to calculate each polygon's geodesic area. The unit is square meters.</p>
<h3 id="example-2-generate-two-fields-at-once">Example 2: Generate Two Fields at Once</h3>
<pre><code class="language-text">Set density = Population / Area, with the unit as people per square kilometer. Then add a density_level field: values less than or equal to 1000 are 'Low', values from 1000 to 3000 are 'Medium', and values greater than 3000 are 'High'.
</code></pre>
<p>Possible result:</p>
<pre><code class="language-text">density = Population * 1000000 / AREA_GEODESIC
density_level = where(density &lt;= 1000, 'Low', where(density &lt;= 3000, 'Medium', 'High'))
</code></pre>
<p>This kind of multi-step logic is well suited to AI because it can automatically split the calculation into more readable lines.</p>
<h3 id="example-3-convert-length-to-kilometers">Example 3: Convert Length to Kilometers</h3>
<pre><code class="language-text">Add a length_km field and calculate length in kilometers.
</code></pre>
<p>Possible result:</p>
<pre><code class="language-text">length_km = PERIMETER_LENGTH_GEODESIC / 1000
</code></pre>
<h2 id="calculate-field-in-the-attribute-table">Calculate Field in the Attribute Table</h2>
<p>In addition to the Field Calculator in the toolbox, the Calculate Field command in a vector layer's attribute table also works well with AI-assisted formula writing.</p>
<p>It is especially useful when:</p>
<ul>
<li>You have already opened the attribute table and want to add a business field immediately.</li>
<li>You do not want to switch away and open the toolbox.</li>
<li>You only need to run one attribute calculation on the current layer.</li>
</ul>
<p>For example, if you are in the attribute table and want to add a risk level field, you can describe it in natural language:</p>
<pre><code class="language-text">Add a risk_level field: when Population is greater than 700000 and Rainfall is greater than 700, set it to 'High'; when Population is greater than 600000 or Rainfall is greater than 600, set it to 'Medium'; otherwise set it to 'Low'.
</code></pre>
<p>AI may return:</p>
<pre><code class="language-text">risk_level = where(logical_and(Population &gt; 700000, Rainfall &gt; 700), 'High', where(logical_or(Population &gt; 600000, Rainfall &gt; 600), 'Medium', 'Low'))
</code></pre>
<p>When calculating fields in the attribute table, pay extra attention to two things:</p>
<ul>
<li>Field names must exactly match the current attribute table.</li>
<li>If area or length is involved, confirm that the current layer's coordinate system and geometry units match the business requirement.</li>
</ul>
<h2 id="human-review">Human Review</h2>
<p>AI can save a lot of repetitive typing, but it is not recommended to copy and run a formula without reading it. Keep a human in the loop.</p>
<p>At minimum, check the following:</p>
<ul>
<li>Whether raster names, band numbers, and field names are correct</li>
<li>Whether condition boundaries include the intended equality signs</li>
<li>Whether intervals overlap or leave gaps</li>
<li>Whether null values are handled as expected</li>
<li>Whether area and length use the correct geometry keywords</li>
<li>Whether output field names and result values match your naming and business rules</li>
</ul>
<p>For classification tasks in particular, review each class yourself even if the AI-generated formula looks smooth.</p>
<h2 id="tip">Tip</h2>
<p>If you already have a formula but it is hard to read, you can ask AI to rewrite it:</p>
<pre><code class="language-text">Rewrite the following one-line formula into a multi-line version that is easier to check, and give the intermediate variables clearer names.
</code></pre>
<p>This is usually more reliable than asking AI to generate everything from scratch, because you have already controlled the core logic. AI is only helping you organize the structure.</p>
<h2 id="related-articles">Related Articles</h2>
<ul>
<li><a href="https://www.ixgis.com/help/gis-toolbox/raster-box/raster-calculate/raster_calculator">Raster Calculator guide</a></li>
<li><a href="https://www.ixgis.com/help/gis-toolbox/vector-box/field/field_calculator">Calculate Field (Vector Calculator) guide</a></li>
<li><a href="https://www.ixgis.com/help/guide/vector-edit/field-calculate">Field calculation in the attribute table</a></li>
<li><a href="https://www.ixgis.com/help/guide/vector-edit/attribute-table-edit">Editing vector attribute tables</a></li>
</ul>]]></content:encoded>
            <author>sjzhakj@163.com (Xinyang)</author>
            <category>Raster</category>
            <category>Raster Data</category>
            <category>Vector Data</category>
        </item>
        <item>
            <title><![CDATA[Overview of iXGIS Data Download Tools and Data Resources]]></title>
            <link>https://www.ixgis.com/fr/articles/ixgis-data-download-tools-overview</link>
            <guid>https://www.ixgis.com/fr/articles/ixgis-data-download-tools-overview</guid>
            <pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[This article introduces the data download tools currently available in iXGIS, along with downloadable imagery, administrative boundary, land cover, soil, terrain, and climate datasets, helping users quickly decide which tool to use and what data can be downloaded.]]></description>
            <content:encoded><![CDATA[<p>In iXGIS, features directly related to downloading data are mainly located under <strong>Data Management Tools</strong> in the <strong>Analysis Toolbox</strong>. The three commonly used tools are:</p>
<ul>
<li>Satellite Imagery Download Tool</li>
<li>Surface Data Download Tool</li>
<li>Administrative Boundary Download Tool</li>
</ul>
<p>These three tools have clear roles: one downloads basemaps, one downloads thematic rasters, and one downloads administrative boundaries. Many users may find the names a little confusing at first, but in practice you can choose based on the result you want to obtain.</p>
<h2 id="tool-overview">Tool Overview</h2>
<table><thead><tr><th>Tool</th><th>Main Purpose</th><th>Output Type</th><th>Typical Data</th><th>Best For</th></tr></thead><tbody><tr><td>Satellite Imagery Download Tool</td><td>Downloads online map tiles and mosaics them</td><td>GeoTIFF raster</td><td>Tianditu imagery, vector basemap, terrain hillshade, global boundaries</td><td>Basemaps, archiving, offline browsing</td></tr><tr><td>Surface Data Download Tool</td><td>Downloads preconfigured base raster datasets</td><td>GeoTIFF raster</td><td>NDVI, land cover, soil, terrain, evapotranspiration, and more</td><td>Raster analysis, thematic mapping, indicator calculation</td></tr><tr><td>Administrative Boundary Download Tool</td><td>Downloads administrative boundaries</td><td>Vector file</td><td>Provincial, municipal, and county or district administrative boundaries</td><td>Clipping boundaries, zonal statistics, administrative unit preparation</td></tr></tbody></table>
<p>If you only want to create a background map, start with the Satellite Imagery Download Tool. If you need rasters that can be used directly in analysis, the Surface Data Download Tool is usually the right choice. If you need administrative boundary polygons, use the Administrative Boundary Download Tool.</p>
<h3 id="satellite-imagery-download-tool">Satellite Imagery Download Tool</h3>
<p>This tool essentially saves an online basemap as a local GeoTIFF. It does not download raw remote sensing data. Instead, it downloads already rendered online tiles and automatically mosaics them into an output file.</p>
<p>According to the current help documentation, the common layers in the interface are Tianditu-related layers:</p>
<ul>
<li>Vector basemap (without labels / with labels)</li>
<li>Imagery basemap (without labels / with labels)</li>
<li>Terrain hillshade</li>
<li>Global boundaries</li>
</ul>
<p>There are several points worth clarifying first:</p>
<ul>
<li>The download result is an RGB raster suitable for display, comparison, and map production, not editable vector features.</li>
<li>The tool works with Tianditu <code>TileMatrixSet = w</code>, which corresponds to Web Mercator <code>EPSG:3857</code>.</li>
<li>The larger the area and the higher the zoom level, the more tiles are required and the longer the download takes.</li>
</ul>
<p>This tool is therefore better suited for tasks such as:</p>
<ul>
<li>Preparing a stable offline basemap for a project</li>
<li>Comparing current project data with an online basemap</li>
<li>Preparing background imagery or road network labels before thematic map production</li>
</ul>
<p>Related article:</p>
<ul>
<li><a href="https://www.ixgis.com/help/gis-toolbox/data-management-box/data-download/satellite_imagery_download">Satellite Imagery Download Tool Guide</a></li>
</ul>
<h3 id="administrative-boundary-download-tool">Administrative Boundary Download Tool</h3>
<p>This tool retrieves boundary data from the Tianditu administrative region API and outputs a vector file. Unlike the basemap download tool above, it produces polygon features that can be used directly for clipping, statistics, or overlay analysis.</p>
<p>According to the current documentation, the tool supports step-by-step selection by administrative level:</p>
<ul>
<li>Province</li>
<li>City</li>
<li>County or district</li>
</ul>
<p>The output usually includes these fields:</p>
<ul>
<li><code>gb</code>: administrative division code</li>
<li><code>pgb</code>: parent administrative division code</li>
<li><code>name</code>: administrative region name</li>
<li><code>level</code>: administrative level</li>
<li><code>center_lng</code> / <code>center_lat</code>: center point coordinates</li>
</ul>
<p>The coordinate reference system is <code>EPSG:4490</code>, which is the CGCS2000 geographic coordinate system.</p>
<p>The three most common uses of this tool are:</p>
<ul>
<li>Quickly downloading administrative boundaries for a project area</li>
<li>Using the boundaries as raster clipping extents or statistical zones</li>
<li>Joining business tables by administrative region code</li>
</ul>
<p>Related article:</p>
<ul>
<li><a href="https://www.ixgis.com/help/gis-toolbox/data-management-box/data-download/tianditu_administrative_region_download">Administrative Boundary Download Tool Guide</a></li>
</ul>
<h3 id="surface-data-download-tool">Surface Data Download Tool</h3>
<p>This tool is the easiest one to misunderstand. "Surface data" here does not refer only to land surface data in the narrow sense. It is a unified download entry for a set of base raster datasets in the platform. Typically, you select a data type first, then choose a source, year, or version, and finally export a GeoTIFF by area.</p>
<p>Based on the current help documentation, several commonly used data categories have already been organized in this tool.</p>
<h2 id="downloadable-data">Downloadable Data</h2>
<h3 id="1-vegetation-index-data-ndvi">1. Vegetation Index Data: NDVI</h3>
<p>The documentation explicitly mentions annual NDVI data.</p>
<ul>
<li>Landsat 8 NDVI<!-- -->
<ul>
<li>Data source: Microsoft Planetary Computer <code>landsat-c2-l2</code></li>
<li>Platform filter: <code>landsat-8</code></li>
<li>Spatial resolution: 30 m</li>
<li>Result format: annual average NDVI</li>
</ul>
</li>
<li>Sentinel-2 NDVI<!-- -->
<ul>
<li>Data source: Microsoft Planetary Computer <code>sentinel-2-l2a</code></li>
<li>Spatial resolution: 10 m</li>
<li>Result format: annual average NDVI</li>
</ul>
</li>
</ul>
<p>This type of data is generally used for vegetation cover change, regional comparison, or preliminary assessment of ecological conditions.</p>
<h3 id="2-land-cover-data">2. Land Cover Data</h3>
<p>The land cover section is currently the most complete and already lists several common public data sources.</p>
<ul>
<li>ESA WorldCover<!-- -->
<ul>
<li>Resolution: 10 m</li>
<li>Coverage: global</li>
<li>Years: the current documentation lists 2020 and 2021</li>
<li>Characteristics: high resolution, suitable for interpreting current land cover conditions</li>
</ul>
</li>
<li>GlobeLand30<!-- -->
<ul>
<li>Resolution: 30 m</li>
<li>Years: 2000, 2010, 2020</li>
<li>Current platform note: downloads are currently available for China</li>
<li>Characteristics: a mature Chinese product system, suitable for domestic regional applications</li>
</ul>
</li>
<li>MODIS MCD12Q1<!-- -->
<ul>
<li>Resolution: approximately 500 m</li>
<li>Time range: annual series</li>
<li>Characteristics: long time span, suitable for long-term change analysis</li>
</ul>
</li>
</ul>
<p>If resolution is more important, WorldCover or GlobeLand30 is usually the first choice. If multi-year change matters more, MODIS is often easier to use.</p>
<p>For more information, see:</p>
<ul>
<li><a href="https://www.ixgis.com/blog/land-use-data-guide">Land Use Data Download and Usage Guide</a></li>
</ul>
<h3 id="3-soil-data">3. Soil Data</h3>
<p>The soil dataset explicitly mentioned in the current help documentation is <code>HWSD v2</code>. This type of data is generally not just a single-band result. Instead, it is organized by soil attribute and depth layer.</p>
<p>According to the documentation, common cases include:</p>
<ul>
<li>Downloadable parameters such as clay, sand, silt, organic carbon, and calcium carbonate</li>
<li>Typically 7 depth layers</li>
<li>Output is usually a multiband raster, with different bands corresponding to different soil layers</li>
</ul>
<p>This type of data is better suited for soil attribute analysis or as base input for ecological and agricultural environment topics.</p>
<h3 id="4-terrain-data">4. Terrain Data</h3>
<p>The current documentation lists two terrain datasets:</p>
<ul>
<li>ASTER GDEM v3</li>
<li>AW3D30 DSM</li>
</ul>
<p>Both are base elevation datasets. Common use cases include:</p>
<ul>
<li>Terrain analysis</li>
<li>Slope and aspect calculation</li>
<li>Hillshade analysis</li>
<li>Data preparation before hydrological analysis</li>
</ul>
<p>If you only need to prepare elevation data for a project area, this tool is much more convenient than downloading tiles manually and mosaicking them yourself.</p>
<h3 id="5-climate-and-meteorological-data">5. Climate and Meteorological Data</h3>
<p>The example given in the current help documentation is the MODIS annual evapotranspiration product:</p>
<ul>
<li>Example product: <code>MOD16A3GF.061</code></li>
<li>Example layer: <code>ET_500m</code></li>
<li>Resolution: approximately 500 m</li>
<li>Temporal resolution: annual</li>
</ul>
<p>This type of data is commonly used as background indicators in ecology, hydrology, or regional assessment.</p>
<h3 id="tianditu-administrative-regions">Tianditu Administrative Regions</h3>
<p>Administrative region vector data usually includes these fields:</p>
<ul>
<li><code>gb</code>: administrative division code</li>
<li><code>pgb</code>: parent administrative division code</li>
<li><code>name</code>: administrative region name</li>
<li><code>level</code>: administrative level</li>
<li><code>center_lng</code> / <code>center_lat</code>: center point coordinates</li>
</ul>
<p>The coordinate reference system is <code>EPSG:4490</code>, which is the CGCS2000 geographic coordinate system.</p>
<h2 id="what-to-check-before-use">What to Check Before Use</h2>
<p>Although the workflow has been simplified, it is still recommended to confirm the following points before using the data in a project:</p>
<ul>
<li>Whether you need a rendered basemap or an analysis-ready raster</li>
<li>Whether the data coordinate reference system matches the project CRS</li>
<li>Whether the resolution meets the business scale requirements</li>
<li>Whether the data coverage is global, China-wide, or limited to a local area</li>
<li>Whether the year and version meet the project's temporal requirements</li>
</ul>
<p>The simplest way to decide can be summarized in three sentences:</p>
<ul>
<li>For display basemaps, use the Satellite Imagery Download Tool.</li>
<li>For raster analysis, use the Surface Data Download Tool.</li>
<li>For administrative clipping and zonal statistics, download administrative boundaries first.</li>
</ul>
<p>Related documentation:</p>
<ul>
<li><a href="https://www.ixgis.com/help/gis-toolbox/data-management-box/data-download/satellite_imagery_download">Satellite Imagery Download Tool Guide</a></li>
<li><a href="https://www.ixgis.com/help/gis-toolbox/data-management-box/data-download/basic_raster_data_download">Surface Data Download Tool Guide</a></li>
<li><a href="https://www.ixgis.com/help/gis-toolbox/data-management-box/data-download/tianditu_administrative_region_download">Administrative Boundary Download Tool Guide</a></li>
</ul>]]></content:encoded>
            <author>sjzhakj@163.com (Xinyang)</author>
            <category>Data Download</category>
            <category>Tianditu</category>
            <category>Surface Data</category>
            <category>Administrative Boundaries</category>
            <category>Raster Data</category>
        </item>
        <item>
            <title><![CDATA[How to Search for POIs]]></title>
            <link>https://www.ixgis.com/fr/articles/poi-sou-suo</link>
            <guid>https://www.ixgis.com/fr/articles/poi-sou-suo</guid>
            <pubDate>Fri, 27 Mar 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Learn how to use POI Search in iXGIS, including search ranges, result display, map positioning, saving results, usage limits, and suitable scenarios based on the Tianditu place-name search service.]]></description>
            <content:encoded><![CDATA[<p>POI stands for Point of Interest. In GIS work, a POI is usually a place object with a name, location, and attributes, such as a school, hospital, park, station, shopping mall, scenic area, government office, or business park.</p>
<p>The POI Search feature in iXGIS is mainly used to retrieve these places within a specified spatial range and display the results directly on the map. The feature is implemented with reference to Tianditu's Place Name Search V2.0 service, so returned results usually include place name, address, longitude and latitude, phone number, and type. It is suitable for site selection research, facility surveys, thematic mapping, and basemap supplementation.</p>
<p>Compared with place search in ordinary web maps, POI Search in iXGIS focuses more on GIS workflows:</p>
<ul>
<li>You can limit the search range to the current view, an administrative region, or a project layer extent.</li>
<li>You can place results directly on the map to inspect their spatial distribution.</li>
<li>You can save selected results as point feature files in the project for further mapping and analysis.</li>
</ul>
<h2 id="1-what-poi-search-can-do">1. What POI Search Can Do</h2>
<p>POI Search is commonly used for four tasks:</p>
<ol>
<li>Quickly find a type of facility in the current map window, such as hospitals, schools, or bus stops.</li>
<li>Systematically retrieve facility distribution within an administrative region, such as parks, community service stations, or parking lots in a district.</li>
<li>Supplement point-of-interest data within the coverage of existing project layers, such as collecting nearby facilities around a planning area, sample area, or survey area.</li>
<li>Save search results as point features for later buffer analysis, overlay analysis, layout mapping, or attribute cleanup.</li>
</ol>
<p>If your goal is to find places and turn them into GIS data, this feature is a good fit. It can also be used directly if you only want to check a place temporarily.</p>
<h2 id="2-entry-point-and-basic-interface">2. Entry Point and Basic Interface</h2>
<p>Click POI Search in the iXGIS toolbar. A POI Search panel opens on the right side.</p>
<p>The panel usually contains three parts:</p>
<ul>
<li>A keyword input area at the top</li>
<li>A Search Options area in the middle</li>
<li>A result list and save controls at the bottom</li>
</ul>
<p>The top input box supports these operations:</p>
<ul>
<li>Press Enter after entering a keyword to search.</li>
<li>Click the search button to search.</li>
<li>Clear the keyword to clear both current results and POI points on the map.</li>
</ul>
<p>This means POI Search uses an explicit input and explicit search workflow, rather than continuously suggesting results while you type.</p>
<h2 id="3-what-to-check-before-searching">3. What to Check Before Searching</h2>
<p>Before using POI Search, confirm the following:</p>
<h3 id="1-a-project-must-be-open">1. A Project Must Be Open</h3>
<p>POI Search depends on the current project environment to manage map extent, result layers, and save paths. If no project is open, the system will not run the search.</p>
<h3 id="2-a-keyword-is-required">2. A Keyword Is Required</h3>
<p>POI Search is not a "browse all places" feature. It searches around a keyword. The keyword can be:</p>
<ul>
<li>A place name, such as "Beijing South Railway Station" or "Zhongshan Park"</li>
<li>A place category, such as "hospital", "school", or "hotel"</li>
<li>A business object, such as "charging station", "parking lot", or "gas station"</li>
</ul>
<p>In general, the more specific the keyword, the more focused the results. The broader the keyword, the more results you may get, and pagination and filtering may take more effort.</p>
<h3 id="3-results-come-from-an-online-service">3. Results Come from an Online Service</h3>
<p>This feature refers to the Tianditu place-name search service, so result quality depends on the online service's data coverage, classification methods, and naming conventions. Keep these points in mind:</p>
<ul>
<li>Names may include abbreviations, aliases, or duplicate names.</li>
<li>Fields such as phone number and address may be empty or incomplete.</li>
<li>Some newly built places or small POIs may not be found immediately.</li>
</ul>
<p>Therefore, POI Search is better used as a quick collection and supporting verification tool. For formal results that require strict review, manual verification is still recommended.</p>
<h2 id="4-choosing-among-three-search-ranges">4. Choosing Among Three Search Ranges</h2>
<p>iXGIS currently provides three search ranges:</p>
<ul>
<li>Current view</li>
<li>Administrative region</li>
<li>Layer extent</li>
</ul>
<p>Although Tianditu place-name search also supports nearby search and category search, the iXGIS interface currently focuses on these three ranges because they better match practical GIS project workflows.</p>
<h3 id="1-current-view">1. Current View</h3>
<p>Current View is suitable for quickly searching places within the current map window.</p>
<p>The workflow is simple:</p>
<ol>
<li>Zoom and pan the map to the target area.</li>
<li>Select Current View.</li>
<li>Enter a keyword and run the search.</li>
</ol>
<p>This method has these characteristics:</p>
<ul>
<li>The search range directly follows the map area visible on the screen.</li>
<li>The larger the map scale and the smaller the visible area, the more focused the results usually are.</li>
<li>It is suitable for finding facilities around a local parcel, block, or station.</li>
</ul>
<p>For example, after you have positioned the map to a district, entering "hospital" or "kindergarten" quickly shows the distribution of related facilities in the current visible area.</p>
<h3 id="2-administrative-region">2. Administrative Region</h3>
<p>Administrative Region is suitable for systematic searches by province, city, district, or county.</p>
<p>During operation, the system provides province, city, and district/county selections. It is usually best to select the most detailed available level so the search range is clearer and the results are easier to control.</p>
<p>This method is suitable for:</p>
<ul>
<li>Facility surveys such as schools, hospitals, and parks within a district</li>
<li>Sorting the distribution of a service facility type across a city</li>
<li>Preparing data before thematic statistics by administrative unit</li>
</ul>
<p>In administrative-region search mode, the system returns POI results and displays the corresponding administrative boundary on the map. This helps you confirm whether the search boundary is correct. For users who work by administrative boundary, this is very practical.</p>
<h3 id="3-layer-extent">3. Layer Extent</h3>
<p>Layer Extent is suitable for searching POIs around existing data extents in a project.</p>
<p>Here, layer extent means that you already have a survey area, planning area, study area, or data coverage layer in the project, and you want to find POIs near or within that range.</p>
<p>Common uses include:</p>
<ul>
<li>Select a polygon layer as the search range.</li>
<li>Select a raster layer as the search range.</li>
</ul>
<p>If you select a polygon layer and enable Use Geometry Extent Only, the system tries to search by the geometry boundary. This is usually more precise than using only the layer's bounding rectangle.</p>
<p>There are two practical limits to note:</p>
<ul>
<li>When a layer contains multiple geometries, this mode is currently better suited to searching around one main geometry.</li>
<li>When the geometry is very complex and has many vertices, the system may automatically switch to the layer's bounding extent to keep the search stable.</li>
</ul>
<p>If you select a raster layer, or do not enable Use Geometry Extent Only, the system generally searches by the overall layer extent. This is more stable in performance, but the spatial constraint is wider.</p>
<h2 id="5-what-information-appears-in-search-results">5. What Information Appears in Search Results</h2>
<p>POI search results usually include:</p>
<ul>
<li>Name</li>
<li>Address</li>
<li>Longitude and latitude</li>
<li>Phone number</li>
<li>Type</li>
</ul>
<p>These fields are useful for quick interpretation in GIS scenarios.</p>
<p>For example:</p>
<ul>
<li>Name helps you judge whether the result is the target object.</li>
<li>Address helps identify places with the same name.</li>
<li>Longitude and latitude help confirm whether the location is reasonable.</li>
<li>Type helps distinguish facility categories.</li>
<li>Phone number can be used as reference information for later investigation or verification.</li>
</ul>
<p>If some POIs do not have phone numbers, the system may show the field as empty or "None". This is normal and does not mean the search failed.</p>
<h2 id="6-how-results-are-displayed-on-the-map">6. How Results Are Displayed on the Map</h2>
<p>After the search is complete, results appear in the list and are loaded onto the map at the same time. Each result is displayed as a point, so users can judge its distribution spatially.</p>
<p>This display method has several direct benefits:</p>
<ul>
<li>You can quickly judge whether points fall inside the target area.</li>
<li>You can identify obvious offsets or same-name places in different locations.</li>
<li>You can combine basemaps, administrative boundaries, and business layers for integrated interpretation.</li>
</ul>
<p>When you click a record in the result list, the corresponding point is highlighted. This lets you switch quickly between reading the list and locating on the map, which is especially useful when there are many results.</p>
<h2 id="7-pagination-rules-and-result-limits">7. Pagination Rules and Result Limits</h2>
<p>To keep the interface responsive, POI Search currently uses paginated display.</p>
<ul>
<li>Each page shows 10 results.</li>
<li>When you switch pages, the system fetches the results for that page again.</li>
<li>The current interface displays up to the first 200 results.</li>
</ul>
<p>Therefore, if you search for common keywords such as "hospital", "school", or "residential community" in a large range, results may quickly hit the limit. In that case, optimize the search by:</p>
<ul>
<li>Narrowing the search range</li>
<li>Selecting a more detailed administrative region</li>
<li>Using a more specific keyword</li>
<li>Limiting the spatial range with a thematic layer before searching</li>
</ul>
<h2 id="8-saving-search-results-as-project-data">8. Saving Search Results as Project Data</h2>
<p>An important advantage of POI Search is that results can be saved, not just viewed.</p>
<p>In the result list, select one or more places, then click Add to File to save them as point feature data in the project.</p>
<h3 id="1-add-to-an-existing-file">1. Add to an Existing File</h3>
<p>If the project already contains a usable point layer, you can write selected results directly into that layer. This is suitable when:</p>
<ul>
<li>You have already created a collection layer for a facility type.</li>
<li>You want to merge POI results from multiple batches into the same file.</li>
<li>You need to edit symbols, fields, and attributes consistently later.</li>
</ul>
<p>After saving, POI information such as name, address, phone number, and type is written into the feature attributes for later cleanup.</p>
<h3 id="2-add-to-a-new-file">2. Add to a New File</h3>
<p>If the current project does not have a suitable target layer, you can create a new point file directly to save the results.</p>
<p>Currently supported save formats include:</p>
<ul>
<li>PostGIS vector</li>
<li>GeoPackage vector</li>
<li>ESRI Shapefile</li>
</ul>
<p>This method is better for thematic data collection, staged deliverable cleanup, or temporary working layer creation.</p>
<h3 id="3-what-you-can-do-after-saving">3. What You Can Do After Saving</h3>
<p>Once saved as a project layer, these POIs are no longer temporary search results; they become formal GIS data. You can continue with:</p>
<ul>
<li>Attribute checking and supplementation</li>
<li>Category-based symbolization</li>
<li>Buffer analysis</li>
<li>Overlay analysis with administrative regions, roads, land use, and other data</li>
<li>Layout mapping and output</li>
</ul>
<h2 id="9-why-administrative-boundaries-are-displayed">9. Why Administrative Boundaries Are Displayed</h2>
<p>In Administrative Region search mode, the system displays the selected administrative region boundary at the same time. This is not just visual decoration; it is a practical aid for judgment.</p>
<p>Its main purpose is to:</p>
<ul>
<li>Make the current search boundary clear.</li>
<li>Help compare whether result points are inside the target administrative region.</li>
<li>Support later screenshots, checks, and thematic interpretation.</li>
</ul>
<p>For users who often make district-level or city-level thematic maps, this boundary hint can greatly reduce misjudgment.</p>
<h2 id="10-recommended-usage-patterns">10. Recommended Usage Patterns</h2>
<p>For practical GIS work, use POI Search in these ways.</p>
<h3 id="scenario-1-quick-local-facility-survey">Scenario 1: Quick Local Facility Survey</h3>
<ul>
<li>Position the map to the target area.</li>
<li>Select Current View.</li>
<li>Enter keywords such as "hospital", "parking lot", or "bus stop".</li>
<li>Review the result distribution and select the points you need.</li>
<li>Save them as a project point layer.</li>
</ul>
<p>Suitable for existing-condition surveys, site selection review, and local infrastructure surveys.</p>
<h3 id="scenario-2-collect-thematic-points-by-administrative-region">Scenario 2: Collect Thematic Points by Administrative Region</h3>
<ul>
<li>Select Administrative Region.</li>
<li>Choose the target district or county level by level.</li>
<li>Enter the target keyword.</li>
<li>Check the results against the administrative boundary.</li>
<li>Save the results as a thematic layer.</li>
</ul>
<p>Suitable for public service facility organization, district/county thematic mapping, and industry distribution surveys.</p>
<h3 id="scenario-3-supplement-external-pois-around-a-project-area">Scenario 3: Supplement External POIs Around a Project Area</h3>
<ul>
<li>Prepare a study area, planning area, or sample area layer first.</li>
<li>Select Layer Extent.</li>
<li>If it is a polygon layer, preferably enable Use Geometry Extent Only.</li>
<li>Enter a keyword and run the search.</li>
<li>Save the results and analyze them together with project data.</li>
</ul>
<p>Suitable for planning research, environmental surveys, regional evaluation, and thematic sample-area analysis.</p>
<h2 id="11-common-misunderstandings">11. Common Misunderstandings</h2>
<h3 id="1-no-results-does-not-necessarily-mean-the-feature-failed">1. No Results Does Not Necessarily Mean the Feature Failed</h3>
<p>Possible reasons include:</p>
<ul>
<li>The keyword is too uncommon or uses a different naming convention.</li>
<li>The search range is too small.</li>
<li>The online service currently has no corresponding POI data.</li>
</ul>
<p>Try expanding the range or using a more common name or category keyword.</p>
<h3 id="2-layer-extent-search-may-not-always-follow-polygon-boundaries-exactly">2. Layer Extent Search May Not Always Follow Polygon Boundaries Exactly</h3>
<p>If the geometry is complex, or the selected layer is not a polygon layer, the system may search by the overall extent. For scenarios that require very precise spatial constraints, review and filter the mapped results manually.</p>
<h3 id="3-many-results-does-not-mean-all-results-are-usable">3. Many Results Does Not Mean All Results Are Usable</h3>
<p>POI Search is suitable for quick collection, but it cannot replace formal verification. For deliverables that need database entry, mapping, or statistics, check at least the following:</p>
<ul>
<li>Whether the name is accurate</li>
<li>Whether the location is offset</li>
<li>Whether the category matches the thematic requirement</li>
<li>Whether same-name points are duplicated</li>
</ul>
<h2 id="12-summary">12. Summary</h2>
<p>POI Search in iXGIS is essentially an online place collection feature for GIS workflows. Based on the Tianditu place-name search service, it combines finding places, placing them on the map, and saving them as features into a relatively complete workflow.</p>
<p>In short, the workflow has three steps:</p>
<ol>
<li>Choose a range.</li>
<li>Enter a keyword.</li>
<li>Review and save results.</li>
</ol>
<p>If you only want to locate places quickly, it can do that directly. If you want to turn external place information into GIS point data in your project, it can also meet that need. This is where POI Search is most valuable in GIS software.</p>]]></content:encoded>
            <author>sjzhakj@163.com (Xinyang)</author>
            <category>POI</category>
            <category>Search</category>
            <category>Place Names</category>
        </item>
        <item>
            <title><![CDATA[Locate]]></title>
            <link>https://www.ixgis.com/fr/articles/locate</link>
            <guid>https://www.ixgis.com/fr/articles/locate</guid>
            <pubDate>Wed, 25 Mar 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Learn how to use the Locate feature in iXGIS, including coordinate input methods, map picking, address display, usage limits, and how address information is sourced from the Tianditu reverse geocoding service.]]></description>
            <content:encoded><![CDATA[<p>In GIS work, "locating" usually means placing a known position on the map quickly and moving the map view near that position for viewing, checking, and follow-up operations.</p>
<p>The Locate feature in iXGIS is essentially a coordinate positioning tool. It lets you enter longitude and latitude coordinates, or pick a location directly on the map, then pans the map to the target point and displays the address information for that point.</p>
<p>This address information is not entered manually. It is retrieved with reference to the Tianditu reverse geocoding service. Reverse geocoding means converting a longitude and latitude coordinate into a readable address description, such as a city, district, road, and house number, or a location near a road or a certain distance northeast of a POI.</p>
<p>Therefore, the Locate feature in iXGIS does two things:</p>
<ul>
<li>Moves the map to a specified coordinate.</li>
<li>Converts the coordinate into a readable address to help users understand the current location.</li>
</ul>
<h2 id="1-when-to-use-locate">1. When to Use Locate</h2>
<p>Locate is most useful in these scenarios:</p>
<ol>
<li>You know a longitude and latitude coordinate and want to jump to the exact position on the map.</li>
<li>You want to check the approximate address or nearby features for a coordinate point.</li>
<li>You are organizing field records, monitoring points, sampling points, or issue points and need to inspect their locations quickly.</li>
<li>You need coordinate checking, manual comparison, or map browsing in a project.</li>
</ol>
<p>If your target is a clearly defined coordinate point, Locate is usually more direct than POI Search.</p>
<h2 id="2-how-to-open-locate">2. How to Open Locate</h2>
<p>Click Locate in the iXGIS toolbar to open the Coordinate Locate window.</p>
<p>When it opens, the system uses the current map center as the initial reference position and automatically displays that position's coordinates and address information. This is useful because:</p>
<ul>
<li>You can immediately see the approximate address of the current map center.</li>
<li>If you only need to adjust the current location slightly, you do not have to start from an empty form.</li>
<li>You can use the current map center as the starting point for a new locate operation.</li>
</ul>
<h2 id="3-supported-coordinate-input-methods">3. Supported Coordinate Input Methods</h2>
<p>Locate currently supports two input formats:</p>
<ul>
<li>Decimal degrees</li>
<li>Degrees, minutes, and seconds</li>
</ul>
<h3 id="1-decimal-degrees">1. Decimal Degrees</h3>
<p>This is the most common input method. Enter longitude and latitude as decimal degree values, for example:</p>
<ul>
<li>Longitude: 116.37304</li>
<li>Latitude: 39.92594</li>
</ul>
<p>This format is suitable for:</p>
<ul>
<li>Coordinates copied directly from GPS devices, web maps, or third-party platforms</li>
<li>Manual checks of standard longitude and latitude values in batch records</li>
<li>Daily positioning and quick comparison</li>
</ul>
<h3 id="2-degrees-minutes-and-seconds">2. Degrees, Minutes, and Seconds</h3>
<p>If your source material uses traditional degrees, minutes, and seconds, you can switch to that input mode, for example:</p>
<ul>
<li>116° 22′ 22.94″</li>
<li>39° 55′ 33.38″</li>
</ul>
<p>This format is common in:</p>
<ul>
<li>Field record sheets</li>
<li>Paper survey materials</li>
<li>Traditional surveying or investigation results</li>
</ul>
<p>In iXGIS, these two formats can be converted to each other. You do not need to convert them manually; just choose the correct input method.</p>
<admonition type="tip"><p>For coordinate input within China, longitude is generally east longitude and latitude is generally north latitude, so both values are usually positive.</p></admonition>
<h2 id="4-pick-a-point-on-the-map-instead-of-typing">4. Pick a Point on the Map Instead of Typing</h2>
<p>In addition to the input boxes, the Locate window provides a map pick button. After enabling it, you can click a position on the map and fill that point's coordinates back into the Locate window.</p>
<p>This is useful when:</p>
<ul>
<li>You want to roughly choose a position on the map first, then view its precise coordinates.</li>
<li>You need to check the center point of a known feature or an intersection.</li>
<li>You want to obtain coordinates through map interaction instead of manual entry.</li>
</ul>
<p>Note that clicking a point on the map mainly fills in the coordinates. If you want the map to formally jump to the point and refresh the address information, click the Locate button after picking the point.</p>
<h2 id="5-what-happens-after-you-click-locate">5. What Happens After You Click Locate</h2>
<p>After you finish entering coordinates and click Locate, the system performs these actions:</p>
<ol>
<li>Converts the entered longitude and latitude to the position required by the current map display.</li>
<li>Places a locate marker at the target position.</li>
<li>Pans the map view to that position.</li>
<li>Queries the corresponding address information and displays it next to the marker.</li>
</ol>
<p>This means Locate does more than move the map. It also tells you roughly where the point is.</p>
<p>From a user experience perspective, this matters for GIS users because a pair of longitude and latitude values is not intuitive on its own. A combination of coordinates and an address description is easier to judge and communicate.</p>
<h2 id="6-where-the-address-information-comes-from">6. Where the Address Information Comes From</h2>
<p>The address description in Locate uses the Tianditu reverse geocoding service.</p>
<p>Reverse geocoding can be understood as looking up an address from coordinates. The input is longitude and latitude, and the output is structured address information. According to the Tianditu reverse geocoding service, returned content usually includes:</p>
<ul>
<li>Detailed address</li>
<li>City or district/county</li>
<li>Nearest road</li>
<li>Nearest POI</li>
<li>Direction and distance relative to nearby roads or POIs</li>
</ul>
<p>In the current Locate feature in iXGIS, users most directly see the address name corresponding to the locate point. This address usually prefers a more complete address description; if the complete address is not clear enough, a shorter location description may be shown.</p>
<p>This feature can therefore tell you where the point is and help you decide whether it is the position you intended to find.</p>
<h2 id="7-how-to-interpret-locate-results">7. How to Interpret Locate Results</h2>
<p>When using locate results, treat them as "coordinate position plus address reference", not as an absolutely unique official street address.</p>
<p>This is because reverse geocoding is essentially semantic matching based on the environment around a coordinate. It may return:</p>
<ul>
<li>The nearest road name instead of a specific building name</li>
<li>A relative position near a POI</li>
<li>Slightly different address wording in the same area because datasets are updated at different times</li>
</ul>
<p>For GIS work, a better way to use the result is:</p>
<ul>
<li>Use the coordinate position as the primary reference.</li>
<li>Use the address text as supporting context.</li>
<li>If an exact street address is required in a formal deliverable, verify it manually.</li>
</ul>
<h2 id="8-common-uses">8. Common Uses</h2>
<h3 id="1-check-field-points">1. Check Field Points</h3>
<p>When you receive field sampling points, monitoring points, or inspection point coordinates, you can enter or paste them one by one to quickly check whether they fall in the correct area.</p>
<h3 id="2-verify-issue-locations">2. Verify Issue Locations</h3>
<p>For complaint points, disaster points, anomaly points, or facility issue points with known longitude and latitude, you can locate them first, inspect their surroundings, then judge the situation with basemaps and thematic layers.</p>
<h3 id="3-support-communication-and-reporting">3. Support Communication and Reporting</h3>
<p>Many non-GIS users are not sensitive to longitude and latitude, but they understand addresses. Displaying the address through Locate makes communication with business users, field staff, or managers easier.</p>
<h3 id="4-start-further-editing-or-analysis">4. Start Further Editing or Analysis</h3>
<p>After the map is positioned at the target point, you can continue zooming, take screenshots, measure, overlay thematic layers, or perform further spatial judgment.</p>
<h2 id="9-things-to-watch-for">9. Things to Watch For</h2>
<h3 id="1-the-input-is-longitude-and-latitude-not-projected-coordinates">1. The Input Is Longitude and Latitude, Not Projected Coordinates</h3>
<p>The values in the Locate window are longitude and latitude in degrees, not projected planar coordinates in meters. Do not paste X and Y values from a projected coordinate system directly into the window.</p>
<p>If your data is in projected coordinates, convert it to longitude and latitude before using Locate.</p>
<h3 id="2-check-signs-for-coordinates-outside-china">2. Check Signs for Coordinates Outside China</h3>
<p>Within China, most longitude and latitude values are positive. For west longitude or south latitude, pay special attention to the positive and negative signs.</p>
<h3 id="3-address-information-is-mainly-for-supporting-judgment">3. Address Information Is Mainly for Supporting Judgment</h3>
<p>Reverse geocoding returns an address description. It is not the same as a legally confirmed address. For formal reporting, database entry, or fine-grained management, manual verification is still recommended.</p>
<h3 id="4-map-picking-is-better-for-rough-positioning">4. Map Picking Is Better for Rough Positioning</h3>
<p>If you only click a position on the map with the mouse, accuracy is affected by the current scale and click position. For high-precision coordinate checks, enter accurate coordinate values directly.</p>
<h2 id="10-recommended-workflow">10. Recommended Workflow</h2>
<p>For daily work, use Locate in this order:</p>
<ol>
<li>Open the project and basemap.</li>
<li>Click Locate and check the current map center.</li>
<li>Choose Decimal Degrees or Degrees, Minutes, and Seconds.</li>
<li>Enter coordinates, or pick a point on the map first.</li>
<li>Click Locate.</li>
<li>Use the map marker and address information to judge whether the location is correct.</li>
<li>If needed, continue zooming, take screenshots, or perform further analysis.</li>
</ol>
<h2 id="11-summary">11. Summary</h2>
<p>The Locate feature in iXGIS is a coordinate positioning tool designed for practical GIS work. It combines coordinate input, map navigation, and address display so users can place a point on the map quickly and understand its approximate spatial meaning through reverse geocoding results.</p>
<p>In short, its core value is:</p>
<ul>
<li>Use coordinates to find a location accurately.</li>
<li>Use addresses to help read the location.</li>
</ul>
<p>For coordinate checks, field point organization, issue point review, and map browsing, this is a very useful basic feature.</p>]]></content:encoded>
            <author>sjzhakj@163.com (Xinyang)</author>
            <category>Locate</category>
            <category>Reverse Geocoding</category>
            <category>Coordinates</category>
        </item>
        <item>
            <title><![CDATA[How to Configure Hillshade]]></title>
            <link>https://www.ixgis.com/fr/articles/hillshade-settings</link>
            <guid>https://www.ixgis.com/fr/articles/hillshade-settings</guid>
            <pubDate>Thu, 16 Oct 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Hillshade is a common terrain visualization technique in GIS. It simulates terrain brightness under sunlight from a DEM so relief is easier to read. This post explains how to configure hillshade in iXGIS.]]></description>
            <content:encoded><![CDATA[<h2 id="what-is-hillshade">What Is Hillshade?</h2>
<p><strong>Hillshade</strong> is a common <strong>terrain visualization technique</strong> in geographic information systems (GIS). It uses a digital elevation model (DEM) to simulate the light and shadow produced by sunlight over terrain, making elevation changes easier to see.</p>
<h3 id="core-principle">Core Principle</h3>
<p>Hillshade applies a simplified lighting model to a DEM. For each pixel, the system estimates the local surface orientation from surrounding elevation changes, determines whether the surface faces toward or away from the light source, and then calculates brightness.</p>
<p>The calculation can be summarized as:</p>
<pre><code class="language-text">DEM (elevation raster)
-&gt; calculate local slope and aspect
-&gt; compute surface normal N
-&gt; compute light vector L from sun parameters
-&gt; calculate brightness I
-&gt; convert to grayscale Gray
</code></pre>
<p>The core brightness formula is:</p>
<span class="katex-display"><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML" display="block"><semantics><mrow><mi>I</mi><mo>=</mo><mi mathvariant="normal">clamp</mi><mo>⁡</mo><mo fence="false" stretchy="true" minsize="1.8em" maxsize="1.8em">(</mo><mi>max</mi><mo>⁡</mo><mo stretchy="false">(</mo><mn>0</mn><mo separator="true">,</mo><mtext> </mtext><mi>N</mi><mo>⋅</mo><mi>L</mi><mo stretchy="false">)</mo><mo>×</mo><mtext>LightIntensity</mtext><mo>+</mo><mtext>AmbientIntensity</mtext><mo separator="true">,</mo><mtext>&nbsp;</mtext><mn>0</mn><mo separator="true">,</mo><mtext>&nbsp;</mtext><mn>1</mn><mo fence="false" stretchy="true" minsize="1.8em" maxsize="1.8em">)</mo></mrow><annotation encoding="application/x-tex">I = \operatorname{clamp}\Big(\max(0,\,N \cdot L) \times \text{LightIntensity} + \text{AmbientIntensity},\ 0,\ 1\Big)</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.6833em"></span><span class="mord mathnormal" style="margin-right:0.07847em">I</span><span class="mspace" style="margin-right:0.2778em"></span><span class="mrel">=</span><span class="mspace" style="margin-right:0.2778em"></span></span><span class="base"><span class="strut" style="height:1.8em;vertical-align:-0.65em"></span><span class="mop"><span class="mord mathrm">clamp</span></span><span class="mspace" style="margin-right:0.1667em"></span><span class="mord"><span class="delimsizing size2">(</span></span><span class="mspace" style="margin-right:0.1667em"></span><span class="mop">max</span><span class="mopen">(</span><span class="mord">0</span><span class="mpunct">,</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mspace" style="margin-right:0.1667em"></span><span class="mord mathnormal" style="margin-right:0.10903em">N</span><span class="mspace" style="margin-right:0.2222em"></span><span class="mbin">⋅</span><span class="mspace" style="margin-right:0.2222em"></span></span><span class="base"><span class="strut" style="height:1em;vertical-align:-0.25em"></span><span class="mord mathnormal">L</span><span class="mclose">)</span><span class="mspace" style="margin-right:0.2222em"></span><span class="mbin">×</span><span class="mspace" style="margin-right:0.2222em"></span></span><span class="base"><span class="strut" style="height:0.8889em;vertical-align:-0.1944em"></span><span class="mord text"><span class="mord">LightIntensity</span></span><span class="mspace" style="margin-right:0.2222em"></span><span class="mbin">+</span><span class="mspace" style="margin-right:0.2222em"></span></span><span class="base"><span class="strut" style="height:1.8em;vertical-align:-0.65em"></span><span class="mord text"><span class="mord">AmbientIntensity</span></span><span class="mpunct">,</span><span class="mspace">&nbsp;</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mord">0</span><span class="mpunct">,</span><span class="mspace">&nbsp;</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mord">1</span><span class="mord"><span class="delimsizing size2">)</span></span></span></span></span></span>
<p>For an 8-bit grayscale output:</p>
<span class="katex-display"><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML" display="block"><semantics><mrow><mi>G</mi><mi>r</mi><mi>a</mi><mi>y</mi><mo>=</mo><mn>255</mn><mo>×</mo><mi>I</mi></mrow><annotation encoding="application/x-tex">Gray = 255 \times I</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.8778em;vertical-align:-0.1944em"></span><span class="mord mathnormal">G</span><span class="mord mathnormal" style="margin-right:0.02778em">r</span><span class="mord mathnormal">a</span><span class="mord mathnormal" style="margin-right:0.03588em">y</span><span class="mspace" style="margin-right:0.2778em"></span><span class="mrel">=</span><span class="mspace" style="margin-right:0.2778em"></span></span><span class="base"><span class="strut" style="height:0.7278em;vertical-align:-0.0833em"></span><span class="mord">255</span><span class="mspace" style="margin-right:0.2222em"></span><span class="mbin">×</span><span class="mspace" style="margin-right:0.2222em"></span></span><span class="base"><span class="strut" style="height:0.6833em"></span><span class="mord mathnormal" style="margin-right:0.07847em">I</span></span></span></span></span>
<h4 id="formula-terms">Formula Terms</h4>
<ul>
<li><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mi>N</mi></mrow><annotation encoding="application/x-tex">N</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.6833em"></span><span class="mord mathnormal" style="margin-right:0.10903em">N</span></span></span></span>: the unit normal vector of the terrain surface, representing slope orientation.</li>
<li><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mi>L</mi></mrow><annotation encoding="application/x-tex">L</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.6833em"></span><span class="mord mathnormal">L</span></span></span></span>: the unit light-direction vector, representing the incoming sunlight direction.</li>
<li><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mi>N</mi><mo>⋅</mo><mi>L</mi></mrow><annotation encoding="application/x-tex">N \cdot L</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.6833em"></span><span class="mord mathnormal" style="margin-right:0.10903em">N</span><span class="mspace" style="margin-right:0.2222em"></span><span class="mbin">⋅</span><span class="mspace" style="margin-right:0.2222em"></span></span><span class="base"><span class="strut" style="height:0.6833em"></span><span class="mord mathnormal">L</span></span></span></span>: the dot product, or cosine of the angle between the surface and the light; larger values mean the slope faces the light more directly.</li>
<li><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mi>max</mi><mo>⁡</mo><mo stretchy="false">(</mo><mn>0</mn><mo separator="true">,</mo><mi>N</mi><mo>⋅</mo><mi>L</mi><mo stretchy="false">)</mo></mrow><annotation encoding="application/x-tex">\max(0, N \cdot L)</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:1em;vertical-align:-0.25em"></span><span class="mop">max</span><span class="mopen">(</span><span class="mord">0</span><span class="mpunct">,</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mord mathnormal" style="margin-right:0.10903em">N</span><span class="mspace" style="margin-right:0.2222em"></span><span class="mbin">⋅</span><span class="mspace" style="margin-right:0.2222em"></span></span><span class="base"><span class="strut" style="height:1em;vertical-align:-0.25em"></span><span class="mord mathnormal">L</span><span class="mclose">)</span></span></span></span>: back-facing slopes may produce negative values, which are usually clipped to 0 to indicate no direct light.</li>
<li><code>LightIntensity</code>: direct-light intensity, used to control highlight contrast.</li>
<li><code>AmbientIntensity</code>: ambient-light intensity, used to preserve detail in shadowed areas and prevent them from becoming completely black.</li>
<li><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mi>I</mi></mrow><annotation encoding="application/x-tex">I</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.6833em"></span><span class="mord mathnormal" style="margin-right:0.07847em">I</span></span></span></span>: normalized brightness, usually in the range <span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mo stretchy="false">[</mo><mn>0</mn><mo separator="true">,</mo><mn>1</mn><mo stretchy="false">]</mo></mrow><annotation encoding="application/x-tex">[0,1]</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:1em;vertical-align:-0.25em"></span><span class="mopen">[</span><span class="mord">0</span><span class="mpunct">,</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mord">1</span><span class="mclose">]</span></span></span></span>.</li>
<li><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mi>G</mi><mi>r</mi><mi>a</mi><mi>y</mi></mrow><annotation encoding="application/x-tex">Gray</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.8778em;vertical-align:-0.1944em"></span><span class="mord mathnormal">G</span><span class="mord mathnormal" style="margin-right:0.02778em">r</span><span class="mord mathnormal">a</span><span class="mord mathnormal" style="margin-right:0.03588em">y</span></span></span></span>: final display grayscale value, usually in the range <span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mo stretchy="false">[</mo><mn>0</mn><mo separator="true">,</mo><mn>255</mn><mo stretchy="false">]</mo></mrow><annotation encoding="application/x-tex">[0,255]</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:1em;vertical-align:-0.25em"></span><span class="mopen">[</span><span class="mord">0</span><span class="mpunct">,</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mord">255</span><span class="mclose">]</span></span></span></span>.</li>
</ul>
<p>In simple terms:</p>
<ul>
<li><strong>Direct light</strong> determines where terrain is bright and how bright it is.</li>
<li><strong>Ambient light</strong> determines whether details remain visible in shadow.</li>
<li>Together they form the final hillshade effect.</li>
</ul>
<h3 id="parameter-overview">Parameter Overview</h3>
<p>The parameters can be grouped into three categories:</p>
<ol>
<li><strong>Where the light comes from</strong>: <code>LightDirection</code>, <code>ZenithAngle</code></li>
<li><strong>How strong the light and shadow are</strong>: <code>LightIntensity</code>, <code>AmbientIntensity</code></li>
<li><strong>How visible the terrain relief appears</strong>: <code>ElevationFactor</code>, <code>Extrusion</code></li>
</ol>
<h4 id="light-direction-azimuth-and-altitude">Light Direction: Azimuth and Altitude</h4>
<p>These two parameters define the light vector <span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mi>L</mi></mrow><annotation encoding="application/x-tex">L</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.6833em"></span><span class="mord mathnormal">L</span></span></span></span>:</p>
<span class="katex-display"><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML" display="block"><semantics><mrow><mi>L</mi><mo>=</mo><mo stretchy="false">(</mo><mi>sin</mi><mo>⁡</mo><msub><mi>A</mi><mi>z</mi></msub><mi>cos</mi><mo>⁡</mo><mi>Z</mi><mo separator="true">,</mo><mtext>&nbsp;</mtext><mi>cos</mi><mo>⁡</mo><msub><mi>A</mi><mi>z</mi></msub><mi>cos</mi><mo>⁡</mo><mi>Z</mi><mo separator="true">,</mo><mtext>&nbsp;</mtext><mi>sin</mi><mo>⁡</mo><mi>Z</mi><mo stretchy="false">)</mo></mrow><annotation encoding="application/x-tex">L = (\sin A_z \cos Z,\ \cos A_z \cos Z,\ \sin Z)</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.6833em"></span><span class="mord mathnormal">L</span><span class="mspace" style="margin-right:0.2778em"></span><span class="mrel">=</span><span class="mspace" style="margin-right:0.2778em"></span></span><span class="base"><span class="strut" style="height:1em;vertical-align:-0.25em"></span><span class="mopen">(</span><span class="mop">sin</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mord"><span class="mord mathnormal">A</span><span class="msupsub"><span class="vlist-t vlist-t2"><span class="vlist-r"><span class="vlist" style="height:0.1514em"><span style="top:-2.55em;margin-left:0em;margin-right:0.05em"><span class="pstrut" style="height:2.7em"></span><span class="sizing reset-size6 size3 mtight"><span class="mord mathnormal mtight" style="margin-right:0.04398em">z</span></span></span></span><span class="vlist-s">​</span></span><span class="vlist-r"><span class="vlist" style="height:0.15em"><span></span></span></span></span></span></span><span class="mspace" style="margin-right:0.1667em"></span><span class="mop">cos</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mord mathnormal" style="margin-right:0.07153em">Z</span><span class="mpunct">,</span><span class="mspace">&nbsp;</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mop">cos</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mord"><span class="mord mathnormal">A</span><span class="msupsub"><span class="vlist-t vlist-t2"><span class="vlist-r"><span class="vlist" style="height:0.1514em"><span style="top:-2.55em;margin-left:0em;margin-right:0.05em"><span class="pstrut" style="height:2.7em"></span><span class="sizing reset-size6 size3 mtight"><span class="mord mathnormal mtight" style="margin-right:0.04398em">z</span></span></span></span><span class="vlist-s">​</span></span><span class="vlist-r"><span class="vlist" style="height:0.15em"><span></span></span></span></span></span></span><span class="mspace" style="margin-right:0.1667em"></span><span class="mop">cos</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mord mathnormal" style="margin-right:0.07153em">Z</span><span class="mpunct">,</span><span class="mspace">&nbsp;</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mop">sin</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mord mathnormal" style="margin-right:0.07153em">Z</span><span class="mclose">)</span></span></span></span></span>
<p>Where:</p>
<ul>
<li><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><msub><mi>A</mi><mi>z</mi></msub></mrow><annotation encoding="application/x-tex">A_z</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.8333em;vertical-align:-0.15em"></span><span class="mord"><span class="mord mathnormal">A</span><span class="msupsub"><span class="vlist-t vlist-t2"><span class="vlist-r"><span class="vlist" style="height:0.1514em"><span style="top:-2.55em;margin-left:0em;margin-right:0.05em"><span class="pstrut" style="height:2.7em"></span><span class="sizing reset-size6 size3 mtight"><span class="mord mathnormal mtight" style="margin-right:0.04398em">z</span></span></span></span><span class="vlist-s">​</span></span><span class="vlist-r"><span class="vlist" style="height:0.15em"><span></span></span></span></span></span></span></span></span></span>: solar azimuth</li>
<li><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML"><semantics><mrow><mi>Z</mi></mrow><annotation encoding="application/x-tex">Z</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.6833em"></span><span class="mord mathnormal" style="margin-right:0.07153em">Z</span></span></span></span>: solar altitude</li>
</ul>
<p>In the parameter settings:</p>
<ul>
<li><strong>LightDirection (Azimuth)</strong>: the solar azimuth, indicating the direction from which light comes. For example, 315° means light from the northwest.</li>
<li><strong>ZenithAngle (Altitude)</strong>: this parameter actually represents solar altitude. Lower values produce longer shadows; higher values produce shorter shadows.</li>
</ul>
<p>Visual effects:</p>
<ul>
<li>Changing <code>LightDirection</code> mainly changes shadow direction.</li>
<li>Changing <code>ZenithAngle</code> mainly changes shadow length and perceived relief strength.</li>
</ul>
<h4 id="brightness-ambient-and-direct-light">Brightness: Ambient and Direct Light</h4>
<p>These parameters control the relationship between highlights and shadows:</p>
<span class="katex-display"><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML" display="block"><semantics><mrow><msub><mi>I</mi><mrow><mi>l</mi><mi>i</mi><mi>g</mi><mi>h</mi><mi>t</mi></mrow></msub><mo>=</mo><mi>max</mi><mo>⁡</mo><mo stretchy="false">(</mo><mn>0</mn><mo separator="true">,</mo><mi>N</mi><mo>⋅</mo><mi>L</mi><mo stretchy="false">)</mo><mo>×</mo><mtext>LightIntensity</mtext><mo>+</mo><mtext>AmbientIntensity</mtext></mrow><annotation encoding="application/x-tex">I_{light} = \max(0, N \cdot L) \times \text{LightIntensity} + \text{AmbientIntensity}</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.9694em;vertical-align:-0.2861em"></span><span class="mord"><span class="mord mathnormal" style="margin-right:0.07847em">I</span><span class="msupsub"><span class="vlist-t vlist-t2"><span class="vlist-r"><span class="vlist" style="height:0.3361em"><span style="top:-2.55em;margin-left:-0.0785em;margin-right:0.05em"><span class="pstrut" style="height:2.7em"></span><span class="sizing reset-size6 size3 mtight"><span class="mord mtight"><span class="mord mathnormal mtight" style="margin-right:0.01968em">l</span><span class="mord mathnormal mtight">i</span><span class="mord mathnormal mtight" style="margin-right:0.03588em">g</span><span class="mord mathnormal mtight">h</span><span class="mord mathnormal mtight">t</span></span></span></span></span><span class="vlist-s">​</span></span><span class="vlist-r"><span class="vlist" style="height:0.2861em"><span></span></span></span></span></span></span><span class="mspace" style="margin-right:0.2778em"></span><span class="mrel">=</span><span class="mspace" style="margin-right:0.2778em"></span></span><span class="base"><span class="strut" style="height:1em;vertical-align:-0.25em"></span><span class="mop">max</span><span class="mopen">(</span><span class="mord">0</span><span class="mpunct">,</span><span class="mspace" style="margin-right:0.1667em"></span><span class="mord mathnormal" style="margin-right:0.10903em">N</span><span class="mspace" style="margin-right:0.2222em"></span><span class="mbin">⋅</span><span class="mspace" style="margin-right:0.2222em"></span></span><span class="base"><span class="strut" style="height:1em;vertical-align:-0.25em"></span><span class="mord mathnormal">L</span><span class="mclose">)</span><span class="mspace" style="margin-right:0.2222em"></span><span class="mbin">×</span><span class="mspace" style="margin-right:0.2222em"></span></span><span class="base"><span class="strut" style="height:0.8889em;vertical-align:-0.1944em"></span><span class="mord text"><span class="mord">LightIntensity</span></span><span class="mspace" style="margin-right:0.2222em"></span><span class="mbin">+</span><span class="mspace" style="margin-right:0.2222em"></span></span><span class="base"><span class="strut" style="height:0.8889em;vertical-align:-0.1944em"></span><span class="mord text"><span class="mord">AmbientIntensity</span></span></span></span></span></span>
<ul>
<li><strong>LightIntensity</strong>: direct-light intensity. Higher values make light-facing slopes brighter and increase contrast.</li>
<li><strong>AmbientIntensity</strong>: ambient-light intensity. Higher values soften shadows and preserve shadow detail.</li>
</ul>
<p>Adjustment guidance:</p>
<ul>
<li>To emphasize relief, increase <code>LightIntensity</code> and moderately lower <code>AmbientIntensity</code>.</li>
<li>To preserve shadow detail, increase <code>AmbientIntensity</code>.</li>
</ul>
<h4 id="geometric-scale-elevation-to-planar-conversion">Geometric Scale: Elevation-to-Planar Conversion</h4>
<p><strong>ElevationFactor</strong> handles differences between elevation units and horizontal coordinate units.</p>
<p>Examples:</p>
<ul>
<li>If both horizontal coordinates and elevation are in meters, it is usually set to 1.</li>
<li>If horizontal coordinates are longitude/latitude degrees and elevation is in meters, a conversion factor is required; otherwise slope calculations will be distorted.</li>
</ul>
<p>This parameter controls whether the calculated slope orientation is geometrically realistic. If it is set incorrectly, terrain may look flattened or exaggerated.</p>
<h4 id="visual-exaggeration-extrusion">Visual Exaggeration: Extrusion</h4>
<p><strong>Extrusion</strong> is a visual terrain-exaggeration factor used to strengthen relief expression.</p>
<p>In the calculation, it can be understood as:</p>
<span class="katex-display"><span class="katex"><span class="katex-mathml"><math xmlns="http://www.w3.org/1998/Math/MathML" display="block"><semantics><mrow><msup><mi>Z</mi><mo mathvariant="normal" lspace="0em" rspace="0em">′</mo></msup><mo>=</mo><mi>Z</mi><mo>×</mo><mtext>ElevationFactor</mtext><mo>×</mo><mtext>Extrusion</mtext></mrow><annotation encoding="application/x-tex">Z' = Z \times \text{ElevationFactor} \times \text{Extrusion}</annotation></semantics></math></span><span class="katex-html" aria-hidden="true"><span class="base"><span class="strut" style="height:0.8019em"></span><span class="mord"><span class="mord mathnormal" style="margin-right:0.07153em">Z</span><span class="msupsub"><span class="vlist-t"><span class="vlist-r"><span class="vlist" style="height:0.8019em"><span style="top:-3.113em;margin-right:0.05em"><span class="pstrut" style="height:2.7em"></span><span class="sizing reset-size6 size3 mtight"><span class="mord mtight"><span class="mord mtight">′</span></span></span></span></span></span></span></span></span><span class="mspace" style="margin-right:0.2778em"></span><span class="mrel">=</span><span class="mspace" style="margin-right:0.2778em"></span></span><span class="base"><span class="strut" style="height:0.7667em;vertical-align:-0.0833em"></span><span class="mord mathnormal" style="margin-right:0.07153em">Z</span><span class="mspace" style="margin-right:0.2222em"></span><span class="mbin">×</span><span class="mspace" style="margin-right:0.2222em"></span></span><span class="base"><span class="strut" style="height:0.7778em;vertical-align:-0.0833em"></span><span class="mord text"><span class="mord">ElevationFactor</span></span><span class="mspace" style="margin-right:0.2222em"></span><span class="mbin">×</span><span class="mspace" style="margin-right:0.2222em"></span></span><span class="base"><span class="strut" style="height:0.6833em"></span><span class="mord text"><span class="mord">Extrusion</span></span></span></span></span></span>
<p>The two parameters have different roles:</p>
<ul>
<li><code>ElevationFactor</code> handles unit conversion.</li>
<li><code>Extrusion</code> handles visual exaggeration.</li>
</ul>
<p>Therefore:</p>
<ul>
<li><code>ElevationFactor</code> determines whether the calculation is realistic.</li>
<li><code>Extrusion</code> determines whether the visual relief is strong enough.</li>
</ul>
<p>As a rule of thumb:</p>
<ul>
<li>For small-scale maps or coarse-resolution DEMs, increase <code>Extrusion</code> moderately, for example to 5-8, to enhance relief.</li>
<li>For high-resolution DEMs such as 10 m data, 1-2 is usually enough.</li>
</ul>
<h4 id="parameter-summary">Parameter Summary</h4>
<div class="xg-table-scroll"><table class="xg-rich-table"><thead><tr><th>Parameter</th><th>Name</th><th>Common Values*</th><th>Mechanism</th><th>Effect and Recommendations</th></tr></thead><tbody><tr><td><code>LightDirection</code></td><td>Solar azimuth (°, clockwise from north)</td><td>0-360 (default 315° = northwest)</td><td>Controls the incoming light direction and directly determines shadow direction.</td><td><ul><li>Morning: 90° (east).</li><li>Noon from the south: 180°.</li><li>Common northwest lighting uses 315°, often useful for emphasizing south-facing slopes.</li></ul></td></tr><tr><td><code>ZenithAngle</code></td><td>Solar altitude (°, 0 = horizon, 90 = overhead)</td><td>0-90 (default 45°)</td><td>Controls the light angle relative to the ground, determining shadow length and relief strength.</td><td><ul><li>Low angle (10°): long shadows and strong relief, but valleys may become too dark.</li><li>High angle (above 60°): shorter shadows and a softer overall effect.</li></ul></td></tr><tr><td><code>LightIntensity</code></td><td>Direct-light intensity</td><td>0-1 (default 0.7-1.0)</td><td>Lambertian coefficient; higher values increase light-dark contrast.</td><td><ul><li>Focus on its ratio to <code>AmbientIntensity</code>.</li><li>Usually <code>LightIntensity + AmbientIntensity</code> is about 1.</li><li>To emphasize ridges, increase it to about 1.2 and reduce ambient light.</li></ul></td></tr><tr><td><code>AmbientIntensity</code></td><td>Ambient-light intensity</td><td>0-1 (default 0.6-0.9)</td><td>Adds non-directional soft light to shaded areas so they do not become fully black.</td><td><ul><li>Useful for improving visibility in dark areas.</li><li>Too high makes shadows gray and reduces relief.</li><li>Too low makes contrast too strong and loses detail.</li><li>For a sunset side-light effect, lower it to about 0.3.</li></ul></td></tr><tr><td><code>ElevationFactor</code></td><td>Elevation factor / elevation-to-planar conversion factor</td><td><ul><li>Longitude/latitude DEM: about 1 / 111 km.</li><li>Horizontal and elevation units both in meters: 1.</li></ul></td><td>Converts Z elevation into the same dimensional scale as X/Y to avoid distorted normal-vector calculations.</td><td><ul><li>For Web Mercator / UTM with DEM elevation also in meters, use 1.</li><li>For longitude/latitude (°) plus elevation (m), multiply by about 0.000009.</li></ul></td></tr><tr><td><code>Extrusion</code></td><td>Exaggeration factor</td><td>0-10 (default 1-5)</td><td>Works with <code>ElevationFactor</code> to exaggerate terrain relief.</td><td><ul><li>Higher values make peaks sharper and valleys deeper.</li><li>0 means a completely flat hillshade effect.</li><li>10 m DEMs often use 1-2; 90 m DEMs can use 5-8.</li></ul></td></tr></tbody></table></div>
<h4 id="four-preset-effects">Four Preset Effects</h4>
<p>For easier use, iXGIS provides four preset modes.</p>
<div class="xg-table-scroll"><table class="xg-rich-table xg-rich-table--compact"><thead><tr><th>Preset</th><th>LightDirection</th><th>ZenithAngle</th><th>LightIntensity</th><th>AmbientIntensity</th><th>Extrusion*</th><th>Use Case</th></tr></thead><tbody><tr><td>Morning Light</td><td>90° (east)</td><td>20-30°</td><td>0.85</td><td>0.4</td><td>2</td><td>Long shadows and strong contrast, emphasizing westward ridge shadows and a dawn atmosphere.</td></tr><tr><td>Noon</td><td>180° (south)</td><td>70-80°</td><td>0.6</td><td>0.55</td><td>1.5</td><td>Shortest shadows and soft relief; suitable as a basemap without dominating the view.</td></tr><tr><td>Sunset</td><td>270° (west)</td><td>15-25°</td><td>0.9</td><td>0.35</td><td>2</td><td>Opposite of morning light, creating a sunset effect with longer eastward valley shadows.</td></tr><tr><td>Night Light</td><td>315° (northwest)</td><td>60°</td><td>0.3</td><td>0.7</td><td>1.5</td><td>Weak direct light and stronger ambient light, suitable for dark basemaps or night-style maps.</td></tr></tbody></table></div>
<h3 id="configure-hillshade">Configure Hillshade</h3>
<p>When using classified coloring for raster data, hillshade can be enabled. The global land-and-sea terrain raster is used here as an example.</p>
<p>The four effects are, in order: Morning Light, Noon, Sunset, and Night Light.</p>]]></content:encoded>
            <author>sjzhakj@163.com (Xinyang)</author>
            <category>Raster</category>
        </item>
        <item>
            <title><![CDATA[Terrain Data Download and Usage Guide]]></title>
            <link>https://www.ixgis.com/fr/articles/terrain-data-guide</link>
            <guid>https://www.ixgis.com/fr/articles/terrain-data-guide</guid>
            <pubDate>Sat, 20 Sep 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[This article introduces commonly used global terrain datasets, their sources, download methods, and how to download and use terrain data in iXGIS.]]></description>
            <content:encoded><![CDATA[<p><strong>Terrain / elevation data</strong> describes the elevation form of the Earth's surface. It is usually expressed in meters together with horizontal coordinates, such as longitude/latitude or projected coordinates.</p>
<p><strong>Concepts</strong></p>
<ul>
<li><strong>DEM (Digital Elevation Model)</strong>: a general raster elevation model; depending on context, it may or may not distinguish terrain from surface objects.</li>
<li><strong>DTM (Digital Terrain Model)</strong>: <strong>bare-earth elevation</strong>, with tree canopy and buildings removed.</li>
<li><strong>DSM (Digital Surface Model)</strong>: <strong>surface elevation</strong>, including the highest surfaces such as tree canopy and buildings.</li>
</ul>
<p><strong>Data forms and formats</strong></p>
<ul>
<li><strong>Raster</strong>: the most common form, including GeoTIFF, Cloud-Optimized GeoTIFF, and BIL; pixel value = elevation.</li>
<li><strong>Point cloud</strong>: LAS/LAZ data from LiDAR or photogrammetry; can be used to derive DSM/DTM.</li>
<li><strong>Contours / TIN</strong>: vector contours or triangulated irregular networks for cartography or local modeling.</li>
</ul>
<p><strong>Typical sources</strong></p>
<ul>
<li><strong>Satellite / radar</strong>: SRTM, NASADEM, ASTER GDEM, ALOS AW3D, Copernicus DEM (GLO-30/90), and partly public TanDEM-X.</li>
<li><strong>Aerial survey / UAV photogrammetry (SfM)</strong>: generates dense point clouds and DSM/DTM.</li>
<li><strong>Airborne / terrestrial LiDAR</strong>: high accuracy and high resolution, commonly used in urban and engineering applications.</li>
<li><strong>Bathymetry</strong>: GEBCO, EMODnet, and national hydrographic surveys; often merged with land DEMs into integrated land-and-sea terrain products such as ETOPO.</li>
</ul>
<h2 id="china-terrain-data">China Terrain Data</h2>
<h3 id="introduction">Introduction</h3>
<p>A DEM represents ground relief using elevation values at regular grid points.</p>
<p>DEM data can be used to extract many terrain and geomorphology derivatives, including slope, aspect, drainage networks, 3D models, visibility analysis, and mobile-phone base-station analysis. DEMs are also used for quantitative analysis of terrain characteristics and to support planning and construction.</p>
<p><a href="https://www.webmap.cn/commres.do?method=jump5&amp;pageFlag=DEM">DEM product introduction from the National Geographic Information Resource Catalog Service System</a></p>
<p>The source lists typical DEM-related uses:</p>
<ul>
<li><strong>Slope</strong>: Slope describes the steepness of a surface unit. Slope values can be used to classify landforms, such as plains, hills, and mountains.</li>
<li><strong>Aspect</strong>: Aspect is the direction of the projection of a slope normal on the horizontal plane; more simply, it is the downslope direction. Aspect can support analysis of shaded and sunny slopes, crop and vegetation light preferences, crop zoning, and selecting suitable slopes for returning farmland to forest.</li>
<li><strong>Site-selection planning analysis</strong>: By combining slope, aspect, and basic geographic information layers, overlay analysis can be applied in different industries. For example, urban construction usually needs flatter terrain.</li>
<li><strong>Hydrological analysis</strong>: DEMs can be used with fill-and-cut calculations to extract river networks and delineate watersheds.</li>
<li><strong>Viewshed analysis</strong>: DEM-based viewshed analysis divides the landscape into visible and invisible areas because terrain can block line of sight.</li>
</ul>
<p>Main data products:</p>
<ul>
<li>1:1,000,000 scale, corresponding to 400 m grid spacing.</li>
<li>1:250,000 scale, corresponding to 100 m grid spacing.</li>
<li>1:50,000 scale, corresponding to 25 m and 10 m grid spacing.</li>
</ul>
<h3 id="download">Download</h3>
<p>After opening the page above, the right side lists digital elevation model data at different map scales. At present, however, the data is temporarily unavailable for download.</p>
<h3 id="coordinate-system-and-vertical-datum">Coordinate System and Vertical Datum</h3>
<p>This terrain data uses the China Geodetic Coordinate System 2000 and the 1985 National Height Datum.</p>
<p>The Yellow Sea height system and the 1985 National Height Datum: In 1956, China defined the long-term mean sea level of the Yellow Sea at Qingdao as the unified datum, called the <strong>1956 Yellow Sea Height System</strong>. It was China's first national height system and ended the previous coexistence of many height systems. Because the Qingdao tide-gauge data series used for that datum (1950-1956) was short, China's surveying and mapping authority recalculated the Yellow Sea mean sea level using Qingdao tide observations from 1952 to 1979. This became the <strong>1985 National Height Datum</strong>. Precise leveling was used at the national leveling origin in Qingdao, establishing the relationship: 1985 National Height Datum elevation = 1956 Yellow Sea elevation - 0.029 m. The 1985 datum was adopted in May 1987, and the 1956 Yellow Sea system was abolished. The 1956 leveling origin elevation was 72.289 m, and the 1985 leveling origin elevation is 72.260 m. Conventionally, the new datum is said to be 0.029 m lower than the old one. Source: <a href="https://snsm.mnr.gov.cn/Information/news/24024">National height system description</a></p>
<p>The 1985 National Height Datum is China's statutory national unified height system, based on the mean sea surface of the Yellow Sea and used as the standard for measuring ground elevation nationwide. Key points:</p>
<ol>
<li><strong>Definition and concepts</strong></li>
</ol>
<ul>
<li><strong>Datum surface</strong>: the Yellow Sea mean sea level calculated from 28 years of Qingdao tide-gauge data from 1952 to 1979.</li>
<li><strong>Leveling origin</strong>: the national leveling origin of the People's Republic of China at Guanxiang Mountain, Qingdao, with an elevation of <strong>72.260 m</strong> above the 1985 datum.</li>
</ul>
<ol start="2">
<li><strong>Technical principle</strong></li>
</ol>
<ul>
<li><strong>Data improvement</strong>: compared with the 1956 Yellow Sea system, which used only 1950-1956 data, the 1985 datum uses a longer tide record and sliding-average calculations to reduce short-term sea-level fluctuation error.</li>
<li><strong>Conversion</strong>: 1985 datum elevation = 1956 Yellow Sea elevation - 0.029 m. For example, a point at 100 m in the 1956 system is 99.971 m in the 1985 system.</li>
</ul>
<ol start="3">
<li><strong>History</strong></li>
</ol>
<ul>
<li><strong>Replacement of the old system</strong>: the 1985 datum was officially adopted in May 1987 with State Council approval, replacing the 1956 Yellow Sea Height System.</li>
<li><strong>Naming significance</strong>: although still based on the Yellow Sea, the name emphasizes national authority and avoids confusion with local height systems.</li>
</ul>
<ol start="4">
<li><strong>Applications</strong></li>
</ol>
<ul>
<li><strong>Engineering and surveying</strong>: widely used in topographic mapping, construction projects such as bridges and dams, airport obstacle-control surfaces, and related fields.</li>
<li><strong>Relationship to other systems</strong>: Wusong elevation = 1956 Yellow Sea elevation + 1.688 m; Pearl River elevation = 1956 Yellow Sea elevation - 0.586 m. Unified conversions are required for compatibility.</li>
</ul>
<ol start="5">
<li><strong>Current status</strong></li>
</ol>
<p>As China's only statutory national height datum, it must be used in national surveying projects, map production, and land planning. Its parameters are governed by <a href="https://openstd.samr.gov.cn/bzgk/gb/newGbInfo?hcno=28920745EFD7B0781E0B1F6DEF97E15A">Specifications for the basic techniques of national geodesy (GB 22021-2008)</a>.</p>
<h2 id="global-terrain-datasets">Global Terrain Datasets</h2>
<p><strong>Global terrain data</strong> digitally describes elevation for the whole Earth, either land-only or integrated land-and-sea. It is usually released as regular grids (raster DEM/DSM/DTM) or vector contour surfaces, representing <strong>the elevation or water depth at a location</strong> and supporting derivatives such as slope, aspect, viewshed, and hillshade.</p>
<table><thead><tr><th>Concept</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>DEM</strong> (Digital Elevation Model)</td><td>General elevation raster; may include vegetation and buildings depending on source.</td></tr><tr><td><strong>DSM</strong> (Digital Surface Model)</td><td>Surface model that keeps trees, buildings, ice sheets, and other surface objects.</td></tr><tr><td><strong>DTM</strong> / Bare-earth</td><td>Bare-earth model with non-terrain objects removed; suitable for hydrology, flood, and geomorphology analysis.</td></tr><tr><td><strong>Bathymetry</strong></td><td>Seafloor depth, usually negative elevation; can be merged with land DEMs into land-and-sea grids.</td></tr></tbody></table>
<p>Note: terrain data should be distinguished from land cover data.</p>
<p>Main data sources:</p>
<table><thead><tr><th>Method</th><th>Representative Datasets</th><th>Resolution</th><th>Characteristics</th></tr></thead><tbody><tr><td><strong>Synthetic Aperture Radar (SAR) interferometry</strong></td><td>SRTM 1″/3″, TanDEM-X 12 m/90 m</td><td>12-90 m</td><td>Works under clouds and rain; partially penetrates vegetation.</td></tr><tr><td><strong>Optical stereo photogrammetry</strong></td><td>ASTER GDEM, ALOS AW3D30</td><td>30 m</td><td>Covers 83°N-83°S; cloud/snow areas may have gaps.</td></tr><tr><td><strong>Optical-laser fusion + post-processing</strong></td><td>Copernicus DEM GLO-30/90, FABDEM</td><td>30-90 m</td><td>Among the highest-quality public global products; FABDEM removes vegetation/buildings.</td></tr><tr><td><strong>Laser altimetry / ice-penetrating radar</strong></td><td>ICESat-2 correction, BedMachine</td><td>Regional 2-15 m</td><td>Improves polar and ice-sheet areas.</td></tr><tr><td><strong>Multibeam and gravity-derived bathymetry</strong></td><td>GEBCO, SRTM15+</td><td>15″ (~450 m)</td><td>Seafloor relief, merged with land DEMs.</td></tr><tr><td><strong>Crowdsourcing / map fusion (OSM)</strong></td><td>MERIT DEM, EarthEnv-DEM90</td><td>90 m</td><td>Multi-source fusion and error correction; hydrologically consistent versions exist.</td></tr></tbody></table>
<h3 id="available-datasets">Available Datasets</h3>
<table><thead><tr><th>Dataset</th><th>Spatial Resolution at Equator</th><th>Type</th><th>Coverage</th><th>Latest Version</th><th>License and Access</th></tr></thead><tbody><tr><td><strong>Copernicus DEM GLO-30 / GLO-90</strong></td><td>30 m / 90 m</td><td>DSM</td><td>Global land, including polar regions; 30 m is not fully public in some countries</td><td>DGED 2023_1</td><td>Free registration (<a href="https://dataspace.copernicus.eu/explore-data/data-collections/copernicus-contributing-missions/collections-description/COP-DEM?utm_source=chatgpt.com">Copernicus Data Space Ecosystem</a>, <a href="https://portal.opentopography.org/datasetMetadata?otCollectionID=OT.032021.4326.1&amp;utm_source=chatgpt.com">portal.opentopography.org</a>)</td></tr><tr><td><strong>FABDEM</strong></td><td>30 m</td><td>DTM, trees/buildings removed</td><td>Global land</td><td>2022+</td><td>Free academic version / commercial FABDEM+ (<a href="https://www.fathom.global/product/global-terrain-data-fabdem/?utm_source=chatgpt.com">fathom.global</a>)</td></tr><tr><td><strong>ALOS World 3D-30 m (AW3D30)</strong></td><td>30 m</td><td>DSM</td><td>Global land, with gaps in cloudy/snowy areas</td><td>v3.2 (2023)</td><td>Public and free (<a href="https://www.eorc.jaxa.jp/ALOS/en/dataset/aw3d30/aw3d30_e.htm?utm_source=chatgpt.com">eorc.jaxa.jp</a>)</td></tr><tr><td><strong>ASTER GDEM v3</strong></td><td>30 m</td><td>DSM</td><td>83°N-83°S, about 99% of land</td><td>2019</td><td>Public and free (<a href="https://asterweb.jpl.nasa.gov/gdem.asp?utm_source=chatgpt.com">asterweb.jpl.nasa.gov</a>)</td></tr><tr><td><strong>TanDEM-X</strong></td><td>12 m commercial / 90 m public</td><td>DSM</td><td>Global land</td><td>90 m version 2023</td><td>90 m free, 12 m licensed (<a href="https://geoservice.dlr.de/web/datasets/tdm90_dem?utm_source=chatgpt.com">geoservice.dlr.de</a>)</td></tr><tr><td><strong>NASADEM / SRTM V3</strong></td><td>30 m (1″) / 90 m (3″)</td><td>DSM</td><td>60°N-56°S, about 80% of land</td><td>2020</td><td>Public and free (<a href="https://portal.opentopography.org/datasetMetadata?otCollectionID=OT.032021.4326.2&amp;utm_source=chatgpt.com">portal.opentopography.org</a>, <a href="https://www.usgs.gov/centers/eros/science/usgs-eros-archive-digital-elevation-shuttle-radar-topography-mission-srtm-1?utm_source=chatgpt.com">USGS</a>)</td></tr><tr><td><strong>MERIT DEM</strong></td><td>90 m</td><td>DTM, error/tree-height corrected</td><td>90°N-60°S</td><td>2019</td><td>Free for research (<a href="https://hydro.iis.u-tokyo.ac.jp/~yamadai/MERIT_DEM/?utm_source=chatgpt.com">Global Hydrology Group</a>)</td></tr><tr><td><strong>EarthEnv-DEM90</strong></td><td>90 m</td><td>DTM, smoothed fusion</td><td>90°N-60°S</td><td>2014</td><td>Public and free (<a href="https://www.earthenv.org/DEM?utm_source=chatgpt.com">earthenv.org</a>)</td></tr><tr><td><strong>IC2-GDEM</strong></td><td>30 m</td><td>DTM, ASTER + ICESat-2 correction</td><td>83°N-83°S</td><td>2025 paper release</td><td>Research access (<a href="https://essd.copernicus.org/articles/17/205/2025/?utm_source=chatgpt.com">essd.copernicus.org</a>)</td></tr><tr><td><strong>GMTED2010</strong></td><td>250 m / 7.5″</td><td>Multi-scale statistics</td><td>Global land</td><td>2010</td><td>Public and free (<a href="https://www.usgs.gov/centers/eros/science/usgs-eros-archive-digital-elevation-global-multi-resolution-terrain-elevation?utm_source=chatgpt.com">USGS</a>)</td></tr><tr><td><strong>GTOPO30</strong></td><td>1 km</td><td>DEM</td><td>Global land</td><td>1996</td><td>Public and free (<a href="https://www.usgs.gov/centers/eros/science/usgs-eros-archive-digital-elevation-global-30-arc-second-elevation-gtopo30?utm_source=chatgpt.com">USGS</a>)</td></tr><tr><td><strong>GEBCO</strong></td><td>15″, about 450 m</td><td>Land + seabed</td><td>Global land and ocean</td><td>2023</td><td>Public and free (<a href="https://www.gebco.net/data-products/gridded-bathymetry-data/gebco2023-grid?utm_source=chatgpt.com">GEBCO</a>)</td></tr></tbody></table>
<p>* <strong>DSM</strong> includes vegetation and buildings. <strong>DTM / bare-earth</strong> removes trees and buildings and is more suitable for hydrology, flood, and drainage-network simulation.</p>
<h3 id="selection-and-usage-tips">Selection and Usage Tips</h3>
<ol>
<li><strong>First choice at 30 m</strong>: <strong>Copernicus GLO-30</strong> currently has strong overall accuracy and consistency with a low download threshold. If bare-earth terrain is needed, use <strong>FABDEM</strong>, which removes building and canopy errors based on GLO-30. <strong>ALOS AW3D30</strong> is a good alternative, especially where it complements ASTER in cloudy or snowy areas. <strong>IC2-GDEM</strong> improves high-latitude mountains but is still mainly a research release.</li>
<li><strong>90 m products</strong>: <strong>Copernicus GLO-90</strong> and <strong>TanDEM-X 90 m</strong> are generally better than traditional SRTM in high-latitude and desert areas. <strong>MERIT DEM</strong> and <strong>EarthEnv-DEM90</strong> include systematic error correction and are useful for large-basin hydrology or ecological modeling.</li>
<li><strong>Integrated land-and-sea terrain</strong>: If analysis includes seafloor terrain, such as global visualization or sea-level-rise scenarios, use <strong>GEBCO</strong> 15″ global grids for consistent land-and-sea coverage.</li>
<li><strong>Polar or high-precision needs</strong>: Polar regions can use <strong>TanDEM-X 12 m</strong> commercially or regional <strong>ArcticDEM/REMA 2 m</strong>. For ice-sheet thickness and bedrock, use <strong>BedMachine</strong> datasets for Greenland or Antarctica.</li>
<li><strong>Data fusion and error control</strong>: Different DEMs may use different vertical references, such as ellipsoid heights versus EGM96 geoid heights, different acquisition periods, and DSM/DTM definitions. Before mosaicking datasets, unify the vertical datum and apply smoothing or bias correction. For large-scale hydrological or flood simulation, use hydrologically corrected products such as MERIT Hydro or FABDEM to reduce false drainage breaks and artificial depressions.</li>
</ol>
<h2 id="gebco-global-land-and-sea-gridded-terrain-model">GEBCO Global Land-and-Sea Gridded Terrain Model</h2>
<h3 id="what-is-gebco">What Is GEBCO?</h3>
<p><strong>GEBCO (General Bathymetric Chart of the Oceans)</strong> is a century-scale project jointly led by the International Hydrographic Organization (IHO) and the Intergovernmental Oceanographic Commission (IOC) of UNESCO. Its goal is to complete high-precision global seafloor mapping by 2030 through the Seabed 2030 initiative. GEBCO's core product is an annually updated <strong>global land-and-sea gridded terrain model (GEBCO Grid)</strong>, released free to the public for research, engineering, mapping, education, and other uses. <a href="https://www.gebco.net/?utm_source=chatgpt.com">GEBCO</a></p>
<h3 id="latest-versions">Latest Versions</h3>
<table><thead><tr><th>Version</th><th>Release Date</th><th>Spatial Resolution</th><th>Data Volume</th><th>Highlights</th></tr></thead><tbody><tr><td><strong>GEBCO_2025 Grid</strong></td><td>2025-06-06</td><td>15″, about 500 m</td><td>3.7 x 10^9 pixels</td><td>Uses SRTM15+ v2.7 as the land and 50°S-60°N ocean base; includes latest multibeam bathymetry from four Seabed 2030 regional centers; 27.3% of the seafloor has modern bathymetry.</td></tr><tr><td>GEBCO_2024 Grid</td><td>2024-07-24</td><td>15″</td><td>Same</td><td>Adds 4.34 x 10^6 km² of data; first release with Greenland and Antarctica sub-ice versions.</td></tr><tr><td>GEBCO_2023 Grid</td><td>2023-07-12</td><td>15″</td><td>Same</td><td>Continues integrating regional-center and crowdsourced bathymetry data.</td></tr></tbody></table>
<h3 id="data-components">Data Components</h3>
<ul>
<li><strong>Elevation Grid</strong>: values are in meters; positive values represent land elevation and negative values represent water depth.</li>
<li><strong>TID Grid</strong>: each raster cell has a <em>Type Identifier</em> showing the data source, such as multibeam, single-beam, satellite-guided reconstruction, or interpolation. <a href="https://www.gebco.net/data-products/gridded-bathymetry-data?utm_source=chatgpt.com">GEBCO</a></li>
<li><strong>Sub-ice versions</strong>: separate grids are available for topography under the Greenland and Antarctic ice sheets.</li>
</ul>
<h3 id="download-and-format">Download and Format</h3>
<table><thead><tr><th>Method</th><th>Content</th><th>Format</th></tr></thead><tbody><tr><td><strong>Global file</strong></td><td>1 NetCDF / GeoTIFF / Esri ASCII file</td><td>Single file, about 7.5 GB</td></tr><tr><td><strong>8 tiles</strong></td><td>90° x 90° tiles</td><td>About 890 MB per file, 8 files total</td></tr><tr><td><strong>Online clipping</strong></td><td>Custom extent download</td><td>GeoTIFF / NetCDF / ASCII</td></tr><tr><td><strong>Web services</strong></td><td>WMS, WMTS, TileXYZ</td><td>Suitable for online basemaps</td></tr></tbody></table>
<p>GeoTIFF is usually recommended. Use the <a href="https://www.bodc.ac.uk/data/open_download/gebco/gebco_2024/geotiff/">GEBCO_2024 Grid download address</a>.</p>
<h3 id="license-and-citation">License and Citation</h3>
<ul>
<li>
<p><strong>Free</strong>: available for commercial and academic use.</p>
</li>
<li>
<p><strong>Requirement</strong>: cite "© GEBCO Year" and include the DOI, such as GEBCO_2025 <code>10.5285/37c52e96-24ea-67ce-e063-7086abc05f29</code>. <a href="https://www.bodc.ac.uk/resources/inventories/edmed/report/7410/">British Oceanographic Data Centre</a></p>
</li>
<li>
<p><strong>Disclaimer</strong>: GEBCO is not responsible for losses caused by data use.</p>
</li>
<li>
<p>Detailed documentation for each year is available through the DOI links.</p>
<ul>
<li><a href="https://doi.org/10.5285/1c44ce99-0a0d-5f4f-e063-7086abc0ea0f">GEBCO_2024 Grid</a></li>
<li><a href="https://doi.org/10.5285/f98b053b-0cbc-6c23-e053-6c86abc0af7b">GEBCO_2023 Grid</a></li>
<li><a href="https://doi.org/doi:10.5285/e0f0bb80-ab44-2739-e053-6c86abc0289c">GEBCO_2022 Grid</a></li>
<li><a href="https://doi.org/10.5285/c6612cbe-50b3-0cff-e053-6c86abc09f8f">GEBCO_2021 Grid</a></li>
<li><a href="https://doi.org/10.5285/a29c5465-b138-234d-e053-6c86abc040b9">GEBCO_2020 Grid</a></li>
<li><a href="https://doi.org/10.5285/836f016a-33be-6ddc-e053-6c86abc0788e">GEBCO 2019 Grid</a></li>
</ul>
</li>
</ul>
<h3 id="using-the-data">Using the Data</h3>
<p>After downloading GeoTIFF data, upload it to the cloud resource manager, or directly use the public-space precached data.</p>
<p>For this dataset, use standard global terrain coloring.</p>
<table><thead><tr><th>Zone</th><th>Class (m)</th><th>RGB</th><th>Description</th></tr></thead><tbody><tr><td>Ultra-deep trench</td><td>≤ -8000</td><td>0, 0, 50</td><td>World's deepest trenches, such as the Mariana Trench</td></tr><tr><td>Deep ocean basin</td><td>-8000 to -6000</td><td>0, 40, 130</td><td>Deep ocean plain and basin</td></tr><tr><td>Abyssal plain</td><td>-6000 to -4000</td><td>0, 80, 200</td><td>Abyssal plain and ridge foot slopes</td></tr><tr><td>Oceanic slope</td><td>-4000 to -2000</td><td>0, 120, 240</td><td>Continental slope / mid-ocean ridge slopes</td></tr><tr><td>Outer continental shelf</td><td>-2000 to -200</td><td>70, 170, 255</td><td>Shallow-sea to slope transition</td></tr><tr><td>Continental shelf and tidal flats</td><td>-200 to 0</td><td>172, 220, 255</td><td>Nearshore shallows and deltas</td></tr><tr><td>Coastline / lowland</td><td>0 to 200</td><td>0, 120, 0</td><td>Low-elevation coastal plains and estuaries</td></tr><tr><td>Low hills</td><td>200 to 1000</td><td>80, 160, 0</td><td>Rolling hills and low mountains</td></tr><tr><td>Middle mountains</td><td>1000 to 2000</td><td>172, 172, 0</td><td>Plateau margins and pastoral highlands</td></tr><tr><td>Plateau</td><td>2000 to 3000</td><td>200, 150, 0</td><td>Inland plateaus and tablelands</td></tr><tr><td>Low mountain ridges</td><td>3000 to 4000</td><td>210, 110, 35</td><td>Mountain ridges and exposed rock walls</td></tr><tr><td>High mountains</td><td>4000 to 5000</td><td>220, 170, 130</td><td>Alpine valleys and first snow/ice zones</td></tr><tr><td>Extremely high mountains</td><td>5000 to 6000</td><td>240, 220, 200</td><td>High-altitude glacier areas</td></tr><tr><td>Snow line</td><td>6000 to 8848</td><td>250, 250, 250</td><td>Perennial snow and ice caps</td></tr><tr><td>Highest peaks</td><td>≥ 8848</td><td>255, 255, 255</td><td>Everest and other extreme elevations</td></tr></tbody></table>
<p>In iXGIS, you can use stretch coloring or classified coloring. Hillshade can also be enabled with classified coloring.</p>
<h3 id="simplified-gebco-template">Simplified GEBCO Template</h3>
<p>A simplified global land-and-sea terrain map can be made by reducing the original data by a factor of 10.</p>
<ol>
<li>Load the simplified GEBCO global land-and-sea raster terrain model from the public space. The resolution is 45'.</li>
<li>Configure symbols and styles. You can use the global land-and-sea terrain colors listed above, with either stretch or classified symbols. The example uses stretch colors. If the project is created from the Global Terrain GEBCO template, the existing symbol settings can be reused.</li>
<li>Load the simplified global country distribution layer.</li>
<li>Enter map layout and add a north arrow, scale bar, and legend.</li>
<li>Select the map frame and set the map scale to 1:150,000,000 in map properties.</li>
</ol>
<h2 id="aster-gdem-v3">ASTER GDEM v3</h2>
<p>On June 30, 2009, NASA and Japan's Ministry of Economy, Trade and Industry (METI) jointly released the ASTER GDEM (Advanced Spaceborne Thermal Emission and Reflection Radiometer Global Digital Elevation Model), produced from detailed observations by NASA's Terra satellite. This global DEM uses 1.3 million stereo images collected by ASTER. ASTER mapping covers all land areas between 83°N and 83°S, about 99% of Earth's land surface. Before this, the most complete terrain data came from NASA's Shuttle Radar Topography Mission (SRTM), which mapped about 80% of Earth's land between 60°N and 57°S.</p>
<p>At one time, SRTM 90 m terrain data could be downloaded for free from the International Scientific Data Service Platform of the Computer Network Information Center, Chinese Academy of Sciences (<code>http://srtm.datamirror.csdb.cn/</code>). It is no longer available there.</p>
<h3 id="production-workflow">Production Workflow</h3>
<p>ASTER GDEM was produced by fully automated processing of 1.5 million archived ASTER scenes. This included 1,264,118 scene-based ASTER DEMs generated through stereo correlation, followed by cloud removal, removal of remaining anomalies, averaging to produce final pixel values, correction of remaining abnormal data, and tiling into 1° x 1° global ASTER GDEM files.</p>
<h3 id="data-access">Data Access</h3>
<p>ASTER GDEM data is currently available online for free. Users can download it from Japan's <a href="https://www.jspacesystems.or.jp/ersdac/GDEM/E/index.html">ERSDAC</a> (Earth Remote Sensing Data Analysis Center) or NASA's <a href="https://search.earthdata.nasa.gov/search">LP DAAC (Land Processes Distributed Active Archive Center)</a>. Registration and data-request permissions are required before download.</p>
<h3 id="access-from-ixgis">Access from iXGIS</h3>
<p>iXGIS has downloaded the data from the sources above and cached it in object storage. Users can download it directly from the Data Download tool in the toolbox. The download format is GeoTIFF.</p>
<p>iXGIS automatically merges and clips the data according to the specified extent.</p>
<p>Global data download is supported.</p>
<h2 id="nasadem--srtm-v3">NASADEM / SRTM V3</h2>
<p>NASADEM (NASA Digital Elevation Model) is a high-precision global digital elevation product developed by NASA from <strong>SRTM V3 (Shuttle Radar Topography Mission, Version 3)</strong> data. SRTM was acquired in 2000 by radar interferometry aboard the Space Shuttle Endeavour, covering most land areas between <strong>60°N and 56°S</strong>, or more than 80% of global land.</p>
<p>NASADEM comprehensively reprocesses and enhances SRTM by combining multiple data sources, such as ASTER GDEM, ICESat, NED/3DEP, and GTOPO30, with improved processing algorithms to improve accuracy, completeness, and consistency.</p>
<h3 id="data-characteristics">Data Characteristics</h3>
<ul>
<li><strong>Coverage</strong>: global 60°N-56°S, covering most inhabited land areas.</li>
<li><strong>Spatial resolution</strong>: 1 arc-second (~30 m) global coverage for SRTM1; 3 arc-second (~90 m) global coverage for SRTM3 and some historical versions.</li>
<li><strong>Vertical accuracy</strong>: absolute vertical accuracy is about <strong><code>&lt;</code> 10 m</strong>, and relative accuracy is better than <strong>5 m</strong>. NASADEM reprocessing further reduces errors.</li>
<li><strong>Projection and format</strong>: WGS84 ellipsoid, geographic coordinates EPSG:4326, GeoTIFF tiles of 1° x 1°.</li>
<li><strong>Processing improvements over SRTM V2 and CGIAR-CSI SRTM</strong>: NASA JPL's new algorithm fills voids in the original data; multiple elevation sources such as ASTER GDEM, NED/3DEP, and ICESat are fused for correction; global seamless coverage is improved; and outputs are better suited for integration with other NASA/USGS datasets such as Landsat and MODIS.</li>
</ul>
<h3 id="access">Access</h3>
<ul>
<li><strong>NASA Earthdata (LP DAAC)</strong>: <a href="https://lpdaac.usgs.gov/">https://lpdaac.usgs.gov/</a></li>
<li><strong>USGS EarthExplorer</strong>: <a href="https://earthexplorer.usgs.gov/">https://earthexplorer.usgs.gov/</a></li>
</ul>
<h2 id="aw3d30-dsm">AW3D30-DSM</h2>
<p><strong>AW3D30</strong> is a global digital surface model (DSM) produced by the Japan Aerospace Exploration Agency (JAXA) from imagery acquired by PRISM (Panchromatic Remote-sensing Instrument for Stereo Mapping) aboard the Advanced Land Observing Satellite ALOS, also called DAICHI.</p>
<ul>
<li><strong>Spatial resolution</strong>: about <strong>30 m</strong> (1 arc-second grid).</li>
<li><strong>Coverage</strong>: global land areas; exact coverage depends on product version.</li>
<li><strong>License</strong>: the dataset can be used free of charge for commercial and non-commercial purposes, subject to the applicable terms of use.</li>
</ul>
<h3 id="access-1">Access</h3>
<ul>
<li>Register on JAXA's EORC official website and download tile packages, usually provided as <code>*.tar.gz</code> files.</li>
<li>Access and analyze it in Google Earth Engine, for example using ImageCollection <code>"JAXA/ALOS/AW3D30/V4_1"</code> and the DSM band for visualization or slope calculation.</li>
<li><a href="https://www.eorc.jaxa.jp/ALOS/en/dataset/aw3d30/aw3d30_e.htm">Data download</a></li>
<li>After email registration, tiled files can be downloaded.</li>
</ul>
<h3 id="file-organization">File Organization</h3>
<p>AW3D30 data is organized as 1° x 1° longitude/latitude tiles. Main files include:</p>
<ul>
<li><strong>DSM file</strong>: surface height (elevation), stored as 16-bit signed values.</li>
<li><strong>MSK file</strong>: 8-bit mask marking cloud, snow, seawater, low-quality areas, and similar conditions.</li>
<li><strong>STK file</strong>: indicates the number of scene stacks used to generate the DSM.</li>
<li><strong>QAI file</strong>: quality-assurance information describing product properties and data quality.</li>
<li><strong>HDR file</strong>: metadata file containing projection, data format, and related information.</li>
</ul>
<h3 id="access-from-ixgis-1">Access from iXGIS</h3>
<p>iXGIS has downloaded the data from the source above and cached it in object storage. Users can download it directly from the Data Download tool in the toolbox. The download format is GeoTIFF.</p>
<p>iXGIS automatically merges and clips the data according to the specified extent.</p>
<p>Global data download is supported.</p>]]></content:encoded>
            <author>sjzhakj@163.com (Xinyang)</author>
            <category>Terrain Data</category>
        </item>
        <item>
            <title><![CDATA[Land Use Data Download and Usage Guide]]></title>
            <link>https://www.ixgis.com/fr/articles/land-use-data-guide</link>
            <guid>https://www.ixgis.com/fr/articles/land-use-data-guide</guid>
            <pubDate>Sat, 20 Sep 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[This article introduces commonly used global land use and land cover datasets, their sources, download methods, and how to download and use land use data in iXGIS.]]></description>
            <content:encoded><![CDATA[<p><strong>Land cover</strong> describes the current natural or artificial cover types on Earth's surface, such as forest, grassland, cropland, water, and glaciers. <strong>Land use</strong> describes how people use land, reflecting socioeconomic functions such as farming, urban construction, and industry. In short, land cover asks "what is on the surface," while land use asks "how the land is used." The concepts are related but different: the same forest cover may correspond to different land uses, such as protected forest or commercial logging. In real data products, <strong>Land Use/Land Cover (LULC)</strong> is often combined into one classification system that considers both natural cover and human use. In general, land cover data is used more for environmental analysis and ecological assessment, while land use data is used more for land management and planning.</p>
<blockquote>
<p><strong>Note:</strong> At the global scale, direct observation of human land use is difficult. Common global "land use" datasets are usually based on remotely sensed land cover maps, with classes that also imply use. For example, "cropland" and "built-up" are both cover types and land-use indicators. The datasets below are therefore mainly global land cover / land use classification products.</p>
</blockquote>
<h2 id="global-land-use--land-cover-datasets">Global Land Use / Land Cover Datasets</h2>
<p>The following sections introduce several mainstream global land use / land cover datasets, including their characteristics, formats, accuracy, and access methods.</p>
<h3 id="esa-worldcover-10-m">ESA WorldCover 10 m</h3>
<p><strong>Overview:</strong> WorldCover is a high-resolution global land cover product released by the European Space Agency (ESA). It currently provides annual global maps for <strong>2020</strong> and <strong>2021</strong> at 10 m resolution, produced from Sentinel-1 radar and Sentinel-2 optical imagery. The classification system contains <strong>11 land cover classes</strong>: tree cover, shrubland, grassland, cropland, built-up, bare/sparse vegetation, snow and ice, permanent water, herbaceous wetland, mangroves, and moss and lichen. Independent validation reported an overall accuracy of about <strong>74.4%</strong> for 2020 and about <strong>76.7%</strong> for 2021, meeting the target accuracy level above 75%.</p>
<p><strong>Spatial and temporal resolution:</strong> 10 m spatial resolution. Each product is a single-year classification map; currently 2020 and 2021 are available. The target is annual updates, with each product completed about 10 months after the last image acquisition of the year.</p>
<p><strong>Access and license:</strong> WorldCover is released under CC BY 4.0. It is free to use without restriction, but attribution is required. Commercial advertising use requires ESA project approval.</p>
<h4 id="format-and-download">Format and Download</h4>
<ol>
<li>WorldCover is provided in a longitude/latitude grid projection (WGS84) and split into <strong>3° x 3° Cloud Optimized GeoTIFF (COG)</strong> tiles. There are 2,651 global tiles with a total size of about 117 GB. Users can download 7zip-compressed GeoTIFF tiles from the official interactive map, or access integrated versions through Zenodo and Google Earth Engine. The data DOI is referenced on [worldcover2020.esa.int](<a href="https://worldcover2020.esa.int/download#:~:text=To">https://worldcover2020.esa.int/download#:~:text=To</a> cite these maps as,5571936).</li>
</ol>
<p>Note: the website mentioned below is no longer accessible. If original data is needed, download it from <a href="https://developers.google.cn/earth-engine/datasets/catalog/ESA_WorldCover_v200?hl=zh-cn">Google Earth Engine</a>.</p>
<ol start="2">
<li>The ESA official <a href="https://worldcover2020.esa.int/downloader">2020 data download page</a> provided 60° x 60° macrotiles:</li>
</ol>
<pre><code class="language-text">https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_N30W180.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_S30W180.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_S90W180.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_N30W120.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_S30W120.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_S90W120.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_N30W060.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_S30W060.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_S90W060.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_N30E000.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_S30E000.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_S90E000.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_N30E060.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_S30E060.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_S90E060.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_N30E120.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_S30E120.zip
https://worldcover2020.esa.int/data/archive/ESA_WorldCover_10m_2020_v100_60deg_macrotile_S90E120.zip
</code></pre>
<p>2021 data:</p>
<pre><code class="language-text">https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_N30W180.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_S30W180.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_S90W180.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_N30W120.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_S30W120.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_S90W120.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_N30W060.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_S30W060.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_S90W060.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_N30E000.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_S30E000.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_S90E000.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_N30E060.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_S30E060.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_S90E060.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_N30E120.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_S30E120.zip
https://worldcover2021.esa.int/data/archive/ESA_WorldCover_10m_2021_v200_60deg_macrotile_S90E120.zip
</code></pre>
<p>The north-south identifiers are <code>N30</code>, <code>S30</code>, and <code>S90</code>; the west-east identifiers are <code>W180</code>, <code>W120</code>, <code>W060</code>, <code>E000</code>, <code>E060</code>, and <code>E120</code>. URLs can be assembled from these identifiers and downloaded in a browser.</p>
<h4 id="file-name-definition">File Name Definition</h4>
<p>Example file name: <code>ESA_WorldCover_10m_2020_v100_N66E063_Map.tif</code>.</p>
<ul>
<li><code>ESA_WorldCover_10m</code>: ESA WorldCover global 10 m land cover dataset.</li>
<li><code>2020_v100</code>: year 2020, <code>v100</code> = Version 100, the first official 2020 release.</li>
<li><code>2021_v200</code>: year 2021, <code>v200</code> = Version 200.</li>
<li><code>N66E063</code>: the <strong>3° x 3° tile ID</strong>.</li>
<li><code>N66</code>: latitude 66°N to 69°N.</li>
<li><code>E063</code>: longitude 63°E to 66°E.</li>
</ul>
<h4 id="classes-and-code-values">Classes and Code Values</h4>
<p>ESA <strong>WorldCover</strong> uses a simplified version of the <strong>FAO LCCS (Land Cover Classification System)</strong> and stores land cover classes as integer codes. The 2020 and 2021 classifications are consistent and contain <strong>11 classes</strong>.</p>
<table><thead><tr><th>Code</th><th>Class</th><th>Recommended Color (RGB)</th></tr></thead><tbody><tr><td>10</td><td>Tree cover</td><td>(0, 100, 0), dark green</td></tr><tr><td>20</td><td>Shrubland</td><td>(255, 187, 34), yellow-brown</td></tr><tr><td>30</td><td>Grassland</td><td>(255, 255, 76), light yellow</td></tr><tr><td>40</td><td>Cropland</td><td>(240, 150, 255), pink-purple</td></tr><tr><td>50</td><td>Built-up</td><td>(255, 0, 0), red</td></tr><tr><td>60</td><td>Bare/sparse vegetation</td><td>(191, 191, 191), gray</td></tr><tr><td>70</td><td>Snow and ice</td><td>(240, 240, 240), white</td></tr><tr><td>80</td><td>Permanent water</td><td>(0, 0, 255), blue</td></tr><tr><td>90</td><td>Herbaceous wetland</td><td>(0, 255, 255), cyan</td></tr><tr><td>95</td><td>Mangroves</td><td>(0, 150, 120), teal</td></tr><tr><td>100</td><td>Moss and lichen</td><td>(255, 220, 210), pale pink</td></tr></tbody></table>
<p>Notes:</p>
<ul>
<li>Code values are integer pixel values in the GeoTIFF and can be used directly for classified rendering.</li>
<li>Built-up (50) includes urban areas, roads, mining and industrial areas, and other artificial impervious surfaces.</li>
<li>Bare/sparse vegetation (60) is common in deserts, Gobi areas, and sparsely vegetated regions.</li>
<li>Mangroves (95) are separated from general wetlands (90), mainly along tropical and subtropical coasts.</li>
<li>Moss and lichen (100) are mainly distributed in polar and high-latitude tundra regions.</li>
</ul>
<h4 id="download-from-ixgis">Download from iXGIS</h4>
<p>iXGIS has downloaded the data from the sources above and cached it in object storage. Users can download it directly from the Data Download tool in the toolbox. The download format is GeoTIFF.</p>
<p>iXGIS automatically merges and clips the data according to the specified extent.</p>
<p>Global data download is supported.</p>
<h3 id="cglc-100-m">CGLC 100 m</h3>
<p><strong>Overview:</strong> This <strong>100 m global land cover</strong> dataset is provided by the Copernicus Global Land Service (CGLS) and produced from VITO PROBA-V satellite imagery. It is available as annual dynamic products from <strong>2015 to 2019</strong>. The classification is relatively detailed and includes major land surface types such as forests, shrubs, herbaceous vegetation, cropland, urban built-up areas, bare areas, snow and ice, permanent and seasonal water, wetlands, and proportional layers for tree cover, grass cover, shrub cover, and bare ground. It emphasizes multi-year consistency for monitoring global land cover change since 2015. Independent validation reports an overall classification accuracy of about <strong>80%</strong>; the 2019 product has a thematic accuracy of 80.3%. The project target is to further improve accuracy above 85%.</p>
<p><strong>Spatial and temporal resolution:</strong> 100 m spatial resolution in a WGS84 longitude/latitude grid. The period is 2015-2019, with one global map per year. It is an annual product; the latest product is 2019 because PROBA-V stopped operating in 2020, and later updates may use other data sources.</p>
<h4 id="format-and-download-1">Format and Download</h4>
<p>The official product is available as GeoTIFF. Annual global data can be downloaded by region or obtained through an API. Users can download clipped regions from the Copernicus Land portal or use the auxiliary download API to obtain the full original GeoTIFF dataset. The data is open and free, but a Copernicus account is required. OGC Web Services such as WMS are also supported. The dataset follows the EU Copernicus open data policy: it is free to use without restriction, but citation of the data source and DOI is required.</p>
<p>Download page: <a href="https://land.copernicus.eu/en/products/global-dynamic-land-cover/copernicus-global-land-service-land-cover-100m-collection-3-epoch-2019-globe#download">Land Cover 2019 (raster 100 m), global, yearly - version 3 - Copernicus Land Monitoring Service</a></p>
<h4 id="classes-and-code-values-1">Classes and Code Values</h4>
<p>Copernicus <strong>Global Land Cover 100 m (CGLS-LC100)</strong> uses the FAO LCCS and provides 23 global land cover classes. The main code values are:</p>
<table><thead><tr><th>Code</th><th>Class</th><th>Description</th></tr></thead><tbody><tr><td>10</td><td>Cropland, rainfed</td><td>Rainfed cropland</td></tr><tr><td>11</td><td>Herbaceous cover</td><td>Herbaceous-cover cropland</td></tr><tr><td>12</td><td>Tree or shrub cover</td><td>Tree- or shrub-cover cropland</td></tr><tr><td>20</td><td>Cropland, irrigated or post-flooding</td><td>Irrigated or seasonally flooded cropland</td></tr><tr><td>30</td><td>Mosaic cropland (&gt; 50%) / natural vegetation (&lt; 50%)</td><td>Cropland-dominant mosaic</td></tr><tr><td>40</td><td>Mosaic natural vegetation (&gt; 50%) / cropland (&lt; 50%)</td><td>Natural-vegetation-dominant mosaic</td></tr><tr><td>50</td><td>Tree cover, broadleaved, evergreen, closed to open (&gt; 15%)</td><td>Evergreen broadleaved forest</td></tr><tr><td>60</td><td>Tree cover, broadleaved, deciduous, closed to open (&gt; 15%)</td><td>Deciduous broadleaved forest</td></tr><tr><td>61</td><td>Tree cover, broadleaved, deciduous, closed (&gt; 40%)</td><td>Closed deciduous broadleaved forest</td></tr><tr><td>62</td><td>Tree cover, broadleaved, deciduous, open (15-40%)</td><td>Open deciduous broadleaved forest</td></tr><tr><td>70</td><td>Tree cover, needleleaved, evergreen, closed to open (&gt; 15%)</td><td>Evergreen needleleaved forest</td></tr><tr><td>71</td><td>Tree cover, needleleaved, evergreen, closed (&gt; 40%)</td><td>Closed evergreen needleleaved forest</td></tr><tr><td>72</td><td>Tree cover, needleleaved, evergreen, open (15-40%)</td><td>Open evergreen needleleaved forest</td></tr><tr><td>80</td><td>Tree cover, needleleaved, deciduous, closed to open (&gt; 15%)</td><td>Deciduous needleleaved forest</td></tr><tr><td>81</td><td>Tree cover, needleleaved, deciduous, closed (&gt; 40%)</td><td>Closed deciduous needleleaved forest</td></tr><tr><td>82</td><td>Tree cover, needleleaved, deciduous, open (15-40%)</td><td>Open deciduous needleleaved forest</td></tr><tr><td>90</td><td>Mosaic tree and shrub (&gt; 50%) / herbaceous cover (&lt; 50%)</td><td>Tree/shrub-dominant mosaic</td></tr><tr><td>100</td><td>Mosaic herbaceous cover (&gt; 50%) / tree and shrub (&lt; 50%)</td><td>Herbaceous-dominant mosaic</td></tr><tr><td>110</td><td>Shrubland</td><td>Shrubland</td></tr><tr><td>120</td><td>Grassland</td><td>Grassland</td></tr><tr><td>130</td><td>Lichens and mosses</td><td>Lichens and mosses</td></tr><tr><td>140</td><td>Sparse vegetation (tree, shrub, herbaceous cover &lt; 15%)</td><td>Sparse vegetation</td></tr><tr><td>150</td><td>Tree cover, flooded, fresh or brakish water</td><td>Freshwater-flooded tree cover</td></tr><tr><td>160</td><td>Tree cover, flooded, saline water</td><td>Saline-water-flooded tree cover</td></tr><tr><td>170</td><td>Shrub or herbaceous cover, flooded, fresh/saline/brakish water</td><td>Flooded shrub or herbaceous cover</td></tr><tr><td>180</td><td>Urban areas</td><td>Urban / built-up areas</td></tr><tr><td>190</td><td>Bare areas</td><td>Bare areas</td></tr><tr><td>200</td><td>Water bodies</td><td>Water bodies</td></tr><tr><td>201</td><td>Permanent water bodies</td><td>Permanent water bodies</td></tr><tr><td>202</td><td>Seasonal water bodies</td><td>Seasonal water bodies</td></tr><tr><td>210</td><td>Permanent snow and ice</td><td>Permanent snow and ice</td></tr></tbody></table>
<h3 id="modis-global-land-cover-mcd12q1">MODIS Global Land Cover (MCD12Q1)</h3>
<p><strong>Overview:</strong> NASA provides this <strong>global 500 m annual land cover</strong> product from MODIS sensors on Terra and Aqua. The product ID is MCD12Q1 (Collection 6.1), covering each year from <strong>2001 to recent years, around 2020 and later</strong>. It includes several classification schemes. The primary classification uses the 17-class IGBP scheme, while UMD, LAI/FPAR, NPP biome, and Plant Functional Type (PFT) layers are also provided, along with quality-control layers. MODIS land cover has moderate accuracy; global average overall accuracy for the IGBP primary classification is about 75% in validation studies. It is a hard classification with one class per pixel and also includes confidence information.</p>
<p>The MODIS Terra + Aqua Land Cover Type Yearly L3 Global 500 m SIN Grid product provides five land cover classification schemes derived using supervised decision-tree classification:</p>
<ul>
<li>Land Cover Type 1: IGBP global vegetation classification scheme.</li>
<li>Land Cover Type 2: University of Maryland (UMD) scheme.</li>
<li>Land Cover Type 3: MODIS-derived LAI/fPAR scheme.</li>
<li>Land Cover Type 4: MODIS-derived Net Primary Production (NPP) scheme.</li>
<li>Land Cover Type 5: Plant Functional Type (PFT) scheme.</li>
</ul>
<p>Additional layers include land cover type assessment SDS, land cover percentage SDS, and land cover quality-control SDS.</p>
<p><strong>Spatial and temporal resolution:</strong> about 500 m spatial resolution. The product is annual, with one classification for each calendar year from 2001 onward. Collection 6.1 has been extended to 2020 or later, and some derived sources extend to 2022.</p>
<p><strong>Format and access:</strong> NASA's original global products are released as HDF-EOS files in Sinusoidal grid tiles. Each year is divided into 36 x 18 tiles and can be downloaded from NASA Earthdata platforms such as LP DAAC or LAADS. Although the official format is not TIFF, derived providers have mosaicked and reprojected annual data into GeoTIFF. OpenGeoHub, for example, provides <strong>2001-2022 global 500 m land cover time series</strong> as Cloud Optimized GeoTIFF mosaics. NASA data is in the public domain and free to use, but users should cite NASA/LP DAAC.</p>
<p><strong>Accuracy and limitations:</strong> MODIS land cover is coarse and has limited ability to represent heterogeneous surfaces and small patches. Overall accuracy is commonly around <strong>70%</strong>, with about 75% for the IGBP scheme. Accuracy varies by class; forests and grasslands are usually better, while urban and mixed classes have more errors. High-precision or fine-scale applications may require refinement or combination with higher-resolution data.</p>
<h4 id="download">Download</h4>
<p>iXGIS does not currently support direct display of HDF data, so GeoTIFF data is recommended. The <a href="https://home.cern/science/computing/data-centre">CERN Data Centre</a> provides GeoTIFF data derived from <a href="https://ladsweb.modaps.eosdis.nasa.gov/missions-and-measurements/products/MCD12Q1">MCD12Q1 v061</a>, covering 2001 to 2022.</p>
<p>Download page: <a href="https://zenodo.org/records/8367523">https://zenodo.org/records/8367523</a>. On the Zenodo page, the DOI is the dataset identifier. Search Zenodo for "MODIS MCD12Q1 Land Cover and Land Use Time Series Global Mosaics 2001-2022" if needed.</p>
<p>The page usually lists files such as:</p>
<pre><code class="language-text">lc_mcd12q1v061.t1_c_500m_s_20010101_20011231_go_epsg.4326_v20230818.tif
lc_mcd12q1v061.t1_c_500m_s_20020101_20021231_go_epsg.4326_v20230818.tif
...
</code></pre>
<p>Click <strong>Download all</strong> to download all files, or use the individual <strong>Download</strong> links for specific years.</p>
<p>File name fields:</p>
<table><thead><tr><th>Position</th><th>Fragment</th><th>Meaning</th></tr></thead><tbody><tr><td>1</td><td><code>lc</code></td><td>Data type: land cover.</td></tr><tr><td>2</td><td><code>mcd12q1v061.t1</code></td><td>Source and band: MCD12Q1, Collection 6.1, <code>t1</code> = Land Cover Type 1 (IGBP).</td></tr><tr><td>3</td><td><code>c</code></td><td>Data type: class result; <code>p</code> means probability/property.</td></tr><tr><td>4</td><td><code>500m</code></td><td>Spatial resolution: 500 m.</td></tr><tr><td>5</td><td><code>s</code></td><td>Surface layer.</td></tr><tr><td>6</td><td><code>20050101</code></td><td>Start date in YYYYMMDD format.</td></tr><tr><td>7</td><td><code>20051231</code></td><td>End date in YYYYMMDD format.</td></tr><tr><td>8</td><td><code>go</code></td><td>Global extent, excluding Antarctica.</td></tr><tr><td>9</td><td><code>epsg.4326</code></td><td>Coordinate system: EPSG:4326, WGS84 longitude/latitude.</td></tr><tr><td>10</td><td><code>v20230818</code></td><td>Version or generation timestamp, 2023-08-18. This is not the data coverage date.</td></tr></tbody></table>
<p>Other layer identifiers:</p>
<ul>
<li><strong>Original classifications <code>t1</code> / <code>t2</code> / <code>t5</code></strong>: <code>t1</code> = IGBP 17-class scheme, <code>t2</code> = UMD scheme, <code>t5</code> = Plant Functional Type (PFT).</li>
<li><strong>Biome property classifications <code>p1</code> / <code>p2</code></strong>: <code>p1</code> = LAI/FPAR biome, <code>p2</code> = NPP biome.</li>
<li><strong>Reliability layers <code>p1a</code> / <code>p2a</code></strong>: confidence or accuracy layers for <code>p1</code> and <code>p2</code>.</li>
<li><strong><code>p2c</code></strong>: Property 2 Continuous, continuous NPP biome-related variables such as proportions or coverage.</li>
<li><strong><code>qc</code></strong>: Quality Control layer indicating classification reliability.</li>
</ul>
<h4 id="igbp-classes-and-code-values">IGBP Classes and Code Values</h4>
<table><thead><tr><th>Code</th><th>Class</th><th>Description</th><th>RGB</th></tr></thead><tbody><tr><td>1</td><td>Evergreen Needleleaf Forests</td><td>Evergreen needleleaf forest</td><td>(5, 69, 10)</td></tr><tr><td>2</td><td>Evergreen Broadleaf Forests</td><td>Evergreen broadleaf forest</td><td>(8, 106, 16)</td></tr><tr><td>3</td><td>Deciduous Needleleaf Forests</td><td>Deciduous needleleaf forest</td><td>(84, 167, 8)</td></tr><tr><td>4</td><td>Deciduous Broadleaf Forests</td><td>Deciduous broadleaf forest</td><td>(120, 210, 3)</td></tr><tr><td>5</td><td>Mixed Forests</td><td>Mixed forest</td><td>(0, 153, 0)</td></tr><tr><td>6</td><td>Closed Shrublands</td><td>Closed shrubland</td><td>(198, 176, 68)</td></tr><tr><td>7</td><td>Open Shrublands</td><td>Open shrubland</td><td>(220, 209, 89)</td></tr><tr><td>8</td><td>Woody Savannas</td><td>Woody savanna</td><td>(218, 222, 72)</td></tr><tr><td>9</td><td>Savannas</td><td>Savanna</td><td>(251, 255, 19)</td></tr><tr><td>10</td><td>Grasslands</td><td>Grassland</td><td>(182, 255, 5)</td></tr><tr><td>11</td><td>Permanent Wetlands</td><td>Permanent wetland</td><td>(39, 255, 135)</td></tr><tr><td>12</td><td>Croplands</td><td>Cropland</td><td>(194, 79, 68)</td></tr><tr><td>13</td><td>Urban and Built-up Lands</td><td>Urban and built-up land</td><td>(165, 165, 165)</td></tr><tr><td>14</td><td>Cropland/Natural Vegetation Mosaics</td><td>Cropland / natural vegetation mosaic</td><td>(255, 109, 76)</td></tr><tr><td>15</td><td>Permanent Snow and Ice</td><td>Permanent snow and ice</td><td>(105, 255, 248)</td></tr><tr><td>16</td><td>Barren</td><td>Barren land</td><td>(249, 255, 164)</td></tr><tr><td>17</td><td>Water Bodies</td><td>Water bodies</td><td>(28, 13, 255)</td></tr><tr><td>255</td><td>Unclassified / No Data</td><td>Unclassified / NoData</td><td>transparent</td></tr></tbody></table>
<h4 id="umd-classes-and-code-values">UMD Classes and Code Values</h4>
<table><thead><tr><th>Code</th><th>Class</th><th>Description</th><th>RGB</th></tr></thead><tbody><tr><td>0</td><td>Water Bodies</td><td>Water bodies</td><td>(28, 13, 255)</td></tr><tr><td>1</td><td>Evergreen Needleleaf Forests</td><td>Evergreen needleleaf forest</td><td>(5, 69, 10)</td></tr><tr><td>2</td><td>Evergreen Broadleaf Forests</td><td>Evergreen broadleaf forest</td><td>(8, 106, 16)</td></tr><tr><td>3</td><td>Deciduous Needleleaf Forests</td><td>Deciduous needleleaf forest</td><td>(84, 167, 8)</td></tr><tr><td>4</td><td>Deciduous Broadleaf Forests</td><td>Deciduous broadleaf forest</td><td>(120, 210, 3)</td></tr><tr><td>5</td><td>Mixed Forests</td><td>Mixed forest</td><td>(0, 153, 0)</td></tr><tr><td>6</td><td>Closed Shrublands</td><td>Closed shrubland</td><td>(198, 176, 68)</td></tr><tr><td>7</td><td>Open Shrublands</td><td>Open shrubland</td><td>(220, 209, 89)</td></tr><tr><td>8</td><td>Woody Savannas</td><td>Woody savanna</td><td>(218, 222, 72)</td></tr><tr><td>9</td><td>Savannas</td><td>Savanna</td><td>(251, 255, 19)</td></tr><tr><td>10</td><td>Grasslands</td><td>Grassland</td><td>(182, 255, 5)</td></tr><tr><td>11</td><td>Permanent Wetlands</td><td>Permanent wetland</td><td>(39, 255, 135)</td></tr><tr><td>12</td><td>Croplands</td><td>Cropland</td><td>(194, 79, 68)</td></tr><tr><td>13</td><td>Urban and Built-up Lands</td><td>Urban and built-up land</td><td>(165, 165, 165)</td></tr><tr><td>14</td><td>Cropland/Natural Vegetation Mosaics</td><td>Cropland / natural vegetation mosaic</td><td>(255, 109, 76)</td></tr><tr><td>15</td><td>Non-Vegetated Lands</td><td>Non-vegetated land</td><td>(249, 255, 164)</td></tr></tbody></table>
<h4 id="land-cover-type-5-pft-classes-and-code-values">Land Cover Type 5: PFT Classes and Code Values</h4>
<table><thead><tr><th>Code</th><th>Class</th><th>Description</th><th>RGB</th></tr></thead><tbody><tr><td>0</td><td>Water Bodies</td><td>Water bodies</td><td>(28, 13, 255)</td></tr><tr><td>1</td><td>Evergreen Needleleaf Trees</td><td>Evergreen needleleaf trees</td><td>(5, 69, 10)</td></tr><tr><td>2</td><td>Evergreen Broadleaf Trees</td><td>Evergreen broadleaf trees</td><td>(8, 106, 16)</td></tr><tr><td>3</td><td>Deciduous Needleleaf Trees</td><td>Deciduous needleleaf trees</td><td>(84, 167, 8)</td></tr><tr><td>4</td><td>Deciduous Broadleaf Trees</td><td>Deciduous broadleaf trees</td><td>(120, 210, 3)</td></tr><tr><td>5</td><td>Shrub</td><td>Shrub</td><td>(220, 209, 89)</td></tr><tr><td>6</td><td>Non-Cultivated Herbaceous</td><td>Non-cultivated herbaceous vegetation</td><td>(182, 255, 5)</td></tr><tr><td>7</td><td>Cereal Croplands</td><td>Cereal cropland</td><td>(218, 222, 72)</td></tr><tr><td>8</td><td>Broadleaf Croplands</td><td>Broadleaf cropland</td><td>(194, 79, 68)</td></tr><tr><td>9</td><td>Urban and Built-up Lands</td><td>Urban and built-up land</td><td>(165, 165, 165)</td></tr><tr><td>10</td><td>Permanent Snow and Ice</td><td>Permanent snow and ice</td><td>(105, 255, 248)</td></tr><tr><td>11</td><td>Non-Vegetated Lands</td><td>Non-vegetated land</td><td>(249, 255, 164)</td></tr></tbody></table>
<h3 id="from-glc-tsinghua-university">FROM-GLC (Tsinghua University)</h3>
<p><strong>Overview:</strong> FROM-GLC (Finer Resolution Observation and Monitoring of Global Land Cover) was developed by Professor Gong Peng's team at Tsinghua University and is an important Chinese contribution to global land cover mapping. In 2014, the team released the <strong>first global 30 m</strong> land cover map based on Landsat data around 2010, using a detailed 28-class system. Because of the rich class system, the first 30 m map had a relatively low overall accuracy of about 52.8%. The team later improved algorithms using a 2015 global sample library and transferred 30 m samples to higher-resolution mapping, producing the <strong>first global 10 m</strong> land cover map from 2017 Sentinel-2 imagery. The <strong>FROM-GLC10 (2017)</strong> product uses 10 major land cover classes similar to GlobeLand30, improving accuracy through a simpler classification. Validation reported an overall accuracy of <strong>72.76%</strong>.</p>
<p><strong>Spatial and temporal resolution:</strong> The FROM-GLC series includes multiple products: <strong>2010 30 m</strong> (FROM-GLC30) and <strong>2017 10 m</strong> (FROM-GLC10). The coverage is global land. Updates are not regular; these are research-stage products for specific time points. Recent work also includes 30 m five-year interval land cover evolution data for 1985-2020 (GLC_FCS30D) and the 2015 fine-class 30 m product (GLC_FCS30-2015), but these may still be academic releases.</p>
<p><strong>Format and access:</strong> FROM-GLC data is provided by the Tsinghua Earth System Science data platform as block-based <strong>GeoTIFF</strong> downloads. Users must register and log in to the Tsinghua ESS data platform (<code>data.ess.tsinghua.edu.cn</code>) to download GeoTIFF files by region. The series is free for global users, with attribution required in publications and results. For potential commercial use, consult the data team.</p>
<p>Update: the Tsinghua data platform can no longer download the data. A Nebula Data service platform provides downloads, but it also appears unavailable.</p>
<h3 id="fao-global-land-cover-share">FAO Global Land Cover SHARE</h3>
<p><strong>Overview:</strong> GLC-SHARE is a global land cover database released by the Food and Agriculture Organization of the United Nations (FAO) in 2014. It uses a spatial resolution of about <strong>1 km</strong> (30 arc-seconds), combining each country's "best available" land cover data with global satellite-image classification results. GLC-SHARE provides <strong>11 thematic layers</strong>, each representing the percentage (0-100%) of one major land cover type in each 1 km cell. The classes include artificial surfaces, cropland, grassland, tree-covered areas, shrub-covered areas, natural wetlands, mangroves, sparse vegetation, bare soil, snow and glaciers, and water bodies. This layered method preserves details from national datasets as much as possible and improves global reliability. The temporal range is marked as 1998-2012, representing land cover conditions around the millennium. GLC-SHARE has not been updated annually and remains a version 1.0 beta baseline product.</p>
<p><strong>Spatial and temporal resolution:</strong> about 1 square kilometer (30 arc-second longitude/latitude grid). It covers global land and is static, representing average conditions around 2000 rather than later changes.</p>
<p>Detailed documentation: <a href="https://www.fao.org/uploads/media/glc-share-doc.pdf">glc-share-doc.pdf</a></p>
<p><a href="https://www.fao.org/4/x0596e/x0596e00.htm">Land Cover Classification System (LCCS): Classification Concepts and User Manual</a></p>
<p><strong>Format and access:</strong> FAO provides GLC-SHARE downloads and map services through GeoNetwork. Data is provided as <strong>GeoTIFF raster</strong> files, with one GeoTIFF per layer or a combined multiband GeoTIFF, in WGS84. OGC WMS services are also available. The data is free for education, research, personal, and other non-commercial use without prior permission, but FAO and the dataset name must be cited. Commercial resale or similar use requires FAO's written permission.</p>
<p><strong>References:</strong></p>
<ul>
<li>ESA, <em>ESA WorldCover 2020 - Info</em> (updated 2025): [worldcover2020.esa.int](<a href="https://worldcover2020.esa.int/#:~:text=,overall">https://worldcover2020.esa.int/#:~:text=,overall</a> accuracy), [validation report](<a href="https://worldcover2020.esa.int/#:~:text=The">https://worldcover2020.esa.int/#:~:text=The</a> ESA WorldCover product has,see the Product Validation Report)</li>
<li>ESA, <em>WorldCover 2020 Download Instructions</em> (2025): [worldcover2020.esa.int](<a href="https://worldcover2020.esa.int/download#:~:text=The">https://worldcover2020.esa.int/download#:~:text=The</a> ESA WorldCover 10 m,There are 2651 tiles), [terms of use](<a href="https://worldcover2020.esa.int/download#:~:text=Terms">https://worldcover2020.esa.int/download#:~:text=Terms</a> of use)</li>
<li>ESA, <em>ESA WorldCover 2021 - Info</em> (updated 2025): [worldcover2021.esa.int](<a href="https://worldcover2021.esa.int/#:~:text=,overall">https://worldcover2021.esa.int/#:~:text=,overall</a> accuracy%2C independently validated), <a href="https://worldcover2021.esa.int/#:~:text=Validation">validation</a></li>
<li>Copernicus Land, <em>Global Land Cover 100m - Characteristics</em> (2019): [land.copernicus.eu](<a href="https://land.copernicus.eu/en/products/global-dynamic-land-cover/copernicus-global-land-service-land-cover-100m-collection-3-epoch-2019-globe#:~:text=Spatial">https://land.copernicus.eu/en/products/global-dynamic-land-cover/copernicus-global-land-service-land-cover-100m-collection-3-epoch-2019-globe#:~:text=Spatial</a> resolution%3A), [update frequency](<a href="https://land.copernicus.eu/en/products/global-dynamic-land-cover/copernicus-global-land-service-land-cover-100m-collection-3-epoch-2019-globe#:~:text=Update">https://land.copernicus.eu/en/products/global-dynamic-land-cover/copernicus-global-land-service-land-cover-100m-collection-3-epoch-2019-globe#:~:text=Update</a> frequency%3A)</li>
<li>Copernicus Land, <em>100m Land Cover 2019 - Thematic Accuracy</em>: [land.copernicus.eu](<a href="https://land.copernicus.eu/en/products/global-dynamic-land-cover/copernicus-global-land-service-land-cover-100m-collection-3-epoch-2019-globe#:~:text=Thematic">https://land.copernicus.eu/en/products/global-dynamic-land-cover/copernicus-global-land-service-land-cover-100m-collection-3-epoch-2019-globe#:~:text=Thematic</a> accuracy%3A)</li>
<li>Copernicus Land, <em>Download via API Instructions</em>: [land.copernicus.eu](<a href="https://land.copernicus.eu/en/products/global-dynamic-land-cover/copernicus-global-land-service-land-cover-100m-collection-3-epoch-2019-globe#:~:text=Download">https://land.copernicus.eu/en/products/global-dynamic-land-cover/copernicus-global-land-service-land-cover-100m-collection-3-epoch-2019-globe#:~:text=Download</a> full dataset)</li>
<li>NASA LAADS, <em>MODIS MCD12Q1 Product Information</em>: [ladsweb.modaps.eosdis.nasa.gov](<a href="https://ladsweb.modaps.eosdis.nasa.gov/missions-and-measurements/products/MCD12Q1/#:~:text=Instrument%3A">https://ladsweb.modaps.eosdis.nasa.gov/missions-and-measurements/products/MCD12Q1/#:~:text=Instrument%3A</a> MODIS Processing Level%3A Level,Number%3A PGE41 File Naming Convention)</li>
<li>ResearchGate, <em>Accuracy Assessment of MODIS Global Land Cover</em>: <a href="https://www.researchgate.net/publication/241869199_Accuracy_assessment_of_global_land_cover_maps_lessons_learnt_from_the_GlobCover_and_GlobCorine_experiences#:~:text=,">researchgate.net</a></li>
<li>Zenodo, <em>MODIS 2001-2022 COG Data Description</em>: [zenodo.org](<a href="https://zenodo.org/records/8367523#:~:text=The">https://zenodo.org/records/8367523#:~:text=The</a> yearly land use and,qc)</li>
<li>UN-SPIDER, <em>GlobeLand30 Data Source Introduction</em>: [un-spider.org](<a href="https://www.un-spider.org/links-and-resources/data-sources/land-cover-map-globeland-30-ngcc#:~:text=Requirements%3ARegistration">https://www.un-spider.org/links-and-resources/data-sources/land-cover-map-globeland-30-ngcc#:~:text=Requirements%3ARegistration</a> necessary Data type%3Aland use%2C,2010)</li>
<li>ESSD, <em>GLC_FCS30-2015 Article Abstract</em>: [essd.copernicus.org](<a href="https://essd.copernicus.org/articles/13/2753/2021/#:~:text=and">https://essd.copernicus.org/articles/13/2753/2021/#:~:text=and</a> a greater diversity of,paper are free access at), [methods](<a href="https://essd.copernicus.org/articles/13/2753/2021/#:~:text=similar">https://essd.copernicus.org/articles/13/2753/2021/#:~:text=similar</a> image data along with,temporal differences among the Landsat)</li>
<li>Tsinghua University, <em>News on the First Global 10 m Land Cover Map</em>: [tsinghua.edu.cn](<a href="https://www.tsinghua.edu.cn/en/info/1244/2976.htm#:~:text=This">https://www.tsinghua.edu.cn/en/info/1244/2976.htm#:~:text=This</a> work proposed the theory,GLC30 product), [download note](<a href="https://www.tsinghua.edu.cn/en/info/1244/2976.htm#:~:text=other">https://www.tsinghua.edu.cn/en/info/1244/2976.htm#:~:text=other</a> years or different sensors,GLC30 product)</li>
<li>UN-SPIDER, <em>GLC-SHARE (FAO) Data Source Information</em>: [un-spider.org](<a href="https://www.un-spider.org/links-and-resources/data-sources/land-cover-map-glc-share-fao#:~:text=File">https://www.un-spider.org/links-and-resources/data-sources/land-cover-map-glc-share-fao#:~:text=File</a> type%3Atiff %2C  62,2012 Technical Specifications), [license](<a href="https://www.un-spider.org/links-and-resources/data-sources/land-cover-map-glc-share-fao#:~:text=Copyright%3A">https://www.un-spider.org/links-and-resources/data-sources/land-cover-map-glc-share-fao#:~:text=Copyright%3A</a> Exclusive right to the,means for resale or other)</li>
</ul>
<h2 id="china-land-use-data-globeland30">China Land Use Data: GlobeLand30</h2>
<p>GlobeLand30 is an important result of China's National High-Tech Research and Development Program (863 Program) project on global land cover remote sensing mapping and key technologies. It includes ten main land cover types: cultivated land, forest, grassland, shrubland, wetland, water bodies, tundra, artificial surfaces, bareland, and permanent snow and ice.</p>
<p>It was the world's first 30 m global land cover map and was first released in 2014 with independent intellectual property rights. GlobeLand30 currently provides global data for <strong>2000, 2010, and 2020</strong>. Compared with earlier 1 km and 300 m products, GlobeLand30 is much more detailed and is widely considered one of the best-quality global land cover datasets. Independent assessments report overall accuracy of about 75-80% for the 2010 product, while the producer reports classification accuracy above 80%. The 2020 data was updated using improved methods and new imagery and is expected to maintain high accuracy.</p>
<p>Land cover and its changes are essential basic information for environmental change studies, geographic monitoring, and sustainable development planning. Existing global land cover datasets with resolutions from 1 km to 300 m cannot fully meet application needs. China's GlobeLand30 is the first global 30 m land cover dataset and provides richer global land cover spatial information, better representing many human land-use activities and the landscape patterns they form.</p>
<p><a href="https://www.webmap.cn/public/style/images/globeLand/brief-3.jpg">Comparison of global land cover products at different resolutions</a></p>
<p>The 2000 and 2010 GlobeLand30 datasets support monitoring and analysis of land cover change. They were produced by the same research team using consistent classification methods, which improves objectivity and comparability.</p>
<p>The information above is from <a href="https://www.webmap.cn/commres.do?method=globeDetails&amp;type=brief">Global Land Cover Data</a>.</p>
<h3 id="download-process">Download Process</h3>
<p>The National Geographic Information Resource Catalog Service System provides GlobeLand30 datasets globally. After registration, the data can be downloaded for free.</p>
<h3 id="data-preview">Data Preview</h3>
<p>The downloaded data is a compressed package such as <code>N50_35_2010LC030.zip</code>. After decompression, the files with the <code>.tif</code> extension are usually the ones needed.</p>
<p>Each tile package contains five parts: classification result files, coordinate information files, classification image map-index files, metadata files, and explanatory files.</p>
<p>You can upload all files to the cloud resource manager, or upload only <code>n50_35_2010lc030.tif</code>. The data information shows an unsigned integer pixel type and a 30 m resolution.</p>
<h3 id="download-from-ixgis-1">Download from iXGIS</h3>
<p>iXGIS has downloaded the data from the source above and cached it in object storage. Users can download it directly from the Data Download tool in the toolbox. The download format is GeoTIFF.</p>
<p>iXGIS automatically merges and clips the data according to the specified extent.</p>
<p>China-region data download is supported.</p>
<h3 id="data-loading">Data Loading</h3>
<p>GlobeLand30 also defines symbology. The code-to-color table is shown below.</p>
<table><thead><tr><th>Code</th><th>Class</th><th>Description</th><th>RGB</th><th>Content Description</th></tr></thead><tbody><tr><td>10</td><td>Cultivated Land</td><td>Cultivated land</td><td>250,161,255</td><td>Land used for agriculture, horticulture, and orchard cultivation</td></tr><tr><td>20</td><td>Forest</td><td>Forest</td><td>0,99,0</td><td>Land covered by trees with vegetation coverage above 30%</td></tr><tr><td>30</td><td>Grassland</td><td>Grassland</td><td>99,255,0</td><td>Land covered by natural grasses with coverage above 10%</td></tr><tr><td>40</td><td>Shrubland</td><td>Shrubland</td><td>0,255,119</td><td>Land covered by shrubs with coverage above 30%</td></tr><tr><td>50</td><td>Wetland</td><td>Wetland</td><td>0,99,255</td><td>Land covered by wetland vegetation or containing water bodies</td></tr><tr><td>60</td><td>Water Bodies</td><td>Water bodies</td><td>0,0,255</td><td>Water areas within land regions</td></tr><tr><td>70</td><td>Tundra</td><td>Tundra</td><td>99,99,51</td><td>Polar land covered by lichens, mosses, perennial cold-tolerant herbs, and shrubs</td></tr><tr><td>80</td><td>Artificial Surfaces</td><td>Artificial surfaces</td><td>255,0,0</td><td>Surfaces transformed by human activities</td></tr><tr><td>90</td><td>Bareland</td><td>Bareland</td><td>191,191,191</td><td>Land with vegetation coverage below 10%</td></tr><tr><td>100</td><td>Permanent Snow &amp; Ice</td><td>Permanent snow and ice</td><td>198,239,255</td><td>Land covered by permanent snow, glaciers, and ice caps</td></tr><tr><td>255</td><td>None</td><td>None</td><td>0,198,255</td><td>None</td></tr></tbody></table>
<h3 id="data-processing">Data Processing</h3>
<p>Pixels with a value of 0 are invalid areas, but the data does not explicitly define a NoData value. It is best to set <code>NoData=0</code> for better display. You can re-export the raster with the raster export tool. Open the toolbox and use <strong>Raster Tools &gt; Raster Processing &gt; Assign NoData</strong> to assign invalid values. Depending on the dataset, set <code>NoData=0</code> or <code>NoData=255</code>.</p>]]></content:encoded>
            <author>sjzhakj@163.com (Xinyang)</author>
            <category>Land Use Data</category>
        </item>
        <item>
            <title><![CDATA[Global Vector Data Sources and Usage Notes]]></title>
            <link>https://www.ixgis.com/fr/articles/global-vector-data-usage-notes</link>
            <guid>https://www.ixgis.com/fr/articles/global-vector-data-usage-notes</guid>
            <pubDate>Fri, 19 Sep 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Introduces sources of global vector data and download methods. For domestic administrative boundary vectors in China, it is recommended to use administrative boundary data from Tianditu; iXGIS already provides a Tianditu download tool.]]></description>
            <content:encoded><![CDATA[<p>Global vector data refers to geographic data that <strong>covers the world</strong> and represents natural and human features as <strong>points, lines, and polygons</strong>. Common features include:</p>
<ul>
<li>Natural features: coastlines, international boundaries, rivers, lakes, watersheds, marine regions, terrain-derived lines, and more</li>
<li>Human features: national/provincial/municipal administrative boundaries, settlements/place names, transportation features such as roads, railways, routes, ports, and airports, protected areas, and more</li>
</ul>
<p><strong>Common formats/coordinate systems</strong>: Shapefile, GeoPackage, GeoJSON, GeoParquet, and similar formats. Most datasets are published in WGS84 (EPSG:4326).
<strong>Scale/detail</strong>: detail is usually described by cartographic scale or minimum mapping unit (MMU), for example 1:110M, 1:50M, or 1:10M.</p>
<p><strong>Common authoritative or widely used data sources at a glance</strong></p>
<ul>
<li><strong>Natural Earth (NE)</strong>: global basemap data, including countries, coastlines, rivers, populated places, and more. It is available at 1:110M, 1:50M, and 1:10M, is clean and suitable for cartography, and is released under a public domain license.</li>
<li><strong>OpenStreetMap (OSM)</strong>: crowdsourced global roads, buildings, points of interest, and more. It is detailed and updated quickly, but semantics depend on tags such as <code>highway=*</code>, and quality varies by region. Licensed under ODbL.</li>
<li><strong>GADM</strong>: global administrative boundaries down to county/township levels, with large differences by country and rich attributes. The license is relatively conservative, so review the terms carefully for commercial use.</li>
<li><strong>FAO GAUL / UN-aligned boundaries</strong>: administrative boundaries aligned with United Nations conventions, useful for statistics and governance scenarios. Downloads must comply with the usage statement.</li>
<li><strong>EEZ (Exclusive Economic Zones, VLIZ)</strong>: global maritime jurisdiction and sea-area boundaries, commonly used in maritime, fisheries, and ocean planning work.</li>
<li><strong>HydroBASINS / HydroRIVERS (WWF)</strong>: global hierarchical watersheds and river networks, convenient for hydrological and freshwater ecology analysis.</li>
<li><strong>GLWD (Global Lakes &amp; Wetlands)</strong>: global lake and wetland polygon features.</li>
<li><strong>WDPA / WD-OECM (Protected Planet databases)</strong>: global protected-area boundaries and attributes, such as national parks and nature reserves. Licensing and usage statements are strict.</li>
<li><strong>GSHHG</strong>: multi-resolution global coastlines, national boundaries, and rivers, suitable for mapping and coastal analysis.</li>
</ul>
<h2 id="data-sources">Data Sources</h2>
<p>The following table summarizes major <strong>publicly accessible global administrative-boundary vector datasets</strong> to help you choose by accuracy, license, and update frequency.</p>
<table><thead><tr><th>Dataset</th><th>Administrative levels*</th><th>Latest/common version</th><th>Update frequency</th><th>License</th><th>Access method</th></tr></thead><tbody><tr><td><strong>GADM</strong></td><td>ADM 0-4</td><td>v4.1 (2022-07-16)</td><td>Irregular</td><td><strong>CC BY-NC 4.0</strong></td><td>Country-by-country downloads from the official site</td></tr><tr><td><strong>GAUL (FAO)</strong></td><td>ADM 0-2</td><td>2024 Edition</td><td>Annual</td><td>Research/humanitarian use only</td><td>FAO GeoNetwork</td></tr><tr><td><strong>geoBoundaries</strong></td><td>ADM 0-4</td><td>Static snapshot released in 2025-01</td><td>Annual/quarterly</td><td><strong>CC BY 4.0</strong></td><td>Official site/API and HDX bulk downloads</td></tr><tr><td><strong>Natural Earth</strong></td><td>ADM 0-2</td><td>v5.1 (2023-12)</td><td>Irregular</td><td><strong>Public Domain</strong></td><td>1:10M/50M/110M ZIP packages</td></tr><tr><td><strong>OCHA COD-AB / HDX</strong></td><td>ADM 0-4</td><td>Dynamic</td><td>Continuous</td><td>Mostly <strong>CC BY 4.0</strong></td><td>Country data packages on HDX</td></tr><tr><td><strong>OpenStreetMap (OSM)</strong></td><td>ADM 0-8</td><td>Real time</td><td><strong>Daily</strong></td><td><strong>ODbL 1.0</strong></td><td>Geofabrik Shapefile/PBF regional packages</td></tr><tr><td><strong>Esri Boundaries</strong></td><td>ADM 0-1</td><td>Updated 2024-09</td><td>Continuous</td><td><strong>Esri proprietary</strong></td><td>Direct ArcGIS Online access or local packages</td></tr></tbody></table>
<p><strong>Dataset characteristics and selection guidance</strong></p>
<ol>
<li><strong>Publication-quality cartography and lightweight visualization</strong>
Prefer <strong>Natural Earth</strong>. It is public domain, has no copyright burden, and the 1:10M package is only several dozen MB. If you need vector coastlines, capital points, maritime dispute lines, and similar features, they can also be downloaded together. <a href="https://www.naturalearthdata.com/downloads/10m-cultural-vectors/10m-admin-0-countries/?utm_source=chatgpt.com">naturalearthdata.com</a></li>
<li><strong>Academic/research analysis</strong>
<ul>
<li><strong>GADM</strong>: deep administrative hierarchy and detailed shapes, useful for statistical analysis. However, commercial use is prohibited, and some island boundaries have gaps. <a href="https://gadm.org/data.html?utm_source=chatgpt.com">gadm.org</a></li>
<li><strong>GAUL</strong>: maintained by FAO and aligned with UN official boundaries. New versions have been released annually in recent years, making it suitable for agriculture and food-security models. A usage statement is required. <a href="https://www.fao.org/hih-geospatial-platform/news/detail/now-available--the-global-administrative-unit-layers-(gaul)-dataset---2024-edition/en?utm_source=chatgpt.com">FAO Home</a></li>
</ul>
</li>
<li><strong>Open-source engineering or commercial products</strong>
<ul>
<li><strong>geoBoundaries</strong>: CC BY and usable commercially. It provides both high-precision original data and simplified CGAZ data, and preserves multiple versions for disputed areas such as De facto and US DoS views. <a href="https://www.geoboundaries.org/?utm_source=chatgpt.com">geoboundaries.org</a></li>
<li><strong>OSM / Geofabrik</strong>: if a project needs daily updates or administrative communities down to street level, OSM relations can be used directly. Pay attention to ODbL share-alike requirements for derived databases. <a href="https://www.geofabrik.de/data/download.html?utm_source=chatgpt.com">geofabrik.de</a></li>
</ul>
</li>
<li><strong>Humanitarian relief and disaster response</strong>
<ul>
<li><strong>OCHA COD-AB</strong> (Common Operational Dataset): official boundaries from national governments or UN country offices. These datasets often include P-codes, making them convenient for joining with population or disaster-location data. <a href="https://data.humdata.org/dataset?vocab_Topics=administrative+boundaries-divisions&amp;utm_source=chatgpt.com">data.humdata.org</a></li>
</ul>
</li>
</ol>
<h2 id="natural-earth-dataset">Natural Earth Dataset</h2>
<p>Natural Earth is a public domain map dataset designed primarily for cartography and visualization rather than high-precision GIS analysis. It is available at 1:10M, 1:50M, and 1:110M scales.</p>
<p>It supports multiple country POV versions, and the boundaries differ between views. Download the version that fits your use case.</p>
<p>Data download page: <a href="https://www.naturalearthdata.com/">Natural Earth - Free vector and raster map data at 1:10m, 1:50m, and 1:110m scales</a></p>
<table><thead><tr><th></th><th>Key information</th></tr></thead><tbody><tr><td><strong>Positioning</strong></td><td>Free public domain global basemap material, intended primarily for cartography and visualization rather than high-precision GIS analysis (<a href="https://gisgeography.com/natural-earth-data-free-gis-public/">GIS Geography</a>)</td></tr><tr><td><strong>Scales</strong></td><td>Three datasets for the same themes: 1:10M, 1:50M, and 1:110M. They are designed to maintain consistent appearance across zoom levels (<a href="https://gisgeography.com/natural-earth-data-free-gis-public/">GIS Geography</a>)</td></tr><tr><td><strong>Categories</strong></td><td><strong>Cultural</strong>: countries/provinces, cities, roads, airports, railways, seaports, disputed areas, and more. <strong>Physical</strong>: land, rivers and lakes, peaks, coastlines, ocean features, vegetation zones, and more. <strong>Raster</strong>: shaded relief, Natural Earth 1/2, ocean bathymetry, cross-blended hypsometric tints, and more (<a href="https://gisgeography.com/natural-earth-data-free-gis-public/">GIS Geography</a>)</td></tr><tr><td><strong>Data formats</strong></td><td>Themes are packaged as <strong>ESRI Shapefile</strong>; rasters are GeoTIFF. The official site also provides a <strong>Quick-start kit</strong> with QGIS/ArcMap styles for immediate use (<a href="https://www.naturalearthdata.com/downloads/?utm_source=chatgpt.com">naturalearthdata.com</a>)</td></tr><tr><td><strong>License</strong></td><td>Fully public domain. You may freely copy, modify, and use it commercially; the authors recommend retaining source attribution (<a href="https://gisgeography.com/natural-earth-data-free-gis-public/">GIS Geography</a>)</td></tr><tr><td><strong>Maintainers</strong></td><td>Volunteer community plus NACIS (North American Cartographic Information Society), with core authors including Nathaniel V. Kelso and Tom Patterson</td></tr></tbody></table>
<h3 id="download-data">Download Data</h3>
<ul>
<li>
<p>Global boundaries down to country level, including <strong>258 countries and territories worldwide</strong>, at 1:10M scale using <strong>v5.1</strong> (Dec 2023) data.</p>
<ul>
<li>
<p><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_admin_0_countries.zip">Download countries</a> (4.7 MB) version 5.1.1</p>
<p><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_admin_0_countries_lakes.zip">Download without boundary lakes</a> (4.87 MB) version 5.1.1</p>
</li>
</ul>
</li>
<li>
<p><strong>Global country-level boundaries from different national points of view. The China POV version is broadly consistent with the boundaries in China's public-version vector data.</strong></p>
<ul>
<li><strong><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_admin_0_countries_chn.zip">Download countries (China POV)</a> (4.68 MB) version 5.1.1</strong></li>
</ul>
</li>
<li>
<p>Global boundaries down to states and provinces</p>
<ul>
<li>
<p><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_admin_1_states_provinces.zip">Download states and provinces</a> (14.22 MB) version 5.1.1</p>
<p><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_admin_1_states_provinces_scale_rank.zip">Download as scale ranks</a> (12.83 MB) version 5.1.1</p>
<p><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_admin_1_states_provinces_lakes.zip">Download without large lakes</a> (14.36 MB) version 5.1.1</p>
<p><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_admin_1_states_provinces_lines.zip">Download boundary lines</a> (5.72 MB) version 5.1.0</p>
</li>
</ul>
</li>
<li>
<p>Populated places: city and town points, from Tokyo to Wasilla and from Cairo to Kandahar</p>
<ul>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_populated_places.zip">Download populated places</a> (2.68 MB) version 5.1.2</li>
</ul>
</li>
<li>
<p>Roads</p>
<ul>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_roads.zip">Download roads</a> (8.66 MB) version 5.0.0</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_roads_north_america.zip">Download North America supplement</a> (45.57 MB) version 4.0.0</li>
</ul>
</li>
<li>
<p>Railways</p>
<ul>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_railroads.zip">Download railroads</a> (14.42 MB) version 4.0.0</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_railroads_north_america.zip">Download North America supplement</a> (405.5 KB) version 4.0.0</li>
</ul>
</li>
<li>
<p>Rivers and lake centerlines</p>
<ul>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/physical/ne_10m_rivers_lake_centerlines.zip">Download rivers and lake centerlines</a> (1.98 MB) version 5.0.0</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/physical/ne_10m_rivers_lake_centerlines_scale_rank.zip">Download scale ranks and tapering</a> (2.3 MB) version 5.0.0</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/physical/ne_10m_rivers_australia.zip">Download Australia supplement</a> (401.62 KB) version 5.0.0</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/physical/ne_10m_rivers_europe.zip">Download Europe supplement</a> (584.96 KB) version 5.0.0</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/physical/ne_10m_rivers_north_america.zip">Download North America supplement</a> (3.07 MB) version 5.0.0</li>
</ul>
</li>
<li>
<p>Lakes and reservoirs</p>
<ul>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/physical/ne_10m_lakes.zip">Download lakes</a> (2.24 MB) version 5.0.0</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/physical/ne_10m_lakes_historic.zip">Download historic lakes</a> (27.12 KB) version 5.0.0</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/physical/ne_10m_lakes_pluvial.zip">Download pluvial lakes</a> (214.24 KB) version 4.0.0</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/physical/ne_10m_lakes_australia.zip">Download Australia supplement</a> (96.06 KB) version 5.0.0</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/physical/ne_10m_lakes_europe.zip">Download Europe supplement</a> (180.74 KB) version 5.0.0</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/physical/ne_10m_lakes_north_america.zip">Download North America supplement</a> (656.21 KB) version 5.0.0</li>
</ul>
</li>
<li>
<p>Time zones, including 24+ time zones with local offsets and map color codes</p>
<ul>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_time_zones.zip">Download time zones</a> (1.88 MB) version 4.0.0</li>
</ul>
</li>
<li>
<p>United States only</p>
<ul>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_admin_2_counties.zip">Download counties</a> (1.83 MB) version 5.1.1</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_admin_2_counties_lakes.zip">Download without large lakes</a> (1.85 MB) version 5.1.1</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_admin_2_counties_scale_rank.zip">Download as scale ranks</a> (1.33 MB) version 5.1.1</li>
<li><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_admin_2_counties_scale_rank_minor_islands.zip">Download scale ranks with minor islands</a> (1.33 MB) version 5.1.1</li>
</ul>
</li>
<li>
<p>Full page: <a href="https://www.naturalearthdata.com/downloads/10m-cultural-vectors/">Natural Earth &gt; 1:10m Cultural Vectors - 1:10m, 1:50m, and 1:110m</a></p>
</li>
</ul>
<h3 id="load-data">Load Data</h3>
<p><strong>Upload data</strong></p>
<p>After extracting the downloaded data, upload it to Cloud Resource Manager. The software recognizes the vector data formats and prompts the user to import the data as the default <code>pgv</code> format or keep the existing <code>shp</code> format.</p>
<p><strong>Load data</strong></p>
<p>Select the uploaded <code>ne_10m_time_zones.pgv</code> data. The Resource Manager dynamic toolbar will show available operations such as <code>Download</code>, <code>Delete</code>, <strong><code>Load</code></strong>, and <code>Rename</code>. Select <code>Load</code> to load the data into the current project.</p>
<h3 id="essential-notes">Essential Notes</h3>
<p>When using Natural Earth or other vector datasets that contain China's boundaries, you must pay special attention to boundary accuracy. Except for <strong><a href="https://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_admin_0_countries_chn.zip">Download countries (China POV)</a> (4.68 MB) version 5.1.1</strong>, other vector datasets contain multiple compilation errors in China's boundaries. Typical examples include Nanggarze County, Lhozhag County, <a href="http://www.cuona.gov.cn/zjcn/">Cuona City</a>, and <a href="http://www.motuo.gov.cn/mtx/zjmt/202407/82b36ef5257f4c2c98bfa06db2d121b1.shtml">Medog County</a>.</p>
<p>Use China's public-version 1:1,000,000 vector data to replace China-region data from these foreign sources. The simplest approach is to use a clipping tool to remove the China portion from Natural Earth data, then replace it with the correct data.</p>
<h3 id="processing-workflow">Processing Workflow</h3>
<ol>
<li>
<p>Delete the China, Hong Kong, and related features from the global vector data.</p>
</li>
<li>
<p>Use China's land-area polygon vector data to erase the corresponding region from the global vector data. In the toolbox, open <code>Analysis Tools &gt; Overlay Analysis &gt; Erase</code>.</p>
</li>
<li>
<p>Merge the erased global vector data with the China land-area polygon vector data. Use <code>GIS Toolbox &gt; Analysis Tools &gt; Overlay Analysis &gt; Union</code> to combine the two files.</p>
</li>
</ol>
<h2 id="gaul-data-source">GAUL Data Source</h2>
<p>The GAUL data source is maintained by the Geospatial Unit of the Food and Agriculture Organization of the United Nations (FAO). It is aligned with UN official boundaries, has released new versions annually in recent years, and is suitable for agriculture and food-security models.</p>
<table><thead><tr><th>Key point</th><th>Description</th></tr></thead><tbody><tr><td><strong>Maintainer</strong></td><td>Geospatial Unit, Food and Agriculture Organization of the United Nations (FAO)</td></tr><tr><td><strong>Boundary principle</strong></td><td>Fully follows the current official boundaries of the United Nations Cartographic Section (UNCS); disputed areas retain a <code>UN view</code> attribute flag</td></tr><tr><td><strong>Levels</strong></td><td><strong>Level 0</strong> (L0): countries/territories. <strong>Level 1</strong> (L1): first-level administrative units such as provinces and states. <strong>Level 2</strong> (L2): second-level administrative units such as counties and districts</td></tr><tr><td><strong>Latest version</strong></td><td><strong>GAUL 2024</strong>, released on 2025-04-08 (<a href="https://www.fao.org/hih-geospatial-platform/news/detail/now-available--the-global-administrative-unit-layers-(gaul)-dataset---2024-edition/en">FAO Home</a>)</td></tr><tr><td><strong>Release cadence</strong></td><td>Annual releases since 2023, such as 2023 and 2024, with timely updates against UN annual boundary bulletins</td></tr><tr><td><strong>Formats</strong></td><td>Shapefile (WGS 84) and GeoPackage; globally seamless and topologically consistent, with a unique <code>GAUL_CODE</code></td></tr><tr><td><strong>License</strong></td><td><strong>Non-commercial</strong> (research/humanitarian use only). Users must accept the GAUL Data License and complete the online declaration</td></tr></tbody></table>
<h3 id="level-1-and-level-2-data-description-and-downloads">Level 1 and Level 2 Data Description and Downloads</h3>
<table><thead><tr><th></th><th><strong>GAUL 2024 Level 1</strong></th><th><strong>GAUL 2024 Level 2</strong></th></tr></thead><tbody><tr><td><strong>Platform URL</strong></td><td><a href="https://data.apps.fao.org/catalog/dataset/60b23906-f21a-49ef-8424-f3645e70264e">Download page</a></td><td><a href="https://data.apps.fao.org/catalog/iso/34f97afc-6218-459a-971d-5af1162d318a">Download page</a></td></tr><tr><td><strong>Administrative level</strong></td><td>First-level administrative units such as provinces and states</td><td>Second-level administrative units such as counties and districts</td></tr><tr><td><strong>Coverage</strong></td><td>249 countries/territories and 6,741 L1 units</td><td>240 countries/territories and about 55,000 L2 units</td></tr><tr><td><strong>Coordinate system</strong></td><td>WGS 84 (EPSG:4326), geometries corrected for seamless topology</td><td>Same as left</td></tr><tr><td><strong>Core fields</strong></td><td><code>GAUL0_CODE</code> / <code>GAUL1_CODE</code>, <code>GAUL1_NAME</code>, <code>ISO3_CODE</code>, <code>DISP_AREA</code> for disputed-area markers, and more</td><td>Adds <code>GAUL2_CODE</code> and <code>GAUL2_NAME</code> to the fields on the left</td></tr><tr><td><strong>File form</strong></td><td>Shapefile (ZIP about 120 MB) and GeoPackage (about 95 MB)</td><td>Shapefile (ZIP about 650 MB) and GeoPackage (about 510 MB)</td></tr><tr><td><strong>Release date</strong></td><td>2025-04-08</td><td>2025-04-08</td></tr><tr><td><strong>Download address</strong></td><td><a href="https://data.apps.fao.org/catalog/iso/34f97afc-6218-459a-971d-5af1162d318a">Administrative boundaries (Level 1) - GAUL 2024</a></td><td><a href="https://data.apps.fao.org/catalog/dataset/60b23906-f21a-49ef-8424-f3645e70264e">Administrative boundaries (Level 2) - GAUL 2024 dataset</a></td></tr></tbody></table>
<h3 id="essential-notes-1">Essential Notes</h3>
<p>When using the GAUL dataset, you must also pay attention to multiple compilation errors in China's boundaries. In addition to the Natural Earth errors around Nanggarze County, Lhozhag County, <a href="http://www.cuona.gov.cn/zjcn/">Cuona City</a>, and <a href="http://www.motuo.gov.cn/mtx/zjmt/202407/82b36ef5257f4c2c98bfa06db2d121b1.shtml">Medog County</a>, there are also compilation errors near the boundary between Ngari Prefecture and Hotan Prefecture.</p>
<p>Use China's public-version 1:1,000,000 vector data to replace China-region data from these foreign sources. The simplest approach is to use a clipping tool to remove the China portion from Natural Earth data, then replace it with the correct data.</p>]]></content:encoded>
            <author>sjzhakj@163.com (Xinyang)</author>
            <category>Vector Data</category>
        </item>
        <item>
            <title><![CDATA[Public-Version 1:1,000,000 Basic Geographic Information Data Guide]]></title>
            <link>https://www.ixgis.com/fr/articles/public-version-1-1000000-basic-geographic-information-data-guide</link>
            <guid>https://www.ixgis.com/fr/articles/public-version-1-1000000-basic-geographic-information-data-guide</guid>
            <pubDate>Fri, 19 Sep 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[The national public-version 11,000,000 scale. The overall currency of the dataset is 2019. The data uses the China Geodetic Coordinate System 2000, the 1985 National Height Datum, and geographic coordinates.]]></description>
            <content:encoded><![CDATA[<p>The national public-version 1:1,000,000 basic geographic information data (2021) covers China's land area and major islands, including Taiwan Island, Hainan Island, Diaoyu Dao, the South China Sea islands, and their adjacent waters. It contains 77 map sheets at 1:1,000,000 scale. The overall currency of the dataset is 2019. The data uses the China Geodetic Coordinate System 2000, the 1985 National Height Datum, and geographic coordinates.</p>
<p>To meet public demand for geographic information data resources, the National Geographic Information Resource Catalog Service System, authorized by the Ministry of Natural Resources, provides free downloads of all national 1:1,000,000 public-version feature layers. The downloaded data is distributed by standard 1:1,000,000 map sheets. It includes nine datasets: hydrography, settlements and facilities, transportation, pipelines, boundaries and administrative divisions, landform and soil, vegetation, place names, and annotations. Spatial relationships between features and related attribute information are preserved.</p>
<p>Data download page: <a href="https://www.webmap.cn/commres.do?method=result100W">1:1,000,000 Public-Version Basic Geographic Information Data</a></p>
<admonition type="important"><p>The downloadable files are vector data, not final maps. Their visual appearance may differ from a symbolized final map. When using this data to compile maps, users must strictly follow the relevant provisions of the <a href="https://www.gov.cn/zhengce/2015-12/14/content_5023591.htm">Regulations on Map Management</a>. If the compiled map will be released to the public, the user must also complete the <a href="https://www.fmprc.gov.cn/web/wjb_673085/zzjg_673183/bjhysws_674671/bhflfg/dtdmxgfl/202303/P020230313586143347764.pdf">map review</a> process according to law.</p></admonition>
<h2 id="data-introduction">Data Introduction</h2>
<h3 id="result-data-organization">Result Data Organization</h3>
<p>The national public-version 1:1,000,000 vector data (2021) includes nine datasets: hydrography, settlements and facilities, transportation, pipelines, boundaries and administrative divisions, landform and soil, vegetation, place names, and annotations.</p>
<p>Layer names use four characters. The first character represents the data category, the second and third characters are abbreviations of the data content, and the fourth character represents the geometry type.</p>
<h3 id="map-sheets">Map Sheets</h3>
<p>The subdivision and numbering of national basic-scale topographic maps are fixed. They are described in detail in the standard <strong>Subdivision and Numbering for National Basic Scale Topographic Maps</strong> (GB/T 13989-2012). Download page: <a href="https://openstd.samr.gov.cn/bzgk/gb/newGbInfo?hcno=30799A9AF9BFA98E77D21ABC5F0984E2">National Standard | Subdivision and Numbering for National Basic Scale Topographic Maps, GB/T 13989-2012</a></p>
<p>For 1:1,000,000 scale, the map-sheet subdivision is as follows:</p>
<h2 id="download-data">Download Data</h2>
<h3 id="user-registration">User Registration</h3>
<p>Step 1: Register</p>
<p>On the homepage of the <a href="http://www.webmap.cn/main.do?method=index">National Geographic Information Resource Catalog Service System</a>, click the <code>Register</code> option to create a user account.</p>
<p>Enter the required user information in the pop-up page to complete registration.</p>
<p>After registration, activate the account through the registered email address.</p>
<p>Step 2: Log in</p>
<p>After account activation, return to the login page and sign in.</p>
<p>Step 3: Maintain personal information</p>
<p>After logging in, go to the homepage and click <code>Personal Center</code>. On the personal information page, update basic information, change the password, and complete other account details as needed.</p>
<h3 id="download-data-1">Download Data</h3>
<p>Use the locating tool to search by administrative area, road name, hydrographic feature name, place name, or map sheet.</p>
<p>For example, search by administrative area and locate Hebei Province.</p>
<p>Click the successful query result on the right. Four standard map sheets will appear. The table lists the sheet number, production time, geodetic datum, and data format. Add all of them to the result cart.</p>
<p>Then go to the result cart and click checkout.</p>
<p>On the review page, a special-service selection appears at the bottom. You can ignore it and submit the order directly.</p>
<p>After submitting the order, a data download button appears on the order page. When downloading data, you need to fill in information on two pages. Be sure to complete the information accurately rather than entering arbitrary values.</p>
<h2 id="use-data">Use Data</h2>
<h3 id="data-overview">Data Overview</h3>
<p>The downloaded data is stored in GDB format, a proprietary ArcGIS format. Each file is a ZIP archive named after the map-sheet number.</p>
<p>Here is an example: <a href="https://www.ixgis.com/fr/download/A49.gdb.zip">download the sample</a>.</p>
<p>You can inspect the archive contents with decompression software, but because it is a database file, it cannot be opened directly like a regular document.</p>
<h3 id="data-upload">Data Upload</h3>
<p>Upload the data in ZIP format. iXGIS can directly recognize this data format and convert it to <code>pgv</code> format.</p>
<h3 id="data-loading">Data Loading</h3>
<p>Load the data.</p>
<p>After loading, the dataset is available in the current project.</p>
<h3 id="layer-content">Layer Content</h3>
<p>The mapping between layer names and features is as follows:</p>
<ul>
<li><strong>Naming rule</strong>: layer names use four characters. The first character corresponds to the feature category, such as C, H, or R. The second and third characters are content abbreviations, such as PT for survey control and HY for hydrography. The fourth character corresponds to the geometry type: P for point, L for line, and A for polygon.</li>
<li><strong>Feature categories</strong>: covers nine major categories based on the original description: positioning foundation (C), hydrography (H), settlements and facilities (R), transportation (L), pipelines (P), boundaries and administrative divisions (B), landform and soil (T), vegetation (V), and place names and annotations (A).</li>
</ul>
<table><thead><tr><th style="text-align:center">Layer name</th><th style="text-align:center">Layer code</th><th style="text-align:center">Feature category</th><th style="text-align:center">Geometry type</th><th style="text-align:left">Main feature content</th></tr></thead><tbody><tr><td style="text-align:center">Survey control points</td><td style="text-align:center">CPTP</td><td style="text-align:center">Positioning foundation (C)</td><td style="text-align:center">Point</td><td style="text-align:left">Survey control points</td></tr><tr><td style="text-align:center">Coordinate grid</td><td style="text-align:center">CPTL</td><td style="text-align:center">Positioning foundation (C)</td><td style="text-align:center">Line</td><td style="text-align:left">Neatlines and coordinate grid</td></tr><tr><td style="text-align:center">Hydrography (polygon)</td><td style="text-align:center">HYDA</td><td style="text-align:center">Hydrography (H)</td><td style="text-align:center">Polygon</td><td style="text-align:left">Lakes, reservoirs, double-line rivers and ditches, and similar features</td></tr><tr><td style="text-align:center">Hydrography (line)</td><td style="text-align:center">HYDL</td><td style="text-align:center">Hydrography (H)</td><td style="text-align:center">Line</td><td style="text-align:left">Single-line rivers, ditches, river structure lines, and similar features</td></tr><tr><td style="text-align:center">Hydrography (point)</td><td style="text-align:center">HYDP</td><td style="text-align:center">Hydrography (H)</td><td style="text-align:center">Point</td><td style="text-align:left">Springs, wells, and similar features</td></tr><tr><td style="text-align:center">Hydrographic associated facilities (polygon)</td><td style="text-align:center">HFCA</td><td style="text-align:center">Hydrography (H)</td><td style="text-align:center">Polygon</td><td style="text-align:left">Dry beaches, tidal flats, danger areas, reefs, and similar features</td></tr><tr><td style="text-align:center">Hydrographic associated facilities (line)</td><td style="text-align:center">HFCL</td><td style="text-align:center">Hydrography (H)</td><td style="text-align:center">Line</td><td style="text-align:left">Drying lines, tidal channels, high-water lines, flow direction, dikes, sluices, dams, and similar features</td></tr><tr><td style="text-align:center">Hydrographic associated facilities (point)</td><td style="text-align:center">HFCP</td><td style="text-align:center">Hydrography (H)</td><td style="text-align:center">Point</td><td style="text-align:left">Underground river entrances/exits, culverts, reefs, sluices, dams, and similar features</td></tr><tr><td style="text-align:center">Settlements (polygon)</td><td style="text-align:center">RESA</td><td style="text-align:center">Settlements and facilities (R)</td><td style="text-align:center">Polygon</td><td style="text-align:left">Blocks, high-rise building areas, vacant land, and similar features</td></tr><tr><td style="text-align:center">Settlements (line)</td><td style="text-align:center">RESL</td><td style="text-align:center">Settlements and facilities (R)</td><td style="text-align:center">Line</td><td style="text-align:left">Houses, cave dwellings, and similar features</td></tr><tr><td style="text-align:center">Settlements (point)</td><td style="text-align:center">RESP</td><td style="text-align:center">Settlements and facilities (R)</td><td style="text-align:center">Point</td><td style="text-align:left">Houses, sheds, cave dwellings, yurts, grazing points, and similar features</td></tr><tr><td style="text-align:center">Facilities (polygon)</td><td style="text-align:center">RFCA</td><td style="text-align:center">Settlements and facilities (R)</td><td style="text-align:center">Polygon</td><td style="text-align:left">Industrial/mining, agricultural, public service, and similar facilities</td></tr><tr><td style="text-align:center">Facilities (line)</td><td style="text-align:center">RFCL</td><td style="text-align:center">Settlements and facilities (R)</td><td style="text-align:center">Line</td><td style="text-align:left">Industrial/mining features, city walls, fences, and similar features</td></tr><tr><td style="text-align:center">Facilities (point)</td><td style="text-align:center">RFCP</td><td style="text-align:center">Settlements and facilities (R)</td><td style="text-align:center">Point</td><td style="text-align:left">Industrial/mining, agricultural, public service, scenic/historic, religious, scientific observation, and similar facilities</td></tr><tr><td style="text-align:center">Railways</td><td style="text-align:center">LRRL</td><td style="text-align:center">Transportation (L)</td><td style="text-align:center">Line</td><td style="text-align:left">Standard-gauge railways, narrow-gauge railways, metro, light rail, and similar features</td></tr><tr><td style="text-align:center">Roads</td><td style="text-align:center">LRDL</td><td style="text-align:center">Transportation (L)</td><td style="text-align:center">Line</td><td style="text-align:left">National roads, provincial roads, county roads, township roads, dedicated roads, other roads, streets, rural roads, and similar features</td></tr><tr><td style="text-align:center">Transportation associated facilities (line)</td><td style="text-align:center">LFCL</td><td style="text-align:center">Transportation (L)</td><td style="text-align:center">Line</td><td style="text-align:left">Vehicle bridges, pedestrian bridges, tunnels, wharves, ferries, and similar features</td></tr><tr><td style="text-align:center">Transportation associated facilities (point)</td><td style="text-align:center">LFCP</td><td style="text-align:center">Transportation (L)</td><td style="text-align:center">Point</td><td style="text-align:left">Stations, road signs, navigation aids, airports, and similar features</td></tr><tr><td style="text-align:center">Pipelines (line)</td><td style="text-align:center">PIPL</td><td style="text-align:center">Pipelines (P)</td><td style="text-align:center">Line</td><td style="text-align:left">Power transmission lines, communication lines, oil/gas/water trunk pipelines, and similar features</td></tr><tr><td style="text-align:center">Pipelines (point)</td><td style="text-align:center">PIPP</td><td style="text-align:center">Pipelines (P)</td><td style="text-align:center">Point</td><td style="text-align:left">Substations and similar features</td></tr><tr><td style="text-align:center">Administrative boundaries (polygon)</td><td style="text-align:center">BOUA</td><td style="text-align:center">Boundaries and administrative divisions (B)</td><td style="text-align:center">Polygon</td><td style="text-align:left">Administrative areas at all levels</td></tr><tr><td style="text-align:center">Administrative boundaries (line)</td><td style="text-align:center">BOUL</td><td style="text-align:center">Boundaries and administrative divisions (B)</td><td style="text-align:center">Line</td><td style="text-align:left">Boundary lines at all levels</td></tr><tr><td style="text-align:center">Administrative boundaries (point)</td><td style="text-align:center">BOUP</td><td style="text-align:center">Boundaries and administrative divisions (B)</td><td style="text-align:center">Point</td><td style="text-align:left">Boundary markers and monuments</td></tr><tr><td style="text-align:center">Regional boundaries (polygon)</td><td style="text-align:center">BRGA</td><td style="text-align:center">Boundaries and administrative divisions (B)</td><td style="text-align:center">Polygon</td><td style="text-align:left">Natural/cultural regions, special areas, development zones, bonded zones, and similar areas</td></tr><tr><td style="text-align:center">Regional boundaries (line)</td><td style="text-align:center">BRGL</td><td style="text-align:center">Boundaries and administrative divisions (B)</td><td style="text-align:center">Line</td><td style="text-align:left">Boundaries of natural/cultural regions, special areas, development zones, and bonded zones</td></tr><tr><td style="text-align:center">Regional boundaries (point)</td><td style="text-align:center">BRGP</td><td style="text-align:center">Boundaries and administrative divisions (B)</td><td style="text-align:center">Point</td><td style="text-align:left">Boundary points for unclear natural/cultural regions, special areas, development zones, and bonded zones</td></tr><tr><td style="text-align:center">Landform and soil (polygon)</td><td style="text-align:center">TERA</td><td style="text-align:center">Landform and soil (T)</td><td style="text-align:center">Polygon</td><td style="text-align:left">Sandy land, snow/ice areas, geological disaster landforms, and similar features</td></tr><tr><td style="text-align:center">Landform and soil (line)</td><td style="text-align:center">TERL</td><td style="text-align:center">Landform and soil (T)</td><td style="text-align:center">Line</td><td style="text-align:left">Contours, gullies, ridges, and similar features</td></tr><tr><td style="text-align:center">Landform and soil (point)</td><td style="text-align:center">TERP</td><td style="text-align:center">Landform and soil (T)</td><td style="text-align:center">Point</td><td style="text-align:left">Elevation annotation points, peaks, pillars, funnels, and similar features</td></tr><tr><td style="text-align:center">Vegetation (polygon)</td><td style="text-align:center">VEGA</td><td style="text-align:center">Vegetation (V)</td><td style="text-align:center">Polygon</td><td style="text-align:left">Cropland, gardens/orchards, forest land, grassland, urban green space, and similar features</td></tr><tr><td style="text-align:center">Vegetation (line)</td><td style="text-align:center">VEGL</td><td style="text-align:center">Vegetation (V)</td><td style="text-align:center">Line</td><td style="text-align:left">Firebreaks, tree rows, and similar features</td></tr><tr><td style="text-align:center">Vegetation (point)</td><td style="text-align:center">VEGP</td><td style="text-align:center">Vegetation (V)</td><td style="text-align:center">Point</td><td style="text-align:left">Scattered trees, isolated trees, and similar features</td></tr><tr><td style="text-align:center">Settlement place names (point)</td><td style="text-align:center">AGNP</td><td style="text-align:center">Place names and annotations (A)</td><td style="text-align:center">Point</td><td style="text-align:left">Administrative place names at all levels and urban/rural settlement names</td></tr><tr><td style="text-align:center">Natural place names (point)</td><td style="text-align:center">AANP</td><td style="text-align:center">Place names and annotations (A)</td><td style="text-align:center">Point</td><td style="text-align:left">Transportation feature names, memorial and historic-site names, mountain names, hydrographic names, maritime region names, natural region names, boundary-marker names, and similar names</td></tr></tbody></table>]]></content:encoded>
            <author>sjzhakj@163.com (Xinyang)</author>
            <category>Public-Version Basic Geographic Information Data</category>
            <category>National Geographic Information Resource Catalog Service System</category>
        </item>
        <item>
            <title><![CDATA[Map Review Approval Number]]></title>
            <link>https://www.ixgis.com/fr/articles/map-review-approval-number</link>
            <guid>https://www.ixgis.com/fr/articles/map-review-approval-number</guid>
            <pubDate>Mon, 01 Sep 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[A map review approval number is a unique number granted after a map has passed technical review and administrative approval by the competent natural resources authority responsible for surveying, mapping, and geographic information before public release. It usually consists of a province abbreviation or national marker, review category code, year, and sequence number, such as Yue GS (2025) No. 001. Obtaining the approval number means the map complies with the requirements of the Regulations on Map Management, the Measures for Map Review Management, and other regulations regarding content correctness, scale accuracy, and handling of confidential information.]]></description>
            <content:encoded><![CDATA[<h2 id="what-is-a-map-review-approval-number">What Is a Map Review Approval Number?</h2>
<p>A map review approval number is a unique number granted after a map has passed technical review and administrative approval by the competent natural resources authority responsible for surveying, mapping, and geographic information before public release. It usually consists of a province abbreviation or national marker, review category code, year, and sequence number, such as <strong>Yue GS (2025) No. 001</strong>. Obtaining the approval number means the map complies with the requirements of the Regulations on Map Management, the Measures for Map Review Management, and other regulations regarding content correctness, scale accuracy, and handling of confidential information.</p>
<p>Reference: <strong><a href="https://www.gov.cn/gongbao/content/2018/content_5271747.htm?utm_source=chatgpt.com">Measures for Map Review Management</a></strong></p>
<p><a href="https://www.zhanjiang.gov.cn/nr/gkmlpt/content/2/2029/post_2029107.html?utm_source=chatgpt.com#889">Public notice of map review administrative approvals from January to March 2025</a></p>
<h2 id="when-do-you-need-to-apply-for-a-map-review-approval-number">When Do You Need to Apply for a Map Review Approval Number?</h2>
<p>According to Article 15 of the Regulations on Map Management, maps released to the public must be submitted to the surveying and mapping geographic information administrative authority with review authority. If an approved map is edited, including enlargement, reduction, cropping, or adding annotations, and then released publicly, it should also be submitted for review again.</p>
<p>Reference: <a href="https://www.csgpc.org/detail/19234.html">Nine types of questions about map submission for review - Chinese Society for Geodesy Photogrammetry and Cartography</a></p>
<table><thead><tr><th>Publicly released?</th><th>Map type (examples)</th><th>Review required?</th></tr></thead><tbody><tr><td>Yes</td><td>Printed publications such as textbooks, paper illustrations, magazines, brochures, exhibition boards, and public reports</td><td>Required</td></tr><tr><td>Yes</td><td>Internet map services such as websites, apps, WebGIS, downloadable data packages, vehicle navigation, and visualization dashboards</td><td>Required</td></tr><tr><td>Yes</td><td>Existing standard maps that are cropped, scaled, or annotated before public release</td><td>Must be submitted again</td></tr><tr><td>No</td><td>Internal enterprise/research use, teaching sketches, and personal study notes</td><td>Review may be exempted, but they must not be publicly distributed without authorization</td></tr></tbody></table>
<h2 id="how-to-apply">How to Apply</h2>
<p><strong>Determine the competent authority</strong></p>
<ul>
<li>National, cross-provincial or cross-regional maps, or maps involving foreign affairs: apply to the <strong>Ministry of Natural Resources</strong> at the national level.</li>
<li>Provincial and smaller-scope maps: apply to the natural resources department or bureau of the relevant province, autonomous region, or municipality.</li>
</ul>
<p><strong>Prepare materials</strong> (submitted online or at a service window)</p>
<table><thead><tr><th>Material</th><th>Description</th></tr></thead><tbody><tr><td>Public-version map review application form</td><td>Fill in the official template online, including contact information for the handler</td></tr><tr><td>Sample map or service link for review</td><td>Two paper sample maps plus electronic files; internet services must provide a test account or access URL</td></tr><tr><td>Data and technical description</td><td>Data sources, scale, projection, accuracy, and handling of confidential information</td></tr><tr><td>Qualification documents</td><td>Business license, surveying and mapping qualification certificate, entrusted contract, or similar documents</td></tr></tbody></table>
<p><strong>Review process and timeline</strong></p>
<ul>
<li><strong>Acceptance</strong>: the service window issues a Map Technical Review Notice within one working day. <a href="https://www.gov.cn/bumenfuwu/2012-11/13/content_2598954.htm?utm_source=chatgpt.com">Government of the People's Republic of China</a></li>
<li><strong>Technical review</strong>: the map technical review center checks coordinates, national boundaries, confidential content, and related items.</li>
<li><strong>Decision</strong>: regular public-version maps are decided within <strong>20 working days</strong>; simpler cases such as maps referencing standard maps may take <strong>7 working days or immediate review</strong>.</li>
<li><strong>Collect approval document and approval number</strong>: after approval, collect the Map Review Opinion Letter and obtain the map review approval number.</li>
</ul>
<p><strong>Marking and follow-up obligations</strong></p>
<ul>
<li><strong>Printed/electronic publications</strong>: mark the approval number on the copyright page or in a prominent position.</li>
<li><strong>Internet maps</strong>: continuously display the approval number in the lower-left corner of the page without blocking it.</li>
<li><strong>Validity period</strong>: approval numbers for internet maps are <strong>valid for 2 years</strong> and must be resubmitted after expiration. Newly added annotation content must be filed every 6 months.</li>
</ul>
<h2 id="preparation-before-applying">Preparation Before Applying</h2>
<p>For maps involving national boundaries, the map content must comply with the <a href="https://www.gov.cn/gongbao/content/2023/content_5752310.htm">Specifications for Content Representation on Public Maps</a>.</p>
<p><strong>The standard sample maps referenced in map review</strong> specify the following:</p>
<blockquote>
<ol>
<li>
<p>Standard depiction maps for China's national boundary line</p>
</li>
<li>
<p>The Standard Sample Map for Drawing China's National Boundary Line at 1:1,000,000, issued by the Ministry of Foreign Affairs and the National Administration of Surveying and Mapping in 2001, applies to the review of national boundary lines on maps with scales equal to or smaller than 1:1,000,000 and larger than 1:4,000,000.</p>
</li>
<li>
<p>The 1:4,000,000 Topographic Map of the People's Republic of China applies to the review of national boundary lines on maps with scales smaller than 1:4,000,000.</p>
</li>
<li>
<p>Standard depiction maps for provincial administrative boundaries in China</p>
</li>
<li>
<p>The Atlas of Standard Depiction Maps for Provincial Administrative Boundaries of the People's Republic of China at 1:1,000,000 and the Standard Depiction Map for Provincial Administrative Boundaries of the People's Republic of China at 1:4,000,000, issued by the Ministry of Civil Affairs and the National Administration of Surveying and Mapping in 2004, are the standards for depicting provincial administrative boundaries on all types of maps.</p>
</li>
<li>
<p>The Atlas of Standard Depiction Maps for Provincial Administrative Boundaries of the People's Republic of China at 1:1,000,000 applies to maps with scales equal to or smaller than 1:1,000,000 and larger than 1:4,000,000. The Standard Depiction Map for Provincial Administrative Boundaries of the People's Republic of China at 1:4,000,000 applies to maps with scales equal to or smaller than 1:4,000,000.</p>
</li>
<li>
<p>Standard maps for depicting national boundaries of countries around the world</p>
</li>
</ol>
<p>The Sample Map for Drawing National Boundaries of Countries Around the World, issued by the National Administration of Surveying and Mapping in 2007, applies to the review of national boundaries, regional boundaries, military demarcation lines, ceasefire lines, and other boundaries around the world.</p>
</blockquote>
<p>Original link: <a href="https://www.zrzyst.cn/qtck/370.jhtml">Map Technical Review Center, Ministry of Natural Resources</a></p>
<p>You can first use the <a href="http://bzdt.ch.mnr.gov.cn/index.html"><strong>Standard Map Service System</strong></a> to check whether national boundaries and sensitive annotations are correct, reducing the number of revision rounds from the source.</p>
<h2 id="frequently-asked-questions">Frequently Asked Questions</h2>
<table><thead><tr><th>Question</th><th>Answer</th></tr></thead><tbody><tr><td><strong>1. Do I need to submit a map for review if I directly use a standard map provided by the Ministry of Natural Resources website?</strong></td><td>No duplicate review is required, but you must keep the original map intact and mark the map's existing approval number in a prominent position. (<a href="https://www.csgpc.org/index.php/detail/24825.html?utm_source=chatgpt.com">csgpc.org</a>)</td></tr><tr><td><strong>2. Do I need an approval number for a small-scale schematic map in a paper?</strong></td><td>If the paper will be published through a public channel, it is considered public release and requires a map review approval number. (<a href="https://www.csgpc.org/detail/19234.html?utm_source=chatgpt.com">csgpc.org</a>)</td></tr><tr><td><strong>3. Is there a fee for review?</strong></td><td>At present, map review itself does <strong>not charge an administrative approval fee</strong>, but the applicant bears costs such as sample-map printing and delivery.</td></tr><tr><td><strong>4. Can an approval number become invalid because national boundaries change?</strong></td><td>After national boundaries or administrative divisions change, the map content corresponding to the original approval number becomes invalid and must be resubmitted for review with a new number.</td></tr><tr><td><strong>5. What are the consequences of publicly releasing a map without an approval number?</strong></td><td>The natural resources authority may order corrections, impose fines, or remove the product from circulation. In serious cases, criminal liability may be pursued under the Surveying and Mapping Law and the Regulations on Map Management.</td></tr><tr><td><strong>6. Can I entrust a third party to handle the application?</strong></td><td>Yes. You need to provide a power of attorney and ensure the agent has the corresponding surveying and mapping qualification or has signed a contract with a qualified organization.</td></tr></tbody></table>
<p>For more questions, see <a href="https://www.csgpc.org/index.php/detail/24825.html?utm_source=chatgpt.com">Map use and map review: the questions you care about are all here - Chinese Society for Geodesy Photogrammetry and Cartography</a></p>]]></content:encoded>
            <author>sjzhakj@163.com (Xinyang)</author>
            <category>Map Review Approval Number</category>
        </item>
    </channel>
</rss>