I would have to test this. i never noticed the 180 to -180 degre extent. I guess i dont fully understand what you mean by a "default extent". I've (sadly) created man shapefiles with arCrapalog. . when you create features in a shapefile, you should always define the projection, and when you do a "zoom to" layer it should get in tighter than 180/180.
<br><br>I dont see why if the projection is defined properly for the shapefile why it would not work, regardless of default extent, even though i dont fully understand what you are saying.<br><br>You could always use the GDAL "ogr2ogr" command to reproject it to the base coordinate system for your project. i've never used mapserver on the fly, always projected everything into the same projection.
<br><br>not sure that helps, but let me know if there's something i'm missing.<br><br>Mark<br><br><div><span class="gmail_quote">On 9/11/06, <b class="gmail_sendername">Ryan Ollerenshaw</b> <<a href="mailto:ollerery@engr.orst.edu">
ollerery@engr.orst.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">ArcGIS seems to default to a spatial extent of -180 - 180 degrees
<br>longitude when creating shapefiles, however my data has an extent of 0 -<br>360 degrees longitude. So my questions is, is it possible for MapServer<br>to re-project this shapefile on the fly to fit to correct spatial
<br>extent? I think that i can remember seeing an example where the data<br>started over when the user zoomes past the extent of the ma, so the<br>farthest eastern edge was connect back to the farthest western edge.<br>Does anyone know how to implement that? That would also fix my problem.
<br><br>thanks,<br>-Ryan<br></blockquote></div><br>