Skip to content
This repository was 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

@JivanAmara

Description

@JivanAmara

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions