[geomesa-users] Geoserver bounding box always (-180, -90) (180, 90)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[geomesa-users] Geoserver bounding box always (-180, -90) (180, 90)

From: John Meehan <john_n_meehan@xxxxxxxxx>
Date: Tue, 05 Dec 2017 08:36:56 -0800
Delivered-to: geomesa-users@xxxxxxxxxxxxxxxx
List-archive: <https://dev.locationtech.org/mhonarc/lists/geomesa-users>
List-help: <mailto:geomesa-users-request@locationtech.org?subject=help>
List-subscribe: <https://dev.locationtech.org/mailman/listinfo/geomesa-users>, <mailto:geomesa-users-request@locationtech.org?subject=subscribe>
List-unsubscribe: <https://dev.locationtech.org/mailman/options/geomesa-users>, <mailto:geomesa-users-request@locationtech.org?subject=unsubscribe>

Hi,

How does Geoserver calculate the bounding box of a Geomesa (HBase) layer? After ingesting shapefiles and adding the store/layer everything seems to work well except for calculating the bounding box of the layer.

Even though geotools can return the real bounds:

scala> ftrSrc.getBounds

res0: org.geotools.geometry.jts.ReferencedEnvelope = ReferencedEnvelope[-122.43996559840414 : -122.24542051576557, 47.4972948937176 : 47.73414290003609]

Follow-Ups:
- Re: [geomesa-users] Geoserver bounding box always (-180, -90) (180, 90)
  - From: Emilio Lahr-Vivaz

Prev by Date: Re: [geomesa-users] kafka streaming
Next by Date: Re: [geomesa-users] Geoserver bounding box always (-180, -90) (180, 90)
Previous by thread: [geomesa-users] kafka streaming
Next by thread: Re: [geomesa-users] Geoserver bounding box always (-180, -90) (180, 90)
Index(es):
- Date
- Thread

Breadcrumbs