Hi, A long time ago we did something similar with Oracle and we had an updatable view combined from three main tables. However, the primary keys of our tables took their values from sequences and we converted the "natural" primary keys that we had (parcel IDs in our case) into normal attributes with UNIQUE constraints. Our natural keys were strings which were not optimal as PK so we did not try hard to keep original schema.
Autoincrement happens when there is no gt_pk_metadata_table at all or when Geoserver does not find what it wants to find from the table. In that case Geoserver does "select max(pk)+1". It may be that a combination of view + composite PK + pk_policy=assigned is not tested so well. But first of all I would check if Geoserver really makes a successful query to the pk_metadata_table. If that query fails the result would be a fallback to Max+1 and the result would be just what you face now. -Jukka Rahkonen- Lähettäjä: Biskup, Paul <paul.bis...@fit.fichtner.de> Lähetetty: keskiviikko 10. marraskuuta 2021 9.38 Vastaanottaja: Stefan Overkamp <overk...@posteo.de>; geoserver-users@lists.sourceforge.net Aihe: Re: [Geoserver-users] Problem inserting a new feature into PostGIS-view with multiple primary key columns Hi Stefan, thank you for your response. I had already tried all combinations and everything is configured properly (the gt_pk_metadata-table is assigned in the datastore und the "expose primary key"-flag is enabled). Unfortunately it is still the same behaviour. The WFS-T-UPDATE is working and the Feature-ID is set correctly when you do a GetFeature-Request. But in the INSERT the autoincrement is done. I think it is a bug. Can someone tell in which class the INSERT and autoincrement oft he primary key is done? I could try to debug it. Thank you for your help. Regards, Paul [cid:image001.jpg@01D7D623.11918D70] Paul Biskup Head of Business Geo Intelligence BGI Fichtner IT Consulting GmbH Sarweystr. 3 70191 Stuttgart Germany Telefon +49 (711) 8995 1453 Mobil +49 (151) 1623 1453 E-mail paul.bis...@fit.fichtner.de<mailto:paul.bis...@fit.fichtner.de> Fichtner IT Consulting GmbH Sarweystr. 3, 70191 Stuttgart, Germany Amtsgericht Stuttgart HRB 761846 Board of Directors Andreas Höfler (Chairman), Dr. Albrecht Reuter www.fit.fichtner.de<https://www.fit.fichtner.de> [cid:image002.jpg@01D7D624.AB113F80]<https://blog.fichtner.de/> [cid:image003.jpg@01D7D624.AB113F80]<https://de.linkedin.com/company/fichtner-it-consulting-ag> [cid:image004.jpg@01D7D624.AB113F80]<https://twitter.com/fit_fichtner> [cid:image005.jpg@01D7D624.AB113F80]<https://www.xing.com/pages/fichtneritconsultinggmbh> [cid:image006.jpg@01D7D624.AB113F80]<https://www.kununu.com/de/fichtner> Sie benötigen Unterstützung bei der Einführung von Microsoft 365 oder wollen sich zunächst mit den Security-Maßnahmen in der Microsoft Cloud bzw. der Anwendung MS Teams vertraut machen? Dann sprechen Sie uns gerne direkt an unter digitalworkpl...@fit.fichtner.de<mailto:digitalworkpl...@fit.fichtner.de> oder informieren Sie sich hier<https://www.fichtnerdigitalworkplace.de/fileadmin/images/FDW_NEU/Dienstleistungspakete_final.jpg>. Wichtiger Hinweis für Besucher: Bitte lesen und beachten Sie die Fichtner Corona Regeln!<https://corona-regeln.fichtner.de> Erklärungen der Fichtner IT Consulting GmbH, die per E-Mail übermittelt werden, sind nur im Falle schriftlicher Bestätigung rechtsverbindlich. Bitte achten Sie auf die Umwelt, drucken Sie nur bei Bedarf. Von: Stefan Overkamp <overk...@posteo.de<mailto:overk...@posteo.de>> Gesendet: Dienstag, 9. November 2021 18:49 An: Biskup, Paul <paul.bis...@fit.fichtner.de<mailto:paul.bis...@fit.fichtner.de>>; geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net> Betreff: Re: [Geoserver-users] Problem inserting a new feature into PostGIS-view with multiple primary key columns ADVICE: This email is from an external source - be careful of attachments and links. Hi, I have no real idea but would look for: - maybe the pk_column_idx is 0-based, so 0,1 instead of 1,2 - is the gt_pk_metadata configured in the PostGIS datastore (Primary key metadata table: schema qualified table name)? - the assigned pk_policy assumes the "expose primary keys" flag has been enabled (datastore) (never worked with this, ever used sequence) good luck Stefan Am 09.11.2021 um 17:35 schrieb Biskup, Paul: Hi list, I have a problem when I try to insert a new feature with WFS-T into my PostGIS-view (name "ausspeisepunkt"). The view consists of two primary key columns, which are stored in the "gt_pk_metadata_table" (https://docs.geoserver.org/stable/en/user/data/database/primarykey.html#using-the-metadata-table-with-views<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.geoserver.org%2Fstable%2Fen%2Fuser%2Fdata%2Fdatabase%2Fprimarykey.html%23using-the-metadata-table-with-views&data=04%7C01%7C%7C1a81e73473a64229be9308d9a3a92c94%7Cb43430ce7d754158ab7b1f39e6fe6b3f%7C0%7C0%7C637720769256989734%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=JM9IX9WRntNWen8ytr4uWThVY5Qw%2FR%2BPgJGV9e3zJ6c%3D&reserved=0>): |table_schema |table_name |pk_column |pk_column_idx|pk_policy|pk_sequence| |-------------|--------------|-----------------|-------------|---------|-----------| | webgis|ausspeisepunkt|version_id |1 |assigned | | | webgis|ausspeisepunkt|primaerschluessel|2 |assigned | | In the GetFeature-Request it is working and the FeatureID is generated as expected. The UPDATE in a WFS-T is working as well. But when I try to insert a new feature, the GeoServer is not behaving as expected: In my WFS-T-INSERT-request both primary key values ("primaerschluessel" and "version_id") are provided. The problem is that, the GeoServer is still autoincrementing the values. Am I doing something wrong and what can I do to fix the problem? Below is the verbose-logging of my Insert-Request. You can see, that the values for "primaerschluessel" ("12312412412") and "version_id" ("1234") are provided: "Setting primaerschluessel to 12312412412" "Setting version_id to 1234" But in the generated Insert SQL-statement it is autoincremented (version_id= 2006, primaerschluessel=1000030): INSERT INTO "webgis"."ausspeisepunkt" ( "nemesys_key","name","typ","station","netzbetreiber","netzbetreibername","kurzname","klarname","at_nummer","eic_code","buchbar","kapazitaetsprodukt","gastag","hoehe___m","rohrbuchhoehe___m","q_min___knm3_h","q_max___knm3_h","p_min___barg","p_max___barg","hydraulische_relevanz","planungsjahr___jjjj","baubeginn___tt_mm_jjjj","inbetrieb___tt_mm_jjjj","ausserbetrieb___tt_mm_jjjj","sichtbarkeit","cv_min","cv_max","messinstrument","online_offline","periode","ableseintervall","wasserstoffanteil","kommentar","geom_g","version_id","primaerschluessel" ) VALUES ( '','PBI',null,'EVAReutte.Tirol.ST',null,'','','','','',null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,'','','','',null,'',ST_GeomFromText('POINT (508242.93957770814 5332317.2897684835)', 32633),2006,1000030) Thank you in advance! Best regards, Paul 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting primaerschluessel to 12312412412 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 1 to 12312412412 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting nemesys_key to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 2 to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting name to PBI 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 3 to PBI 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting typ to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 4 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting station to EVAReutte.Tirol.ST 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 5 to EVAReutte.Tirol.ST 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting netzbetreiber to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 6 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting netzbetreibername to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 7 to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting kurzname to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 8 to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting klarname to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 9 to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting at_nummer to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 10 to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting eic_code to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 11 to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting buchbar to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 12 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting kapazitaetsprodukt to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 13 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting gastag to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 14 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting hoehe___m to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 15 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting rohrbuchhoehe___m to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 16 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting q_min___knm3_h to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 17 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting q_max___knm3_h to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 18 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting p_min___barg to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 19 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting p_max___barg to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 20 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting hydraulische_relevanz to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 21 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting planungsjahr___jjjj to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 22 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting baubeginn___tt_mm_jjjj to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 23 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting inbetrieb___tt_mm_jjjj to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 24 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting ausserbetrieb___tt_mm_jjjj to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 25 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting sichtbarkeit to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 26 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting cv_min to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 27 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting cv_max to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 28 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting messinstrument to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 29 to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting online_offline to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 30 to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting periode to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 31 to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting ableseintervall to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 32 to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting wasserstoffanteil to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 33 to null 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting kommentar to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 34 to 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting geom_g to POINT (508242.93957770814 5332317.2897684835) 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 35 to POINT (508242.93957770814 5332317.2897684835) 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting version_id to 1234 2021-11-09 15:53:39,500 DEBUG [org.geotools.jdbc] - Setting 0 to 1234 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.data.jdbc] - exporting LiteralExpression 2021-11-09 15:53:39,502 DEBUG [org.geotools.jdbc] - Inserting new feature: INSERT INTO "webgis"."ausspeisepunkt" ( "nemesys_key","name","typ","station","netzbetreiber","netzbetreibername","kurzname","klarname","at_nummer","eic_code","buchbar","kapazitaetsprodukt","gastag","hoehe___m","rohrbuchhoehe___m","q_min___knm3_h","q_max___knm3_h","p_min___barg","p_max___barg","hydraulische_relevanz","planungsjahr___jjjj","baubeginn___tt_mm_jjjj","inbetrieb___tt_mm_jjjj","ausserbetrieb___tt_mm_jjjj","sichtbarkeit","cv_min","cv_max","messinstrument","online_offline","periode","ableseintervall","wasserstoffanteil","kommentar","geom_g","version_id","primaerschluessel" ) VALUES ( '','PBI',null,'EVAReutte.Tirol.ST',null,'','','','','',null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,'','','','',null,'',ST_GeomFromText('POINT (508242.93957770814 5332317.2897684835)', 32633),2006,1000030) [cid:image001.jpg@01D7D623.11918D70] Paul Biskup Head of Business Geo Intelligence BGI Fichtner IT Consulting GmbH Sarweystr. 3 70191 Stuttgart Germany Telefon +49 (711) 8995 1453 Mobil +49 (151) 1623 1453 E-mail paul.bis...@fit.fichtner.de<mailto:paul.bis...@fit.fichtner.de> Fichtner IT Consulting GmbH Sarweystr. 3, 70191 Stuttgart, Germany Amtsgericht Stuttgart HRB 761846 Board of Directors Andreas Höfler (Chairman), Dr. Albrecht Reuter www.fit.fichtner.de<https://www.fit.fichtner.de> [cid:image017.jpg@01D7D623.11918D70]<https://blog.fichtner.de/> [cid:image018.jpg@01D7D623.11918D70]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fde.linkedin.com%2Fcompany%2Ffichtner-it-consulting-ag&data=04%7C01%7C%7C1a81e73473a64229be9308d9a3a92c94%7Cb43430ce7d754158ab7b1f39e6fe6b3f%7C0%7C0%7C637720769256999690%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=68hHLZedCnLqQ%2BIatp28Q4w1kzRiluuGFJwXuLTTWbc%3D&reserved=0> [cid:image019.jpg@01D7D623.11918D70]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Ffit_fichtner&data=04%7C01%7C%7C1a81e73473a64229be9308d9a3a92c94%7Cb43430ce7d754158ab7b1f39e6fe6b3f%7C0%7C0%7C637720769256999690%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FPyM9lMUphyufMZFguc1%2FwR9GPzqLY5WgOvPZKv2Lc0%3D&reserved=0> [cid:image020.jpg@01D7D623.11918D70]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.xing.com%2Fpages%2Ffichtneritconsultinggmbh&data=04%7C01%7C%7C1a81e73473a64229be9308d9a3a92c94%7Cb43430ce7d754158ab7b1f39e6fe6b3f%7C0%7C0%7C637720769257009646%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gwuQ2TtxEpmpHjbs6MLL%2BpUKdM26ewvMeV2oeTjoAdM%3D&reserved=0> [cid:image021.jpg@01D7D623.11918D70]<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.kununu.com%2Fde%2Ffichtner&data=04%7C01%7C%7C1a81e73473a64229be9308d9a3a92c94%7Cb43430ce7d754158ab7b1f39e6fe6b3f%7C0%7C0%7C637720769257009646%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=8zB4LxSnITOm1ziYIvAYDnWcBDNvxNTsImy6gQEkMTs%3D&reserved=0> Sie benötigen Unterstützung bei der Einführung von Microsoft 365 oder wollen sich zunächst mit den Security-Maßnahmen in der Microsoft Cloud bzw. der Anwendung MS Teams vertraut machen? Dann sprechen Sie uns gerne direkt an unter digitalworkpl...@fit.fichtner.de<mailto:digitalworkpl...@fit.fichtner.de> oder informieren Sie sich hier<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fichtnerdigitalworkplace.de%2Ffileadmin%2Fimages%2FFDW_NEU%2FDienstleistungspakete_final.jpg&data=04%7C01%7C%7C1a81e73473a64229be9308d9a3a92c94%7Cb43430ce7d754158ab7b1f39e6fe6b3f%7C0%7C0%7C637720769257019603%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CCld4JBITDnD%2FLIQDqyq144Vo1udZLnRHwbwHxlb2GA%3D&reserved=0>. Wichtiger Hinweis für Besucher: Bitte lesen und beachten Sie die Fichtner Corona Regeln!<https://corona-regeln.fichtner.de> Erklärungen der Fichtner IT Consulting GmbH, die per E-Mail übermittelt werden, sind nur im Falle schriftlicher Bestätigung rechtsverbindlich. Bitte achten Sie auf die Umwelt, drucken Sie nur bei Bedarf. _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ianturton.com%2Ftalks%2Ffoss4g.html%23%2F&data=04%7C01%7C%7C1a81e73473a64229be9308d9a3a92c94%7Cb43430ce7d754158ab7b1f39e6fe6b3f%7C0%7C0%7C637720769257019603%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YvBYPs2%2FnGmi%2Bd1XB2FAOqXNxJdyJw9%2FmmCIx4XRqAs%3D&reserved=0> - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgeoserver.org%2Fcomm%2Fuserlist-guidelines.html&data=04%7C01%7C%7C1a81e73473a64229be9308d9a3a92c94%7Cb43430ce7d754158ab7b1f39e6fe6b3f%7C0%7C0%7C637720769257029562%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YO%2F5Z6l%2FLUWa3B6ADQeK%2BW5NQvGzyA30bOzxT4ERId0%3D&reserved=0> If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgeoserver%2Fgeoserver%2Fwiki%2FSuccessfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer&data=04%7C01%7C%7C1a81e73473a64229be9308d9a3a92c94%7Cb43430ce7d754158ab7b1f39e6fe6b3f%7C0%7C0%7C637720769257029562%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=EWMrlSz%2FoEZl%2FC0yCASAyAXojEf2dD51F2tmjq5bzxc%3D&reserved=0> Geoserver-users@lists.sourceforge.net<mailto:Geoserver-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/geoserver-users<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fgeoserver-users&data=04%7C01%7C%7C1a81e73473a64229be9308d9a3a92c94%7Cb43430ce7d754158ab7b1f39e6fe6b3f%7C0%7C0%7C637720769257039520%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zud6LbldoAHWWD8jFbsR%2Fj2E7qBILo27%2BYeICiaRNo4%3D&reserved=0> -- Dipl. Ing. Stefan Overkamp Laakmannsbusch 44, 42555 Velbert tel.: 0177 / 79 76 159 overk...@posteo.de<mailto:overk...@posteo.de>
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
