[mapserver-users] Shapezip 3D

Guillaume Sueur no-reply at neogeo-online.net
Mon Mar 3 01:20:12 PST 2014


OK, got it, but actually no need of MapServer to do that. zip is enough :-)



Le 03/03/2014 10:16, Even Rouault a écrit :
> Selon Guillaume Sueur <no-reply at neogeo-online.net>:
>
>> Hi Even,
>>
>> Thanks for your reply even if it is disappointing. So I guess all the
>> http://mapserver.org/fr/output/ogr_output.html stuff about 2.5D/3D is
>> just rubbish and the USE_POINT_Z_M compile option is useless.
>
> Actually.... no, it is correct. My previous comment was on the input interface
> of MapServer with OGR, where Z support is not currently available. But for the
> output part (mapogroutput.c), Z support should work. So you could likely use a
> 3D shapefile (with MapServer native shapefile connection) and output a 3D
> shapezip.
>
>>
>> Thanks for your investigations
>>
>> Best regards
>>
>> Guillaume
>>
>>
>> Le 01/03/2014 12:53, Even Rouault a écrit :
>>> Le vendredi 28 février 2014 17:29:15, Guillaume Sueur a écrit :
>>>> Hi list,
>>>>
>>>> I'm trying to generate a 3D shapefile with OGR SHAPEZIP format. I'm
>>>> using MapServer 6.5 compiled with USE_POINT_Z_M options.
>>>> mapserv -v gives :
>>>> MapServer version 6.5-dev OUTPUT=PNG OUTPUT=JPEG SUPPORTS=PROJ
>>>> SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=ICONV
>>>> SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER
>>>> SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER
>>>> SUPPORTS=GEOS SUPPORTS=POINT_Z_M INPUT=JPEG INPUT=POSTGIS INPUT=OGR
>>>> INPUT=GDAL INPUT=SHAPEFILE
>>>>
>>>> My data are stored in Postgis 2.1. They are 3D. I've added the
>>>> "ows_geomtype"  "MultiPolygon25D" metadata to my layer.
>>>>
>>>> What I get is a 3D shapefile, but all the Z values are set to 0.
>>>>
>>>> Lookking at the request made by MapServer to Postgis, I see the geom is
>>>> requested with Force2D function :
>>>> encode(ST_AsBinary(ST_Force2D("the_geom"),'NDR'),'hex') as geom
>>>>
>>>> Is this a bug or is there some more settings I didn't set properly ?
>>>
>>> Guillaume,
>>>
>>> there's no support yet for parsing 3D geometries in mappostgis.c
>> (mentionned
>>> in comments of https://github.com/mapserver/mapserver/pull/4803 ). I
>> wouldn't
>>> expect adding support for it to be that difficult.
>>>
>>> As a workaround, I would have suggested that you could use the OGR
>> PostgreSQL
>>> driver, but looking at mapogr.cpp, I also see that the Z support of OGR
>> isn't
>>> used. Grrrr....
>>>
>>> Even
>>>
>>
>
>
>
>


More information about the mapserver-users mailing list