Bringing the scalability of distributed computing to modern geospatial software.
I think I could see that in the RasterDataAdapter implementation
Im trying to do dbscan in geowave and here is what i did Ingested shape file using below command and the following tables are created in cassandra -
"adapter_geowave_metadata ,aim_geowave_metadata , index_geowave_metadata ,internal_adapter_geowave_metadata , stats_geowave_metadata ,testindex5 "
, it gives the following output.geowave ingest localtogw /mnt/ne_50m_admin_0_countries teststore5 testindex5 -f geotools-vector After this when i do " geowave store listtypes teststore5""Available types: ne_50m_admin_0_countries "
- But when i do DBSCAN on top of this using the command
I get the error"geowave analytic dbscan -cmi 5 -cms 10 -emn 2 -emx 6 -pmd 1000 -orc 4 -hdfs localhost:9870 -jobtracker localhost:8088 -hdfsbase /test_dir teststore5 --query.typeNames ne_50m_admin_0_countries "
can anyone help me how to solve this? Thank you."Error: java.lang.IllegalArgumentException: Can not set [Ljava.lang.String; field org.locationtech.geowave.core.cli.parsed.cli_6816fd68_a6d5_46ed_ae49_9547821da5c3_42.field_37 to java.lang.String"
@HaochengNn you can just install it from RPM rather than build from source ... instructions for that are here and you'll want to install the "HBase Components" (you can install it on master only, its going to put the libraries on HDFS for the other nodes to pick up) and you'll also likely want the commandline tools (and perhaps others depending on what you plan to do with it)
Hi, I am new to geowave. In one of the geowave examples there are these commands:
- geowave store add gdelt -t redis --gwNamespace geowave.gdelt --address redis://127.0.0.1:6379
- geowave index add -t spatial gdelt gdelt-spatial
- geowave ingest localtogw /mnt/gdelt gdelt gdelt-spatial -f gdelt --gdelt.cql "INTERSECTS(geometry,$GERMANY)"
I do not see there instructions to geowave how it should construct the index. I assume that gdelt and gdelt-spatial are just names. Or are these names recognized by geowave and used to construct the right index?How does geowave know how to construct the index? Can you shed some light on this? Thanks!
@pluresideas good question ... the commandline tools are extensible and most of the options are discovered at runtime.
gdelt is just a named placeholder for the store which got added in the first command. Its essentially the connection info plus perhaps a few more advanced options. gdelt-spatial is also a placeholder for the index whose options are provided by java SPI implementations of DimensionalityTypeProviderSpi. The types available are defined by each implementation's "type name" such as this and the other options are defined by the JCommander annotations on this object. Then the actual index is programmatically built based on the commandline options here. There are also always available options such as num_partitions (typing --help on any of the commands will give you feedback on what you can do, and at times defining the type with -t and then --help will give you additional options). In addition to the "spatial" type used here, we also have a -t spatial_temporal type option and a -t temporal type option that we provide out of the box. Additionally by just dropping in implementations of the SPI interface with the appropriates META-INF/services within any directory on the classpath (we should automatically create a /plugins directory on the classpath with any of our installers) you can define your own index types. Additionally, because the ingest tooling is very flexible with several extension points such as index types, you can print out all available plugins currently on the classpath with the geowave ingest listplugins command.
@bradh nothing great in the open source world that I know of for simulating tracks...there are various projects that can do routing, and then its potentially a matter of coming up with a reasonable distribution of start and end points to simulate traffic patterns. However, you can take large sets of publicly available real data, and if you need to generate more, use temporal and/or spatial offsets. The largest set that I know of is OSM GPS which as I recall is a few billion track points. Otherwise, Microsoft Research had published a couple interesting trajectory datasets: T-Drive and GeoLife ... hopefully these can help?
I was hoping for a 4676 generator. The actual need is a bit outside of the geowave area - I'm trying to do a "ground truth" track, then generate the observables for that. If I can make enough time, maybe a mix-n-match style approach so you can take those big trajectory sets, completely synthetic sets (maybe off OSM routing outputs for something a bit more real), maybe real tracks from ADS-B or AIS; and then tie those to various sensors (with error distribution), and then out to different kinds of formats.
BTW: If you want AIS data sets, https://www.operations.amsa.gov.au/Spatial/DataServices/DigitalData will give you AIS tracks from around Australia. One month at a time, thinned to 60 minutes (or 15 minutes for subset areas), years of data over the same coordinates. A typical month is 1.5m points. CC-BY-NC.
that type of use case is basically the moral of the story in that foss4g academic paper ... the 5 and 6 dimensional indexing as a whole performs much better than lower dimensional indexing, even though only 3 of those dimensions are well-constrained on any given query, it gives you the flexibility to query by combinations of those dimensions without resorting to a full table scan (something like 7+ hours on that dataset) although its not going to be quite as performant as having exactly the dimensions indexed that you are querying (trading off flexibility to support a variety of types of queries without needing to duplicate data using multiple indices)
@rfecher Hm… I profiled Cassandra queries (basically just by enabling Cassandra tracing)
And in all cases I had 3 dim index (geometry, time) and my query had only geometry it looks like it was just performing the select * from indexTable; query, am I reading it a bit incorrect?
In cases when my query contained all the index dimensions it performed a set of range queries (smth like 17k for ~400 entries // but these numbers can be smth different from my head):
SELECT * FROM indexTable
WHERE partition=:partition_val
AND adapter_id IN :adapter_id_val
AND sort>=:sort_min AND sort<:sort_max;Mb the differende is in the Index type? I used XZHierarchicalIndexFactory for the tests
Ah just to clarify my words a little bit (in terms of language):
table was indexed with a spatialtemporal index
All
ExplicitSpatialQuerieswereselect * from indexTable;All
ExplicitSpatialTemporalQuerywereSELECT * FROM indexTable WHERE partition=:partition_val AND adapter_id IN :adapter_id_val AND sort>=:sort_min AND sort<:sort_max;
no, you're right... I just followed along to verify - the code falls into this block which converts to full table scan ... sorry about that, for our benchmarks we set the constraints in unconstrained dimensions to be the extent of the data from stats and I think thats what we do from geoserver/geotools queries, but unfortunately not internally ... I know at some point we were thinking the geowave datastore API is more explicit while geotools/geoserver could infer things to make reasonable choices, but I think that philosophy isn't too applicable here anyways, seems it should always try to avoid full table scans if it can ... you may want to add this as an issue if you don't mind? I think its worthwhile to backlog. In the interim is it easy enough to set the bounds of any unconstrained dimensions to be the extent of the data? We store all extents of numeric/time data in the stats so I think something like this will get you your full time range:
datastore.aggregateStatistics(VectorStatisticsQueryBuilder.newBuilder().factory().timeRange().build());
if you need to maintain a statistic on your own adapter you can implement StatisticsProvider, I guess this example from the unit tests is as good as any, the stats types have a query builder that you can use by invoking
newBuilder() for the datastore statistics queries or aggregations
each statistic is required to implement
IngestCallback so its automatically updated on write (its the primary purpose of statistics really) ... a statistic can also implement DeleteCallback if it can be inverted properly, some like extents would have to be recomputed, but others like counts are easy to just decrement
all stats are merged together so there's no concern about maintaining the full datasets statistic within any one ingest client
hmm, well, to some extent yes, but I'd consider ways to work around that in certain use cases - for example if you have a lot of queries, but once you have a large corpus its unlikely extents dramatically change I'd be trying to do some form of caching, maybe even extend what is coming from stats a little just to be confident it covers the full data set
for example, for time it seems like it can be special cased a bit if you know you're not getting data in the future you could just use the current time as the end of the extent
and if the dimension is bounded already like lat/lon, you don't really need .to go the route of stats, you could also just use the bounds on the dimension
such a flexible API, this is pretty sweet :D
Exactly which versions, and what example code are you referring to?
@hipotato you need to be more descriptive. Please remember we can't see your screen, so you need to provide background that allows us to understand what you have done before this, what your environment looks like (e.g. the IDE - does the basic geowave command work, have you adjusted
PATH or similar) and what you expected to happen instead.
I have ingested raster (GeoTiff) successfully on the standalone installation on linux. Now I want debug the source code of gw in IntelliJ IDEA on Windows7, to go through add store ,add index ,ingest raster function. The main class is
org.locationtech.geowave.core.cli.GeoWaveMain,the program arguments is store add raster --gwNamespace geowave.raster -t hbase --zookeeper node24,node25,node26:2181, when run ,the console output is Usage: geowave [options]
Options:
-cf, --config-file
Override configuration file (default is
<home>/.geowave/config.properties)
--debug
Verbose output
--version
Output Geowave build version information
Commands:
config
Commands that affect local configuration only
explain
See what arguments are missing and what values will be used for GeoWave commands
help
Get descriptions of arguments for any GeoWave command
util, utility
GeoWave utility commands
Error: Expected a command, got store
@hipotato It looks like only the core CLI is on your classpath. GeoWave builds up the CLI with each project adding commands here and there. In order to get all of the commands, execute the main class from a classpath that has the artifacts for all of the GeoWave projects. One easy way to do it is to debug from the
geowave-test project, which includes most of the other GeoWave projects as dependencies.