Skip to content
This repository has been archived by the owner on Jul 19, 2023. It is now read-only.

Global Map instead of Layer Map for some imported gpkg files. #73

Open
JivanAmara opened this issue Dec 6, 2016 · 0 comments
Open

Global Map instead of Layer Map for some imported gpkg files. #73

JivanAmara opened this issue Dec 6, 2016 · 0 comments

Comments

@JivanAmara
Copy link
Collaborator

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant