Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geomesa-users] Ingesting Polygons into GeoMesa 
Hi Jon,
If you mean a list of geometry types, those include Point, LineString, Polygon, their Multi-versions. If you are asking about a list of Java types GeoMesa supports in SimpleFeatures, check out this: https://github.com/locationtech/geomesa/blob/accumulo1.5.x/1.x/geomesa-utils/src/main/scala/org/locationtech/geomesa/utils/geotools/SimpleFeatureTypes.scala#L373-390
It is worth noting that we've added support for Lists and Maps. If you want to use those types, you'll need to be careful to work with GeoMesa's SimpleFeatureTypes class/object rather than using GeoTools' DataUtilities for functions which create and encode SFTs. 

From what you are describing, intersects is the correct spatial predicate.

Thanks,

Jim

On 05/06/2015 03:08 PM, Parise, Jonathan wrote:

Chris,

Thanks for the quick reply, it is helpful.

Is there a listing of the various simple feature types somewhere? I'm trying to determine the best one for my application.

The polygon is a bounding box that I am going to use to check  for containment against another user specified bounding box in my application. Possibly using CQL's intersect function.

Thanks again,

Jon Parise

-----Original Message-----
From: geomesa-users-bounces@xxxxxxxxxxxxxxxx [mailto:geomesa-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Chris Eichelberger
Sent: Wednesday, May 06, 2015 3:02 PM
To: Geomesa User discussions
Subject: Re: [geomesa-users] Ingesting Polygons into GeoMesa

Jon,

Yes, GeoMesa can ingest and query non-point geometries.  If you are ingesting data from text files, for example, you can embed the well-known text (WKT) representation directly.  For example,
"POLYGON(-79 38, -79 39, -78 39, -78 38, -79 38)".

You just need to be sure that your simple feature type declares the geometry column to be an appropriate type.  The default "Geometry" will contain any of these, but you may want to be more specific, and declare it as type "Polygon", which is also supported.

I hope this helps; if not, please just write again.

Thanks!

Sincerely,
   -- Chris


On Wed, 2015-05-06 at 18:46 +0000, Parise, Jonathan wrote:

Hello,


I’ve done a GeoMesa ingest of data that was point based, basically
every record had one latitude and one longitude. Now, I have some
different data that I am trying to handle.


I have some data records I would like to ingest that contain a four
latitude/longitude pairs that essentially are a bounding box. I think
that GeoMesa has support for polygons, but I am having trouble finding
examples.


Is there a good example out there of how to ingest data that actually
has multiple points instead of a single point?


Note that the data is not a shape file, it is just data that happens
to be best represented as a polygon.


Thanks,


Jon Parise



_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geomesa-users


_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit http://www.locationtech.org/mailman/listinfo/geomesa-users
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geomesa-users

Back to the top