Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MapServer 6.2.0-beta1 - WFS - Templating Issue - Custom OUTPUTFORMAT #4367

Closed
DonaldKerr opened this issue Jul 2, 2012 · 5 comments
Closed
Assignees
Milestone

Comments

@DonaldKerr
Copy link

MS4W compilation of MapServer 6.2.0-beta1.

With a WFS request that specifies an alternative template outputformat, mapserv.exe crashes with the message "mapserv.exe has encountered a problem and needs to close." This request is working with the existing MS4W version.

The request: http://localhost:81/cgi-bin/mapserv.exe?map=osmmwfs.map&service=wfs&version=
1.0.0&request=getfeature&typename=TopographicLine&bbox=258213,665662,258875,
666158&outputformat=OSMMWFS

The outputformat section of the map file:

OUTPUTFORMAT
    NAME "OSMMWFS"
    DRIVER "TEMPLATE"
    MIMETYPE "text/xml; subtype=gml/2.1.2"
    FORMATOPTION "FILE=osmmwfstemplate.gml"
    FORMATOPTION "ATTACHMENT=osmmwfs.gml"
END # OUTPUTFORMAT

osmmwfstemplate.gml contents:

<!-- mapserver template -->
<?xml version='1.0' encoding='UTF-8'?>
<osgb:FeatureCollection xmlns:osgb='http://www.ordnancesurvey.co.uk/xml/namespaces/osgb'
xmlns:gml='http://www.opengis.net/gml'
xmlns:xlink='http://www.w3.org/1999/xlink'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xsi:schemaLocation='http://www.ordnancesurvey.co.uk/xml/namespaces/osgb
http://www.ordnancesurvey.co.uk/xml/schema/v7/OSDNFFeatures.xsd'
fid='GDS-87948-1169'>
<gml:description>Ordnance Survey, (c) Crown Copyright. All rights reserved, 2012-03-20</gml:description>     [resultset layer=TopographicLine] [feature] <osgb:topographicMember>
    <osgb:TopographicLine fid='[toid]'>
        <osgb:featureCode>[featurecode]</osgb:featureCode>

<osgb:descriptiveGroup>[descriptivegroup]</osgb:descriptiveGroup>
        <osgb:physicalLevel>[lineclass]</osgb:physicalLevel>
        <osgb:polyline>
            <gml:LineString srsName='osgb:BNG'>
                <gml:coordinates>[shpxy]</gml:coordinates>
            </gml:LineString>
        </osgb:polyline>
    </osgb:TopographicLine>
</osgb:topographicMember>
[/feature]
[/resultset]
<osgb:boundedBy>
    <gml:Box srsName='osgb:BNG'>
        <gml:coordinates>[bbox]</gml:coordinates>
    </gml:Box>
</osgb:boundedBy>
</osgb:FeatureCollection>

Without "&outputformat=OSMMWFS", all is well. I have tried this with IIS on port 80 and Apache on port 81 with the same results.

No error with the Mapserver 6.0.3 MS4W compilation.

Also, DEBUG 5 in map file and layer results in log being created with no contents.

Regards,

Donald

@tbonfort
Copy link
Member

I can look into this one, provided you supply a self-contained test case that reproduces this

@DonaldKerr
Copy link
Author

Thomas,

Thank you for taking the time to look at this problem. I have created a small test case that includes some data held in an access database. This is a completely different setup to that mentioned above which uses PostGis but the problem is replicated all the same.

The test files are available to download from here: http://www.dkerr.co.uk/TestWFS.zip

There's a readme in the zip file with some information about setting up the test case. If you need anything further then please let me know.

Many thanks, once again.

Regards,

Donald

@tbonfort
Copy link
Member

tbonfort commented Aug 1, 2012

I was able to produce a segfault with your mapfile after modifying it to use a postgis db (I'm not equipped to test with windows formats), and assume this will fix your issue (the segfault was related to multi-label support, and is consistent with 6.0.3 working correctly). Closing, but please confirm.
thanks,
thomas

@tbonfort tbonfort closed this as completed Aug 1, 2012
@DonaldKerr
Copy link
Author

Thanks for that, Thomas. I can't test as I can't compile the source. Will wait for the next beta release and MS4W compilation and will provide feedback when that comes out.

Regards,

Donald

@DonaldKerr
Copy link
Author

Thomas,

I have now had an opportunity to have a look at the Beta 2 MS4W package from Jeff McKenna and can confirm that this issue is now sorted. Great work from you all.

Many thanks.

Regards,

Donald

mkofahl pushed a commit to faegi/mapserver that referenced this issue Apr 9, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants