Dear All,
I am using geoserver with WCS. I have a question to you about *.JPW and
*.PGW files.
I don't understand what ar JPW and PGW files, how create them ?
Anybody can help me please\?
Thanks a lot !
Bui Hong Son
Deputy Chief of SCIREN
http://ciren.vn
http://www2.hcm.ciren.gov.vn/cirengis
-----Original Message-----
From: geoserver-users-bounces@lists.sourceforge.net
[mailto:geoserver-users-bounces@lists.sourceforge.net] On Behalf Of
geoserver-users-request@lists.sourceforge.net
Sent: Thursday, October 25, 2007 11:43 PM
To: geoserver-users@lists.sourceforge.net
Subject: Geoserver-users Digest, Vol 17, Issue 53
Send Geoserver-users mailing list submissions to
geoserver-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/geoserver-users
or, via email, send a message with subject or body 'help' to
geoserver-users-request@lists.sourceforge.net
You can reach the person managing the list at
geoserver-users-owner@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Geoserver-users digest..."
Today's Topics:
1. Re: 1.6.3 Beta 3 war in JBoss 4.0.5 (Andy Dale)
2. Re: How to adjust the tolerance of FeatureInfo-requests?
(Justin Deoliveira)
3. Specifying a custom native projection (David R Robison)
4. Re: Specifying a custom native projection (Justin Deoliveira)
5. Re: How to adjust the tolerance of FeatureInfo-requests?
(Gabriel Rold?n)
----------------------------------------------------------------------
Message: 1
Date: Thu, 25 Oct 2007 11:36:44 +0200
From: "Andy Dale" <andy.dale@anonymised.com>
Subject: Re: [Geoserver-users] 1.6.3 Beta 3 war in JBoss 4.0.5
To: "Andrea Aime" <aaime@anonymised.com>
Cc: geoserver-users@lists.sourceforge.net
Message-ID:
<faa313130710250236k477031ep597793cc9f88e25a@anonymised.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi,
I have carried out a bit of testing, with a config I know works (
JBoss-4.0.4.GA and geoserver-1.5.1.war) without the data dir being set and
it works fine, but when i try to deploy the 1.6 war i get the same errors as
in the JBoss-4.0.5.GA environment. This leads me to believe that the data
dir is not the cause/solution to the problem.
Thanks,
Andy
On 25/10/2007, Andrea Aime <aaime@anonymised.com> wrote:
Andy Dale ha scritto:
> Hi,
>
> I am trying to deploy geoserver as a war archive within JBoss-4.0.5.GA
> <http://JBoss-4.0.5.GA>, but unfortunately it will not deploy at all
> . The first error that appears is the following :
>
> 2007-10-25 10:59:23,886 DEBUG [org.jboss.web.tomcat.tc5.TomcatDeployer]
> Using session cookies default setting
> 2007-10-25 10:59:24,396 ERROR [STDERR] log4j:ERROR A
> "org.jboss.logging.util.OnlyOnceErrorHandler" object is not assignable
> to a " org.apache.log4j.spi.Error
> Handler" variable.
> 2007-10-25 10:59:24,397 ERROR [STDERR] log4j:ERROR The class
> "org.apache.log4j.spi.ErrorHandler" was loaded by
> 2007-10-25 10:59:24,397 ERROR [STDERR] log4j:ERROR [WebappClassLoader
> delegate: false
> repositories:
> /WEB-INF/classes/
> ----------> Parent Classloader:
> java.net.FactoryURLClassLoader@anonymised.com
> ] whereas object of type
> 2007-10-25 10:59:24,398 ERROR [STDERR] log4j:ERROR "
> org.jboss.logging.util.OnlyOnceErrorHandler" was loaded by
> [org.jboss.system.server.NoAnnotationURLClass
> Loader@anonymised.com].
> 2007-10-25 10:59:24,532 ERROR [STDERR] log4j:ERROR Could not create an
> Appender. Reported error follows.
> 2007-10-25 10:59:24,532 ERROR [STDERR] java.lang.ClassCastException:
> org.jboss.logging.appender.DailyRollingFileAppender
> 2007-10-25 10:59:24,534 ERROR [STDERR] at
> org.apache.log4j.xml.DOMConfigurator.parseAppender
> (DOMConfigurator.java:175)
> 2007-10-25 10:59:24,535 ERROR [STDERR] at
> org.apache.log4j.xml.DOMConfigurator.findAppenderByName(
DOMConfigurator.java:150)
> 2007-10-25 10:59:24,535 ERROR [STDERR] at
> org.apache.log4j.xml.DOMConfigurator.findAppenderByReference
> (DOMConfigurator.java:163)
> 2007-10-25 10:59:24,536 ERROR [STDERR] at
> org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(
DOMConfigurator.java:425)
> 2007-10-25 10:59:24,536 ERROR [STDERR] at
> org.apache.log4j.xml.DOMConfigurator.parseRoot (DOMConfigurator.java
:394)
> 2007-10-25 10:59:24,536 ERROR [STDERR] at
> org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:829)
> 2007-10-25 10:59:24,537 ERROR [STDERR] at
> org.apache.log4j.xml.DOMConfigurator.doConfigure (DOMConfigurator.java
:712)
> 2007-10-25 10:59:24,537 ERROR [STDERR] at
> org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java
:618)
> 2007-10-25 10:59:24,537 ERROR [STDERR] at
> org.apache.log4j.helpers.OptionConverter.selectAndConfigure
> (OptionConverter.java:470)
> 2007-10-25 10:59:24,538 ERROR [STDERR] at
> org.apache.log4j.LogManager.<clinit>(LogManager.java:122)This one I've never seen, but does not seem to be fatal.
> This then has a knock on effect, and the next exception is:
>
> Initialization of bean failed; nested exception is
> java.lang.NullPointerException: null
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'config' defined in URL
> [jar:file:/usr/local/jboss-4.0.5.GA_NO_IMS/se
> rver/default/tmp/deploy/tmp54840geoserver-
> exp.war/WEB-INF/lib/main-1.6-beta3.jar!/applicationContext.xml]:
> Initialization of bean failed; nested exception i
> s java.lang.NullPointerException: null
> java.lang.NullPointerException
> at java.io.FileInputStream .<init>(FileInputStream.java:103)
> at
> org.vfny.geoserver.global.xml.XMLConfigReader.loadServices(
XMLConfigReader.java:241)
> at
> org.vfny.geoserver.global.xml.XMLConfigReader.load(XMLConfigReader.java
> :205)
> at
> org.vfny.geoserver.global.xml.XMLConfigReader.<init>(
XMLConfigReader.java:169)
> at
> org.vfny.geoserver.global.Config.setApplicationContext(Config.java:70)
> at
>
org.springframework.context.support.ApplicationContextAwareProcessor.postPro
cessBeforeInitialization
> (ApplicationContextAwareProcessor.java:84)
> at
>
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory
.applyBeanPostProcessorsBeforeInitialization
(AbstractAutowireCapableB
> eanFactory.java :248)
> at
>
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory
.createBean
(AbstractAutowireCapableBeanFactory.java:362)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean
> (AbstractBeanFactory.java:226)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(
AbstractBeanFactory.java:147)
> at
>
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolv
eReference
> (BeanDefinitionValueResolver.java:176)
> at
>
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolv
eValueIfNecessary
(BeanDefinitionValueResolver.java:105)
> at
>
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactoThis usually happens when GeoServer war is not unpacked
during deploy. If you don't set the GEOSERVER_DATA_DIR environment
variable GeoServer will try to use the data_dir we ship
inside the war, and fail if the war is not unpacked.Hope this helps
Cheers
Andrea
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Thu, 25 Oct 2007 08:26:52 -0700
From: Justin Deoliveira <jdeolive@anonymised.com>
Subject: Re: [Geoserver-users] How to adjust the tolerance of
FeatureInfo-requests?
To: Andrea Aime <aaime@anonymised.com>
Cc: Tilo W?therich <tilo.wuetherich@anonymised.com>, Mailingliste Geoserver
<geoserver-users@lists.sourceforge.net>
Message-ID: <4720B5BC.3090807@anonymised.com>
Content-Type: text/plain; charset=us-ascii
+1, sounds like a good way to handle it.
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi Tilo,
Currently this is not configurable. but i agree that it would be useful
for the client to be able to specify the size of a buffer. As clicking
on points and lines sometimes can be quite tedious.Do you want to create a feature request in the issue tracker?
Tilo has created the issue here:
http://jira.codehaus.org/browse/GEOS-1434Now, I was thinking about it a little and it occurred to me it
has a striking resemblance to the meta-buffer issue.
The meta-buffer is the number of extra pixels we consider around
an image to make sure every feature contributing to the
current map gets rendered for good. When features such as points
have big symbolizers (think a big circle) they do contribute
(partially) to the current map even if their geometry lay outside
of the map bounds. The meta buffer is the measure of the biggest
symbolizer (bigger point, thicker line) used in the map styling.Now, if you think about it, the size of the ideal getfeatureinfo
search area is exactly the meta-buffer. What's more interesting is
that we already have code to automatically compute the meta buffer
from the map style, so most of the time you would not even need
to provide it manually.To recap the idea is:
* make GetFeatureInfo use the metabuffer computation code and
use a search area that matches the biggest symbol size for each
layer (in fact, half of the symbol size)
* as with GetMap, if the user provides "&buffer=xxx" then use
it as the search area for GetFeatureInfo.How does this sound?
Cheers
Andrea-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users!DSPAM:4007,472051e0273333668746562!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
------------------------------
Message: 3
Date: Thu, 25 Oct 2007 11:42:59 -0400
From: David R Robison <drrobison@anonymised.com>
Subject: [Geoserver-users] Specifying a custom native projection
To: Mailingliste Geoserver <geoserver-users@lists.sourceforge.net>
Message-ID: <4720B983.8090405@anonymised.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I have received a shapefile that has a custom projection associated with
it. I loaded it into PostGIS and then linked it to geoserver, however, I
do not know how to indicate what the native SRS WKT is. Can anyone give
me any pointers? Thanks, David Robison
--
David R Robison
Open Roads Consulting, Inc.
708 S. Battlefield Blvd., Chesapeake, VA 23322
phone: (757) 546-3401
e-mail: drrobison@anonymised.com
web: http://openroadsconsulting.com
blog: http://therobe.blogspot.com
book: http://www.xulonpress.com/book_detail.php?id=2579
------------------------------
Message: 4
Date: Thu, 25 Oct 2007 09:31:32 -0700
From: Justin Deoliveira <jdeolive@anonymised.com>
Subject: Re: [Geoserver-users] Specifying a custom native projection
To: David R Robison <drrobison@anonymised.com>
Cc: Mailingliste Geoserver <geoserver-users@lists.sourceforge.net>
Message-ID: <4720C4E4.4000409@anonymised.com>
Content-Type: text/plain; charset=us-ascii
Hi David,
So are you saying that you have the SRS WKT? or that you do not have it
and need a way to figure it out. If its the former you can follow the
instructions here:
http://docs.codehaus.org/display/GEOSDOC/Custom+projection+definition+in+Geo
server+1.5.0+(onwards)
If the latter i am unsure. Reverse engineering the projection of a
shapefile is kind of tough. I will leave that one for the experts.
-Justin
David R Robison wrote:
I have received a shapefile that has a custom projection associated with
it. I loaded it into PostGIS and then linked it to geoserver, however, I
do not know how to indicate what the native SRS WKT is. Can anyone give
me any pointers? Thanks, David Robison
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
------------------------------
Message: 5
Date: Thu, 25 Oct 2007 18:43:22 +0200
From: Gabriel Rold?n <gabriel.roldan@anonymised.com>
Subject: Re: [Geoserver-users] How to adjust the tolerance of
FeatureInfo-requests?
To: geoserver-users@lists.sourceforge.net
Cc: Tilo W?therich <tilo.wuetherich@anonymised.com>, Justin Deoliveira
<jdeolive@anonymised.com>
Message-ID: <200710251843.22599.gabriel.roldan@anonymised.com>
Content-Type: text/plain; charset="iso-8859-1"
+1 on the metabuffer stuff.
Also, it is not strange that it gets difficult to find a point through
GetFeatureInfo. When sending a GetFeatureInfo from a ui, it gets really
tricky to click on a point near enough to the actual point. See for example
the attached image. Its the result of rendering the same point with a small
circle marker and a bigger triangle marker.
The triangle is never centered at the point location, but its top most
corner
seems to be.
So, I don't quite remember if the SLD spec says nothing about how to locate
a
marker regarding the point location, still it seems quite intuitive (as a
user) to get them centered.
So, should we open an issue against the renderer at all?
Gabriel
On Thursday 25 October 2007 05:26:52 pm Justin Deoliveira wrote:
+1, sounds like a good way to handle it.
Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> Hi Tilo,
>>
>> Currently this is not configurable. but i agree that it would be useful
>> for the client to be able to specify the size of a buffer. As clicking
>> on points and lines sometimes can be quite tedious.
>>
>> Do you want to create a feature request in the issue tracker?
>
> Tilo has created the issue here:
> http://jira.codehaus.org/browse/GEOS-1434
>
> Now, I was thinking about it a little and it occurred to me it
> has a striking resemblance to the meta-buffer issue.
> The meta-buffer is the number of extra pixels we consider around
> an image to make sure every feature contributing to the
> current map gets rendered for good. When features such as points
> have big symbolizers (think a big circle) they do contribute
> (partially) to the current map even if their geometry lay outside
> of the map bounds. The meta buffer is the measure of the biggest
> symbolizer (bigger point, thicker line) used in the map styling.
>
> Now, if you think about it, the size of the ideal getfeatureinfo
> search area is exactly the meta-buffer. What's more interesting is
> that we already have code to automatically compute the meta buffer
> from the map style, so most of the time you would not even need
> to provide it manually.
>
> To recap the idea is:
> * make GetFeatureInfo use the metabuffer computation code and
> use a search area that matches the biggest symbol size for each
> layer (in fact, half of the symbol size)
> * as with GetMap, if the user provides "&buffer=xxx" then use
> it as the search area for GetFeatureInfo.
>
> How does this sound?
> Cheers
> Andrea
>
>
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
> !DSPAM:4007,472051e0273333668746562!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: point_rendered_with_two_sympolizers.png
Type: image/png
Size: 670 bytes
Desc: not available
------------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
End of Geoserver-users Digest, Vol 17, Issue 53
***********************************************
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.15.10/1091 - Release Date: 10/24/2007
2:31 PM
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.15.10/1091 - Release Date: 10/24/2007
2:31 PM