[mapserver-users] Xml support in Mapserver v8
Hi I maintain my maps in xml, converting to map files utilising xsltproc. 1. will there be an xsltproc in v8? 2. will there be an updated xsd file for v8? 3 if 1 & 2 are yes, is it possible to get an early release of the xsd file? Thanks Aimee ___ MapServer-users mailing list MapServer-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] Version 7.7 & proj.db
Hi I used proj-bin/testing,now 7.2.0-1 amd64 [installed] proj-data/testing,now 7.2.0-1 all [installed,automatic] libproj-dev/testing,now 7.2.0-1 amd64 [installed,automatic] and gdal-bin/testing,now 3.1.4+dfsg-1+b1 amd64 [installed] gdal-data/testing,now 3.1.4+dfsg-1 all [installed] libgdal-dev/testing,now 3.1.4+dfsg-1+b1 amd64 [installed] These are the ones available from the Bullseye repository. I am not clear where the proj.db file would have been installed, and where it should go / how it is referenced in the MapServer directory structure. From my point of view the map looks the same as the existing > On 24 Nov 2020, at 12:28, Jeff McKenna wrote: > > On 2020-11-24 8:18 a.m., Jeff McKenna wrote: >> On 2020-11-24 8:12 a.m., Jeff McKenna wrote: >>> Master now requires PROJ 7 (and PROJ now requires SQLite, LibTIFF, Curl). >>> The PROJ build process should generate 'proj.db' inside /data, and 'make >>> install' should place that file in something like >>> /usr/local/share/proj/proj.db >>> >>> Make sure that GDAL and MapServer are built with PROJ 7 (7.2.0 is >>> recommended). >>> >>> -jeff >>> >>> >> Be careful also that if you have compiled the GeoTIFF library yourself, that >> it also requires PROJ (and therefore PROJ 7). I've had to recompile that on >> many client systems. >> -jeff > > and GDAL 3.2.0 is recommended with PROJ 7.2.0 > > clear as mud? :) > > Hello from the east coast of Canada, > > > > -- > Jeff McKenna > MapServer Consulting and Training Services > co-founder of FOSS4G > http://gatewaygeo.com/ > ___ > mapserver-users mailing list > mapserver-users@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] Version 7.7 & proj.db
Built mapserver 7.7? from the master on github, using Debian Bullseye & Postgresql 13 with PostGis v 3.. root@bullseye-alpha:/home/osm/var/www/gis# mapserv -v MapServer version 7.7-dev OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER SUPPORTS=WFS_SERVER SUPPORTS=WCS_SERVER SUPPORTS=FASTCGI SUPPORTS=GEOS SUPPORTS=POINT_Z_M SUPPORTS=PBF INPUT=JPEG INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE root@bullseye-alpha:/home/osm/var/www/gis# While scanning the debug.log, noticed debugFile.log:[Mon Nov 23 16:24:25 2020].912914 PROJ: Debug: proj_as_proj_string: Cannot find proj.db debugFile.log:[Mon Nov 23 16:24:25 2020].913854 PROJ: Debug: proj_create_operation_factory_context: Cannot find proj.db The map presents ok as far as I can tell. Is this cause for concern as a Google search shows a number of hits with various software having a similar message. ___ mapserver-users mailing list mapserver-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] MS RFC CLASS Name
Mapfile Structure Request: Please consider changing the CLASS name to LAYERCLASS Reason: CLASS conflicts with other programming languages where CLASS is a reserved name. Example: Using the Map file classes derived from the xml or json reference definitions to auto-create GUI’s causes conflicts. Thanks ___ mapserver-users mailing list mapserver-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-users
