Hi Chris,
I was wondering if the commit for GEOMESA-102 included the changes required by GEOMESA-64. I couldn’t find any specific commits for the -64 and I don’t have
access to the atlassian.net jira website.
Thanks,
Ref: https://github.com/locationtech/geomesa/commit/f5eab7ed915a93e2c7ea3b388ec4a9aa13c8334e
Chris Snider
Senior Software Engineer
Intelligent Software Solutions, Inc.
From: Chris Eichelberger [mailto:cne1x@xxxxxxxx]
Sent: Thursday, May 08, 2014 6:58 AM
To: Chris Snider; Geomesa User discussions; geomesa@xxxxxxxx
Subject: RE: [geomesa-users] Data retrieval and Rendering times
Chris,
We are reviewing a pull request for this ticket now, and hope to have that incorporated into the master branch later today.
Sincerely,
----- Original Message -----
"hunter@xxxxxxxx" <hunter@xxxxxxxx>, "Geomesa User discussions" <geomesa-users@xxxxxxxxxxxxxxxx>,
"geomesa@xxxxxxxx" <geomesa@xxxxxxxx>
Thu, 8 May 2014 12:47:08 +0000
RE: [geomesa-users] Data retrieval and Rendering times
Hi Hunter,
I was wondering if there are any updates on this bounding box issue.
Thanks,
Chris Snider
Senior Software Engineer
Intelligent Software Solutions, Inc.
Direct (719) 452-7257
Hi Chris,
It is GEOMESA-64.
https://geomesa.atlassian.net/browse/GEOMESA-64
thanks,
Hunter
On 04/23/2014 02:57 PM, Chris Snider wrote:
Thanks Hunter. Is there a JIRA/tracking number I can reference for my team status updates?
Chris Snider
Senior Software Engineer
Intelligent Software Solutions, Inc.
Direct (719) 452-7257
Hi Chris,
I was able to reproduce your issue. It looks like the issue is that some GeoServer requests containing an OR of two BBOXes may not be getting unioned correctly by GeoMesa. I'm working toward a solution and will update you on the status.
thanks,
Hunter
On 04/23/2014 10:08 AM, Chris Snider wrote:
Hi Hunter,
I am currently using GeoServer 24.4 and Geotools 10.4. I’ll try and get an update to 2.5/11 for our sandbox. Thanks for the hints.
Chris Snider
Senior Software Engineer
Intelligent Software Solutions, Inc.
Direct (719) 452-7257
Hi Chris,
We have used GeoMesa to view hundreds of thousands of points, so 26000 features should be no problem.
Are you using master? There have been some recent improvements to the query planner and we are now implementing relational projections, so you should be using master to take advantage of this. Also be sure you are using geoserver 2.5 and geotools 11.0.
I will try to reproduce the issue with your cellular data file and let you know what I find.
Thanks,
Hunter
On 04/22/2014 10:24 AM, Chris Snider wrote:
Hi,
My team has been working with geomesa and the accumulo tables for a prototype product. We have spent a lot of time learning about accumulo and geomesa. I was able to use the
shapefile ingest class to push the FCC cell towers shapefile (26000+ features) into accumulo and generate a layer in GeoServer.
Using the GeoServer preview layers page, we get some pretty information back with WMS requests. However, at certain zoom levels, the image times out, or the image doesn’t render.
I can click the image at a presumed location and the getfeatureinfo call works and returns the features around my x/y coordinate. Zooming in or out will generally return the expected image.
Are there JVM/memory settings for GeoServer or Accumulo that I can begin looking at tweaking to increase performance? Is there an expected limitation on the number of features
that are returned from a WMS getmap call?
Ref:
http://wireless.fcc.gov/geographic/data/db/cellular06142012.zip
Thanks,
Chris Snider
Senior Software Engineer
Intelligent Software Solutions, Inc.
Direct (719) 452-7257
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
http://www.locationtech.org/mailman/listinfo/geomesa-users
|
