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

Automatically create not-yet-existing attribute on WFS-T (insert, update) #95

Closed
jirik opened this issue Aug 19, 2020 · 3 comments · Fixed by #100
Closed

Automatically create not-yet-existing attribute on WFS-T (insert, update) #95

jirik opened this issue Aug 19, 2020 · 3 comments · Fixed by #100
Labels
enhancement New feature or request

Comments

@jirik
Copy link
Member

jirik commented Aug 19, 2020

No description provided.

@jirik
Copy link
Member Author

jirik commented Sep 11, 2020

We should support all WFS versions as GeoServer:

Sample requests for WFS 1.0:

There is no Replace action in WFS 1.

The main difference between WFS 1.0 and WFS 1.1 is that it uses different versions of GML: 2 and 3. GML 3 is backwards compatible with GML 2. For this issue, we can treat WFS 1.0 and WFS 1.1 in the same way.

@jirik
Copy link
Member Author

jirik commented Sep 14, 2020

@index-git Sample WFS request from client:

Request URL: https://example.cz/geoserver/user_1/wfs
Request Method: POST
Status Code: 200 
Remote Address: 88.86.113.227:443
Referrer Policy: no-referrer-when-downgrade

<Request-Headers>
:authority: example.cz
:method: POST
:path: /geoserver/user_1/wfs
:scheme: https
accept: application/json, text/plain, */*
accept-encoding: gzip, deflate, br
accept-language: sk-SK,sk;q=0.9,cs;q=0.8,en-US;q=0.7,en;q=0.6
cache-control: no-cache
content-length: 691
content-type: application/xml
origin: https://example.cz
pragma: no-cache
referer: https://example.cz/map1?hs_x=1661994.736015416&hs_y=6111640.741218487&hs_z=5&visible_layers=OpenStreetMap;vrstva1&hs_panel=draw
sec-fetch-dest: empty
sec-fetch-mode: cors
sec-fetch-site: same-origin
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36
</Request-Headers>

<Transaction xmlns="http://www.opengis.net/wfs" service="WFS" version="1.1.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd">
    <Insert>
        <drawlayer xmlns="http://user_1">
            <wkb_geometry>
                <Polygon xmlns="http://www.opengis.net/gml" srsName="EPSG:3857">
                    <exterior>
                        <LinearRing srsName="EPSG:3857">
                            <posList srsDimension="2">2120209.191811929 7362137.75957741 2083519.4182350442 7129769.193590474 2474877.003055147 7027853.106113216 2568639.7079879395 7378444.375375272 2120209.191811929 7362137.75957741</posList>
                        </LinearRing>
                    </exterior>
                </Polygon>
            </wkb_geometry>
        </drawlayer>
    </Insert>
</Transaction>

@index-git
Copy link
Collaborator

I see a big difference in a way, how user and layer are identified. Maybe this is alternative way for all types of queries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants