Re: [geomesa-users] Is SF_PROPERTY_END_TIME still supported?

[Chris Eichelberger <cne1x@xxxxxxxx>]

Ben,

The end-date as originally construed is no longer part of the
spatio-temporal index.  (In fact, it was never actually part of the
index, but was available to be queried against.)

GeoMesa now has support for indexes on secondary attributes, and in that
way you could certainly query for all records that satisfied something
like...

  arrivalDate <= queryDate AND
  departureDate >= queryDate

The best way to ensure that you're using a secondary index is to set the
right flag when the SimpleFeatureType is initially created in GeoMesa.
Here is an example from a unit test on how to use one of the GeoMesa
utility classes to help do this:

https://github.com/locationtech/geomesa/blob/master/geomesa-utils/src/test/scala/org/locationtech/geomesa/utils/geotools/SimpleFeatureTypesTest.scala#L93

If you have any additional questions, please let us know.

Thanks!

Sincerely,
  -- Chris


On Tue, 2015-09-01 at 20:56 +0000, Ben Southall wrote:
> Hello,
> 
>  
> 
> I’m putting together a design for a visit log, e.g. a ship visits a
> port, and is there from Date arrivalDate to Date departureDate (so the
> record would include ship ID, port ID, port location, arrivalDate and
> departureDate). I was wondering if SF_PROPERTY_END_TIME was still
> being used in the index, and whether temporal queries use it. You
> might imagine that I’d like to be able to query a location for
> visitors at some Date queryDate, and have all visitors whose
> arrivalDate and departureDate bracket queryDate returned. Will the
> current indexing structure support queries of that type?
> 
>  
> 
> Thanks!
> 
>  
> 
> Ben
> 
> 
> _______________________________________________
> 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