Good question. What's your actual projection definition?
CubeWerx (http://www.cubewerx.com/) holds the 42xxx projection definitions. We've worked with them to establish codes which are not natively in EPSG. I've cc'd Craig here for info. ..Tom > -----Original Message----- > From: UMN MapServer Users List > [mailto:[EMAIL PROTECTED] On Behalf Of Bob Basques > Sent: Monday, June 05, 2006 10:38 AM > To: [email protected] > Subject: [UMN_MAPSERVER-USERS] [Fwd: Re: WFS gurus . . . .] > > > Ok, we'll try that. > > Any rule-of-thumb for assigning an arbitrary code? > > bobb > > > -------- Original Message -------- > Subject: Re: WFS gurus . . . . > Date: Mon, 5 Jun 2006 10:32:23 -0400 > From: Kralidis,Tom [Burlington] <[EMAIL PROTECTED]> > Reply-To: Kralidis,Tom [Burlington] <[EMAIL PROTECTED]> > To: [email protected] > > > > >=20 > > I'm trying to get a WFS output in a local coordinate system. =20 > >Everything=20 works just fine with a EPSG code, but our coordinate > >system is not in=20 the list. Do we need to add it in in more than > >one location? We're=20 using a few extensions that all > seem to have > >their own=20 version of a EPSG=20 > > code list, different formats and everything. > > > > What's your projection parameters? If it's indeed not an > EPSG code, you'll need to add this to your proj install's > epsg file, then cite that EPSG code in your WFS request. =20 > > All I need is to be able to get the WFS output with a same > > coordinate=20 system BBOX. Can I get around the EPSG > requirement with > > some form of=20 fakery? Can the GML be output with a > MODE=3D option > > perhaps, in it's=20 native coordinate system? >
