[mapserver-users] WMS Client and SLD
All, This is the first time I have tried styling external WMS data using SLD and cannot get the returned data/image in the desired style. Below is the simplified mapfile and SLD file. If anyone has any pointers I'd be more than grateful. Please note that the link to the SLD file does work with the following return: 56 APPLICATION STATUS #ff GRANTED STATUS #be Tony Mapfile: # # Start of map file # MAP NAME qld_tenement STATUS ON SIZE 800 500 EXTENT 140 -23.25 150 -17 UNITS DD SHAPEPATH /var/www/remwms/htdocs/data IMAGECOLOR 192 213 255 SYMBOLSET /var/www/remwms/htdocs/includes/symbols.sym FONTSET /usr/share/fonts/truetype/font.list DEBUG 2 CONFIG MS_ERRORFILE /var/www/ms_tmp/ms_error.txt #IMAGETYPE PNG OUTPUTFORMAT NAME AGGA MIMETYPE image/png DRIVER AGG/PNG EXTENSION png IMAGEMODE RGBA TRANSPARENT ON END # # Start of web interface definition # WEB IMAGEPATH /var/www/ms_tmp/ IMAGEURL http://mapserver1/ms_tmp/; END # # Assign Projection # PROJECTION init=epsg:4283 END LAYER NAME EPM TYPE RASTER STATUS ON CONNECTIONTYPE WMS CONNECTION 'http://atlas.information.qld.gov.au/ArcGIS/services/IRTM/MapServer/WMSServer?' METADATA wms_srs EPSG:4326 wms_name 56 wms_server_version 1.1.1 wms_format image/png wms_title EPM wms_include_itemsall wms_sld_url http://mapserver1/remwms/includes/sld/publicsld.xml; wms_legend_graphic 0 wms_feature_info_mime_type text/plain END END END SLD File: ?xml version=1.0 encoding=UTF-8? StyledLayerDescriptor version=1.0.0 xmlns=http://www.opengis.net/sld; xmlns:ogc=http://www.opengis.net/ogc; xmlns:xlink=http://www.w3.org/1999/xlink; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.opengis.net/sld http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd; NamedLayer Name56/Name UserStyle FeatureTypeStyle Rule NameAPPLICATION/Name ogc:Filterogc:PropertyIsEqualToogc:PropertyNameSTATUS/ogc:PropertyName/ogc:PropertyIsEqualTo/ogc:Filter PolygonSymbolizer Fill CssParameter name=fill#ff/CssParameter /Fill /PolygonSymbolizer /Rule Rule NameGRANTED/Name ogc:Filterogc:PropertyIsEqualToogc:PropertyNameSTATUS/ogc:PropertyName/ogc:PropertyIsEqualTo/ogc:Filter PolygonSymbolizer Fill CssParameter name=fill#be/CssParameter /Fill /PolygonSymbolizer /Rule /FeatureTypeStyle /UserStyle /NamedLayer /StyledLayerDescriptor -- Tony Baylis Spatial Information Specialist Resource and Exploration Mapping Suite 8, 290 Boundary St Spring Hill QLD 4000 Ph3832 1600 Fax 3832 1603 Mob 0419 759 131 Email tony.bay...@resexmap.com.au www resexmap.com.au ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] Fatal error: Call to undefined function dl() in C:\ms4w\Apache\htdocs\phpmapscript.php on line 5
gee...@ttkmaps.com wrote: Hi all, I tried to install php/mapscript in windows,I get the above error.I use mapserver version 5.4.2,Apache 2.2.11,PHP 5.3.Php works fine.Im able to run files with .php extension,but the below coding produces error: HTML BODY ?php dl(php_mapscript.dll); phpinfo(); ? /BODY /HTML My php_mapscript.dll is in ..php/ext folder by default.My php.ini php.exe is in /ms4w/Apache/cgi-bin.Is there any other dll i should add?It is said php/mapscript is preconfigured right...then what might be wrong?Thanks in advance. NewUser. Hello NewUser, Since PHP version 5.3.0 you can no longer use PHP's dl() function (it has been deprecated and removed as noted in http://ca2.php.net/manual/en/function.dl.php). In MS4W version 3.0 the mapscript dll is already enabled, through the php.ini If you have any questions regarding MS4W, please use the MS4W email list (subscribe at http://lists.maptools.org/mailman/listinfo/ms4w-users). -jeff -- Jeff McKenna FOSS4G Consulting and Training Services http://www.gatewaygeomatics.com/ ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] Fatal error: Call to undefined function dl() in C:\ms4w\Apache\htdocs\phpmapscript.php on line 5
new wrote: No,i am still not able to get it.It was given in http://www.maptools.org/ms4w/index.phtml?page=README_INSTALL.html troubleshooting part, to check for dll errors using cmd prompt.I did so,but it gives file info. newuser. Remove all dl() functions from your PHP scripts, and load those dlls through your php.ini instead, and your errors will go away. If you have any questions regarding MS4W, please use the MS4W email list (subscribe at http://lists.maptools.org/mailman/listinfo/ms4w-users). -jeff -- Jeff McKenna FOSS4G Consulting and Training Services http://www.gatewaygeomatics.com/ ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] WMS: raster's x and y pixel dimension
Hi to all, I've a problem with the loading of a raster image via WMS (1.3.0). To load the layers of my project I use gvSIG. If I load my digital elevation model (DEM) directly from filesystem (which is a HFA/Erdas Image file - .img), x and y pixel dimension are fixed to 2.5 and -2.5 meters respectively, and fixed are also the width and height attributes. If I load the layer from Mapserver's WMS instead, x and y pixel dimension change as I zoom in or out (i. e. changing the width and height parameters of the getMap request). Is there the possibility to tell the wms client that x and y pixel dimension are constant and should never be calculated? Here's my layer definition and the tiff outputformat definition: OUTPUTFORMAT NAME GTiff DRIVER GDAL/GTiff MIMETYPE image/tiff IMAGEMODE FLOAT32 EXTENSION tif END LAYER NAME my_dem EXTENT 669913.75 5143998.75 678313.75 5150701.25 METADATA wms_titlemy_dem ##required wms_extent 669913.75 5143998.75 678313.75 5150701.25 gml_include_items all END TYPE RASTER STATUS ON PROJECTION init=epsg:25832 END DATA my_dem.tiff PROCESSING NODATA=- PROCESSING SCALE=227.23,1741.15 PROCESSING SCALE_BUCKETS=2000 PROCESSING BANDS=1 DEBUG on DUMP true TEMPLATE void # enable queryable attribute on the layer END Any help is appreciated, Flavio ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] WMS: raster's x and y pixel dimension
Hi, Width, height and BBOX are all compulsory parameters in WMS GetMap request and Mapserver is sending an image according to the request. If you want to be able to control the pixel size easily, without making WMS client to balance the BBOX and image size in pixels, consider using WCS. One way to make a WCS request is http://server.fi/cgi-bin/mapserver_wcs?SERVICE=WCSVERSION=1.0.0REQUEST =GetCoverageCOVERAGE=DEMFORMAT=image/tiffCRS=EPSG:3067ResX=1.0ResY= 1.0BBOX=533652,6973434,534658,6974219 You can see parameters ResX and ResY which are used for controlling the pixel size. -Jukka Rahkonen- fla83tn wrote: Hi to all, I've a problem with the loading of a raster image via WMS (1.3.0). To load the layers of my project I use gvSIG. If I load my digital elevation model (DEM) directly from filesystem (which is a HFA/Erdas Image file - .img), x and y pixel dimension are fixed to 2.5 and -2.5 meters respectively, and fixed are also the width and height attributes. If I load the layer from Mapserver's WMS instead, x and y pixel dimension change as I zoom in or out (i. e. changing the width and height parameters of the getMap request). Is there the possibility to tell the wms client that x and y pixel dimension are constant and should never be calculated? Here's my layer definition and the tiff outputformat definition: OUTPUTFORMAT NAME GTiff DRIVER GDAL/GTiff MIMETYPE image/tiff IMAGEMODE FLOAT32 EXTENSION tif END LAYER NAME my_dem EXTENT 669913.75 5143998.75 678313.75 5150701.25 METADATA wms_titlemy_dem ##required wms_extent 669913.75 5143998.75 678313.75 5150701.25 gml_include_items all END TYPE RASTER STATUS ON PROJECTION init=epsg:25832 END DATA my_dem.tiff PROCESSING NODATA=- PROCESSING SCALE=227.23,1741.15 PROCESSING SCALE_BUCKETS=2000 PROCESSING BANDS=1 DEBUG on DUMPtrue TEMPLATE void # enable queryable attribute on the layer END Any help is appreciated, Flavio ___ 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] Black background with palette
Steve Lime wrote: Are you compiling with the experimental png support? No, but I just tried with it and it didn't resolved the issue. I noticed a slight change of the image quality though. Thanks, -- Alexandre Dubé Mapgears www.mapgears.com ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] map_web_template
Hi Lee: There's been a lot of change in that area in 5.x series. I believe the syntax is: input type=hidden name=map.web value=TEMPLATE+/topo/topo1.html Steve Lee hate...@yahoo.com 11/29/09 9:42 PM Greetings, I have one mapfile and use many template files to read from the mapfile. In Mapserver 4, I could use templatepattern '.*' in the mapfile, and from an html form send a variable like this; input type='hidden' name='map_web_template' value='/topo/topo1.htm' In Mapserver 5 it doesn't seem to work ( loadWeb(): Unknown identifier ). Is it possible to pass the name of an HTML template in Mapserver 5 using an HTML form? And if it is, then how? Thanks Lee ___ 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: Re: [mapserver-users] WMS: raster's x and y pixel dimension
Thank you Jukka for the quick reply. Now I'm able to correctly generate z- dimension from DEM layer. However, since I'm new to GIS, I'm not able to understand the differences between WCS and WMS..could you briefly summarize the goal of the two approach? And, as last question , should I set the resX and resY parameters from client or could I embed them directly into the map file? Best regards, Flavio Hi, Width, height and BBOX are all compulsory parameters in WMS GetMap request and Mapserver is sending an image according to the request. If you want to be able to control the pixel size easily, without making WMS client to balance the BBOX and image size in pixels, consider using WCS. One way to make a WCS request is http://server.fi/cgi- bin/mapserver_wcs?SERVICE=WCSVERSION=1.0.0REQUEST =GetCoverageCOVERAGE=DEMFORMAT=image/tiffCRS=EPSG:3067ResX=1.0ResY= 1. 0BBOX=533652,6973434,534658,6974219 You can see parameters ResX and ResY which are used for controlling the pixel size. -Jukka Rahkonen- fla83tn wrote: Hi to all, I've a problem with the loading of a raster image via WMS (1.3.0). To load the layers of my project I use gvSIG. If I load my digital elevation model (DEM) directly from filesystem (which is a HFA/Erdas Image file - .img), x and y pixel dimension are fixed to 2.5 and -2.5 meters respectively, and fixed are also the width and height attributes. If I load the layer from Mapserver's WMS instead, x and y pixel dimension change as I zoom in or out (i. e. changing the width and height parameters of the getMap request). Is there the possibility to tell the wms client that x and y pixel dimension are constant and should never be calculated? Here's my layer definition and the tiff outputformat definition: OUTPUTFORMAT NAME GTiff DRIVER GDAL/GTiff MIMETYPE image/tiff IMAGEMODE FLOAT32 EXTENSION tif END LAYER NAME my_dem EXTENT 669913.75 5143998.75 678313.75 5150701.25 METADATA wms_title my_dem ##required wms_extent 669913.75 5143998.75 678313.75 5150701.25 gml_include_items all END TYPE RASTER STATUS ON PROJECTION init=epsg:25832 END DATA my_dem.tiff PROCESSING NODATA=- PROCESSING SCALE=227.23,1741.15 PROCESSING SCALE_BUCKETS=2000 PROCESSING BANDS=1 DEBUG on DUMP true TEMPLATE void # enable queryable attribute on the layer END Any help is appreciated, Flavio ___ 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 Client and SLD
Hi There, The first thing would be to make sure that the server supports SLD styling. Doing a GetCapabilities [1], It seems it does not (at least it does not the DescribeLayer operation which would indicate that SLD is supported). If there server indeed supports sld, I would suggest to do a manual call first [2][3] and see if it applies the sld properly. If all goes well you can then try it from MapServer. Note also that there seems to be a error in your sld: ogc:Filterogc:PropertyIsEqualToogc:PropertyNameSTATUS/ogc:PropertyName/ogc:PropertyIsEqualTo/ogc:Filter should have a literal value in it, something like: ogc:Filterogc:PropertyIsEqualToogc:PropertyNameSTATUS/ogc:PropertyNameogc:Literal1/ogc:Literal/ogc:PropertyIsEqualTo/ogc:Filter Hope it helps. regards,, [1]: http://atlas.information.qld.gov.au/ArcGIS/services/IRTM/MapServer/WMSServer?service=WMSRequest=GetCapabilities [2]:http://atlas.information.qld.gov.au/ArcGIS/services/IRTM/MapServer/WMSServer?service=WMSVERSION=1.1.0Request=GetMapLayers=56SRS=EPSG:4326BBOX=137.984510,-28.998470,153.534386,-10.098496FORMAT=image/pngWIDTH=300HEIGHT=200STYLES=; [3]http://atlas.information.qld.gov.au/ArcGIS/services/IRTM/MapServer/WMSServer?service=WMSVERSION=1.1.0Request=GetMapLayers=56SRS=EPSG:4326BBOX=137.984510,-28.998470,153.534386,-10.098496FORMAT=image/pngWIDTH=300HEIGHT=200STYLES=sld=http://../mysld.xml Tony Baylis wrote: All, This is the first time I have tried styling external WMS data using SLD and cannot get the returned data/image in the desired style. Below is the simplified mapfile and SLD file. If anyone has any pointers I'd be more than grateful. Please note that the link to the SLD file does work with the following return: 56 APPLICATION STATUS #ff GRANTED STATUS #be Tony Mapfile: # # Start of map file # MAP NAME qld_tenement STATUS ON SIZE 800 500 EXTENT 140 -23.25 150 -17 UNITS DD SHAPEPATH /var/www/remwms/htdocs/data IMAGECOLOR 192 213 255 SYMBOLSET /var/www/remwms/htdocs/includes/symbols.sym FONTSET /usr/share/fonts/truetype/font.list DEBUG 2 CONFIG MS_ERRORFILE /var/www/ms_tmp/ms_error.txt #IMAGETYPE PNG OUTPUTFORMAT NAME AGGA MIMETYPE image/png DRIVER AGG/PNG EXTENSION png IMAGEMODE RGBA TRANSPARENT ON END # # Start of web interface definition # WEB IMAGEPATH /var/www/ms_tmp/ IMAGEURL http://mapserver1/ms_tmp/; END # # Assign Projection # PROJECTION init=epsg:4283 END LAYER NAME EPM TYPE RASTER STATUS ON CONNECTIONTYPE WMS CONNECTION 'http://atlas.information.qld.gov.au/ArcGIS/services/IRTM/MapServer/WMSServer?' METADATA wms_srs EPSG:4326 wms_name 56 wms_server_version 1.1.1 wms_format image/png wms_title EPM wms_include_itemsall wms_sld_url http://mapserver1/remwms/includes/sld/publicsld.xml; wms_legend_graphic 0 wms_feature_info_mime_type text/plain END END END SLD File: ?xml version=1.0 encoding=UTF-8? StyledLayerDescriptor version=1.0.0 xmlns=http://www.opengis.net/sld; xmlns:ogc=http://www.opengis.net/ogc; xmlns:xlink=http://www.w3.org/1999/xlink; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.opengis.net/sld http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd; NamedLayer Name56/Name UserStyle FeatureTypeStyle Rule NameAPPLICATION/Name ogc:Filterogc:PropertyIsEqualToogc:PropertyNameSTATUS/ogc:PropertyName/ogc:PropertyIsEqualTo/ogc:Filter PolygonSymbolizer Fill CssParameter name=fill#ff/CssParameter /Fill /PolygonSymbolizer /Rule Rule NameGRANTED/Name ogc:Filterogc:PropertyIsEqualToogc:PropertyNameSTATUS/ogc:PropertyName/ogc:PropertyIsEqualTo/ogc:Filter PolygonSymbolizer Fill CssParameter name=fill#be/CssParameter /Fill /PolygonSymbolizer /Rule /FeatureTypeStyle /UserStyle /NamedLayer /StyledLayerDescriptor -- Assefa Yewondwossen Software Analyst Email: ass...@dmsolutions.ca http://www.dmsolutions.ca/ Phone: (613) 565-5056 (ext 14) Fax: (613) 565-0925 ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] Is that mapserver support download map???
Hello, My project require that allow user draw a rectangle and download map in this frame into his machine. After that, he can use some software (ex: quantum gis) to work with this map. I spent a lot of time finding solution on web but unsuccess. Please help me if you can. Thanks for your attention and sorry about my language skill. -- View this message in context: http://n2.nabble.com/Is-that-mapserver-support-download-map-tp4095271p4095271.html Sent from the Mapserver - User mailing list archive at Nabble.com. ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] Using Open street map tiles via GDAL_WMS
I've been trying to use Open street map tiles via a mapserver WMS
service displayed in OpenLayers.
This is sort of working - in that I'm getting maps displayed and they
seem to be in the right position (as checked against other datasets).
My issue is that the images are nowhere near as clear as the originals
from the Open Street map tiles. I've kept projections the same
throughout - and they don't appear to be being re-projected. The
images saved in the local cache (if enabled) are the same as from Open
Street Map. What appears to be happening is that mapserver is getting
images from (perhaps) a zoom level too high - and then re-sampling
these to produce the WMS output image - which then appears to have too
much detail displayed for its zoom level (if you understand what I'm
trying to say).
Any ideas why this is happening - I've messed around with Bounding
boxes and image sizes - but it doesn't seem to make any difference.
Thanks
James
MapFile extract:
LAYER
NAME OSM
STATUS ON
TYPE RASTER
DATA D:\Websites\OpenStreetMap\OSM.xml
PROJECTION
init=EPSG:900913
END
END
GDAL_WMS
Service name=TMS
ServerUrlhttp://tile.openstreetmap.org/${z}/${x}/${y}.png/ServerUrl
/Service
DataWindow
UpperLeftX-20037508.34/UpperLeftX
UpperLeftY20037508.34/UpperLeftY
LowerRightX20037508.34/LowerRightX
LowerRightY-20037508.34/LowerRightY
TileLevel19/TileLevel
TileCountX1/TileCountX
TileCountY1/TileCountY
YOrigintop/YOrigin
/DataWindow
ProjectionEPSG:900913/Projection
BlockSizeX256/BlockSizeX
BlockSizeY256/BlockSizeY
BandsCount3/BandsCount
/GDAL_WMS
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] Using Open street map tiles via GDAL_WMS
On Tue, Dec 01, 2009 at 06:51:58PM +, James Perrins wrote: I've been trying to use Open street map tiles via a mapserver WMS service displayed in OpenLayers. Er... why? Why not just load the tiles directly in OpenLayers? Regards, -- Christopher Schmidt MetaCarta ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] Using Open street map tiles via GDAL_WMS
Sorry - meant to cover that - should have said this is just a mechanism to test getting the OSM tiles into a WMS layer - as I appreciate that if the ultimate aim was getting OSM tiles in openlayers its a pretty silly way of doing it ! Ultimately the aim was to use them in a custom desktop app along with other WMS delivered data. The other possible route is to reference the tiles directly from the desktop app (which was actually what I was looking at when I saw this option in GDAL and thought seeing as WMS service was going to be used anyway - this might be an easier route getting all the data delivered in in one go) Thanks On Tue, Dec 1, 2009 at 6:59 PM, Christopher Schmidt crschm...@metacarta.com wrote: On Tue, Dec 01, 2009 at 06:51:58PM +, James Perrins wrote: I've been trying to use Open street map tiles via a mapserver WMS service displayed in OpenLayers. Er... why? Why not just load the tiles directly in OpenLayers? Regards, -- Christopher Schmidt MetaCarta ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: Re: [mapserver-users] WMS: raster's x and y pixel dimension
Hi, I would say that the main difference is that WMS is meant for showing a map on a computer screen, while WCS is made for letting users to download data so they can utilise it locally or process further. Real life is not so black and white. I promise you will find lots of good reading about WMS and WCS easily. Do not forget to read a little bit about WFS as well, service for downloading vector data. -Jukka Rahkonen- fla83tn wrote: Lähetetty: ti 1.12.2009 17:31 Vastaanottaja: Rahkonen Jukka; mapserver-users@lists.osgeo.org Aihe: Re: Re: [mapserver-users] WMS: raster's x and y pixel dimension Thank you Jukka for the quick reply. Now I'm able to correctly generate z- dimension from DEM layer. However, since I'm new to GIS, I'm not able to understand the differences between WCS and WMS..could you briefly summarize the goal of the two approach? And, as last question , should I set the resX and resY parameters from client or could I embed them directly into the map file? Best regards, Flavio Hi, Width, height and BBOX are all compulsory parameters in WMS GetMap request and Mapserver is sending an image according to the request. If you want to be able to control the pixel size easily, without making WMS client to balance the BBOX and image size in pixels, consider using WCS. One way to make a WCS request is http://server.fi/cgi- bin/mapserver_wcs?SERVICE=WCSVERSION=1.0.0REQUEST =GetCoverageCOVERAGE=DEMFORMAT=image/tiffCRS=EPSG:3067ResX=1.0ResY= 1. 0BBOX=533652,6973434,534658,6974219 You can see parameters ResX and ResY which are used for controlling the pixel size. -Jukka Rahkonen- fla83tn wrote: Hi to all, I've a problem with the loading of a raster image via WMS (1.3.0). To load the layers of my project I use gvSIG. If I load my digital elevation model (DEM) directly from filesystem (which is a HFA/Erdas Image file - .img), x and y pixel dimension are fixed to 2.5 and -2.5 meters respectively, and fixed are also the width and height attributes. If I load the layer from Mapserver's WMS instead, x and y pixel dimension change as I zoom in or out (i. e. changing the width and height parameters of the getMap request). Is there the possibility to tell the wms client that x and y pixel dimension are constant and should never be calculated? Here's my layer definition and the tiff outputformat definition: OUTPUTFORMAT NAME GTiff DRIVER GDAL/GTiff MIMETYPE image/tiff IMAGEMODE FLOAT32 EXTENSION tif END LAYER NAME my_dem EXTENT 669913.75 5143998.75 678313.75 5150701.25 METADATA wms_title my_dem ##required wms_extent 669913.75 5143998.75 678313.75 5150701.25 gml_include_items all END TYPE RASTER STATUS ON PROJECTION init=epsg:25832 END DATA my_dem.tiff PROCESSING NODATA=- PROCESSING SCALE=227.23,1741.15 PROCESSING SCALE_BUCKETS=2000 PROCESSING BANDS=1 DEBUG on DUMP true TEMPLATE void # enable queryable attribute on the layer END Any help is appreciated, Flavio ___ 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's x and y pixel dimension
Hi, Thank you for clarifying my quick answer. I am looking WCS from a narrow viewport because I use it mostly for delivering aerial images in original resolution and quality. WCS does give more. Delivering raw data is not the only alternative with WCS but it offers also some limited processing options like resampling to different resolution, reprojecting and a set of user selectable outputformats. When it comes to spatial relevance, for me the image captured from WMS does not have much spatial relevance after it has arrived to the computer if the request used for ordering it from the server is not known. GIS program who made the request does remember it but save it on a disk, or capture it with a web browser and it is just an image. Of course the situation is similar if you take an image from WCS server in png or jpeg format which do not carry embedded metadata. But this is not black and white either, Mapserver WMS can also create georeferenced geotiff or ecw files, even most WMS clients do not know what do do with them. Is it too simple to say that WMS was planned to be used for showing a map, WCS for downloading coverages and WFS for querying and downloading features? -Jukka- Gerald Creager wrote: Er... not quite. WMS is designed to provide a map for, say, a baselayer or background with spatial relevance for GIS work. A picture on a screen is similar, but a WMS result has spatial relevance. Web Coverage Service delivers a product with spatial relevance and data embedded within the pixels, voxels, etc of the coverage. You're not too far off, but I believe you're attempting to oversimplify this. A WFS result will provide a feature (line, polygon, point, polyline, etc.) with all of its attributes. In a coverage, e.g., a geotiff of a 3-band LandSAT image, you would have information on which bands were provided for the RGB elements, and the pixel values for each. The coverage is georegistered so that the spatial relevance of the image is preserved. Similarly, a netcdf with significantly more values could be passed as a coverage and utilized, not limited to simply 3 bands of color (data). gerry Rahkonen Jukka wrote: Hi, I would say that the main difference is that WMS is meant for showing a map on a computer screen, while WCS is made for letting users to download data so they can utilise it locally or process further. Real life is not so black and white. I promise you will find lots of good reading about WMS and WCS easily. Do not forget to read a little bit about WFS as well, service for downloading vector data. -Jukka Rahkonen- fla83tn wrote: Lähetetty: ti 1.12.2009 17:31 Vastaanottaja: Rahkonen Jukka; mapserver-users@lists.osgeo.org Aihe: Re: Re: [mapserver-users] WMS: raster's x and y pixel dimension Thank you Jukka for the quick reply. Now I'm able to correctly generate z- dimension from DEM layer. However, since I'm new to GIS, I'm not able to understand the differences between WCS and WMS..could you briefly summarize the goal of the two approach? And, as last question , should I set the resX and resY parameters from client or could I embed them directly into the map file? Best regards, Flavio Hi, Width, height and BBOX are all compulsory parameters in WMS GetMap request and Mapserver is sending an image according to the request. If you want to be able to control the pixel size easily, without making WMS client to balance the BBOX and image size in pixels, consider using WCS. One way to make a WCS request is http://server.fi/cgi- bin/mapserver_wcs?SERVICE=WCSVERSION=1.0.0REQUEST =GetCoverageCOVERAGE=DEMFORMAT=image/tiffCRS=EPSG:3067ResX=1.0ResY= 1. 0BBOX=533652,6973434,534658,6974219 You can see parameters ResX and ResY which are used for controlling the pixel size. -Jukka Rahkonen- fla83tn wrote: Hi to all, I've a problem with the loading of a raster image via WMS (1.3.0). To load the layers of my project I use gvSIG. If I load my digital elevation model (DEM) directly from filesystem (which is a HFA/Erdas Image file - .img), x and y pixel dimension are fixed to 2.5 and -2.5 meters respectively, and fixed are also the width and height attributes. If I load the layer from Mapserver's WMS instead, x and y pixel dimension change as I zoom in or out (i. e. changing the width and height parameters of the getMap request). Is there the possibility to tell the wms client that x and y pixel dimension are constant and should never be calculated? Here's my layer definition and the tiff outputformat definition: OUTPUTFORMAT NAME GTiff DRIVER GDAL/GTiff MIMETYPE image/tiff IMAGEMODE FLOAT32 EXTENSION tif END LAYER NAME my_dem EXTENT 669913.75 5143998.75 678313.75 5150701.25 METADATA wms_title my_dem ##required wms_extent 669913.75 5143998.75 678313.75 5150701.25
Re: [mapserver-users] WMS: raster's x and y pixel dimension
Jukka The key issue here is that you should be making the WMS request, and thus, you know what the spatial extents, projection, and CRS are for that map. If all you are doing is using a WMS result someone else got, without the key metadata, what you have is not a web _map_ but a picture. If you've the metadata, you have a map processable via a GIS or suitable for use on another spatial display system such as MapServer. gerry Rahkonen Jukka wrote: Hi, Thank you for clarifying my quick answer. I am looking WCS from a narrow viewport because I use it mostly for delivering aerial images in original resolution and quality. WCS does give more. Delivering raw data is not the only alternative with WCS but it offers also some limited processing options like resampling to different resolution, reprojecting and a set of user selectable outputformats. When it comes to spatial relevance, for me the image captured from WMS does not have much spatial relevance after it has arrived to the computer if the request used for ordering it from the server is not known. GIS program who made the request does remember it but save it on a disk, or capture it with a web browser and it is just an image. Of course the situation is similar if you take an image from WCS server in png or jpeg format which do not carry embedded metadata. But this is not black and white either, Mapserver WMS can also create georeferenced geotiff or ecw files, even most WMS clients do not know what do do with them. Is it too simple to say that WMS was planned to be used for showing a map, WCS for downloading coverages and WFS for querying and downloading features? -Jukka- Gerald Creager wrote: Er... not quite. WMS is designed to provide a map for, say, a baselayer or background with spatial relevance for GIS work. A picture on a screen is similar, but a WMS result has spatial relevance. Web Coverage Service delivers a product with spatial relevance and data embedded within the pixels, voxels, etc of the coverage. You're not too far off, but I believe you're attempting to oversimplify this. A WFS result will provide a feature (line, polygon, point, polyline, etc.) with all of its attributes. In a coverage, e.g., a geotiff of a 3-band LandSAT image, you would have information on which bands were provided for the RGB elements, and the pixel values for each. The coverage is georegistered so that the spatial relevance of the image is preserved. Similarly, a netcdf with significantly more values could be passed as a coverage and utilized, not limited to simply 3 bands of color (data). gerry Rahkonen Jukka wrote: Hi, I would say that the main difference is that WMS is meant for showing a map on a computer screen, while WCS is made for letting users to download data so they can utilise it locally or process further. Real life is not so black and white. I promise you will find lots of good reading about WMS and WCS easily. Do not forget to read a little bit about WFS as well, service for downloading vector data. -Jukka Rahkonen- fla83tn wrote: Lähetetty: ti 1.12.2009 17:31 Vastaanottaja: Rahkonen Jukka; mapserver-users@lists.osgeo.org Aihe: Re: Re: [mapserver-users] WMS: raster's x and y pixel dimension Thank you Jukka for the quick reply. Now I'm able to correctly generate z- dimension from DEM layer. However, since I'm new to GIS, I'm not able to understand the differences between WCS and WMS..could you briefly summarize the goal of the two approach? And, as last question , should I set the resX and resY parameters from client or could I embed them directly into the map file? Best regards, Flavio Hi, Width, height and BBOX are all compulsory parameters in WMS GetMap request and Mapserver is sending an image according to the request. If you want to be able to control the pixel size easily, without making WMS client to balance the BBOX and image size in pixels, consider using WCS. One way to make a WCS request is http://server.fi/cgi- bin/mapserver_wcs?SERVICE=WCSVERSION=1.0.0REQUEST =GetCoverageCOVERAGE=DEMFORMAT=image/tiffCRS=EPSG:3067ResX=1.0ResY= 1. 0BBOX=533652,6973434,534658,6974219 You can see parameters ResX and ResY which are used for controlling the pixel size. -Jukka Rahkonen- fla83tn wrote: Hi to all, I've a problem with the loading of a raster image via WMS (1.3.0). To load the layers of my project I use gvSIG. If I load my digital elevation model (DEM) directly from filesystem (which is a HFA/Erdas Image file - .img), x and y pixel dimension are fixed to 2.5 and -2.5 meters respectively, and fixed are also the width and height attributes. If I load the layer from Mapserver's WMS instead, x and y pixel dimension change as I zoom in or out (i. e. changing the width and height parameters of the getMap request). Is there the possibility to tell the wms client that x and y pixel dimension are constant and should never be
Re: [mapserver-users] WMS: raster's x and y pixel dimension
And, as usual, I was too fast for my own good. Your last sentence summarized the abstracts of the Open Geospatial Consortium for WMS, WFS and WCS. However, it begs the question of defining the terms. A knowledge of teh definitions is necessary to understand what you want to access and what you're getting. Mistakes are common where one thinks they understand a feature but then get something back that didn't match their understanding. I could substitute 'map' or 'coverage' for feature above. And then, there's the metadata. Metadata and a coherent vocabulary and ontology, often formated as a registered schema (GML in this case) provides the description of the data for further use. When one issues a GetCapabilities request to a Web [Map|Feature|Coverage] server one gets a GML response back with all the pertinent metadata available about the requested object that's on that server. From that, one may craft a request for the data and data-type desired. While you're working with that object, you will need to retain the metadata. Note that in my earlier post, I indicated use of a 3-band geotiff of landsat data. This represents a processed image, as you've restricted the dataset to those three bands of data. The netCDF example was an unprocessed (potentially) example (Hmmm. Maybe I should add some cgi-hooks for NCAR's NCL package for netcdf subsetting and processing?). The WxS packages, as I've taken to calling them, are powerful tools for their specific tasks. They can be used out-of-context, too, but that tends to confuse others who aren't familiar with how you were thinking if you ask them to do strange things. Your approach to this does not appear incorrect to me, but doesn't take advantage of the full capabilities of the services. gerry Rahkonen Jukka wrote: Hi, Thank you for clarifying my quick answer. I am looking WCS from a narrow viewport because I use it mostly for delivering aerial images in original resolution and quality. WCS does give more. Delivering raw data is not the only alternative with WCS but it offers also some limited processing options like resampling to different resolution, reprojecting and a set of user selectable outputformats. When it comes to spatial relevance, for me the image captured from WMS does not have much spatial relevance after it has arrived to the computer if the request used for ordering it from the server is not known. GIS program who made the request does remember it but save it on a disk, or capture it with a web browser and it is just an image. Of course the situation is similar if you take an image from WCS server in png or jpeg format which do not carry embedded metadata. But this is not black and white either, Mapserver WMS can also create georeferenced geotiff or ecw files, even most WMS clients do not know what do do with them. Is it too simple to say that WMS was planned to be used for showing a map, WCS for downloading coverages and WFS for querying and downloading features? -Jukka- Gerald Creager wrote: Er... not quite. WMS is designed to provide a map for, say, a baselayer or background with spatial relevance for GIS work. A picture on a screen is similar, but a WMS result has spatial relevance. Web Coverage Service delivers a product with spatial relevance and data embedded within the pixels, voxels, etc of the coverage. You're not too far off, but I believe you're attempting to oversimplify this. A WFS result will provide a feature (line, polygon, point, polyline, etc.) with all of its attributes. In a coverage, e.g., a geotiff of a 3-band LandSAT image, you would have information on which bands were provided for the RGB elements, and the pixel values for each. The coverage is georegistered so that the spatial relevance of the image is preserved. Similarly, a netcdf with significantly more values could be passed as a coverage and utilized, not limited to simply 3 bands of color (data). gerry Rahkonen Jukka wrote: Hi, I would say that the main difference is that WMS is meant for showing a map on a computer screen, while WCS is made for letting users to download data so they can utilise it locally or process further. Real life is not so black and white. I promise you will find lots of good reading about WMS and WCS easily. Do not forget to read a little bit about WFS as well, service for downloading vector data. -Jukka Rahkonen- fla83tn wrote: Lähetetty: ti 1.12.2009 17:31 Vastaanottaja: Rahkonen Jukka; mapserver-users@lists.osgeo.org Aihe: Re: Re: [mapserver-users] WMS: raster's x and y pixel dimension Thank you Jukka for the quick reply. Now I'm able to correctly generate z- dimension from DEM layer. However, since I'm new to GIS, I'm not able to understand the differences between WCS and WMS..could you briefly summarize the goal of the two approach? And, as last question , should I set the resX and resY parameters from client or could I embed
