On Thu, Jun 11, 2015 at 1:04 PM, Stefano Costa <
stefano.co...@geo-solutions.it> wrote:
>
> I tried to modify DataStoreFileResource as you suggested and the first
> hurdle I bumped in is that, as the name suggests, the implementation is
> based off DataStoreFactorySpi/DataStore, while app-schema u
On Wed, Jun 10, 2015 at 10:16 PM, Jody Garnett
wrote:
> This is kind of tricky as general problem - how do we manage configuration
> files such as required for templates, icons, app-schema mapping
> configuration, pregeneralized datastore config etc...
>
> I think we have now isolated all file ac
On Thu, Jun 11, 2015 at 8:25 PM, Marks, David
wrote:
> In my current GeoServer project, we have a custom dimension that shows up
> and can be queried against in WMS 1.1.1 and 1.3.0, as well as WCS 2.0.1.
> But for some reason, none of the layers even display the dimension when
> viewed via getCap
In my current GeoServer project, we have a custom dimension that shows up and
can be queried against in WMS 1.1.1 and 1.3.0, as well as WCS 2.0.1. But for
some reason, none of the layers even display the dimension when viewed via
getCapabilities or describeCoverage using WCS 1.0.0.
Anyone able
Hi Andrea,
thanks for your answer, see my comments inline.
Il giorno mer, 10/06/2015 alle 20.31 +0200, Andrea Aime ha scritto:
> In the REST api those are two different use cases. In vector stores,
> you PUT a shp/property/h2/spatialite to create a new store,
> and the file location you provides
Hi,
I noticed a performance issue with serving WFS 1.1.0 GetFeature requests
with GeoJSON output format.
1. GetFeature.run() calculates the total number of features that the
query matches (for paging purposes)
2. GeoJSONGetFeatureResponse.getFeatureCountFromWFS11Request() counts
the n
