Re: [Geoserver-users] Caching with Response Headers Settings
Hi, The direct integration creates a cache on disk that don't expires, (geowebcache direct integration), while caching headers tell the browser to cache the tiles for a period of time on the client. So they are 2 different levels of cache. When you update the data, you have to empty the cache on disk. You can do it using the gwc rest interface or using the web interface manually. For the caching headers, keep in mind that if a user gets the tile 1 second before the update, he will see the changes after 2 hours ( the headers tell the browser to don' t update the tile for the time indicated) Il 04/mag/2014 21:06 Shadin shadin...@hotmail.com ha scritto: \in this post http://osgeo-org.1560.x6.nabble.com/Terminate-GeoWebCache-REST-API-Request-td5137944.html I was trying to find a method to cache one layer that its data is updated every 2 hours in the DB. What I've done is: 1. enable direct integration with GeoServer WMS. 2. ass tiled=true parameter to WMS request 3. replace [http://GEOSERVER_URL/wms] with [http://GEOSERVER_URL/gwc/service/wms] 4. check Response Cache Headers with 7200 time specified as in http://docs.geoserver.org/stable/en/user/webadmin/data/layers.html and when i look at the headers I see: Cache-Control:max-age=7200, must-revalidate Content-Disposition:inline; filename=geoserver-dispatch.image Content-Type:image/png *Date:Sun, 04 May 2014 18:38:16 GMT Expires:Sun, 04 May 2014 20:36:36 GMT* geowebcache-cache-result:HIT geowebcache-crs:EPSG:900913 geowebcache-gridset:EPSG:900913 geowebcache-tile-bounds:12523442.71249,2504688.542504,15028131.25499,5009377.08501 geowebcache-tile-index:[13, 9, 4] geowebcache-tile-index:[13, 9, 4] Last-Modified:Sun, 04 May 2014 07:06:05 GMT Server:Apache-Coyote/1.1 Transfer-Encoding:chunked I thought it worked but after 2 hours the layers didn't get updated! it's like that the layer is cached and frozen like forever. I think I'm missing something. any idea? -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Caching-with-Response-Headers-Settings-tp5138490.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] How to know in a coordinate (x, y) is into a ascii grid file
Hi Sandro, it think you can have a better answer in the GeoTools mailing list. https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users Anyway, I guess you can get the envelope of the grid and check the coordinates on it. File file = new File(/home/xxx/grid.asc); AbstractGridFormat format = GridFormatFinder.findFormat(file); reader = format.getReader(file); GridCoverage2D coverage = reader.read(null); Envelope2D envelope = coverage.getEnvelope2D(); // the envelope DirectPosition2D point_to_check = new DirectPosition2D ( x , y ); // your coordinates boolean is_inside = envelope.contains(point_to_check); // check if point is inside the envelope Regards Lorenzo Pini Software Engineer == Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK for more information. == GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it On Fri, May 2, 2014 at 4:56 PM, spresta73 sandro.pre...@digimat.it wrote: Hello, I'm a beginner in using asc grid and geotools library. I'm developing some processes in java and I would understand the way to know if a generic coordinate (x,y) is inside the asc file using geotools libraries. Thanks in advance for any help you will give me. Sandro -- View this message in context: http://osgeo-org.1560.x6.nabble.com/How-to-know-in-a-coordinate-x-y-is-into-a-ascii-grid-file-tp5138303.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] problem using different palettes
well, I am trying to learn... I created this bug report: https://jira.codehaus.org/browse/GEOS-6474 -Jakob jody.garnett wrote That sounds like a bug :) Are you comfortable reporting it to the geoserver issue tracker? -- Jody Garnett On 29 April 2014 at 3:44:34 pm, Jakob Ventin ( jventin@ ) wrote: Hi list, we have encountered a problem with Geoserver 2.5 using palette files. It seems, that (after Tomcat restart) the first palette file to be used in a wms getmap request, will be used in all other wms getmap requests, that have palette= defined, as well. To make it clear, even if we define another palette in the wms getmap request, the one that has been used first (after tomcat restart) will be called. 'Clear cache' or 'Reload configuration' does not help, the only way we have found to define a new palette is to restart Tomcat. This leads to the fact, that it is possible to use only one palette file in Geoserver. Is this the intention, or does it sound like a bug? (If no palette is defined, the output is a normal png without any palette definitions) best regards, Jakob -- View this message in context: http://osgeo-org.1560.x6.nabble.com/problem-using-different-palettes-tp5137653.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Geoserver-users mailing list Geoserver-users@.sourceforge https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Geoserver-users mailing list Geoserver-users@.sourceforge https://lists.sourceforge.net/lists/listinfo/geoserver-users -- View this message in context: http://osgeo-org.1560.x6.nabble.com/problem-using-different-palettes-tp5137653p5138534.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] Why does GetFeature round my floating point numbers, but only for outputFormat=CSV?
Hello All,
I've looked about but I haven't found any thread discussing this, so forgive me
if it has been covered and please point me to the post.
When I use GetFeature I find floating point numbers are being rounded, but only
when I have the parameter outputFormat=CSV. I am using GeoServer v2.4.5. I have
documented this as a question on gis.stackexchange.com
(http://gis.stackexchange.com/questions/93194/why-does-geoservers-getfeature-round-my-numbers-but-only-for-outputformat-csv)
but I'll reiterate here:
Here's my request as JSON:
http://geothermal.smu.edu:9000/geoserver/gtda-contributions/ows?service=WFSversion=1.0.0request=GetFeaturetypeName=gtda-contributions:UNDRadiogenicHeatmaxFeatures=1outputFormat=application/json
...and an excerpt from the response. Note the values for latitude and longitude:
{
type : FeatureCollection,
totalFeatures : 343,
features : [{
type : Feature,
id : UNDRadiogenicHeat.2540ea6b-f94a-3088-9b32-762c77a8e57f,
geometry : {
type : Point,
coordinates : [-92.79726665, 47.90752513]
},
geometry_name : shape,
properties : {
latitude : 47.90752513,
longitude : -92.79726665,
...
Now the same request with outputFormat=cvs:
http://geothermal.smu.edu:9000/geoserver/gtda-contributions/ows?service=WFSversion=1.0.0request=GetFeaturetypeName=gtda-contributions:UNDRadiogenicHeatmaxFeatures=1outputFormat=csv
...and an except of the response. The same portion of the data has been rounded
off (48 instead of 47.90752513, and -93 instead of -92.79726665). (I added the
spaces for easy legibility):
FID, latitude,
longitude,...
UNDRadiogenicHeat.2540ea6b-f94a-3088-9b32-762c77a8e57f, 48,-93,...
I've looked for configurations that might cause this, but I see none. I know
there are filters that could do this, but I get the impression that these need
to be explicitly requested, and the above requests do not include filters.
Is there something I'm overlooking? Is there some way that GeoServer is
treating the data so glaringly differently just because I'm requesting CSV?
Thank you for any insights.
Raj Tanikella
This message and any attachments are solely for the use of intended recipients.
The information contained herein may include trade secrets, protected health or
personal information, privileged or otherwise confidential information.
Unauthorized review, forwarding, printing, copying, distributing, or using such
information is strictly prohibited and may be unlawful. If you are not an
intended recipient, you are hereby notified that you received this email in
error, and that any review, dissemination, distribution or copying of this
email and any attachment is strictly prohibited. If you have received this
email in error, please contact the sender and delete the message and any
attachment from your system. Thank you for your cooperation
--
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
#149; 3 signs your SCM is hindering your productivity
#149; Requirements for releasing software faster
#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Why does GetFeature round my floating point numbers, but only for outputFormat=CSV?
Hi,
At least it seems that the demo layers do not behave like that. The
topp:states has plenty of double fields and values look the same with
http://demo.opengeo.org/geoserver/wfs?service=wfsversion=1.0.0request=getfeaturetypename=topp:statesoutputformat=JSON
and with
http://demo.opengeo.org/geoserver/wfs?service=wfsversion=1.0.0request=getfeaturetypename=topp:statesoutputformat=csv.
Topp:states comes from shapefile, how about your data? Which Geoserver version
do you run?
-Jukka Rahkonen-
Tanikella, Rajanikanth (SCR US) wrote:
Hello All,
I've looked about but I haven't found any thread discussing this, so forgive
me if
it has been covered and please point me to the post.
When I use GetFeature I find floating point numbers are being rounded, but
only
when I have the parameter outputFormat=CSV. I am using GeoServer v2.4.5. I
have documented this as a question on gis.stackexchange.com
(http://gis.stackexchange.com/questions/93194/why-does-geoservers-
getfeature-round-my-numbers-but-only-for-outputformat-csv) but I'll reiterate
here:
Here's my request as JSON:
http://geothermal.smu.edu:9000/geoserver/gtda-
contributions/ows?service=WFSversion=1.0.0request=GetFeaturetypeNam
e=gtda-
contributions:UNDRadiogenicHeatmaxFeatures=1outputFormat=application/
json
...and an excerpt from the response. Note the values for latitude and
longitude:
{
type : FeatureCollection,
totalFeatures : 343,
features : [{
type : Feature,
id : UNDRadiogenicHeat.2540ea6b-f94a-3088-9b32-762c77a8e57f,
geometry : {
type : Point,
coordinates : [-92.79726665, 47.90752513]
},
geometry_name : shape,
properties : {
latitude : 47.90752513,
longitude : -92.79726665,
...
Now the same request with outputFormat=cvs:
http://geothermal.smu.edu:9000/geoserver/gtda-
contributions/ows?service=WFSversion=1.0.0request=GetFeaturetypeNam
e=gtda-contributions:UNDRadiogenicHeatmaxFeatures=1outputFormat=csv
...and an except of the response. The same portion of the data has been
rounded off (48 instead of 47.90752513, and -93 instead of -92.79726665). (I
added the spaces for easy legibility):
FID, latitude,
longitude,...
UNDRadiogenicHeat.2540ea6b-f94a-3088-9b32-762c77a8e57f, 48,-93,...
I've looked for configurations that might cause this, but I see none. I know
there
are filters that could do this, but I get the impression that these need to be
explicitly requested, and the above requests do not include filters.
Is there something I'm overlooking? Is there some way that GeoServer is
treating the data so glaringly differently just because I'm requesting CSV?
Thank you for any insights.
Raj Tanikella
This message and any attachments are solely for the use of intended
recipients.
The information contained herein may include trade secrets, protected health
or
personal information, privileged or otherwise confidential information.
Unauthorized review, forwarding, printing, copying, distributing, or using
such
information is strictly prohibited and may be unlawful. If you are not an
intended
recipient, you are hereby notified that you received this email in error, and
that
any review, dissemination, distribution or copying of this email and any
attachment is strictly prohibited. If you have received this email in error,
please
contact the sender and delete the message and any attachment from your
system. Thank you for your cooperation
--
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
#149; 3 signs your SCM is hindering your productivity #149; Requirements for
releasing software faster #149; Expert tips and advice for migrating your SCM
now http://p.sf.net/sfu/perforce
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
#149; 3 signs your SCM is hindering your productivity
#149; Requirements for releasing software faster
#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Why does GetFeature round my floating point numbers, but only for outputFormat=CSV?
Hi,
You must push the beast into the corner and then you can catch it. Eliminate
one possibility at a time. I would start by converting your data into
shapefile and creating a test layer from that. If it fails in a similar way you
can make a minimal shapefile with couple of features and send it for further
investigations. If it works, the fault is somewhere on the database side.
Convert some data from your view into a regular table and test again. It table
works but view not, then it is something in how the view is handled.
-Jukka Rahkonen-
Tanikella, Rajanikanth (SCR US) wrote:
Hello Jukka,
I'm using GeoServer 2.4.5. Interesting that that the demo data behaves
correctly. My data is not from a shapefile. Rather, we have a custom routine
which loads a database from various files, and the layer is defined as a view
in
that database.
Raj
-Original Message-
From: Rahkonen Jukka (Tike) [mailto:jukka.rahko...@mmmtike.fi]
Sent: Monday, May 05, 2014 10:04 AM
To: Tanikella, Rajanikanth (SCR US); geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Why does GetFeature round my floating point
numbers, but only for outputFormat=CSV?
Hi,
At least it seems that the demo layers do not behave like that. The
topp:states
has plenty of double fields and values look the same with
http://demo.opengeo.org/geoserver/wfs?service=wfsversion=1.0.0request=
getfeaturetypename=topp:statesoutputformat=JSON
and with
http://demo.opengeo.org/geoserver/wfs?service=wfsversion=1.0.0request=
getfeaturetypename=topp:statesoutputformat=csv.
Topp:states comes from shapefile, how about your data? Which Geoserver
version do you run?
-Jukka Rahkonen-
Tanikella, Rajanikanth (SCR US) wrote:
Hello All,
I've looked about but I haven't found any thread discussing this, so
forgive me if it has been covered and please point me to the post.
When I use GetFeature I find floating point numbers are being rounded,
but only when I have the parameter outputFormat=CSV. I am using
GeoServer v2.4.5. I have documented this as a question on
gis.stackexchange.com
(http://gis.stackexchange.com/questions/93194/why-does-geoservers-
getfeature-round-my-numbers-but-only-for-outputformat-csv) but I'll
reiterate
here:
Here's my request as JSON:
http://geothermal.smu.edu:9000/geoserver/gtda-
contributions/ows?service=WFSversion=1.0.0request=GetFeaturetypeNam
e=gtda-
contributions:UNDRadiogenicHeatmaxFeatures=1outputFormat=application
/
json
...and an excerpt from the response. Note the values for latitude and
longitude:
{
type : FeatureCollection,
totalFeatures : 343,
features : [{
type : Feature,
id : UNDRadiogenicHeat.2540ea6b-f94a-3088-9b32-762c77a8e57f,
geometry : {
type : Point,
coordinates : [-92.79726665, 47.90752513]
},
geometry_name : shape,
properties : {
latitude : 47.90752513,
longitude : -92.79726665, ...
Now the same request with outputFormat=cvs:
http://geothermal.smu.edu:9000/geoserver/gtda-
contributions/ows?service=WFSversion=1.0.0request=GetFeaturetypeNam
e=gtda-
contributions:UNDRadiogenicHeatmaxFeatures=1outputFormat=csv
...and an except of the response. The same portion of the data has
been rounded off (48 instead of 47.90752513, and -93 instead of
-92.79726665). (I added the spaces for easy legibility):
FID, latitude,
longitude,...
UNDRadiogenicHeat.2540ea6b-f94a-3088-9b32-762c77a8e57f, 48,-
93,...
I've looked for configurations that might cause this, but I see none.
I know there are filters that could do this, but I get the impression
that these need to be explicitly requested, and the above requests do not
include filters.
Is there something I'm overlooking? Is there some way that GeoServer
is treating the data so glaringly differently just because I'm requesting
CSV?
Thank you for any insights.
Raj Tanikella
This message and any attachments are solely for the use of intended
recipients.
The information contained herein may include trade secrets, protected
health or personal information, privileged or otherwise confidential
information.
Unauthorized review, forwarding, printing, copying, distributing, or
using such information is strictly prohibited and may be unlawful. If
you are not an intended recipient, you are hereby notified that you
received this email in error, and that any review, dissemination,
distribution or copying of this email and any attachment is strictly
prohibited. If you have received this email in error, please contact
the sender and delete the message and any attachment from your system.
Thank you for your cooperation
--
Is your legacy SCM system
Re: [Geoserver-users] Why does GetFeature round my floating point numbers, but only for outputFormat=CSV?
Hello Jukka,
I'm using GeoServer 2.4.5. Interesting that that the demo data behaves
correctly. My data is not from a shapefile. Rather, we have a custom routine
which loads a database from various files, and the layer is defined as a view
in that database.
Raj
-Original Message-
From: Rahkonen Jukka (Tike) [mailto:jukka.rahko...@mmmtike.fi]
Sent: Monday, May 05, 2014 10:04 AM
To: Tanikella, Rajanikanth (SCR US); geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Why does GetFeature round my floating point
numbers, but only for outputFormat=CSV?
Hi,
At least it seems that the demo layers do not behave like that. The
topp:states has plenty of double fields and values look the same with
http://demo.opengeo.org/geoserver/wfs?service=wfsversion=1.0.0request=getfeaturetypename=topp:statesoutputformat=JSON
and with
http://demo.opengeo.org/geoserver/wfs?service=wfsversion=1.0.0request=getfeaturetypename=topp:statesoutputformat=csv.
Topp:states comes from shapefile, how about your data? Which Geoserver version
do you run?
-Jukka Rahkonen-
Tanikella, Rajanikanth (SCR US) wrote:
Hello All,
I've looked about but I haven't found any thread discussing this, so
forgive me if it has been covered and please point me to the post.
When I use GetFeature I find floating point numbers are being rounded,
but only when I have the parameter outputFormat=CSV. I am using
GeoServer v2.4.5. I have documented this as a question on
gis.stackexchange.com
(http://gis.stackexchange.com/questions/93194/why-does-geoservers-
getfeature-round-my-numbers-but-only-for-outputformat-csv) but I'll
reiterate
here:
Here's my request as JSON:
http://geothermal.smu.edu:9000/geoserver/gtda-
contributions/ows?service=WFSversion=1.0.0request=GetFeaturetypeNam
e=gtda-
contributions:UNDRadiogenicHeatmaxFeatures=1outputFormat=application
/
json
...and an excerpt from the response. Note the values for latitude and
longitude:
{
type : FeatureCollection,
totalFeatures : 343,
features : [{
type : Feature,
id : UNDRadiogenicHeat.2540ea6b-f94a-3088-9b32-762c77a8e57f,
geometry : {
type : Point,
coordinates : [-92.79726665, 47.90752513]
},
geometry_name : shape,
properties : {
latitude : 47.90752513,
longitude : -92.79726665, ...
Now the same request with outputFormat=cvs:
http://geothermal.smu.edu:9000/geoserver/gtda-
contributions/ows?service=WFSversion=1.0.0request=GetFeaturetypeNam
e=gtda-contributions:UNDRadiogenicHeatmaxFeatures=1outputFormat=csv
...and an except of the response. The same portion of the data has
been rounded off (48 instead of 47.90752513, and -93 instead of
-92.79726665). (I added the spaces for easy legibility):
FID, latitude,
longitude,...
UNDRadiogenicHeat.2540ea6b-f94a-3088-9b32-762c77a8e57f, 48,-93,...
I've looked for configurations that might cause this, but I see none.
I know there are filters that could do this, but I get the impression
that these need to be explicitly requested, and the above requests do not
include filters.
Is there something I'm overlooking? Is there some way that GeoServer
is treating the data so glaringly differently just because I'm requesting CSV?
Thank you for any insights.
Raj Tanikella
This message and any attachments are solely for the use of intended
recipients.
The information contained herein may include trade secrets, protected
health or personal information, privileged or otherwise confidential
information.
Unauthorized review, forwarding, printing, copying, distributing, or
using such information is strictly prohibited and may be unlawful. If
you are not an intended recipient, you are hereby notified that you
received this email in error, and that any review, dissemination,
distribution or copying of this email and any attachment is strictly
prohibited. If you have received this email in error, please contact
the sender and delete the message and any attachment from your system.
Thank you for your cooperation
--
Is your legacy SCM system holding you back? Join Perforce May
7 to find out:
#149; 3 signs your SCM is hindering your productivity #149;
Requirements for releasing software faster #149; Expert tips and
advice for migrating your SCM now http://p.sf.net/sfu/perforce
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
This message and any attachments are solely for the use of intended recipients.
The information contained herein may include trade secrets, protected health or
personal information, privileged or otherwise confidential information.
Unauthorized review, forwarding, printing, copying,
Re: [Geoserver-users] Why does GetFeature round my floating point numbers, but only for outputFormat=CSV?
But doesn't the fact that the view works for JSON and XML output suggest that
the view is not the problem?
But your suggested methodology (pushing the beast into the corner, I like
that!) is quite sound. I shall have to figure out how to make a shapefile of it.
Thanks for the suggestion!
-Original Message-
From: Rahkonen Jukka (Tike) [mailto:jukka.rahko...@mmmtike.fi]
Sent: Monday, May 05, 2014 10:20 AM
To: Tanikella, Rajanikanth (SCR US); geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Why does GetFeature round my floating point
numbers, but only for outputFormat=CSV?
Hi,
You must push the beast into the corner and then you can catch it. Eliminate
one possibility at a time. I would start by converting your data into
shapefile and creating a test layer from that. If it fails in a similar way you
can make a minimal shapefile with couple of features and send it for further
investigations. If it works, the fault is somewhere on the database side.
Convert some data from your view into a regular table and test again. It table
works but view not, then it is something in how the view is handled.
-Jukka Rahkonen-
Tanikella, Rajanikanth (SCR US) wrote:
Hello Jukka,
I'm using GeoServer 2.4.5. Interesting that that the demo data
behaves correctly. My data is not from a shapefile. Rather, we have
a custom routine which loads a database from various files, and the
layer is defined as a view in that database.
Raj
-Original Message-
From: Rahkonen Jukka (Tike) [mailto:jukka.rahko...@mmmtike.fi]
Sent: Monday, May 05, 2014 10:04 AM
To: Tanikella, Rajanikanth (SCR US);
geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Why does GetFeature round my floating
point numbers, but only for outputFormat=CSV?
Hi,
At least it seems that the demo layers do not behave like that. The
topp:states has plenty of double fields and values look the same with
http://demo.opengeo.org/geoserver/wfs?service=wfsversion=1.0.0reques
t= getfeaturetypename=topp:statesoutputformat=JSON
and with
http://demo.opengeo.org/geoserver/wfs?service=wfsversion=1.0.0reques
t= getfeaturetypename=topp:statesoutputformat=csv.
Topp:states comes from shapefile, how about your data? Which Geoserver
version do you run?
-Jukka Rahkonen-
Tanikella, Rajanikanth (SCR US) wrote:
Hello All,
I've looked about but I haven't found any thread discussing this, so
forgive me if it has been covered and please point me to the post.
When I use GetFeature I find floating point numbers are being
rounded, but only when I have the parameter outputFormat=CSV. I am
using GeoServer v2.4.5. I have documented this as a question on
gis.stackexchange.com
(http://gis.stackexchange.com/questions/93194/why-does-geoservers-
getfeature-round-my-numbers-but-only-for-outputformat-csv) but I'll
reiterate
here:
Here's my request as JSON:
http://geothermal.smu.edu:9000/geoserver/gtda-
contributions/ows?service=WFSversion=1.0.0request=GetFeaturetypeNam
e=gtda-
contributions:UNDRadiogenicHeatmaxFeatures=1outputFormat=application
/
json
...and an excerpt from the response. Note the values for latitude
and
longitude:
{
type : FeatureCollection,
totalFeatures : 343,
features : [{
type : Feature,
id : UNDRadiogenicHeat.2540ea6b-f94a-3088-9b32-762c77a8e57f,
geometry : {
type : Point,
coordinates : [-92.79726665, 47.90752513]
},
geometry_name : shape,
properties : {
latitude : 47.90752513,
longitude : -92.79726665, ...
Now the same request with outputFormat=cvs:
http://geothermal.smu.edu:9000/geoserver/gtda-
contributions/ows?service=WFSversion=1.0.0request=GetFeaturetypeNam
e=gtda-
contributions:UNDRadiogenicHeatmaxFeatures=1outputFormat=csv
...and an except of the response. The same portion of the data has
been rounded off (48 instead of 47.90752513, and -93 instead of
-92.79726665). (I added the spaces for easy legibility):
FID, latitude,
longitude,...
UNDRadiogenicHeat.2540ea6b-f94a-3088-9b32-762c77a8e57f, 48,-
93,...
I've looked for configurations that might cause this, but I see none.
I know there are filters that could do this, but I get the
impression that these need to be explicitly requested, and the above
requests do not
include filters.
Is there something I'm overlooking? Is there some way that GeoServer
is treating the data so glaringly differently just because I'm requesting
CSV?
Thank you for any insights.
Raj Tanikella
This message and any attachments are solely for the use of intended
recipients.
The information contained herein may include trade secrets,
protected health or personal information, privileged or otherwise
confidential
information.
Unauthorized review, forwarding,
[Geoserver-users] Geoserver WPS python scripting
*Hi list:* *I'm trying to run python script done through WPS but geoserver does not recognize the existence of geoprocesses I created.* *I'm following the instructions:* http://docs.geoserver.org/stable/en/user/community/scripting/py/index.html http://suite.opengeo.org/docs/latest/processing/scripting/processcreate.html *When I make a GetCapabilities* ( http://localhost:8080/geoserver/ows?service=wpsversion=1.0.0request=GetCapabilities), get the list of all who are part of geoprocesses geoserver (gs.*, geo.*, vec.*, ras.*, JTS.*,gt.*) but none of them is py.* *When I run a DescribeProcess* ( http://localhost:8080/geoserver/ows?service=WPSversion=1.0.0request=DescribeProcessidentifier=py:distbear ) get the next response: ows:ExceptionReport xmlns:ows=http://www.opengis.net/ows/1.1; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; version=1.1.0 xsi:schemaLocation=http://www.opengis.net/ows/1.1 http://localhost:8080/geoserver/schemas/ows/1.1.0/owsAll.xsd; ows:Exception exceptionCode=NoApplicableCode ows:ExceptionTextNo such process: py:distbear/ows:ExceptionText /ows:Exception /ows:ExceptionReport *and the log of the geoserver reports:* 2014-05-05 11:50:12,296 WARN [geoserver.ows] - Could not get a ServiceInfo for service wps thus could not check if the service is enabled 2014-05-05 11:50:12,298 ERROR [geoserver.ows] - org.geoserver.wps.WPSException: No such process: py:distbear at org.geoserver.wps.DescribeProcess.processDescription(DescribeProcess.java:106) at org.geoserver.wps.DescribeProcess.run(DescribeProcess.java:96) at org.geoserver.wps.DefaultWebProcessingService.describeProcess(DefaultWebProcessingService.java:69) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318) *If for exmaple i do describeprocess of JTS:buffer:* http://localhost:8080/geoserver/ows?service=WPSversion=1.0.0request=DescribeProcessidentifier=JTS:buffer *this works fine and works well for any pre-existing geoprocessing in geoserver.* *My geoserver was compiled with*: mvn clean install -Pwps *The version I'm using is* : (geoserver and tomcat) Versión:2.4-SNAPSHOT Revisión de Git: ea0d7c50695f6c2a4564fc5f8fceb1c0b6eb543a Fecha de compilación :21-Mar-2014 19:03 Versión de GeoTools :10-SNAPSHOT (rev ff340eb96a28b463470cc79a566f8ed12fab934e) Versión GeoWebCache 1.5.0 (rev 1.5.x/f981cafd349886bb2a1ef45067f26b1aa8e4aff4) Apache Tomcat/6.0.35 JVM: 1.6.0_30-b30- Appreciate your help! Cheers Pablo -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Why does GetFeature round my floating point numbers, but only for outputFormat=CSV?
Hi,
Geoserver WFS should make a zipped shapefile for you with outputformat
SHAPE-ZIP.
http://demo.opengeo.org/geoserver/wfs?service=wfsversion=1.0.0request=getfeaturetypename=topp:statesoutputformat=SHAPE-ZIP
I don't know why Firefox did not save the URL for me, but the DownThemAll
plugin did.
-Jukka Rahkonen-
Tanikella, Rajanikanth (SCR US) wrote:
But doesn't the fact that the view works for JSON and XML output suggest that
the view is not the problem?
But your suggested methodology (pushing the beast into the corner, I like
that!) is quite sound. I shall have to figure out how to make a shapefile of
it.
Thanks for the suggestion!
-Original Message-
From: Rahkonen Jukka (Tike) [mailto:jukka.rahko...@mmmtike.fi]
Sent: Monday, May 05, 2014 10:20 AM
To: Tanikella, Rajanikanth (SCR US); geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Why does GetFeature round my floating point
numbers, but only for outputFormat=CSV?
Hi,
You must push the beast into the corner and then you can catch it. Eliminate
one possibility at a time. I would start by converting your data into
shapefile and creating a test layer from that. If it fails in a similar way you
can make a minimal shapefile with couple of features and send it for further
investigations. If it works, the fault is somewhere on the database side.
Convert some data from your view into a regular table and test again. It table
works but view not, then it is something in how the view is handled.
-Jukka Rahkonen-
Tanikella, Rajanikanth (SCR US) wrote:
Hello Jukka,
I'm using GeoServer 2.4.5. Interesting that that the demo data
behaves correctly. My data is not from a shapefile. Rather, we have
a custom routine which loads a database from various files, and the
layer is defined as a view in that database.
Raj
-Original Message-
From: Rahkonen Jukka (Tike) [mailto:jukka.rahko...@mmmtike.fi]
Sent: Monday, May 05, 2014 10:04 AM
To: Tanikella, Rajanikanth (SCR US);
geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Why does GetFeature round my floating
point numbers, but only for outputFormat=CSV?
Hi,
At least it seems that the demo layers do not behave like that. The
topp:states has plenty of double fields and values look the same with
http://demo.opengeo.org/geoserver/wfs?service=wfsversion=1.0.0reques
t= getfeaturetypename=topp:statesoutputformat=JSON
and with
http://demo.opengeo.org/geoserver/wfs?service=wfsversion=1.0.0reques
t= getfeaturetypename=topp:statesoutputformat=csv.
Topp:states comes from shapefile, how about your data? Which Geoserver
version do you run?
-Jukka Rahkonen-
Tanikella, Rajanikanth (SCR US) wrote:
Hello All,
I've looked about but I haven't found any thread discussing this, so
forgive me if it has been covered and please point me to the post.
When I use GetFeature I find floating point numbers are being
rounded, but only when I have the parameter outputFormat=CSV. I am
using GeoServer v2.4.5. I have documented this as a question on
gis.stackexchange.com
(http://gis.stackexchange.com/questions/93194/why-does-geoservers-
getfeature-round-my-numbers-but-only-for-outputformat-csv) but I'll
reiterate
here:
Here's my request as JSON:
http://geothermal.smu.edu:9000/geoserver/gtda-
contributions/ows?service=WFSversion=1.0.0request=GetFeaturetypeNam
e=gtda-
contributions:UNDRadiogenicHeatmaxFeatures=1outputFormat=application
/
json
...and an excerpt from the response. Note the values for latitude
and
longitude:
{
type : FeatureCollection,
totalFeatures : 343,
features : [{
type : Feature,
id : UNDRadiogenicHeat.2540ea6b-f94a-3088-9b32-762c77a8e57f,
geometry : {
type : Point,
coordinates : [-92.79726665, 47.90752513]
},
geometry_name : shape,
properties : {
latitude : 47.90752513,
longitude : -92.79726665, ...
Now the same request with outputFormat=cvs:
http://geothermal.smu.edu:9000/geoserver/gtda-
contributions/ows?service=WFSversion=1.0.0request=GetFeaturetypeNam
e=gtda-
contributions:UNDRadiogenicHeatmaxFeatures=1outputFormat=csv
...and an except of the response. The same portion of the data has
been rounded off (48 instead of 47.90752513, and -93 instead of
-92.79726665). (I added the spaces for easy legibility):
FID, latitude,
longitude,...
UNDRadiogenicHeat.2540ea6b-f94a-3088-9b32-762c77a8e57f, 48,-
93,...
I've looked for configurations that might cause this, but I see none.
I know there are filters that could do this, but I get the
impression that these need to be explicitly requested, and the above
requests do not
include filters.
Is there something I'm overlooking? Is there some way that GeoServer
is
Re: [Geoserver-users] how to create a totally dynamic GeoServer layer - and dynamic heights in KML output ?
Hi, maybe I need to rephrase my question but before I do that - is there really no one that could give us any hint what we could to to approach that in any way ? Karsten -- View this message in context: http://osgeo-org.1560.x6.nabble.com/how-to-create-a-totally-dynamic-GeoServer-layer-and-dynamic-heights-in-KML-output-tp5136957p5138686.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Geoserver WPS python scripting
Hey Pablo, The python scripting stuff doesn't come by default with the wps module, so if building from sources you'll have to enable it separately. Instead build with this command. mvn clean install -P wps,script,script-py That should enable the basic scripting functionality plus the python runtime. -Justin On Mon, May 5, 2014 at 9:00 AM, pablo zader pza...@gmail.com wrote: *Hi list:* *I'm trying to run python script done through WPS but geoserver does not recognize the existence of geoprocesses I created.* *I'm following the instructions:* http://docs.geoserver.org/stable/en/user/community/scripting/py/index.html http://suite.opengeo.org/docs/latest/processing/scripting/processcreate.html *When I make a GetCapabilities* ( http://localhost:8080/geoserver/ows?service=wpsversion=1.0.0request=GetCapabilities), get the list of all who are part of geoprocesses geoserver (gs.*, geo.*, vec.*, ras.*, JTS.*,gt.*) but none of them is py.* *When I run a DescribeProcess* ( http://localhost:8080/geoserver/ows?service=WPSversion=1.0.0request=DescribeProcessidentifier=py:distbear ) get the next response: ows:ExceptionReport xmlns:ows=http://www.opengis.net/ows/1.1; xmlns:xsi =http://www.w3.org/2001/XMLSchema-instance; version=1.1.0 xsi:schemaLocation=http://www.opengis.net/ows/1.1 http://localhost:8080/geoserver/schemas/ows/1.1.0/owsAll.xsd; ows:Exception exceptionCode=NoApplicableCode ows:ExceptionTextNo such process: py:distbear/ows:ExceptionText /ows:Exception /ows:ExceptionReport *and the log of the geoserver reports:* 2014-05-05 11:50:12,296 WARN [geoserver.ows] - Could not get a ServiceInfo for service wps thus could not check if the service is enabled 2014-05-05 11:50:12,298 ERROR [geoserver.ows] - org.geoserver.wps.WPSException: No such process: py:distbear at org.geoserver.wps.DescribeProcess.processDescription(DescribeProcess.java:106) at org.geoserver.wps.DescribeProcess.run(DescribeProcess.java:96) at org.geoserver.wps.DefaultWebProcessingService.describeProcess(DefaultWebProcessingService.java:69) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318) *If for exmaple i do describeprocess of JTS:buffer:* http://localhost:8080/geoserver/ows?service=WPSversion=1.0.0request=DescribeProcessidentifier=JTS:buffer *this works fine and works well for any pre-existing geoprocessing in geoserver.* *My geoserver was compiled with*: mvn clean install -Pwps *The version I'm using is* : (geoserver and tomcat) Versión:2.4-SNAPSHOT Revisión de Git: ea0d7c50695f6c2a4564fc5f8fceb1c0b6eb543a Fecha de compilación :21-Mar-2014 19:03 Versión de GeoTools :10-SNAPSHOT (rev ff340eb96a28b463470cc79a566f8ed12fab934e) Versión GeoWebCache 1.5.0 (rev 1.5.x/f981cafd349886bb2a1ef45067f26b1aa8e4aff4) Apache Tomcat/6.0.35 JVM: 1.6.0_30-b30- Appreciate your help! Cheers Pablo -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users -- *Justin Deoliveira* Vice President, Engineering | Boundless jdeol...@boundlessgeo.com @j_deolive https://twitter.com/j_deolive -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] how to create a totally dynamic GeoServer layer - and dynamic heights in KML output ?
Maybe you have to set a valid default value in the sql view parameters table below the view (one existing column) to allow geoserver to validate the query and check the type of the attribute. For instance, if your table has the following columns: gid,value1, value2, the_geom try to set value1 as default value and try to save. Check the geoserver log if you have errors to see the generated query and why it fails. Il 05/mag/2014 22:52 Karsten-3-2 kars...@terragis.net ha scritto: Hi, maybe I need to rephrase my question but before I do that - is there really no one that could give us any hint what we could to to approach that in any way ? Karsten -- View this message in context: http://osgeo-org.1560.x6.nabble.com/how-to-create-a-totally-dynamic-GeoServer-layer-and-dynamic-heights-in-KML-output-tp5136957p5138686.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: #149; 3 signs your SCM is hindering your productivity #149; Requirements for releasing software faster #149; Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
