-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Disable GPX export for polygons #4
Comments
@igeofr Did you try to add this code in the python file? Did it work? |
No, I didn't try because I rent a Lizmap server from you and I don't have the possibility to do the test. |
Ah yes, it makes sense, sorry. I will try ;-) |
Done : 55912fd The GPX has some restrictions on field names. |
That's great. Thanks |
According to a unittest added, GPX is failing : https://travis-ci.org/github/3liz/qgis-wfsOutputExtension/jobs/734199354#L246 |
Yes, it works perfectly for points and lines. |
Indeed, it's correct. |
@rldhont, @igeofr I tried to deactivate this export for polygons. For now the, the list of format generated by this QGIS Server plugin is inserted at the root WFS service (global for all layers provided by the WFS Server) and is not configured per layer. <FeatureTypeList>
<FeatureType>
<Name xmlns:gn="urn:x-inspire:specification:gmlas:GeographicalNames:3.0">gn:NamedPlace</Name>
<Title>gn:NamedPlace</Title>
<DefaultCRS>urn:ogc:def:crs:EPSG::4326</DefaultCRS>
<OutputFormats>
<Format>application/xml; subtype="gml/3.2.1"</Format>
</OutputFormats> http://opengeospatial.github.io/e-learning/wfs/text/operations.html#response But then I'm not sure this will be used by LWC. So I will let this feature request open and I have renamed it. |
Hello,
It would be interesting to add the gpx format to the list in order to easily load the data into a GPS.
Thanks
The text was updated successfully, but these errors were encountered: