<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Quick Export (MBTiles) Issues in ArcGIS Data Interoperability Ques.</title>
    <link>https://community.esri.com/t5/arcgis-data-interoperability-ques/quick-export-mbtiles-issues/m-p/1377041#M225</link>
    <description>&lt;P&gt;I'm new to working in ArcGIS, and have been trying to transform data from a REST API into an MBTiles-format vector tile package.&amp;nbsp; However, I've been running into a few issues through the process, and haven't been able to find solutions from what's documented online.&amp;nbsp; For context, I'm using the ArcGIS Pro trial (so Pro Advanced), version 3.2.1 on Windows 11.&lt;/P&gt;&lt;P&gt;I've added the layer via `Data from Path`, and have been attempting to export it with the Quick Export tool.&amp;nbsp; That layer's data is filtered with a definition query, reducing its size from ~173k entries to ~3k as a proof of concept and to ensure only valid geometry is included.&amp;nbsp; From there, I've selected the layer (with "Use the filtered records" option) as my input layer, configured my MBTiles output accordingly (e.g. zoom range of 4-8, metadata beyond default values, and so forth), and run the export.&lt;/P&gt;&lt;P&gt;The first issue that I run into in the export is a warning, which reports that:&lt;/P&gt;&lt;P&gt;None of the layers to be read contain features in the selection set. Therefore all the features in the layers will be read&lt;BR /&gt;&amp;nbsp;The process continues to run with ~170k features, so oddly missing around 3k from the original dataset, but otherwise generally what one would expect from the warning.&amp;nbsp; I've attempted the same thing with no filtering on the dataset, other export formats (e.g. JSON), and even a layer from a local file (a subset of the dataset exported in KML format) rather than a REST API, and have continued to see the same results.&lt;/P&gt;&lt;P&gt;After this warning and switch to the full dataset, the debug log reveals some other issues with the MBTiles export, which may or may not be a result of that initial warning.&amp;nbsp; The most substantial ones are related to the tileset's zoom levels, appearing to revert the tileset's zoom levels to the defaults (0-5) after being unable to find zoom level options for the input layer:&lt;/P&gt;&lt;P&gt;MBTILES_MVT writer: Feature Type Parameter 'mvt_min_zoom' has not been set for feature type 'L0National_Forest_System_Roads'. Using default value '0'&lt;BR /&gt;MBTILES_MVT writer: Feature Type Parameter 'mvt_max_zoom' has not been set for feature type 'L0National_Forest_System_Roads'. Using default value '5'&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;From this point, the tileset appears to generally be written as expected with the 0-5 zoom change and unfiltered data.&amp;nbsp; Some of the higher-zoom tiles might not be being generated correctly, as multiple programs display lower-detail tiles than expected across much of the extent of the dataset, but the underlying SQLite database appears to have its tiles table configured in a reasonable manner, so I'd have to some more digging to get more details.&lt;/P&gt;&lt;P&gt;Is there something I'm missing in my workflow or baseline understanding of the process that would be causing this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A more precise workflow to recreate this:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Add data from path, no additional parameters: &lt;A href="https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_RoadBasic_01/MapServer/0" target="_blank"&gt;https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_RoadBasic_01/MapServer/0&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;Layer properties -&amp;gt; Definition query -&amp;gt; Add query: LOC_ERROR = 'NO ERROR' AND PRIMARY_MAINTAINER =&amp;nbsp;'C - COUNTY, PARISH, BOROUGH'&lt;/LI&gt;&lt;LI&gt;Data Interoperability Tools -&amp;gt; Quick Export&lt;/LI&gt;&lt;LI&gt;Select new layer as input layer from dropdown&lt;/LI&gt;&lt;LI&gt;Output dataset: MVT&lt;/LI&gt;&lt;LI&gt;Parameters -&amp;gt; Zoom levels: Minimum other than 0, maximum other than 5 (e.g. 4-8)&lt;/LI&gt;&lt;LI&gt;Run&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;From this point, relevant debug printouts are visible in View Details -&amp;gt; Messages.&amp;nbsp; Assuming zoom levels of 0-5 and an unfiltered dataset, the tiles would be expected to appear similar to the segment of map in purple (exported via QGIS, which has some small errors in geometry).&amp;nbsp; Instead, the resulting tiles render as shown in yellow.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="JeremyPeplinski_0-1706798508209.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/93432i120CA2E2DA93BADC/image-size/medium?v=v2&amp;amp;px=400" role="button" title="JeremyPeplinski_0-1706798508209.png" alt="JeremyPeplinski_0-1706798508209.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="JeremyPeplinski_3-1706798764172.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/93435iFFA1AF2D043638FD/image-size/medium?v=v2&amp;amp;px=400" role="button" title="JeremyPeplinski_3-1706798764172.png" alt="JeremyPeplinski_3-1706798764172.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Feb 2024 14:47:59 GMT</pubDate>
    <dc:creator>JeremyPeplinski</dc:creator>
    <dc:date>2024-02-01T14:47:59Z</dc:date>
    <item>
      <title>Quick Export (MBTiles) Issues</title>
      <link>https://community.esri.com/t5/arcgis-data-interoperability-ques/quick-export-mbtiles-issues/m-p/1377041#M225</link>
      <description>&lt;P&gt;I'm new to working in ArcGIS, and have been trying to transform data from a REST API into an MBTiles-format vector tile package.&amp;nbsp; However, I've been running into a few issues through the process, and haven't been able to find solutions from what's documented online.&amp;nbsp; For context, I'm using the ArcGIS Pro trial (so Pro Advanced), version 3.2.1 on Windows 11.&lt;/P&gt;&lt;P&gt;I've added the layer via `Data from Path`, and have been attempting to export it with the Quick Export tool.&amp;nbsp; That layer's data is filtered with a definition query, reducing its size from ~173k entries to ~3k as a proof of concept and to ensure only valid geometry is included.&amp;nbsp; From there, I've selected the layer (with "Use the filtered records" option) as my input layer, configured my MBTiles output accordingly (e.g. zoom range of 4-8, metadata beyond default values, and so forth), and run the export.&lt;/P&gt;&lt;P&gt;The first issue that I run into in the export is a warning, which reports that:&lt;/P&gt;&lt;P&gt;None of the layers to be read contain features in the selection set. Therefore all the features in the layers will be read&lt;BR /&gt;&amp;nbsp;The process continues to run with ~170k features, so oddly missing around 3k from the original dataset, but otherwise generally what one would expect from the warning.&amp;nbsp; I've attempted the same thing with no filtering on the dataset, other export formats (e.g. JSON), and even a layer from a local file (a subset of the dataset exported in KML format) rather than a REST API, and have continued to see the same results.&lt;/P&gt;&lt;P&gt;After this warning and switch to the full dataset, the debug log reveals some other issues with the MBTiles export, which may or may not be a result of that initial warning.&amp;nbsp; The most substantial ones are related to the tileset's zoom levels, appearing to revert the tileset's zoom levels to the defaults (0-5) after being unable to find zoom level options for the input layer:&lt;/P&gt;&lt;P&gt;MBTILES_MVT writer: Feature Type Parameter 'mvt_min_zoom' has not been set for feature type 'L0National_Forest_System_Roads'. Using default value '0'&lt;BR /&gt;MBTILES_MVT writer: Feature Type Parameter 'mvt_max_zoom' has not been set for feature type 'L0National_Forest_System_Roads'. Using default value '5'&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;From this point, the tileset appears to generally be written as expected with the 0-5 zoom change and unfiltered data.&amp;nbsp; Some of the higher-zoom tiles might not be being generated correctly, as multiple programs display lower-detail tiles than expected across much of the extent of the dataset, but the underlying SQLite database appears to have its tiles table configured in a reasonable manner, so I'd have to some more digging to get more details.&lt;/P&gt;&lt;P&gt;Is there something I'm missing in my workflow or baseline understanding of the process that would be causing this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A more precise workflow to recreate this:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Add data from path, no additional parameters: &lt;A href="https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_RoadBasic_01/MapServer/0" target="_blank"&gt;https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_RoadBasic_01/MapServer/0&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;Layer properties -&amp;gt; Definition query -&amp;gt; Add query: LOC_ERROR = 'NO ERROR' AND PRIMARY_MAINTAINER =&amp;nbsp;'C - COUNTY, PARISH, BOROUGH'&lt;/LI&gt;&lt;LI&gt;Data Interoperability Tools -&amp;gt; Quick Export&lt;/LI&gt;&lt;LI&gt;Select new layer as input layer from dropdown&lt;/LI&gt;&lt;LI&gt;Output dataset: MVT&lt;/LI&gt;&lt;LI&gt;Parameters -&amp;gt; Zoom levels: Minimum other than 0, maximum other than 5 (e.g. 4-8)&lt;/LI&gt;&lt;LI&gt;Run&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;From this point, relevant debug printouts are visible in View Details -&amp;gt; Messages.&amp;nbsp; Assuming zoom levels of 0-5 and an unfiltered dataset, the tiles would be expected to appear similar to the segment of map in purple (exported via QGIS, which has some small errors in geometry).&amp;nbsp; Instead, the resulting tiles render as shown in yellow.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="JeremyPeplinski_0-1706798508209.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/93432i120CA2E2DA93BADC/image-size/medium?v=v2&amp;amp;px=400" role="button" title="JeremyPeplinski_0-1706798508209.png" alt="JeremyPeplinski_0-1706798508209.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="JeremyPeplinski_3-1706798764172.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/93435iFFA1AF2D043638FD/image-size/medium?v=v2&amp;amp;px=400" role="button" title="JeremyPeplinski_3-1706798764172.png" alt="JeremyPeplinski_3-1706798764172.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Feb 2024 14:47:59 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-data-interoperability-ques/quick-export-mbtiles-issues/m-p/1377041#M225</guid>
      <dc:creator>JeremyPeplinski</dc:creator>
      <dc:date>2024-02-01T14:47:59Z</dc:date>
    </item>
    <item>
      <title>Re: Quick Export (MBTiles) Issues</title>
      <link>https://community.esri.com/t5/arcgis-data-interoperability-ques/quick-export-mbtiles-issues/m-p/1383560#M234</link>
      <description>&lt;P&gt;Hello Jeremy, apologies for the delay.&lt;/P&gt;&lt;P&gt;Quick Export doesn't know about definition queries.&amp;nbsp; In the attached is a Pro 3.2 toolbox with a spatial ETL tool in it that exports your query features to mbtiles, zoom levels 4-8.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Feb 2024 18:53:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-data-interoperability-ques/quick-export-mbtiles-issues/m-p/1383560#M234</guid>
      <dc:creator>BruceHarold</dc:creator>
      <dc:date>2024-02-16T18:53:00Z</dc:date>
    </item>
  </channel>
</rss>

