I found warn information in my log file like this:
2008-06-24 13:15:00,508 WARN [geoserver.filters] - Mime type was not set before first write!
2008-06-24 13:15:00,508 INFO [geoserver.filters] - Not compressing output for mimetype: null
2008-06-24 13:15:02,179 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:03,398 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:04,554 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:05,116 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:05,975 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
then the default openlayer of geoserver, it can show me the attribute table if I click the map. but there is no map display.
I could not find any information about how to solve this warn. my data stored in PostGIS.
Thanks in advance
all the best
Xiaoyu
–
Xiaoyu Guan (Sam)
Geo-information Science
Wageningen UR
I found warn information in my log file like this:
2008-06-24 13:15:00,508 WARN [geoserver.filters] - Mime type was not set before first write!
2008-06-24 13:15:00,508 INFO [geoserver.filters] - Not compressing output for mimetype: null
2008-06-24 13:15:02,179 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:03,398 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:04,554 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:05,116 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:05,975 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
then the default openlayer of geoserver, it can show me the attribute table if I click the map. but there is no map display.
I could not find any information about how to solve this warn. my data stored in PostGIS.
Most likely case is that your SLD has some rules that prevent the display, GetFeatureInfo is not using anything from the SLD so it's still
working. Usual suspects are scale denominator rules, filters, or the
wrong FeatureType being declared (try removing the feature type
declaration in FeatureTypeStyle or just declare "Feature", the generic
superclass that matches every kind of vector data).
These error messages are not related to the rendering (they deal with GZIP compression of the results, and probably should not be enabled in the default configuration since they are reported for each request.)
It sounds like you are simply using an SLD style that does not render any features at the zoom level you are viewing. You could check this out by using one of the catch-all styles that is included with GeoServer, just set styles=point (or polygon, or line) in your request parameters. If this causes features to be rendered then you probably just have a problem with your style.
Hope this helps,
-David Winslow
Xiaoyu Guan wrote:
Dear All:
I found warn information in my log file like this:
2008-06-24 13:15:00,508 WARN [geoserver.filters] - Mime type was not set before first write!
2008-06-24 13:15:00,508 INFO [geoserver.filters] - Not compressing output for mimetype: null
2008-06-24 13:15:02,179 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:03,398 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:04,554 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:05,116 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:05,975 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
then the default openlayer of geoserver, it can show me the attribute table if I click the map. but there is no map display.
I could not find any information about how to solve this warn. my data stored in PostGIS.
Thanks in advance
all the best
Xiaoyu
--
Xiaoyu Guan (Sam)
Geo-information Science
Wageningen UR
!DSPAM:4040,4860d9a2291831804284693!
------------------------------------------------------------------------
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source. http://sourceforge.net/services/buy/index.php
Thanks for your information:
both of you said are true. I did modified my sld.
To test whether my SLD file works, I am just use default ‘line’ at feature type. then the result still same situation, only can view table.
the data which I used is openstreetmap data, there are four layers, point, line, road, polygon, I have already convert them into postgis.
I have two questions about this situation:
is there any limitations of GeoServer? such as the OSM line file, it contains many many lines. Is there a kind of ‘time out’ between GeoServer and PostGIS? When I open the map, it seem like rendered for a while then stop.
Is this problem relate to Enable caching?
These error messages are not related to the rendering (they deal with GZIP compression of the results, and probably should not be enabled in the default configuration since they are reported for each request.)
It sounds like you are simply using an SLD style that does not render any features at the zoom level you are viewing. You could check this out by using one of the catch-all styles that is included with GeoServer, just set styles=point (or polygon, or line) in your request parameters. If this causes features to be rendered then you probably just have a problem with your style.
Hope this helps,
-David Winslow
Xiaoyu Guan wrote:
Dear All:
I found warn information in my log file like this:
2008-06-24 13:15:00,508 WARN [geoserver.filters] - Mime type was not set before first write!
2008-06-24 13:15:00,508 INFO [geoserver.filters] - Not compressing output for mimetype: null
2008-06-24 13:15:02,179 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:03,398 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:04,554 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:05,116 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:05,975 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
then the default openlayer of geoserver, it can show me the attribute table if I click the map. but there is no map display.
I could not find any information about how to solve this warn. my data stored in PostGIS.
Thanks in advance
all the best
Xiaoyu
–
Xiaoyu Guan (Sam)
Geo-information Science
Wageningen UR
Dear all:
Here is a short message about the problem.
the problem have been kind of solved.
GeoServer 1.7Beta1 can show the map correctly.
I have no idea about the difference between 1.6.4 and 1.7. but on the this dataset 1.7 works.
Thanks for your information:
both of you said are true. I did modified my sld.
To test whether my SLD file works, I am just use default ‘line’ at feature type. then the result still same situation, only can view table.
the data which I used is openstreetmap data, there are four layers, point, line, road, polygon, I have already convert them into postgis.
I have two questions about this situation:
is there any limitations of GeoServer? such as the OSM line file, it contains many many lines. Is there a kind of ‘time out’ between GeoServer and PostGIS? When I open the map, it seem like rendered for a while then stop.
Is this problem relate to Enable caching?
These error messages are not related to the rendering (they deal with GZIP compression of the results, and probably should not be enabled in the default configuration since they are reported for each request.)
It sounds like you are simply using an SLD style that does not render any features at the zoom level you are viewing. You could check this out by using one of the catch-all styles that is included with GeoServer, just set styles=point (or polygon, or line) in your request parameters. If this causes features to be rendered then you probably just have a problem with your style.
Hope this helps,
-David Winslow
Xiaoyu Guan wrote:
Dear All:
I found warn information in my log file like this:
2008-06-24 13:15:00,508 WARN [geoserver.filters] - Mime type was not set before first write!
2008-06-24 13:15:00,508 INFO [geoserver.filters] - Not compressing output for mimetype: null
2008-06-24 13:15:02,179 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:03,398 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:04,554 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:05,116 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
2008-06-24 13:15:05,975 INFO [geoserver.filters] - Not compressing output for mimetype: image/png
then the default openlayer of geoserver, it can show me the attribute table if I click the map. but there is no map display.
I could not find any information about how to solve this warn. my data stored in PostGIS.
Thanks in advance
all the best
Xiaoyu
–
Xiaoyu Guan (Sam)
Geo-information Science
Wageningen UR
Well, I encountered the issue with 1.6.4 and then found out the problem is
that
I have configured a watermark image that's at a different URL, and that
image
was accidentally moved. So the image rendering is not working.
Found this out by requesting for the output in Format=image/png, and the
subsequent error message gave the clue.
You can try the same to see what kind of problem you are having.
Well, I encountered the issue with 1.6.4 and then found out the problem is
that
I have configured a watermark image that's at a different URL, and that
image
was accidentally moved. So the image rendering is not working.
Found this out by requesting for the output in Format=image/png, and the
subsequent error message gave the clue.
You can try the same to see what kind of problem you are having.
Ah, interesting one. Wondering what's the best course of action here.
The current behaviour at least guarantees that no un-watermarked
images are served. We could make the code more resilient to missing
watermarks, and make it serve un-watermarked images in case of error,
but for some users this could be a major problem (since watermarks
are there to protect their data...).