Fine and thanks for the report. A quiet strange error seems to have disappeared with that. Maybe one should post this once on the Mapserver list.
The "setExtent()" is necessary if you want to apply correct query tolerances defined in pixels (which usually makes more sense than in absolute values like meters). But the side effect seems to be that the scale is not correct any more afterwards and has to be set again. For the second question: I guess its just a typo, try "RESULT_FIELDS" (removing the "S" from "RESULTS") and it should work. armin Richie Pierce wrote: > Great. It looks like that solved the problem. I am still having an issue > with the attributes that are returned. Within my map file I have specified > > LAYER > TEMPLATE 'void' > ...... > METADATA > "RESULTS_FIELDS" "MUNAME COUNTY LCU ACD Crop Rice Pasture Timber" > END #METADATA > ....... > END > > > But using the identify tool still returns all the attributes for the Layer. > Thanks for your help. > > > Richie Pierce > Sr GIS Analyst > a.c.t.GeoSpatial, Inc. > 2900 Percy Machin Drive, Suite One > North Little Rock, AR 72114 > Ph(501) 771-2985 > [EMAIL PROTECTED] > www.actgeospatial.com > > -----Original Message----- > From: Armin Burger [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 15, 2007 3:12 PM > To: Richie Pierce > Cc: pmapper-users@lists.sourceforge.net > Subject: Re: [pmapper-users] MAXSCALE and Identify > > Could you check if this problem still appears with the patch provided > some days ago by Alessandro Pasotti? It's available for p.mapper 3.1 at > > http://svn.pmapper.net/trac/browser/pmapper/trunk/incphp/query/query.php > > or just take the lines > > $this->map->setSize($this->mapwidth, $this->mapheight); > $this->map->preparequery(); > > and insert them below line 190 in your query.php (below the line > starting with "$this->map->setExtent($this->GEOEX..."). > If this solves your problem could you report this back to the list? > > Armin > > > Richie Pierce wrote: >> I've got a pmapper viewer up and running. One of the Queryable layers >> within my map file is acting a bit strange. The MAXSCALE for the layer is >> set to 18000 which works fine, the layer turns on appropriately. However, >> the query-ability is not enabled until 11000. I'm not sure why this is >> happening and I am unable to locate any configuration that would cause > this. >> I double checked to make sure the "RESULT_FIELDS" is in my map file and > that >> doesn't seem to be working either. It still returns all the attributes > from >> the table. To clarify just in case, when I zoom on the map within the > 18000 >> MAXSCALE threshold, the layer becomes visible in the viewer, but it does > not >> return any records unless I am within 11000. I'm not sure if this is an >> issue but the dataset is extremely large (350,000+ records). I have built > a >> spatial index and it is not causing any problems for Mapserver. Thanks in >> advance for any help. >> >> >> >> Richie Pierce >> >> Sr GIS Analyst >> >> a.c.t.GeoSpatial, Inc. >> >> 2900 Percy Machin Drive, Suite One >> >> North Little Rock, AR 72114 >> >> Ph(501) 771-2985 >> >> [EMAIL PROTECTED] >> >> www.actgeospatial.com >> > > > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users
