Please have a look at http://kite.gns.cri.nz/PBE/index.html#MAP:seismic.json
It shows identical data on the same map, but one is sourced from
geoserver 2.1 and the other from geoserver 2.0.2
The 2.0.2 data is fine. The 2.1 data is highly incomplete. As you zoom
it, more becomes visible, but not till well zoomed in do some tiles
become visible. Even more oddly, it is clear that the data visibility is
on a per tile basis. If a tile is drawn, then it all there or none. The
openlayers application is requesting the same tiles from both instances.
What is going on here? I first thought this was further 180 degree
problem but it clearly isnt. The problem shows even when 180 is not in
the frame.
--
Phil Scadden, GNS Science Ltd 764 Cumberland St, Private Bag 1930,
Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477 5232
Notice: This email and any attachments are confidential. If received in error please destroy and immediately notify us. Do not copy or disclose the contents.
On Fri, Jul 15, 2011 at 2:13 AM, Phil Scadden <p.scadden@anonymised.com89…> wrote:
Please have a look at http://kite.gns.cri.nz/PBE/index.html#MAP:seismic.json
It shows identical data on the same map, but one is sourced from
geoserver 2.1 and the other from geoserver 2.0.2
The 2.0.2 data is fine. The 2.1 data is highly incomplete. As you zoom
it, more becomes visible, but not till well zoomed in do some tiles
become visible. Even more oddly, it is clear that the data visibility is
on a per tile basis. If a tile is drawn, then it all there or none. The
openlayers application is requesting the same tiles from both instances.
What is going on here? I first thought this was further 180 degree
problem but it clearly isnt. The problem shows even when 180 is not in
the frame.
No idea… the map does not show anything, just waits forever for tiles
that do not show up.
You might want to try disabling GWC direct integration, if you have it on
Cheers
Andrea
–
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
Hi Phil,
Is your problem solved?
Same problem i have also observed. we need to create new style for 2.1 version (some styles of 2.0.2 may not work in 2.1). There are major differences between 2.0.2 & 2.1 (I’m not sure but enhancements of specs in sld may be problem for line styles & polygon styles, while points styles are not a problem)
Please check by adding uom (unit of measure) value as pixel (its a very good feature of 2.1 i hope) to the old SLD of 2.0.2 version. It may be creating problem. by creating new style with uom option, we have reduced 50% sld code and increased performance.
If that also didnt work, you may remove the layer and reconfigure once again in GS 2.1 with new style compatible to GS 2.1 version
Regards,
Hari.
On Fri, Jul 15, 2011 at 5:43 AM, Phil Scadden <p.scadden@anonymised.com> wrote:
Please have a look at http://kite.gns.cri.nz/PBE/index.html#MAP:seismic.json
It shows identical data on the same map, but one is sourced from
geoserver 2.1 and the other from geoserver 2.0.2
The 2.0.2 data is fine. The 2.1 data is highly incomplete. As you zoom
it, more becomes visible, but not till well zoomed in do some tiles
become visible. Even more oddly, it is clear that the data visibility is
on a per tile basis. If a tile is drawn, then it all there or none. The
openlayers application is requesting the same tiles from both instances.
What is going on here? I first thought this was further 180 degree
problem but it clearly isnt. The problem shows even when 180 is not in
the frame.
–
Phil Scadden, GNS Science Ltd 764 Cumberland St, Private Bag 1930,
Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477 5232
Notice: This email and any attachments are confidential. If received in error please destroy and immediately notify us. Do not copy or disclose the contents.
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on “Lean Startup
Secrets Revealed.” This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Hi Phil
Seems you have found a solution or gone with direct geoserver rendering than use GWC. I have raised issue in GeoServer JIRA that, With GeoServer 2.1RC4, we need to use Native JAI library, otherwise rendering broken for me. I installed native JAI lib and every thing solved. Now using 2.1 and planning to upgrade 2.1.1 coming week.
Regards
Senthil
On Mon, Jul 18, 2011 at 12:23 PM, Harikumar Reddy <harik.gis@anonymised.com> wrote:
Hi Phil,
Is your problem solved?
Same problem i have also observed. we need to create new style for 2.1 version (some styles of 2.0.2 may not work in 2.1). There are major differences between 2.0.2 & 2.1 (I’m not sure but enhancements of specs in sld may be problem for line styles & polygon styles, while points styles are not a problem)
Please check by adding uom (unit of measure) value as pixel (its a very good feature of 2.1 i hope) to the old SLD of 2.0.2 version. It may be creating problem. by creating new style with uom option, we have reduced 50% sld code and increased performance.
If that also didnt work, you may remove the layer and reconfigure once again in GS 2.1 with new style compatible to GS 2.1 version
Regards,
Hari.
On Fri, Jul 15, 2011 at 5:43 AM, Phil Scadden <p.scadden@anonymised.com> wrote:
Please have a look at http://kite.gns.cri.nz/PBE/index.html#MAP:seismic.json
It shows identical data on the same map, but one is sourced from
geoserver 2.1 and the other from geoserver 2.0.2
The 2.0.2 data is fine. The 2.1 data is highly incomplete. As you zoom
it, more becomes visible, but not till well zoomed in do some tiles
become visible. Even more oddly, it is clear that the data visibility is
on a per tile basis. If a tile is drawn, then it all there or none. The
openlayers application is requesting the same tiles from both instances.
What is going on here? I first thought this was further 180 degree
problem but it clearly isnt. The problem shows even when 180 is not in
the frame.
–
Phil Scadden, GNS Science Ltd 764 Cumberland St, Private Bag 1930,
Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477 5232
Notice: This email and any attachments are confidential. If received in error please destroy and immediately notify us. Do not copy or disclose the contents.
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on “Lean Startup
Secrets Revealed.” This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on “Lean Startup
Secrets Revealed.” This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
No, I havent found a solution for this. (I've been on leave for a week).
However, we will try disabling the GWC integration and also try the
native JAI library.
Notice: This email and any attachments are confidential. If received in error please destroy and immediately notify us. Do not copy or disclose the contents.
No, I havent found a solution for this. (I've been on leave for a week).
However, we will try disabling the GWC integration and also try the
native JAI library.
Okay, we tried going to 2.1.1, tried the native JAI library and tried
disabling GWC integration. No effect at all. We did notice that 2.0.2
loses tiles as well at zoom 7 for some reason as well.
However, what we did do was move the data from ArcSDE to PostGIS since
GWC doesnt allow seeding of SDE Layers. Once there, the layer works
fine. So this strange problem is actually somewhere in the arcsde
integration.
Notice: This email and any attachments are confidential. If received in error please destroy and immediately notify us. Do not copy or disclose the contents.