[Mapserver-users] layer not drawn in utm projection
niklas wörmann
nwoe at privat.utfors.se
Thu Dec 11 15:41:05 EST 2003
This is a multi-part message in MIME format.
------=_NextPart_000_0049_01C3C02F.7AFDDFC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Niklas -
(please reply to everyone on the list)
The reason I ask about the coordinates is that I have seen odd =
behavior when trying to reproject extreme or edge conditions. I cannot =
recall the details right now, but some time ago I believe I had trouble =
with a similar "backdrop" layer that hit some out-of-range or boundary =
conditions in the projection. For example, the lat/lon rectangle =
running from -180,-90 to 180,90 cannot be projected into UTM.
I would suggest creating a feature layer with a simple polygon =
(rectangle is fine) that is only large enough for your needs. You don't =
need to try very hard to trim it precisely, but don't try to make it the =
entire globe.
- Ed
Ed McNierney
President and Chief Mapmaker
TopoZone.com / Maps a la carte, Inc.
73 Princeton Street, Suite 305
North Chelmsford, MA 01863
ed at topozone.com
(978) 251-4242=20
great!
thanks.
inlining was the way to go.
but this brings up a new question.=20
I am thinking of using this background layer (my now inlined square) =
to run queries against, (how stupid can you get?). since it
seems the only way to "map" from pixels to real world coords is thru =
a query.
i have asked variations of this question before and never gotten a =
reply, but it seems to me that this must be the way to go.
would be kind of hard to query the new inlined layer wouldnt it?
one workaround would be if some kind soul could prepare a world =
rectangle shape file, covering almost, but not quite, all the world with =
one feature on it, that i could use to run my query against.
any other bright ideas?
niklas
------=_NextPart_000_0049_01C3C02F.7AFDDFC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY style=3D"MARGIN-TOP: 2px; FONT: 10pt Arial; MARGIN-LEFT: 2px"=20
bgColor=3D#ffffff>
<DIV> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial"> </DIV>
<DIV><BR></DIV>
<DIV><SPAN class=3D748075919-11122003>Niklas -</SPAN></DIV>
<DIV><SPAN class=3D748075919-11122003></SPAN> </DIV>
<DIV><SPAN class=3D748075919-11122003>(please reply to everyone on the =
list)</SPAN></DIV>
<DIV><SPAN class=3D748075919-11122003></SPAN> </DIV>
<DIV><SPAN class=3D748075919-11122003>The reason I ask about the =
coordinates is=20
that I have seen odd behavior when trying to reproject extreme or edge =
conditions. I cannot recall the details right now, but some time =
ago I=20
believe I had trouble with a similar "backdrop" layer that hit some=20
out-of-range or boundary conditions in the projection. For =
example, the=20
lat/lon rectangle running from -180,-90 to 180,90 cannot be projected =
into=20
UTM.</SPAN></DIV>
<DIV><SPAN class=3D748075919-11122003></SPAN> </DIV>
<DIV><SPAN class=3D748075919-11122003>I would suggest creating a =
feature layer=20
with a simple polygon (rectangle is fine) that is only large enough =
for your=20
needs. You don't need to try very hard to trim it precisely, but =
don't=20
try to make it the entire globe.</SPAN></DIV>
<DIV><SPAN class=3D748075919-11122003></SPAN> </DIV>
<DIV><SPAN class=3D748075919-11122003> - =
Ed</SPAN></DIV>
<DIV><SPAN class=3D748075919-11122003>
<P><FONT size=3D2>Ed McNierney<BR>President and Chief =
Mapmaker<BR>TopoZone.com /=20
Maps a la carte, Inc.<BR>73 Princeton Street, Suite 305<BR>North =
Chelmsford,=20
MA 01863<BR>ed at topozone.com<BR>(978) 251-4242 =
</FONT></P></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
face=3DTahoma>great!</FONT></DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
face=3DTahoma>thanks.</FONT></DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
face=3DTahoma></FONT> </DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
face=3DTahoma>inlining was the way to go.</FONT></DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma>but=20
this brings up a new question. </FONT></DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma>I am=20
thinking of using this background layer (my now inlined =
square) to run=20
queries against, (how stupid can you get?). since it</FONT></DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma>seems=20
the only way to "map" from pixels to real world coords is thru a=20
query.</FONT></DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
face=3DTahoma></FONT> </DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma>i have=20
asked variations of this question before and never gotten a reply, =
but it=20
seems to me that this must be the way to go.</FONT></DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
face=3DTahoma></FONT> </DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma>would=20
be kind of hard to query the new inlined layer wouldnt =
it?</FONT></DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
face=3DTahoma></FONT> </DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma>one=20
workaround would be if some kind soul could prepare a world =
rectangle shape=20
file, covering almost, but not quite, all the world with one =
feature on=20
it, that i could </FONT><FONT face=3DTahoma>use to run my query=20
against.</FONT></DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
face=3DTahoma></FONT> </DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma>any=20
other bright ideas?</FONT></DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
face=3DTahoma></FONT> </DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
face=3DTahoma></FONT> </DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
face=3DTahoma>niklas</FONT></DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT=20
=
face=3DTahoma></FONT> </DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>=
------=_NextPart_000_0049_01C3C02F.7AFDDFC0--
More information about the mapserver-users
mailing list