Re: [Geoserver-users] Geoserver: Adding space around graphic fills

Olá, Esse erro de validação acontece porque o código que faz a validação não foi estendido para ter esse elemento em conta. Ou seja independentemente desse erro de validação, o estilo (parece) estar coreto e vai ser corretamente interpretado pelo código que vai desenhar o mapa. Eu fiz um

Re: [Geoserver-users] Creating coverages from ImageMosaic without harvesting all granules

Hi Andrea, I had been using the "configure=none" procedure described in the training. But you convinced me to take another look at the results I was getting. It turns out the problem was caused by having an "IndexingDirectories" parameter specified in the indexer XML. (The docs [1] imply this

[Geoserver-users] YSLD Styling Help Needed

I am trying to create a style that uses line casings to deferinate highway types and surface types. The two types of highways appear as the correct color. But the surface line is always white. (White is the color used for a null value in surface.) The legend created geoserver is correct. I'm

[Geoserver-users] Geoserver: Adding space around graphic fills

Olá!! Estou usando a versão 2.12.1 do geoserver e o tópico da documentação 'Adding space around graphic fills' permite o uso do 10 para espaçar os símbolos usados para estilizar com o 'graphic fills'.(http://docs.geoserver.org/2.12.1/user/styling/sld/extensions/margins.html) Mas quando insiro

[Geoserver-users] NullPointerException occurred when using gt-imagemosaic-jdbc-19.0 to load tiles from PostGIS

Hi, When I tried to create a coverage view by using tiles from PosGIS. NullPointerException occurred as seen in the attached log file and screenshot. The tiles in PostGIS are created with overviews, pgraster configuration files were prepared and from the geoserver log, it could be seen that the

Re: [Geoserver-users] Creating coverages from ImageMosaic without harvesting all granules

On Thu, Mar 22, 2018 at 5:47 PM, Daniel Baston wrote: > Hi Andrea, > > After digging through this more, my understanding now is that all granules > are harvested because: > > 1) The CoverageStore post handler instantiates an ImageMosaicReader [1] > 2) An ImageMosaicReader

Re: [Geoserver-users] Creating coverages from ImageMosaic without harvesting all granules

Hi Andrea, After digging through this more, my understanding now is that all granules are harvested because: 1) The CoverageStore post handler instantiates an ImageMosaicReader [1] 2) An ImageMosaicReader automatically harvests granules when it is created. Example test showing this behavior in

Re: [Geoserver-users] Creating coverages from ImageMosaic without harvesting all granules

Hi Andrea, Thank you for the reply. After the curl command above, every file that matches the wildcard in the XML Indexer file (a) is listed in the PostGIS granule index table, and (b) has an index file created in NETCDF_DATA_DIR. Files that do not match the wildcard are not processed. If I pass

Re: [Geoserver-users] Creating coverages from ImageMosaic without harvesting all granules

Hi Daniel, the underlying mechanism does not have a notion of single file, but one of "directory + file filter". In theory the filter should make the code scroll over the directory contents, and skip all files but the ones that is due to be harvested. If you have evidence it's actually opening

Re: [Geoserver-users] createstoredquery for virtual service

Hi, I'm not aware of anyone currently sponsoring such work, but you can open a bug report here: https://osgeo-org.atlassian.net/projects/GEOS/summary and anyone interested in a fix real soon can follow this instructions: https://github.com/geoserver/geoserver/blob/master/CONTRIBUTING.md or look in

[Geoserver-users] createstoredquery for virtual service

Hi Are there plans to make it possible to create storedqueries for virtual services? Up to now (2.13.0) it only seems to work on the base url. On a virtual service I receive Request parsing failed[Assertion failed] - this argument is required; it must not be null Thanks