Hi Milan,
1. In general, I think using GeoServer to return GeoJSON over WFS
should be pretty performant. At least, I would assume that is the
case before investigating alternatives. There might be some
theoretical performance penalty over the REST API, as GeoServer will
be building the GeoJSON on the fly, while the REST API will just
return the stored GeoJSON directly. In practice this probably won't
matter. (One caveat - if you require the feature collection size to
be 100% accurate in the returned GeoJSON, the query will end up
being run twice. We default to an estimated size that doesn't
require the extra scan)
2. It's not possible to query existing features through the custom
REST API, sorry. The code assumes a simple feature type with
particular, well-known attributes.
Thanks,
Emilio
On 12/29/2016 03:31 AM, Milan Muňko
wrote:
Hello Matt,
thank you for your response, I would like to introduce the use
case:
I will ingest data into GeoMesa using custom scala code then
the node.js server needs to querry this data. (We will assume
that lots of data is written to geomesa and queried)
1.) Is there any performance cost using standard geoserver WFS
to query features?
2.) still, is it possible to query existing features (already
stored in GeoMesa) through REST endpoind?
Thank you,
-- Milan
On 28.12.2016 16:05, Matt Zimmerman
wrote:
Milan --
A little bit of clarification-- the interface that you are
trying to use is not the GeoServer interface but rather a REST
endpoint provided by GeoMesa. This endpoint is best suited for
GeoJSON data used end-to-end (ingest and querying) within the
interface described (http://www.geomesa.org/documentation/current/user/geojson.html).
If you've already ingested your data into GeoMesa via a
GeoTools interface (e.g. with the GeoMesa command line tools),
this is probably not what you want.
Rather, if you want to query GeoServer to get previously
ingested features in GeoJSON format, you will probably be
better off just using the standard GeoServer WFS interface
instead:
curl "http://localhost:8080/geoserver/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=<workspace>:trashbin&maxFeatures=50&outputFormat=application%2Fjson"
Obviously you will need to replace '<workspace>' with
the name of the workspace where you have created your layer.
Hope this helps!
-- Matt
On 12/28/2016 07:10 AM, Milan Muňko
wrote:
Hello everyone,
I followed instructions from https://github.com/ccri/geomesa/blob/fcr_docs_1.3/docs/user/geojson.rst#querying-features,
I would like to access features that I imported using geomesa
ingest through geoserver REST API.
I registered new datastore using /ds method with parameters to
the existing one, how should I configure index? e.g. this is
the output of geomesa get-schema
Using GEOMESA_ACCUMULO_HOME =
/home/milan/Tools/geomesa-accumulo_2.11-1.3.0-m2
INFO Describing attributes of feature 'trashbin' from catalog
table 'trashbin'...
globalId: String (Indexed - Join)
value: Integer
address: String
time: Long (Indexed - Join)
geom: Point (ST-Geo-index)
User data:
geomesa.keywords: [""]
geomesa.table.sharing: true
geomesa.indices: z2:2:3,records:2:3,attr:3:3
geomesa.table.sharing.prefix:
Thank you,
Milan
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://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
https://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
https://www.locationtech.org/mailman/listinfo/geomesa-users
|
