Re: [geomesa-users] Z-Index Time Interval of hours

[Emilio Lahr-Vivaz <elahrvivaz@xxxxxxxx>]

    Hello,
    
    I'm actually surprised that you didn't get an error. There isn't any
    implementation for hourly intervals, so it either didn't index the
    time, or it fell back to the default weekly interval. You might be
    able to use the 'describe-schema' CLI command to see if the user
    data was persisted as you specified.
    
    Thanks,
    
    Emilio

On 7/8/20 4:14 AM, Laudan, Janek wrote:

Hi,

 

I just started working with geomesa. I’m planning to use it for storing traffic simulation data generated with MATSim (https://matsim.org). Because a simulation run usually covers only a  single day, I thought it would make sense to have a Z-Index Time Interval of ‘hour’. Now, the documentation (https://www.geomesa.org/documentation/user/datastores/index_config.html#configuring-z-index-time-interval) says that only ‘day’, ‘week’, ‘month’ and ‘year’ are supported. I tried to set the index of my schema to hourly intervals like so:

 

sft.getUserData().put("geomesa.z3.interval", "hour");

 

and my test set up stored and retrieved the feature I submitted to the store just fine.

 

Will geomesa silently fall back to another form of indexing or are smaller intervals than covered by the documentation supported?

 

Best Regards

Janek Laudan

 

-----------------------------------------------------------------------------------------------------------------------------------

Janek Laudan

Research Associate

Transport Systems Planning and Transport Telematics, TU Berlin

 

Website: https://vsp.tu-berlin.de

E-Mail:     laudan@xxxxxxxxxxxx

Skype:     live:janek.laudan

 

_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/geomesa-users