[mapserver-users] CGI controls - Symbol
Dear All, Just wondering if there are any known problems when trying to modify a symbol via the URL in Mapserver 5.0.3. I am trying to do on-the-fly symbol changes with the CGI variables as follows: ...&map.layer[0].CLASS[0].STYLE[0]=SYMBOL+'./blue_star.gif'&... The above produces no errors and a blank image. Seems to me as though the symbol is simply ignored in the URL because when I assign a color (map.layer[0].class[0].style[0]=COLOR+151+151+151) I get a whole whack of points back. Predefining the SYMBOL in the mapfile (SYMBOL "./blue_star.gif") also works perfectly fine. Not sure if I'm doing something wrong, but I've tried pretty much every combination including using using non-image symbols, playing around with the mapfile, and pulling out my hair. Note that I am also using the DATA CGI var to supply dynamic data content in the same URL (not sure if this would make a difference). Any ideas/suggestions would be greatly appreciated. Thanks, Ben Brehmer The mapfile is pretty straight forward: . .. ... DATAPATTERN ".*" LAYER NAME "pointlayer" DATA "" CONNECTIONTYPE postgis CONNECTION "host=localhost user=postgres port=5432 dbname=name password=pass" CLASSITEM "point_id" CLASS NAME "" STYLE END END ... .. . Mapserver is compiled with the following options: MapServer version 5.0.3 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_CLIENT SUPPORTS=FASTCGI INPUT=EPPL7 INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] WMS raster display, getfeatureinfo from vectorlayer
Bruce, thanks for the suggestion. That might work, and I might try it at some point, but I need this to work across all clients, and what I've noticed is that even if have layers named the same thing, each instance shows up in the list of available layers to the client. Then if the user selects the unobtrusive layer to turn on, they won't see anything, and if they choose the one that has the raster, it won't be queryable! I think either the WxS wrapper or a mod_rewrite are my two potential short term solutions. I'd be delighted to hear otherwise :-) Cheers, Percy Bruce Cheney wrote: Just a couple of thoughts - shouldn't your type be Polygon if you are referring to your polygon shapefile? Then make the symbology for this layer nonintrusive (so the users don't see it). I believe your query will reference the NAME item to obtain specific feature information. LAYER NAME QUERYLAYER DATA yourshapefilename TYPE POLYGON STATUS ON CLASS Define symbology - one symbol for entire layer END TEMPLATE "x" END Bruce Cheney -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of percy Sent: Thursday, July 10, 2008 5:43 PM To: Steve Lime Cc: mapserver Subject: Re: [mapserver-users] WMS raster display,getfeatureinfo from vectorlayer thanks, nice idea. I tried it, and that did not work... relevant mapfile section: LAYER NAME "Geologic_Map_Of_North_America" TYPE RASTER STATUS ON data "/vol/www/ngmdb/htdocs/GMNA_INDEX_tiled.tif" maxscale 1000 MINSCALE 50 Metadata "WMS_TITLE" "Geologic Map Of North America" "WMS_SRS" "epsg:4326" END # metadata END #layer LAYER NAME "Geologic_Map_Of_North_America" TYPE query STATUS On data GMNA_S_OneGeo TOLERANCE 0 TOLERANCEUNITS pixels TRANSFORM TRUE DUMP TRUE HEADER "templates/GMNA_query_header.html" TEMPLATE "templates/GMNA_query_body.html" FOOTER "templates/GMNA_query_footer.html" Metadata "WMS_TITLE" "Geologic Map Of North America" "WMS_SRS" "epsg:4326" GML_INCLUDE_ITEMS "DisplayNam,OneGeology,Lithologic,GeologicAg,AgeMin,AgeMax,AgeMetadat" WMS_INCLUDE_ITEMS "DisplayNam,OneGeology,Lithologic,GeologicAg,AgeMin,AgeMax,AgeMetadat" END # metadata END #layer Steve Lime wrote: What about using GROUPs or layers with the same name where the second layer is TYPE QUERY? Steve On 7/10/2008 at 2:14 PM, in message <[EMAIL PROTECTED]>, percy <[EMAIL PROTECTED]> wrote: I discussed this issue with Tom K. on the IRC yesterday, and he thought it was of general interest and should be posted and potentially requested as a feature. Scenario: we have a Geologic map that has super complex cartography that we don't want to reproduce in the mapfile (600+ classes, tons of patterns, etc). So we dumped out a raster of it to serve as WMS. However, when the user does a GetFeatureInfo on this WMS, we want to return attribute data from the original shapefile. I can envision this being taken care of at the layer level as a metadata tag like "WMS_query_redirect". In the short term we're working on a little apache mod_rewrite magic to take care of it :-) Cheers, Percy -- David Percy Geospatial Data Manager Geology Department Portland State University http://gisgeek.pdx.edu 503-725-3373 ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users -- David Percy Geospatial Data Manager Geology Department Portland State University http://gisgeek.pdx.edu 503-725-3373 ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] legend and layer opacity
I think your stuck. I consider this a bug (probably) so if you'd be so kind as to file a ticket we can take a look for the 5.4 release or perhaps earlier depending on how difficult the solution is. One work around, although not a great one, would be do develop the image to use for a given layer or class outside of mapserver and use the KEYIMAGE class property to reference it instead of generating one. Steve >>> On 7/10/2008 at 9:02 AM, in message <[EMAIL PROTECTED]>, "Michael Schulz" <[EMAIL PROTECTED]> wrote: > Hi, > > does the legend icon generation take the opacity settings of the > corresponding layer into account? In a mapfile where a layer is set to > 50% opacity the legend shows the colors as if the opacity is 100%. Is > there a way to get legend and map display consistent when using layer > opacity? > > Cheers, Michael ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] [Scalebar] Wrong values
Unfortunately MapServer only supports 1 scalebar object so you're kinda
stuck unless you
change things from your interface. For example, you could get at the
scale in a templated
interface via the [scale] tag and with a little javascript you could
change the UNITS parameter
for the scalebar. Something like this (assumes MapServer 5.0+) in your
template:
function updateScalebar(img) {
var scale = [scale];
var units;
if(scale < 1)
units = 'CENTIMETERS'; # does MapServer support centimeters?
elsif (scale < 1)
units = 'METERS';
else
units = 'KILOMETERS';
img.src =
'/cgi-bin/mapserv?map=[map]&mapext=0+0+[maxx]+[maxy]&mapwidth=[mapwidth]+[mapheight]';
}
and then add a call to updateScalebar() to your onload method, passing
a reference to the image
used to display the scalebar.
A similar technique would work with other clients.
The idea of supporting multiple scalebars with MIN/MAX scale
denominators is interesting though. I'll file a
ticket so it doesn't get lost...
Steve
>>> On 7/10/2008 at 4:28 AM, in message
<[EMAIL PROTECTED]>, Fabian
Rami <[EMAIL PROTECTED]> wrote:
> Fabian Rami a écrit :
>> Hi everyone,
>>
>> I have a mistake with the scalebar.
>> When i use the demo with my mapfile i have meters for europe level
,
>> centimeters for country level and kilometers for street level.
>>
>> I still a beginner with MapServer so if you see something wrong
>> please tell me :)
>>
>> I use Teleatlas data, i have found the specification of the data :
>> Projection: Geographic (not projected)
>> Datum WGS84 (labeled GCS_WGS_1984 in ESRI products)
>> Paramaters:
>> ●GEOGCS["GCS_WGS_1984",
>> ●DATUM["D_WGS_1984",
>> ●SPHEROID["WGS_1984",6378137,298.257223563]],
>> ●PRIMEM["Greenwich",0],
>> ●UNIT["Degree",0.017453292519943295]]
>>
>>
>> THANKS FOR YOUR HELP :o)
>>
>>
> Hummm, i found that the minscale mapscale used to draw the map is the
> reason of the error.
>
> How can i know the good value to put in minscale, maxscale for having
a
> correct behavior at the scalebar ?
> for example :
> Before with 65 at the top scale we have a graduation in meters ( +/-
0
> to 80 )
> Now with 65.000.000 at the top scale we have a graduation in
kilometers
> ( 0 to 4500)
>
> How know how to set this value correctly ?
>
>
>
> ___
> mapserver-users mailing list
> mapserver-users@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] Fwd: [OSGeo-Discuss] Quick Survey
Hi all: The OSGeo folks are looking for info to aid in conference planning... Steve >>> On 7/11/2008 at 2:22 PM, in message <[EMAIL PROTECTED]>, "Tyler Mitchell (OSGeo)" <[EMAIL PROTECTED]> wrote: > We've got some good responses so far to the OSGeo Survey re: FOSS4G > and other conferences. I know we can get some more input if we > forwarded the invitation to other OSGeo-related software project > lists. I'd love to have some more feedback from software users since > they might attend these events but not be on this list. Could you > please forward to your other lists, where applicable? > > Here is the very short survey: > http://community.osgeo.net/survey/osgeo_events > ___ > Discuss mailing list > [EMAIL PROTECTED] > http://lists.osgeo.org/mailman/listinfo/discuss ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] New limitations with mapserver 5 CGI
We aren't limited solely to the lexer. DATA and TEMPLATE, the two most widely used CGI overrides have a second control: DATAPATTERN and TEMPLATEPATTERN. When in a particular parsing state we check the appropriate pattern (which NULL, or unmatchable, by default) to decide if we should accept the override or not. The parameters at issue are those that aren't held to any validation by the lexer. Colors, sizes and such all have to be of a certain format or data type. Others like filters, data paths, connection strings etc... aren't subject to validation. We could impose validation like DATAPATTERN or TEMPLATEPATTERN on those parameters specifically. I wouldn't want to add a boat load of new parameters but we could do something like this in layer metadata: METADATA data_validation_pattern 'my pattern' filter_validation_pattern 'another pattern' ... END We already use this scheme for validation of runtime substitutions and query strings for attribute tables. This way the user could control which of these parameters could be overridden at runtime. All parameters that are subject to validation as part of mapfile parsing would be web accessible by default. Other parameters that we never want to allow override of can still be controlled within the lexer. The METADATA code would need special provisions to never allow setting keys ending in "_validation_pattern" from a URL source. DATAPATTERN and TEMPLATEPATTERN would become deprecated. Steve >>> On 7/10/2008 at 10:19 PM, in message <[EMAIL PROTECTED]>, "Paul Ramsey" <[EMAIL PROTECTED]> wrote: > I'd like to see backwards feature compatibility available, and I think > the CGI override controller is one of the most powerful > (under-appreciated) features of Mapserver. > > Since the control of what is over-rideable is in the lexer though, > we're sort of in a narrow box. We could do a compile-time option, > which would allow us to default to strict but allow (relatively) easy > conversion to flexible. That wouldn't really help our Windows brethren > though, since they mostly rely on pre-compiled versions, and binary > maintainers don't maintain lots of different builds. > > Having a map-level run-time directive to control the availability of > URL over-rides would be the ideal, IMO. Default, NONE. Other > options, STRICT and FULL. However, I don't see how to get there from > here with the lexer requirement. > > P. > > On Thu, Jul 10, 2008 at 6:05 PM, Graeme Watmuff > <[EMAIL PROTECTED]> wrote: >> Hi Steve, >> >> Thanks for replying and thanks for the coding pointers. You are right >> about the mapserv 4.10 tileindex syntax. Like filter, it is simply >> ignored by v5 rather than throwing an error. My apologies. >> >> Would it make sense to create a 'secure' version for the paranoid and a >> another version with full functionality? I realize this would create >> more maintenance work for you, but not all mapserver users are going to >> be able to climb inside the code themselves to modify functionality >> (fortunately we can). >> >> Regarding security, I presume you are concerned about mapserver exposing >> sensitive data to unintended users. If so, should you be taking that >> responsibility on yourself by limiting mapserver or should the onus be >> upon mapserver users to manage their own data more responsibly? I am a >> great believer in personal responsibility. If the security risk is made >> clear to users, they can make their own decisions as to the data they >> potentially expose to the world. >> >> We have greatly appreciated and benefited from the tremendous work you >> and your associates have done in bringing mapserver to the world and we >> have always looked forward to the added features of each new version. >> But upgrading now comes at some degree of inconvenience for us and maybe >> others unless someone wants to publish the workaround to resurrect lost >> functionality for all to simply acquire. >> >> I am not convinced that limiting the previous functionality is the right >> direction for mapserver unless you fear say a litigious threat from >> security breaches that people may bring upon themselves (hardly your >> responsibility). Those with seriously sensitive data are not going to >> want expose the CGI to all the world via a browser-sent URL anyway. I >> would expect them to send URLs from say, a java web app embedded in a >> secured tomcat container. >> >> Just my thoughts. >> >> Regards and best wishes >> >> Graeme >> >> On Thu, 2008-07-10 at 17:13 -0500, Steve Lime wrote: >>> Hi Graeme: Comments inline... I definitely underestimated the impacts of > those >>> changes. Anyway... >>> >>> >>> On 7/9/2008 at 11:23 PM, in message >>> <[EMAIL PROTECTED]>, Graeme Watmuff >>> <[EMAIL PROTECTED]> wrote: >>> > It has become apparent through some frustrating moments of trial and >>> > error that many of the mapfile variables that were changeable via URL >>> > with mapserver 4.10.x CGI seem no longer changeable with v5.x or 5
RE: [mapserver-users] WMS raster display, getfeatureinfo from vectorlayer
Just a couple of thoughts - shouldn't your type be Polygon if you are referring to your polygon shapefile? Then make the symbology for this layer nonintrusive (so the users don't see it). I believe your query will reference the NAME item to obtain specific feature information. LAYER NAME QUERYLAYER DATA yourshapefilename TYPE POLYGON STATUS ON CLASS Define symbology - one symbol for entire layer END TEMPLATE "x" END Bruce Cheney -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of percy Sent: Thursday, July 10, 2008 5:43 PM To: Steve Lime Cc: mapserver Subject: Re: [mapserver-users] WMS raster display,getfeatureinfo from vectorlayer thanks, nice idea. I tried it, and that did not work... relevant mapfile section: LAYER NAME "Geologic_Map_Of_North_America" TYPE RASTER STATUS ON data "/vol/www/ngmdb/htdocs/GMNA_INDEX_tiled.tif" maxscale 1000 MINSCALE 50 Metadata "WMS_TITLE" "Geologic Map Of North America" "WMS_SRS" "epsg:4326" END # metadata END #layer LAYER NAME "Geologic_Map_Of_North_America" TYPE query STATUS On data GMNA_S_OneGeo TOLERANCE 0 TOLERANCEUNITS pixels TRANSFORM TRUE DUMP TRUE HEADER "templates/GMNA_query_header.html" TEMPLATE "templates/GMNA_query_body.html" FOOTER "templates/GMNA_query_footer.html" Metadata "WMS_TITLE" "Geologic Map Of North America" "WMS_SRS" "epsg:4326" GML_INCLUDE_ITEMS "DisplayNam,OneGeology,Lithologic,GeologicAg,AgeMin,AgeMax,AgeMetadat" WMS_INCLUDE_ITEMS "DisplayNam,OneGeology,Lithologic,GeologicAg,AgeMin,AgeMax,AgeMetadat" END # metadata END #layer Steve Lime wrote: > What about using GROUPs or layers with the same name where the second > layer is TYPE QUERY? > > Steve > On 7/10/2008 at 2:14 PM, in message <[EMAIL PROTECTED]>, percy > <[EMAIL PROTECTED]> wrote: >> I discussed this issue with Tom K. on the IRC yesterday, and he >> thought it was of general interest and should be posted and >> potentially requested as a feature. >> >> Scenario: we have a Geologic map that has super complex cartography >> that we don't want to reproduce in the mapfile (600+ classes, tons of >> patterns, etc). So we dumped out a raster of it to serve as WMS. >> >> However, when the user does a GetFeatureInfo on this WMS, we want to >> return attribute data from the original shapefile. >> >> I can envision this being taken care of at the layer level as a >> metadata tag like "WMS_query_redirect". >> >> In the short term we're working on a little apache mod_rewrite magic >> to take care of it :-) >> >> Cheers, >> Percy > > -- David Percy Geospatial Data Manager Geology Department Portland State University http://gisgeek.pdx.edu 503-725-3373 ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
RE: [mapserver-users] WMS raster display, getfeatureinfo from vectorlayer
You could use a mapscript WxS wrapper to, when receiving a GetFeatureInfo request, replace the LAYERS/QUERY_LAYERS parameters with the vector layer. ..Tom -Original Message- From: [EMAIL PROTECTED] on behalf of percy Sent: Fri 11-Jul-08 10:38 To: mapserver Cc: Steve Lime Subject: Re: [mapserver-users] WMS raster display,getfeatureinfo from vectorlayer I'm starting to think that just handling this with a mapscript wrapper script might be the easiest approach. Any thoughts? Thanks, Percy percy wrote: > thanks, nice idea. I tried it, and that did not work... > > relevant mapfile section: > > LAYER > NAME "Geologic_Map_Of_North_America" > TYPE RASTER > STATUS ON > data "/vol/www/ngmdb/htdocs/GMNA_INDEX_tiled.tif" > maxscale 1000 > MINSCALE 50 > Metadata > "WMS_TITLE" "Geologic Map Of North America" > "WMS_SRS" "epsg:4326" > END # metadata > END #layer > LAYER > NAME "Geologic_Map_Of_North_America" > TYPE query > STATUS On > data GMNA_S_OneGeo > TOLERANCE 0 > TOLERANCEUNITS pixels > TRANSFORM TRUE > DUMP TRUE > HEADER "templates/GMNA_query_header.html" > TEMPLATE "templates/GMNA_query_body.html" > FOOTER "templates/GMNA_query_footer.html" > Metadata > "WMS_TITLE" "Geologic Map Of North America" > "WMS_SRS" "epsg:4326" > GML_INCLUDE_ITEMS > "DisplayNam,OneGeology,Lithologic,GeologicAg,AgeMin,AgeMax,AgeMetadat" > WMS_INCLUDE_ITEMS > "DisplayNam,OneGeology,Lithologic,GeologicAg,AgeMin,AgeMax,AgeMetadat" > END # metadata > END #layer > > > Steve Lime wrote: >> What about using GROUPs or layers with the same name where the second >> layer >> is TYPE QUERY? >> >> Steve >> > On 7/10/2008 at 2:14 PM, in message <[EMAIL PROTECTED]>, percy >> <[EMAIL PROTECTED]> wrote: >>> I discussed this issue with Tom K. on the IRC yesterday, and he >>> thought it was of general interest and should be posted and >>> potentially requested as a feature. >>> >>> Scenario: we have a Geologic map that has super complex cartography >>> that we don't want to reproduce in the mapfile (600+ classes, tons >>> of patterns, etc). So we dumped out a raster of it to serve as WMS. >>> >>> However, when the user does a GetFeatureInfo on this WMS, we want to >>> return attribute data from the original shapefile. >>> >>> I can envision this being taken care of at the layer level as a >>> metadata tag like "WMS_query_redirect". >>> >>> In the short term we're working on a little apache mod_rewrite magic >>> to take care of it :-) >>> >>> Cheers, >>> Percy >> >> > -- David Percy Geospatial Data Manager Geology Department Portland State University http://gisgeek.pdx.edu 503-725-3373 ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] WMS raster display,getfeatureinfo from vector layer
I'm starting to think that just handling this with a mapscript wrapper script might be the easiest approach. Any thoughts? Thanks, Percy percy wrote: thanks, nice idea. I tried it, and that did not work... relevant mapfile section: LAYER NAME "Geologic_Map_Of_North_America" TYPE RASTER STATUS ON data "/vol/www/ngmdb/htdocs/GMNA_INDEX_tiled.tif" maxscale 1000 MINSCALE 50 Metadata "WMS_TITLE" "Geologic Map Of North America" "WMS_SRS" "epsg:4326" END # metadata END #layer LAYER NAME "Geologic_Map_Of_North_America" TYPE query STATUS On data GMNA_S_OneGeo TOLERANCE 0 TOLERANCEUNITS pixels TRANSFORM TRUE DUMP TRUE HEADER "templates/GMNA_query_header.html" TEMPLATE "templates/GMNA_query_body.html" FOOTER "templates/GMNA_query_footer.html" Metadata "WMS_TITLE" "Geologic Map Of North America" "WMS_SRS" "epsg:4326" GML_INCLUDE_ITEMS "DisplayNam,OneGeology,Lithologic,GeologicAg,AgeMin,AgeMax,AgeMetadat" WMS_INCLUDE_ITEMS "DisplayNam,OneGeology,Lithologic,GeologicAg,AgeMin,AgeMax,AgeMetadat" END # metadata END #layer Steve Lime wrote: What about using GROUPs or layers with the same name where the second layer is TYPE QUERY? Steve On 7/10/2008 at 2:14 PM, in message <[EMAIL PROTECTED]>, percy <[EMAIL PROTECTED]> wrote: I discussed this issue with Tom K. on the IRC yesterday, and he thought it was of general interest and should be posted and potentially requested as a feature. Scenario: we have a Geologic map that has super complex cartography that we don't want to reproduce in the mapfile (600+ classes, tons of patterns, etc). So we dumped out a raster of it to serve as WMS. However, when the user does a GetFeatureInfo on this WMS, we want to return attribute data from the original shapefile. I can envision this being taken care of at the layer level as a metadata tag like "WMS_query_redirect". In the short term we're working on a little apache mod_rewrite magic to take care of it :-) Cheers, Percy -- David Percy Geospatial Data Manager Geology Department Portland State University http://gisgeek.pdx.edu 503-725-3373 ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
