Perdjesk commented on issue #726:
URL: 
https://github.com/apache/incubator-baremaps/issues/726#issuecomment-1645787981

   I am not personally familiar with the `ExportVectorTiles` command, however 
by skimming into it, it becomes apparent that the `bounds` configuration highly 
influences the processing time regardless of the content size in postgresql. 
The export feature is "unaware" of what is the scope of data in the database 
provided and solely uses the bounds and zoom levels to determine what will 
queried. Thus in case of partial data the `bounds` configuration in 
`tileset.json` should be specified as minimal as possible.
   
   `examples/openstreetmap/tileset.json` Liechtenstein:
   ```
     "bounds": [
       9.471078,
       47.04774,
       9.636217,
       47.27128
     ]
   ```
   
[count](https://github.com/apache/incubator-baremaps/blob/e93c031fab93f7584ca0fa230a72d09b1489bc09/baremaps-core/src/main/java/org/apache/baremaps/workflow/tasks/ExportVectorTiles.java#L66)
 = 180 
   
   
   "world" bounds:
   ```
     "bounds": [
       -180,
       -85,
       180,
       85
     ]
   ```
   
[count](https://github.com/apache/incubator-baremaps/blob/e93c031fab93f7584ca0fa230a72d09b1489bc09/baremaps-core/src/main/java/org/apache/baremaps/workflow/tasks/ExportVectorTiles.java#L66)
  = 351'207'424
   
   
   State of Texas bounds:
   ```
     "bounds": [
       -106.645646,
       25.837377,
       -93.508292,
       36.500704
     ]
   ```
   
[count](https://github.com/apache/incubator-baremaps/blob/e93c031fab93f7584ca0fa230a72d09b1489bc09/baremaps-core/src/main/java/org/apache/baremaps/workflow/tasks/ExportVectorTiles.java#L66)
  =  448'823
   
   Thus the 500 seconds achieved when using those bounds better reflect the 
effective required time to process the data in postgresql you imported.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to