Hello again,
I've got an interesting glitch here. We use the GSHHS land shape file
to generate a blank vector base map (no country borders, only land and
water). This works fine in its native EPSG:4326, but when I try to
display the same map in EPSG:900913 I get what looks like a few
misplaced points that cause part of Antarctica to actually stretch all
the way to the north edge of the map. I'm hoping this is a bug and
not a problem with the data set, since it's the only one I've found
that meets my requirements.
A sample image showing the problem is attached.
--
This message brought to you by Speed of Light Beer
When you're approaching infinite mass
It's Speed of Light time!
Joshua M. Thompson ha scritto:
Hello again,
I've got an interesting glitch here. We use the GSHHS land shape file
to generate a blank vector base map (no country borders, only land and
water). This works fine in its native EPSG:4326, but when I try to
display the same map in EPSG:900913 I get what looks like a few
misplaced points that cause part of Antarctica to actually stretch all
the way to the north edge of the map. I'm hoping this is a bug and
not a problem with the data set, since it's the only one I've found
that meets my requirements.
A sample image showing the problem is attached.
I fear you'll have to process your data so that the pole areas are cut
off, the 900913 projection is simply not defined at poles.
Actually I believe Google limits the maximum latitude to 80/85° for
this very reason (besides avoiding the areas in which the deformation
is simply too big).
I guess you can do the above using PostGIS for example, but also
OpenJump should be able to do the job if you give it enough memory
to load the whole dataset.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Is it possible to specify the template to use in a WMS GetFeatureInfo call? Thanks, David
--
David R Robison
Open Roads Consulting, Inc.
103 Watson Road, Chesapeake, VA 23320
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
I fear you'll have to process your data so that the pole areas are cut
off, the 900913 projection is simply not defined at poles.
Actually I believe Google limits the maximum latitude to 80/85° for
this very reason (besides avoiding the areas in which the deformation
is simply too big).
I guess you can do the above using PostGIS for example, but also
OpenJump should be able to do the job if you give it enough memory
to load the whole dataset.
Ah, damn, that is what I was afraid of. The data set is really hard to
work with; I can't even import it into Oracle because the shapes are
too big, and there is very little attribute data to work with for
filtering out the bad shapes.
I guess my next step is to switch to DCW countries, which will involve
trying to coax geoserver into drawing them without borders or visual
artifacts at the polygon boundaries.
--
This message brought to you by Speed of Light Beer
When you're approaching infinite mass
It's Speed of Light time!