Thank you so much. I copied the view statement from postgres to geoserver, set the identifier. And the problem was resolved in arcpro. Thank you so much!
Hi,
Instead of publishing a feature type directly from the store, use a sql view.
That way you can specify the ID column by selecting the column name as Identifier. You’ll be able to rename fields using sql AS keyword, perform joins, etc … All the power of SQL.
Have a look at this : https://docs.geoserver.org/master/en/user/data/database/sqlview.html
Good luck !
Envoyé à partir d’Outlook
De : Arjun Dongre via Geoserver-users <geoserver-users@anonymised.comrge.net>
Envoyé : 25 août 2021 10:27
À : geoserver-users@lists.sourceforge.net <geoserver-users@anonymised.comorge.net>
Objet : Re: [Geoserver-users] Geoserver ResourceId (rid) filter
Sorry, to specify, we are publishing a view from postgis. I don’t think you can set a “primary key” in a postgres view. I was assuming you could select the field in the geoserver layer settings.
On Wed, Aug 25, 2021 at 10:23 AM Arjun Dongre <adongre@anonymised.com> wrote:
This is exactly what is happening, how do I specify the unique id field?
On Wed, Aug 25, 2021 at 10:07 AM Olivier Gagnon <mcnolii@anonymised.com> wrote:
Hi,
Geoserver will generate a distinct ID for all features for you if you don’t specify the field to use as ID while using a sql view as source.
If you don’t specify it, Geoserver will generate an ID of this format : layerName.uid (ex: LayerName.fid-1e25e6bb_17b7379da69_-720a)
If you specify a field to represent the unique ID then the value of this field will be bound to each feature in this format : layerName.fieldValue (ex: layerName.1)
Hope this helps.
Good luck
Envoyé à partir d’Outlook
De : Arjun Dongre via Geoserver-users <geoserver-users@anonymised.com.sourceforge.net>
Envoyé : 25 août 2021 08:37
À : geoserver-users@lists.sourceforge.net <geoserver-users@anonymised.comorge.net>
Objet : [Geoserver-users] Geoserver ResourceId (rid) filter
Good morning,
Im running into an issue with ArcGIS Pro trying to retrieve WFS data through http post method. The program is trying to request data from our geoserver instance with a filter on rid:
fes:Filter
<fes:ResourceId rid=“{layer}.0”/>
</fes:Filter>
I see in the OGC 2.0 specifications that the server should specify a resource id for every feature.
Am I supposed to add this field myself? Is geoserver supposed to do it automatically? We are running 2.18.2. Is this fixed in layer versions?
Any guidance would be greatly appreciated. Thanks!
–
Arjun Dongre
Western EcoSystems Technology, Inc.
Environmental & Statistical Consultants
415 W. 17th St. Suite 200
Cheyenne, WY 82001
adongre@anonymised.com047…
www.west-inc.com
Follow WEST: Facebook, Twitter, Linked In, Join our Mailing list
CONFIDENTIALITY NOTICE: This message and any accompanying communications are covered by the Electronic Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient or an agent responsible for delivering the communication to the intended recipient, you are hereby notified that you have received this communication in error. Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Thank you.
P Please consider the environment before printing.
–
Arjun Dongre
Western EcoSystems Technology, Inc.
Environmental & Statistical Consultants
415 W. 17th St. Suite 200
Cheyenne, WY 82001
adongre@anonymised.com047…
www.west-inc.com
Follow WEST: Facebook, Twitter, Linked In, Join our Mailing list
CONFIDENTIALITY NOTICE: This message and any accompanying communications are covered by the Electronic Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient or an agent responsible for delivering the communication to the intended recipient, you are hereby notified that you have received this communication in error. Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Thank you.
P Please consider the environment before printing.
–
Arjun Dongre
Western EcoSystems Technology, Inc.
Environmental & Statistical Consultants
415 W. 17th St. Suite 200
Cheyenne, WY 82001
adongre@anonymised.com047…
www.west-inc.com
Follow WEST: Facebook, Twitter, Linked In, Join our Mailing list
CONFIDENTIALITY NOTICE: This message and any accompanying communications are covered by the Electronic Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient or an agent responsible for delivering the communication to the intended recipient, you are hereby notified that you have received this communication in error. Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Thank you.
P Please consider the environment before printing.
Western EcoSystems Technology, Inc.
Environmental & Statistical Consultants
415 W. 17th St. Suite 200
Cheyenne, WY 82001
CONFIDENTIALITY NOTICE: This message and any accompanying communications are covered by the Electronic Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient or an agent responsible for delivering the communication to the intended recipient, you are hereby notified that you have received this communication in error. Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. Thank you.
P Please consider the environment before printing.
