Layer Extents do not appear in Layer Listing page

[slibby]

No layer extents ever appear on the map on the left side of the Layers listing or Search Results pages:

[state-hiu]

This is more of an enhancement than a bug.

That's a good idea, but might be more complicated than anticipated. GeoServer doesn't provide an easy way to render extents for all layers. Solution might be to keep in sync a separate table that just stores extents.

We could pass all the extents to the browser for client-side rendering, but we would need some type of check for exteremely large deployments (we wouldn't want to overwhelm someone's browser).

Since we don't have that many layers, maybe we could work on a downstream (read:Ebola GeoNode only) fix for now that uses client-side rendering.

[slibby]

Another option would be to remove the "Extent" section from the layer/map list UI. I assumed this was the purpose, but it sounds like it doesn't work out of the box?

[jj0hns0n]

Its working, it just doesnt draw the extents. Drag that map out of africa
and you will see you get no results. Its using the BBOX of that map window
to query the service. Not intuitive, but it does work.

On Wed, Dec 17, 2014 at 10:25 AM, Sam Libby [email protected]
wrote:

Another option would be to remove the "Extent" section from the layer/map
list UI. I assumed this was the purpose, but it sounds like it doesn't work
out of the box?

—
Reply to this email directly or view it on GitHub
#44 (comment)
.

[state-hiu]

Maybe this could be a WPS process? @jj0hns0n, is it querying PostGIS directly now or using GeoServer?

[slibby]

Got it - definitely didn't think of that, which maybe points at a UX tweak rather than a code change - what if we changed the top heading above the various filters to say "Filter by..." instead of "Your selections" (which doesn't mean much)

[jj0hns0n]

No need for a WPS process. Its querying via the GeoNode API which is using
the BBOX in the postgis database. We have the bbox in the geonode layer
mode, just need to find a way to render it.

On Wed, Dec 17, 2014 at 10:32 AM, Humanitarian Information Unit <
[email protected]> wrote:

Maybe this could be a WPS process? @jj0hns0n https://github.com/jj0hns0n,
is it querying PostGIS directly now or using GeoServer?

—
Reply to this email directly or view it on GitHub
#44 (comment)
.

[jj0hns0n]

Makes sense to change it to Filter by.

On Wed, Dec 17, 2014 at 10:39 AM, Jeffrey Johnson [email protected]
wrote:

No need for a WPS process. Its querying via the GeoNode API which is using
the BBOX in the postgis database. We have the bbox in the geonode layer
mode, just need to find a way to render it.

On Wed, Dec 17, 2014 at 10:32 AM, Humanitarian Information Unit <
[email protected]> wrote:

Maybe this could be a WPS process? @jj0hns0n
https://github.com/jj0hns0n, is it querying PostGIS directly now or
using GeoServer?

—
Reply to this email directly or view it on GitHub
#44 (comment)
.