Skip to content
This repository has been archived by the owner on Mar 15, 2022. It is now read-only.

Dataset Extent - Update Bbox #520

Open
abrown920 opened this issue Nov 21, 2014 · 4 comments
Open

Dataset Extent - Update Bbox #520

abrown920 opened this issue Nov 21, 2014 · 4 comments
Assignees
@FuhuXia
Labels
bug ckan

Comments

@abrown920
Copy link

To fix the issue with dataset extent improperly displaying locations, we need to split the bbox into two boxes and send two queries to get correct spatial query results for bbox covering long180 lines.
@abrown920 abrown920 added this to the Release 2.12 milestone Nov 21, 2014
@kvuppala kvuppala mentioned this issue Nov 21, 2014
Closed
@kvuppala kvuppala modified the milestones: Release 2.13, Release 2.12 Nov 24, 2014
@kvuppala
Copy link
Contributor

kvuppala commented Dec 5, 2014

related to CKAN issue ckan/ckanext-spatial#90

@kvuppala kvuppala modified the milestones: Release 2.14, Release 2.13 Jan 6, 2015
@kvuppala
Copy link
Contributor

kvuppala commented Jan 6, 2015

No update from CKAN team on the issue, it will require understanding of the CKAN spatial library completely to change the queries and fix it, moving it to 2.14

@kvuppala kvuppala modified the milestones: Catalog.data.gov Release 2.14, Data.gov Release 2.14 Feb 12, 2015
@kvuppala kvuppala removed this from the Catalog.data.gov Release 2.14 milestone Feb 19, 2015
@hkdctol
Copy link
Contributor

hkdctol commented Mar 8, 2017

@kvuppala is this obsolete/can it be closed?

@kvuppala
Copy link
Contributor

kvuppala commented Mar 8, 2017

@hkdctol Will check, the second part of the issue might need a fix.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@FuhuXia FuhuXia

Labels
bug ckan
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@FuhuXia @kvuppala @hkdctol @abrown920