Re: [Geoserver-users] Parameterized data_dir
Hello,
Just for completeness, my infrastructure was quite complex with multiple
components, etc. and the problem was that the -DALLOW_ENV_PARAMETRIZATION
property was not arriving to GeoServer. It's working perfectly now!
Sorry for bothering.
El lun., 5 nov. 2018 a las 7:33, Víctor González (<
victor.gonza...@geomati.co>) escribió:
> Hi,
>
> Yes, I did. Although I found that the GeoServerEnvironment class is in the
> platform project and Alessio suggested that the extension is not necessary:
>
> http://osgeo-org.1560.x6.nabble.com/spring-PropertyPlaceholderConfigurer-for-data-directory-files-tp5313190p5313197.html
>
> I'll try to do it again with a fresh installation; maybe there's something
> messed up with my current setup.
>
> Cheers.
>
> El vie., 2 nov. 2018 a las 17:58, Nuno Oliveira (<
> nuno.olive...@geo-solutions.it>) escribió:
>
>> Hi,
>>
>> your configuration look good, did you install the Backup & Restore module
>> ?
>>
>> https://docs.geoserver.org/latest/en/user/community/backuprestore/installation.html
>>
>> Regards,
>>
>> Nuno Oliveira
>>
>> On Fri, 2018-11-02 at 14:17 +0100, Víctor González wrote:
>>
>> Hi all,
>>
>> I was trying to use the technique explained here:
>>
>>
>> https://docs.geoserver.org/latest/en/user/community/backuprestore/configtemplate.html
>>
>>
>> but I cannot make it work. I set the host of a PG datastore to
>> ${mypghost}, wrote a /geoserver-environment.properties with
>> mypghost=localhost and then restarted with -DALLOW_ENV_PARAMETRIZATION=true
>> but it doesn't connect (it does when setting "localhost" directly).
>>
>> Then I tried to remove the geoserver-environment.properties file and set
>> the logging level to verbose but I don't see this message in the logs
>> anywhere:
>>
>>
>> https://github.com/geoserver/geoserver/blob/master/src/platform/src/main/java/org/geoserver/platform/GeoServerEnvironment.java#L104
>>
>> https://github.com/geoserver/geoserver/blob/master/src/platform/src/main/java/org/geoserver/platform/GeoServerEnvironment.java#L120
>>
>> It seems like the bean is never initialized. Do I need to configure
>> something else to enable this feature?
>>
>> Thanks in advance.
>>
>> --
>> Víctor González
>> http://geomati.co
>>
>> ___
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to this
>> list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> If you want to request a feature or an improvement, also see this:
>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>>
>> Geoserver-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>> --
>> Regards,
>> Nuno Oliveira
>> ==
>> GeoServer Professional Services from the
>> experts!
>> Visit http://goo.gl/it488V for more information.
>> ==
>>
>> Nuno Miguel Carvalho Oliveira
>> @nmcoliveira
>> Software Engineer
>>
>> GeoSolutions S.A.S.
>> Via di Montramito 3/A
>> 55054 Massarosa (LU)
>> Italy
>> phone: +39 0584 962313
>> fax: +39 0584 1660272
>> http://www.geo-solutions.ithttp://twitter.com/geosolutions_it
>>
>> ---
>>
>> Con riferimento alla normativa sul trattamento dei dati
>> personali (Reg. UE 2016/679 - Regolamento generale sulla
>> protezione dei dati “GDPR”), si precisa che ogni
>> circostanza inerente alla presente email (il suo contenuto,
>> gli eventuali allegati, etc.) è un dato la cui conoscenza
>> è riservata al/i solo/i destinatario/i indicati dallo
>> scrivente. Se il messaggio Le è giunto per errore, è
>> tenuta/o a cancellarlo, ogni altra operazione è illecita.
>> Le sarei comunque grato se potesse darmene notizia.
>>
>> This email is intended only for the person or entity to
>> which it is addressed and may contain information that
>> is privileged, confidential or otherwise protected from
>> disclosure. We remind that - as provided by European
>> Regulation 2016/679 “GDPR” - copying, dissemination or
>> use of this e-mail or the information herein by anyone
>&
Re: [Geoserver-users] Parameterized data_dir
Hi,
Yes, I did. Although I found that the GeoServerEnvironment class is in the
platform project and Alessio suggested that the extension is not necessary:
http://osgeo-org.1560.x6.nabble.com/spring-PropertyPlaceholderConfigurer-for-data-directory-files-tp5313190p5313197.html
I'll try to do it again with a fresh installation; maybe there's something
messed up with my current setup.
Cheers.
El vie., 2 nov. 2018 a las 17:58, Nuno Oliveira (<
nuno.olive...@geo-solutions.it>) escribió:
> Hi,
>
> your configuration look good, did you install the Backup & Restore module ?
>
> https://docs.geoserver.org/latest/en/user/community/backuprestore/installation.html
>
> Regards,
>
> Nuno Oliveira
>
> On Fri, 2018-11-02 at 14:17 +0100, Víctor González wrote:
>
> Hi all,
>
> I was trying to use the technique explained here:
>
>
> https://docs.geoserver.org/latest/en/user/community/backuprestore/configtemplate.html
>
>
> but I cannot make it work. I set the host of a PG datastore to
> ${mypghost}, wrote a /geoserver-environment.properties with
> mypghost=localhost and then restarted with -DALLOW_ENV_PARAMETRIZATION=true
> but it doesn't connect (it does when setting "localhost" directly).
>
> Then I tried to remove the geoserver-environment.properties file and set
> the logging level to verbose but I don't see this message in the logs
> anywhere:
>
>
> https://github.com/geoserver/geoserver/blob/master/src/platform/src/main/java/org/geoserver/platform/GeoServerEnvironment.java#L104
>
> https://github.com/geoserver/geoserver/blob/master/src/platform/src/main/java/org/geoserver/platform/GeoServerEnvironment.java#L120
>
> It seems like the bean is never initialized. Do I need to configure
> something else to enable this feature?
>
> Thanks in advance.
>
> --
> Víctor González
> http://geomati.co
>
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to this
> list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
> Geoserver-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/geoserver-users
>
> --
> Regards,
> Nuno Oliveira
> ==
> GeoServer Professional Services from the
> experts!
> Visit http://goo.gl/it488V for more information.
> ==
>
> Nuno Miguel Carvalho Oliveira
> @nmcoliveira
> Software Engineer
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> http://www.geo-solutions.ithttp://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati
> personali (Reg. UE 2016/679 - Regolamento generale sulla
> protezione dei dati “GDPR”), si precisa che ogni
> circostanza inerente alla presente email (il suo contenuto,
> gli eventuali allegati, etc.) è un dato la cui conoscenza
> è riservata al/i solo/i destinatario/i indicati dallo
> scrivente. Se il messaggio Le è giunto per errore, è
> tenuta/o a cancellarlo, ogni altra operazione è illecita.
> Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to
> which it is addressed and may contain information that
> is privileged, confidential or otherwise protected from
> disclosure. We remind that - as provided by European
> Regulation 2016/679 “GDPR” - copying, dissemination or
> use of this e-mail or the information herein by anyone
> other than the intended recipient is prohibited. If you
> have received this email by mistake, please notify
> us immediately by telephone or e-mail.
>
>
--
Víctor González
http://geomati.co
___
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] Parameterized data_dir
Hi all,
I was trying to use the technique explained here:
https://docs.geoserver.org/latest/en/user/community/backuprestore/configtemplate.html
but I cannot make it work. I set the host of a PG datastore to ${mypghost},
wrote a /geoserver-environment.properties with mypghost=localhost
and then restarted with -DALLOW_ENV_PARAMETRIZATION=true but it doesn't
connect (it does when setting "localhost" directly).
Then I tried to remove the geoserver-environment.properties file and set
the logging level to verbose but I don't see this message in the logs
anywhere:
https://github.com/geoserver/geoserver/blob/master/src/platform/src/main/java/org/geoserver/platform/GeoServerEnvironment.java#L104
https://github.com/geoserver/geoserver/blob/master/src/platform/src/main/java/org/geoserver/platform/GeoServerEnvironment.java#L120
It seems like the bean is never initialized. Do I need to configure
something else to enable this feature?
Thanks in advance.
--
Víctor González
http://geomati.co
___
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Missing band definitions when adding a GeoTIFF via REST
Hi Andrea,
I couldn't make it work. It seems like when using external. the
whole request body is taken as a URL:
$ curl -u admin:geoserver -XPUT -H "Content-type: multipart/form-data" -F
"file=/tmp/test.tif"
http://localhost:8080/geoserver/rest/workspaces/files/coveragestores/myraster/external.geotiff
-F coverageName=testingName
Error while storing uploaded file::no protocol:
--96b1a53245d1e6ac
Content-Disposition: form-data; name="file"
/tmp/test.tif
--96b1a53245d1e6ac
Content-Disposition: form-data; name="coverageName"
testingName
--96b1a53245d1e6ac--
Here some relevant lines from the log:
...
at java.net.URL.(URL.java:439)
at
org.geoserver.rest.util.RESTUtils.handleEXTERNALUpload(RESTUtils.java:264)
at
org.geoserver.catalog.rest.StoreFileResource.handleFileUpload(StoreFileResource.java:187)
Cheers.
2016-11-13 15:43 GMT+01:00 Andrea Aime :
> Hi Victor,
> not sure, but from a quick glance in the code, try adding "coverageName"
> as a form parameter in the upload (I believe this means the upload will
> have to be a form multipart one)
>
> Cheers
> Andrea
>
> On Sun, Nov 13, 2016 at 12:33 PM, Víctor González <
> victor.gonza...@geomati.co> wrote:
>
>> Hi,
>>
>> Thanks for your responses.
>>
>> @Peter The problem is that the raster files are uploaded by other process
>> to the server and we
>> don't know their metadata beforehand nor we have the possibility to use a
>> GUI manually for each of them.
>>
>> @Andrea Thanks, I should have read the doc more carefully... That's
>> great, with 'external' the metadata gets loaded automatically. The only
>> thing is that the layer name is taken from the file name. Is it possible to
>> specify the name of the resulting layer in the same request?
>>
>> Regards.
>>
>> 2016-11-11 14:18 GMT+01:00 Andrea Aime :
>>
>>> As far as I know, you have to change the way you're creating the
>>> coverage store,
>>> using the "external" syntax similar to this example configuring a
>>> shapefile that's
>>> already on disk:
>>>
>>> http://docs.geoserver.org/latest/en/user/rest/examples/curl.
>>> html#adding-an-existing-shapefile
>>>
>>> Sorry I don't have an example for raster data handy (if anybody reading
>>> has one, there's
>>> a guide for quick documentation contributions here:
>>> http://docs.geoserver.org/latest/en/docguide/quickfix.html )
>>>
>>> Cheers
>>> Andrea
>>>
>>>
>>> On Fri, Nov 11, 2016 at 1:32 PM, Víctor González <
>>> victor.gonza...@geomati.co> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm loading a new GeoTIFF layer using REST by adding a new
>>>> coveragestore and coverage (requests below). After that, the layer does not
>>>> have information about bands and I have to use the "Reload band
>>>> definitions" option in the web GUI to load them manually (because I don't
>>>> know the raster metadata and I cannot include it in the request).
>>>>
>>>> Why is the band information not loaded automatically? Is it possible to
>>>> load it programmatically without using the web GUI?
>>>>
>>>> I'm using 2.9.1.
>>>>
>>>> $ curl -u admin:geoserver -XPOST http://localhost:8080/geoserve
>>>> r/rest/workspaces/files/coveragestores.json -H "Content-Type:
>>>> application/json" --data '{
>>>> "coverageStore" : {
>>>> "name" : "myraster",
>>>> "type" : "GeoTIFF",
>>>> "enabled" : true,
>>>> "workspace" : {
>>>> "name" : "files"
>>>> },
>>>> "url" : "file:test.tif"
>>>> }
>>>> }'
>>>>
>>>> $ curl -u admin:geoserver -XPOST http://localhost:8080/geoserve
>>>> r/rest/workspaces/files/coveragestores/myraster/coverages.json -H
>>>> "Content-Type: application/json" --data '{
>>>> "coverage" : {
>>>> "name" : "myraster",
>>>> "enabled" : true,
>>>> "store" : {
>>>> "name" : "files:myraster"
>>>> }
>>>> }
>>>> }'
>
Re: [Geoserver-users] Missing band definitions when adding a GeoTIFF via REST
Hi,
Thanks for your responses.
@Peter The problem is that the raster files are uploaded by other process
to the server and we
don't know their metadata beforehand nor we have the possibility to use a
GUI manually for each of them.
@Andrea Thanks, I should have read the doc more carefully... That's great,
with 'external' the metadata gets loaded automatically. The only thing is
that the layer name is taken from the file name. Is it possible to specify
the name of the resulting layer in the same request?
Regards.
2016-11-11 14:18 GMT+01:00 Andrea Aime :
> As far as I know, you have to change the way you're creating the coverage
> store,
> using the "external" syntax similar to this example configuring a
> shapefile that's
> already on disk:
>
> http://docs.geoserver.org/latest/en/user/rest/examples/
> curl.html#adding-an-existing-shapefile
>
> Sorry I don't have an example for raster data handy (if anybody reading
> has one, there's
> a guide for quick documentation contributions here:
> http://docs.geoserver.org/latest/en/docguide/quickfix.html )
>
> Cheers
> Andrea
>
>
> On Fri, Nov 11, 2016 at 1:32 PM, Víctor González <
> victor.gonza...@geomati.co> wrote:
>
>> Hi,
>>
>> I'm loading a new GeoTIFF layer using REST by adding a new coveragestore
>> and coverage (requests below). After that, the layer does not have
>> information about bands and I have to use the "Reload band definitions"
>> option in the web GUI to load them manually (because I don't know the
>> raster metadata and I cannot include it in the request).
>>
>> Why is the band information not loaded automatically? Is it possible to
>> load it programmatically without using the web GUI?
>>
>> I'm using 2.9.1.
>>
>> $ curl -u admin:geoserver -XPOST http://localhost:8080/geoserve
>> r/rest/workspaces/files/coveragestores.json -H "Content-Type:
>> application/json" --data '{
>> "coverageStore" : {
>> "name" : "myraster",
>> "type" : "GeoTIFF",
>> "enabled" : true,
>> "workspace" : {
>> "name" : "files"
>> },
>> "url" : "file:test.tif"
>> }
>> }'
>>
>> $ curl -u admin:geoserver -XPOST http://localhost:8080/geoserve
>> r/rest/workspaces/files/coveragestores/myraster/coverages.json -H
>> "Content-Type: application/json" --data '{
>> "coverage" : {
>> "name" : "myraster",
>> "enabled" : true,
>> "store" : {
>> "name" : "files:myraster"
>> }
>> }
>> }'
>>
>> Best regards.
>>
>> --
>> Víctor González
>> http://geomati.co
>>
>>
>> --
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>> ___
>> Geoserver-users mailing list
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
>
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054 Massarosa (LU)
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>
>
>
&
[Geoserver-users] Missing band definitions when adding a GeoTIFF via REST
Hi,
I'm loading a new GeoTIFF layer using REST by adding a new coveragestore
and coverage (requests below). After that, the layer does not have
information about bands and I have to use the "Reload band definitions"
option in the web GUI to load them manually (because I don't know the
raster metadata and I cannot include it in the request).
Why is the band information not loaded automatically? Is it possible to
load it programmatically without using the web GUI?
I'm using 2.9.1.
$ curl -u admin:geoserver -XPOST
http://localhost:8080/geoserver/rest/workspaces/files/coveragestores.json
-H "Content-Type: application/json" --data '{
"coverageStore" : {
"name" : "myraster",
"type" : "GeoTIFF",
"enabled" : true,
"workspace" : {
"name" : "files"
},
"url" : "file:test.tif"
}
}'
$ curl -u admin:geoserver -XPOST
http://localhost:8080/geoserver/rest/workspaces/files/coveragestores/myraster/coverages.json
-H "Content-Type: application/json" --data '{
"coverage" : {
"name" : "myraster",
"enabled" : true,
"store" : {
"name" : "files:myraster"
}
}
}'
Best regards.
--
Víctor González
http://geomati.co
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Show all geometries when the WMS TIME parameter is not provided
Hi Andrea, Great! It's working very nice in GeoServer 2.9-beta. 0/ is not accepted in 2.9-beta (it was accepted when provided as TIME param in 2.8.1), but 0/9998 is; so 2.9-beta solves the problem for me. Thanks! 2016-03-03 19:11 GMT+01:00 Andrea Aime : > Hi Victor, > what you are asking for is not possible in GeoServer 2.8, but you can try > out > GeoServer 2.9-beta where you should be able to enter a range as the default > value. Mind however it still has to be a date range, I'm not sure 0/ > is going > to work (you can try and see, according to the docs it might work as a > reduced > accuracy time range > http://docs.geoserver.org/latest/en/user/services/wms/time.html#reduced-accuracy-times > ) > > Cheers > Andrea > > > On Tue, Mar 1, 2016 at 8:59 AM, Víctor González < > victor.gonza...@geomati.co> wrote: > >> Hello, >> >> I have a layer in GeoServer with time dimension: no End attribute, >> Presentation: List (in fact I tried other options with no luck). >> >> I'm accessing it via WMS and I would like to show all the geometries when >> the TIME parameter is not provided. I tried setting the 0/ range as >> default value (Default value: Use the reference value) but the Reference >> value field only accepts an ISO8601 date, not a range. >> >> If I can send a range in the TIME parameter request, shouldn't it be >> possible to put it as default value as well? Is there any other approach to >> do this that I'm not considering? >> >> Cheers. >> -- >> Víctor González >> http://geomati.co >> >> >> -- >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >> ___ >> Geoserver-users mailing list >> Geoserver-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-users >> >> > > > -- > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > phone: +39 0584 962313 > fax: +39 0584 1660272 > mob: +39 339 8844549 > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* > > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinatario del messaggio, > per le finalità indicate nel messaggio stesso. Qualora riceviate questo > messaggio senza esserne il destinatario, Vi preghiamo cortesemente di > darcene notizia via e-mail e di procedere alla distruzione del messaggio > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od > utilizzarlo per finalità diverse, costituisce comportamento contrario ai > principi dettati dal D.Lgs. 196/2003. > > > > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please contact > immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > completeness of sent messages and accepts no responsibility for changes > made after they were sent or for other risks which arise as a result of > e-mail transmission, viruses, etc. > > --- > -- Víctor González http://geomati.co -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Show all geometries when the WMS TIME parameter is not provided
I forgot to mention, GeoServer version is 2.8.1. I haven't tried with any other version. 2016-03-01 8:59 GMT+01:00 Víctor González : > Hello, > > I have a layer in GeoServer with time dimension: no End attribute, > Presentation: List (in fact I tried other options with no luck). > > I'm accessing it via WMS and I would like to show all the geometries when > the TIME parameter is not provided. I tried setting the 0/ range as > default value (Default value: Use the reference value) but the Reference > value field only accepts an ISO8601 date, not a range. > > If I can send a range in the TIME parameter request, shouldn't it be > possible to put it as default value as well? Is there any other approach to > do this that I'm not considering? > > Cheers. > -- > Víctor González > http://geomati.co > -- Víctor González http://geomati.co -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] Show all geometries when the WMS TIME parameter is not provided
Hello, I have a layer in GeoServer with time dimension: no End attribute, Presentation: List (in fact I tried other options with no luck). I'm accessing it via WMS and I would like to show all the geometries when the TIME parameter is not provided. I tried setting the 0/ range as default value (Default value: Use the reference value) but the Reference value field only accepts an ISO8601 date, not a range. If I can send a range in the TIME parameter request, shouldn't it be possible to put it as default value as well? Is there any other approach to do this that I'm not considering? Cheers. -- Víctor González http://geomati.co -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] NPE in WFS GetFeature request. Problem with data permissions
Hi, I just added an issue to the tracker for this, in case someone wants to follow the progress: https://osgeo-org.atlassian.net/browse/GEOS-7391 Cheers. 2016-01-19 10:12 GMT+01:00 Víctor González : > Hi, > > I found a problem with WFS GetFeature requests returning a NPE (see > exception below). These conditions must occur at the same time for the > problem to appear: > > * There must be a data rule that allows an entire workspace only for a > specific role (for example, sf.*.r: myrole). > * There must be a data rule that allows a single layer in that workspace > for any role (sf.roads.r: *). > * The first WFS request that arrives to the server must come from a user > that doesn't have the role described in the first condition. > > You can reproduce it with the following data_dir (tested on GeoServer > 2.8.1): https://www.dropbox.com/s/gdkmht7hsipgcg9/data_dir.tar.gz?dl=0. > Performing this request: > > curl -X POST "http://localhost:8080/geoserver/wfs"; -d @/tmp/payload.xml > -H "Content-Type: application/xml; charset=UTF-8" > > with this payload.xml: > > http://www.opengis.net/wfs"; service="WFS" > version="1.0.0" xsi:schemaLocation="http://www.opengis.net/wfs > http://schemas.opengis.net/wfs/1.0.0/WFS-transaction.xsd"; xmlns:xsi=" > http://www.w3.org/2001/XMLSchema-instance";> typeName="feature:tiger_roads" xmlns:feature="http://www.census.gov"/ > > > > The problem comes because the XML schema for the WFS request has not been > obtained previously and the user that performs the request doesn't have > permissions to see the workspace (even though it can see a specific layer > within that workspace). It doesn't happen after the admin user (or any > other user that can see all layers) performs a WFS request and the schema > is built successfully. > > What I'm trying to do is to secure all layers in a workspace except from > one. Am I doing something wrong or is this a bug in GeoServer? > > Best regards. > > --- > > java.lang.NullPointerException > at > org.geoserver.wfs.xml.FeatureTypeSchemaBuilder.buildSchemaInternal(FeatureTypeSchemaBuilder.java:194) > at > org.geoserver.wfs.xml.FeatureTypeSchemaBuilder.addApplicationTypes(FeatureTypeSchemaBuilder.java:503) > at org.geoserver.wfs.xml.v1_0_0.WFS.buildSchema(WFS.java:231) > at org.geotools.xml.XSD.getSchema(XSD.java:232) > at org.geotools.xml.SchemaLocator.locateSchema(SchemaLocator.java:96) > at > org.geotools.xml.impl.ParserHandler.startElement(ParserHandler.java:404) > at > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509) > at > com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:380) > at > com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook(XMLNSDocumentScannerImpl.java:614) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3135) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:880) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606) > at > com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:118) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848) > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777) > at > com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) > at > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213) > at > com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:642) > at > com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:326) > at org.geotools.xml.Parser.parse(Parser.java:240) > at org.geotools.xml.Parser.parse(Parser.java:188) > at org.geoserver.wfs.xml.v1_0_0.WfsXmlReader.read(WfsXmlReader.java:79) > at org.geoserver.ows.Dispatcher.parseRequestXML(Dispatcher.java:1553) > at org.geoserver.ows.Dispatcher.dispatch(Dispatcher.java:691) > at > org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:265) > at > org.springframework.web.servlet.mvc.AbstractControll
[Geoserver-users] NPE in WFS GetFeature request. Problem with data permissions
DebugFilter.doFilter(SessionDebugFilter.java:48)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at
org.geoserver.filters.FlushSafeFilter.doFilter(FlushSafeFilter.java:44)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
--
Víctor González
http://geomati.co
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
