You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2023. It is now read-only.
When importing layers from some gpkg files the map which is shown in the UI is a global map of the world instead of a map matching the bounding box of the layer.
san_diego_downtown_generic-osm-data-20161202.gpkg: Shows problem
tiger_roads.gpkg: No Problem
portauprince.fixedcolnames.gpkg: No problem; has multiple layers & rtrees like problem gpkg.
When importing layers from some gpkg files the map which is shown in the UI is a global map of the world instead of a map matching the bounding box of the layer.
The layer created in geoserver at: https://github.com/GeoNode/django-osgeo-importer/blob/master/osgeo_importer/handlers/geoserver/__init__.py#L167 has bad bounding limits for layers from the file which shows the problem; this is probably why the map is global.
san_diego_downtown_generic-osm-data-20161202.gpkg: Shows problem
tiger_roads.gpkg: No Problem
portauprince.fixedcolnames.gpkg: No problem; has multiple layers & rtrees like problem gpkg.
example_gpkgs.zip
The text was updated successfully, but these errors were encountered: