Hi,
Ok, “name” seems to be accepted in cql_filter and json output. Maybe there is still an issue (or something to know) with the GML output as explained here wfs - GeoServer DescribeFeatureType response missing attribute for GML only - Geographic Information Systems Stack Exchange<https://gis.stackexchange.com/questions/388394/geoserver-describefeaturetype-response-missing-attribute-for-gml-only>
-Jukka Rahkonen-
Lähettäjä: Peter Smythe <gs...@sm...>
Lähetetty: maanantai 12. helmikuuta 2024 13.58
Vastaanottaja: Rahkonen Jukka <juk...@ma...>
Kopio: wam...@po...; geoserver-devel <geo...@li...>; Ian Turton <ijt...@gm...>; Geo...@li...
Aihe: Re: [Geoserver-users] [Geoserver-devel] trouble with cql_filter
Hi Jukka
Repeating the test on WFS 2.0.0 on layer sf:bugsites:
[cid:image001.png@01DA5DBE.BA59AEE0]
http://localhost:8080/geoserver/ows?service=WFS&version=2.0.0&request=GetFeature&typenames=sf:bugsites&outputFormat=json&cql_filter=<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/0NV-Um8KXJPAnE3ImFnuHnQVvdFjaBiOjtR4RYe2R6wVzYQ99xiygdSW3Nfq9wjTd73HT-cpw4ezl9DVA4uqvhvagQuXoBwzD6UrxKD-aSsKbk1-S9jSlQI8t6tyZJZg5L1USbvB_wS_r9ijelZIrgtcO8SfBkgd80uhkkuQtaa2f5Jux1EzPeIb7CzcV2GKe_HSijsB9rEIyq39wMqRgEf-4J791cAKTjAA1_dljisYliHiUrqzd5fbM_p1JrZff6fIKt7slrcxNxUkrnSRL3nDQRVByhX_pFLUp67aBnuEL8ihOQ76BnHvkFiHDk01rnLq4ZfWrquIvksEA6BVmvHIWxYm4Uy3wIr0EeKSfCsDlcLu3nyygKC2wLcn9mMDserbVhf4doG39oAaXg2Wa7-pAg7Sa3STD9jVMNllLp439HnwUqiliyBU33_Tcs3xE71K8gZnVSUPAE3XDSsVaLaAZSfu-6a4UefBcnb8d8gHaAkrTIJp9CL9PXc2suk>name+IN+('Beetle%20site')
also appears to work just fine:
[cid:image002.png@01DA5DBE.BA59AEE0]
Peter
GeoServer PSC
AWS Solutions Architect
https://github.com/petersmythe<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/Mxwp4DQkffIiHvWlRMrwW40g9y1wTCPGLtmLrg1BdiTbgz_2c1cNaKm2TkqczBa_1rHP37_o30B_OtM-UYPIKeeCiGhRJ8IqcAHbwIP5Ktxe5GCdPBmDTWHa2nvsty0wcAA4WidqPUvW1n-8dUKGWeNdo5KYHCq1h8sg-thevA0MFxKvKuca3ew7SbVtMvSi5-_3Xd4ahPoCqXifvNgv1rQqv-L7HB0-bhGSqe4j5eZDb52IfYDBimW-mWryLat5N_hsiK1C7HIqKU3J4sCIP59B_epWvXc5Ff_em4c>
On Mon, 12 Feb 2024 at 13:22, Rahkonen Jukka <juk...@ma...<mailto:juk...@ma...>> wrote:
Hi,
Please try with WFS 2.0, I think that the name thing is connected to GML 3.x versions.
-Jukka Rahkonen-
Lähettäjä: Peter Smythe <gs...@sm...<mailto:gs...@sm...>>
Lähetetty: maanantai 12. helmikuuta 2024 13.16
Vastaanottaja: Ian Turton <ijt...@gm...<mailto:ijt...@gm...>>
Kopio: wam...@po...<mailto:wam...@po...>; geoserver-devel <geo...@li...<mailto:geo...@li...>>; Geo...@li...<mailto:Geo...@li...>
Aihe: Re: [Geoserver-users] [Geoserver-devel] trouble with cql_filter
Thanks Ian
I checked, `name` does not appear to suffer from the same problem as `id`:
[cid:image004.png@01DA5DBE.BA59AEE0]
http://localhost:8080/geoserver/ows?service=WFS&version=1.0.0&request=GetFeature&typeNames=topp:states&outputFormat=json&cql_filter=name+IN+('Washington<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/QBI6eUuCMyuHxguVvxUYTM7pyfEN3ZcjAAqgO8p51yPfxg35cntT5ErQojn1bZK7IspHN-qqsAiogdU3tome_jPh6tL_FTmYfeMLbgVjU2JNiTPMiDcg3pqnWkqbfgIvgd5sA2WiWCcAUnALPtqc5sTPXurE2niFrlhSisVfuQ_ybV_PoO-r5hnF1TULIBnNDya_HptOgwuIilLaWMFg2cN8ApxkflwHXApI8mUxZWen7eaH1RZ3YwP2wxfa142fnLVeW3WnFxaryNoTWhWsByEsw09Vsf-BYV_UGorWtAdKYKF3Zu_CKIUqfWpzj-cHY1AxPmMuZFGDt8gpWdkuyPuvzNrZ92cdgbnhaghhSMKeFoizxGk4hOtHBhs4P8PmE2_nuqVjth_B40vEvPY3_xtuVXlulw7r3-E-58FlG6cpDLkrJYnRycoMgS7DWcFvB_uWR06LVIwbmrqdqJ1v48ck8A_Tx1wvKS1tbCU4pxs-J2kNH9dRklpWNHBSqxJOlJw6yf31lkXWXmm1BhRLmKT6HR1Mvv505MmTE9wOsSiV>') returns the 1 record, as expected.
[cid:image005.png@01DA5DBE.BA59AEE0]
As a result, I have only included `id` in the documentation warning:
https://github.com/geoserver/geoserver/pull/7414<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/rpLLV5L2ToDw5MmVZ-adbbfWBweVtakJiE4jUqOkZnzd7529RwZdmdRATchc5u1USdo85CWClKdXETro_hQYxZyA0IdhgrD0OosueMbl84QwNNMQGqmAH2N1GIJOay6PS74w9CfNI4PX-W4hSLrCj8rqTU42vqeB8XLj68xe9niJ39oLK-6vVSLo5nROYFb94GHAZuXQzkdk64z77V1-YEMkL3BrsNWYIRcRFyYEjCXXongjvBPeUbMmIC-7Lei1tC4qJyNfCfM-WPXuXl1GCCGwcEOSbiGyIv-GNk8Je6-Vi7kW3S4XLfJ2T0bK9ZMB1oyf7nw>
Peter
GeoServer PSC
AWS Solutions Architect
https://github.com/petersmythe<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/NpKy4Xyz4cZEnf0TYntmglNbA3dILIwJQk_iIj5E6cTErg7ZcmLiSjKJA2fraqeupNuJ6PsikVkB7wDR5cIitsM17vTA63NW_op_1o7_K3SQNQJujenTNHNUsrrk1BULhg34IZgI5QUdQiLmtroNc2niGdDt56m_rxe0rXAxxLFuB6v834DrQmK9-Mpm4nEBvox3fD9zY5kn32GuF_ZINQ_fApunwE2wQUZVvTfzYZK2W7VICyNQD4IQWQYDX9tzLmdwhdP1MyaPBvAZK4GZ5b9RHgsS1pAFwDQFxQ8>
On Sun, 11 Feb 2024 at 14:01, Ian Turton <ijt...@gm...<mailto:ijt...@gm...>> wrote:
I believe that `id` has always been special for WFS data sets (along with `name`) as the GML spec specifies them so they are automagically removed from any features that are returned
Ian
On Sun, 11 Feb 2024 at 07:59, Peter Smythe <gs...@sm...<mailto:gs...@sm...>> wrote:
My observations and recommendation:
`id` appears to be interpreted as an internal keyword for FeatureID and not a property/attribute/column name. Many datasets will use `id` as a column name and might get tripped up by this.
Example, using the topp:states layer in the default data:
http://localhost:8080/geoserver/ows?service=WFS&version=1.0.0&request=GetFeature&typeNames=topp:states&outputFormat=json<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/0-DE7TyxLeudnucGi_GhZ8EVe5mqd1I_0MkqidJH9RwOukdAho13sAsNRae6xJc8KSvMsLinyvsBcpx2J9S5WBGzdRV3B5vPxPtlSRkoZRhI6aM5zQMAsD1qimINCQdU6IlGG56siKEHcs2LNA27c4UIPVtrP6PaOei1TKu_YVbWnv63PlDKj76IUsfXghaAVebLJmGnK8Nz8aZf9nZa5ZfARkJAM6jPKeFQ6Lj6sOF8144Ng97EO-sdCROYlqQh637zlFoOt-s5kc_9CiycdRHU-_7Mq0mkXuaHpQFofdHUSGiZAHa4AmlpdnNWs4mbU6crzuaB39r7B0TMHBuUbM6-noqBii5t22sSueUJvXDwO3Q3FQMfe6UC6fId4nU7pqWAuwf9bcheWXKaH7LjaCzm5a55YBWZ2JA5ZwNGLWYgYJETb2gYRjKex9pVjK5ZuR_TnCfrRekAdHq09izern1Ndv3_tMp6DA>
[cid:image006.png@01DA5DBE.BA59AEE0]
Here, `id` is the FeatureID = `states.49` and thus http://localhost:8080/geoserver/ows?service=WFS&version=1.0.0&request=GetFeature&typeNames=topp:states&outputFormat=json&cql_filter=id+IN+('states.49<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/NO0b6xrHfaTvabJ6mKU1NGgKqjCybVN1vpKP6trKlPO1KNQ-TrYC1vb5otvQUrDMwyrH-n2GlSOHwnINwjEuqNZckrqdoWjQCKVhyt8sQT2UrPuazZ2Jy5ICAU6BSyYtdc1RtLkGH3754xifLhka6cSvce-l6d-Z_suMeh16whLUcDSok8IQD4aFQ8rkXUK6ymceBqc-8DXU-mEmYb_H-1eaQKbRl-In-SkyqatCyLKEZU0NfwQ5LPz31OuZP_18XYa3pqKjMLOuwSfvtv6js14ijJsSPEbXjKqPi4ejgE3vZgks_AvVUZMl5qar4eB_qch_WUmvWdkMJRl17DWZKqcBuRu8CoPcLMUmL3lgoqSqu0e4HEOKs6PtTRR0G-gkqJZLmCiD1A6ADizGWR7V5kMWcA4fcKVzSQPmRgWLzeaWVxEcHC6Xql1Y5jPRQ1rVnw5SNxCXTKWWi5nPxCK6iDDqXnd8G5aAoWjUi6qPLsNEhaMrRA8qKg3eVvAYPORTUmExTdDaGwhYmuAd8Bl3in0wcFdAV_e1fuc_fVSX>') will return this one result.
However, if we customise the attributes and change attribute `STATE_NAME` to `id`, simulating a non-index database column called `id`:
[cid:image007.png@01DA5DBE.BA59AEE0]
then http://localhost:8080/geoserver/ows?service=WFS&version=1.0.0&request=GetFeature&typeNames=topp:states&outputFormat=json&cql_filter=id+IN+('Washington<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/s66c-QwpjdEvMZZLKDCqh3Vt6zVkG1jYJKJnUHqukOKrxSB2DUsjuVE6MDWD5W2RvEAcUrNP5k5bUTIeyFQFpd5aSS8w0g76SE9y8lToZZh_NRs-ykKTZg-CQrzjXb9QsNvKX_6gNa4-pkH6sYVyypeW1JSfBgqT7lXTPzNvnD9WYNk9hn235a4Wy3uJUPvB2vQJi8oqAkLWTawuMG-C10HmQc30kHgGbYUZ9l2UvFuY6dxBoM_I6KrLN49EIJvaQP4llXwrsIFsandAYYkNC7WztYpn1Q1MQZVvCJRE7bsxZRW5JSWjUhJ7DTg2nqtm8-4DWdYTwPOTzFo6f41BN6dDO2NZQmZGhtVZMZuju-lT1kZwXMa2oJnmgl_0jMMVw3d-KveIRCzOdFpVabkNZehtJfMk5alSHe-1GIC6F0ZxDKQw7Znl6sSjyGk43xcighQ-K6q3dkjjSUD0TpiCip_VTV1e9nq4yU-PrXPuzFxpaxEYMAfGfup4rtNwgPPbuH9blUbbk8jjnzW-Qk2ce9HNHm1zQeWfOvUr0u_e3w>') will not match the record, as `id` is being used as the FeatureID. In order to use the column `id`, we need to put it in double quotes:
http://localhost:8080/geoserver/ows?service=WFS&version=1.0.0&request=GetFeature&typeNames=topp:states&outputFormat=json&cql_filter=<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/zrrtG6I3Y4bwSGD6YZKAoUs6k82cMdV2TOuGq6-OA-uLAKTR0zqkukdQVJHsE-IZd2Uoor6oAB-vWPMNU6d2bkUbLBmkBhwcfedB6XpUe7RCkB77qr7gQbkDtMuLR_JYhKQHIAD_S1QMgAQr15OCi6xm6MExLDIIofq0_y4tCDIIHQmsztds5wFuaojxvLBRBl6bp8EeFmNvXMtseX8lGwcMVsNEJxT4WfbcvrJeduedPPPTEyl9Y90T5aSCOkv7yGma7bk3c451Uxl7c7HDzzSk2lQxgnZ46AkXDZc8UOfqMEhEYcTjMZa5UBWUIB4B2mFqoMzHvz9JbcnAIeoresWT7dT5zieXgDQp-9a31koHq5Jp2wv6k0BbT7AXWH4vjYOkNYiTVTmDwZyngBnnd7wQWmgzaYREiIB0PFo1Gen9HL9XNHTQbXgLftfehHWlmcF9Br_ODMNGibUsadYMWCez3U7KY_drzTwr5clohV-ebEI3nMPkexFKD_tZ7Ic>"id"+IN+('Washington'), and this then works, as per the https://gis.stackexchange.com/questions/373005/geoserver-wms-cql-filter-id-xxx-works-but-id-in-xxx-does-not<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/NsaepbDBaqwRbaYvtHCE-_fT8TCs4q3QDXbfMFdlsfofY8rWqs2K3vBzXgU6HPDGDgPLVakclcYSeTtFh7X4lMimnlCwLvXQoDh5ISw3jyJsuI_ki_dflxhgyjLxhRXKPXNnQZ8hXYVeNtH4znctai16Ad3p0JgId2MWr1mabpVysl_sg_cWV1JKzcU_iKvZuCK5ORs23frIi-Ht0PD-tG2pM5w6S3ULqvNCR84mD4ODCa1rVOrLTZCV-Q6TSLhS4_NKdGJcDodKFT0MmKg55HjFn8YnMse0qLnkPx1ABk7RovvUn0Qrij4AJGY5rebxZ84kXvXoSdu_aI4DEqettddxh6vNsp_FJ6L04xuj6Ov1q_BrzoE4O0h4xyXuFGvCZd2_b5W189MnV1YirTg> recommendation.
Simply using the IN(filter) format: http://localhost:8080/geoserver/ows?service=WFS&version=1.0.0&request=GetFeature&typeNames=topp:states&outputFormat=json&cql_filter=IN+('Washington')<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/9Ct27NMLVDoOMP2aXz1OptYfdM-MkbtOzhZxXpg4Xw2ANQz8o2Al8vBI1iMCATWiqCSMXKJU1J02LbTw3YBqsAstkf7LZsYcMPGSsxRn0JXFaslvgcu6sJCwiEAwhHgB2yn9ktiAy3EnNmYxFL26-UOKv54kplQBzp53ZLfZXpwAktFUgIO7Tz_Nk5RWXTe__zNR2YF9cBVhGUg0Tv8Mdai7z4HGyEV-OfWlVluo-R7sfdskk6nOJXkTNyHn51T_W9z25J2-J7NAwWvcDw8kWffIolnStZ7UcFTiomFXIKm9RJ7YfZNsj1a6iCStUpHyxJWtbRh9ZHwlNqgU8kTzw68b_f5gARmch4eBE6Qh87zsx79Ts6ITOkzJP37W54B5ZIU15Ih7Wb_TPWxqU_fOWZPGex6MTyb57ZZpDXnzC8wfunzpnwqQ3asb2utoiYfmJXEPKINwN9h6AYCxLnXdd1gJzGa3jDN9IpcTplp2xXWlYcazoowYkPzxIVLjE8KD7BNuYlqnOrd_Oks_FO1M59Zv5zIjPd0XJJ4ZXVXrDDvtoMXrokU>, implies the FeatureID `id` and does not return any data.
The XML equivalent: http://localhost:8080/geoserver/wfs?request=GetFeature&version=1.0.0&typeName=topp:states&outputFormat=json&FILTER=%3CFilter%20xmlns%3D%22http%3A%2F%2Fwww.opengis.net%2Fogc%22%3E%3CPropertyIsEqualTo%3E%3CPropertyName%3Eid%3C%2FPropertyName%3E%3CLiteral%3EWashington%3C%2FLiteral%3E%3C%2FPropertyIsEqualTo%3E%3C%2FFilter%3E<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/5KFQMiTHKU777adJyF5FdiJc4aYTc6TS97oRvf9iAxzIUBMCNf85_qgUL4u2O7sEULwzhcq5MG7uH8AYrzGVNOMldwbYgaiERNu8htFsVtrJcPRxi08rH5KAGKp9EfhBYYvqXKJLZIHJ_P96snQfYazfsK9DRQcHwP0sc_G-kQrgV8m7pKrwLAMhGpAofcoq6LWHtrHpuCdkmsG5hVSgUfFYxaI01Rj7SYDCXtXGYomCOuaHt6X_q9q--cLhvd4LdYrWv_jFvZbFPaBqr_XRgsqLExqmEZI7jvBh8Y_mvn0ZJ6siSLVdwUtHYf2ywbxYXR6Tc8J2eK7q7k1hARhvcflBOGVKS4yaLmb5MfgMDVx1Oc20knmX_ao3enFmElWRPxMs7z6Y_4aOJrA11deV5hnYAccz6HWSrR3f7XIWlbJEdZoe9uUFzjm7cxsvdDLvt4IZYB75QnjKOVCAQcQAueeml5PF8BnHBy3kiDajjG3FF4lGwMp2Yeg30ifZDwc3pQlOlLB18NvooEPkQ_OhmDG1jYYb3R_qAhVvKT2sbXYrakKlLbEchW5Ixckr_X-K2gMbSBGEvqtBBE6aW587zKmKQJw_ibzEhsaok81R_10esUDQDomPtsUbyUJLd1I85LAWpb-jnmTIHj_y-gfidWxIFNXjyIrRn3Sp9J9wiosXp0toURFqV4qSU6YVqr_6q-DDO9CCxcF08LJHW73ZeogTcH2sbosEcMKF_PpVOpZDX962lxdT4LJncs4wrTHt_g54hOy2dGzq5WcFlOOCCdESUVJZFoCpujhDGraQcuzpMfLjZxrrQWY2mA> (which encodes this filter, for those of us who can't easily URL-decode in our heads:
<Filter xmlns="http://www.opengis.net/ogc<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/cQkT9J4mHW8Kdn-XX_vGdivqGdA-mwYa9VAD49d-KMJkXyTivu3qhbGzEu0Z6H_7W14DNoLYog_0lD4mo1F95OFYe6xtWzjRLTu8pjg4En7EURhn3L9uJdqAzu8-Iao-zijeAZldZt3SThC3u9SI591uu0ZOUp8-dwKof3c_9URDM9FxopbTJPn0TcqlnkdlX2IpLs-TK-lPU_08XFc_9RPK2-71RTPB3_cpBIUT--rO99NwHpOrmDaeHlpqZa2yG1M4KV4KCJETbNR8RbRn25nOMtxZU_4KwA>">
<PropertyIsEqualTo>
<PropertyName>id</PropertyName>
<Literal>Washington</Literal>
</PropertyIsEqualTo>
</Filter>
)
does correctly use the attribute `id`, as expected, and not the FeatureID `id`.
According to the both https://docs.geoserver.org/latest/en/user/filter/ecql_reference.html<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/2XhlCOGQuXN3CYCv6i2V1pDzupPSRXdEMwnBR5QIDEWFd-EPpKWGgRt2SSK--F7AW-p5yj4PGL3Og7tfbQvzq-CpJub9y_G7W8c5zHsLoee2OpnPawr6bm77Ta2csgqLop_63nEP2l4to809akQJNfXgh_eB1Gu2jekNejU_98-Cr1nNJ0t3eIlYhe6snaytxnGyq03eONqJX2-2l7cp19v6vgjMThUopOUKQ2wYtjjnWodonv4P-nix5MIGKkZ3hrO8Dn2YZPCyV72VOsGWk--9737Q4nS_qFJj4rogfS8eWvmk00MTCRLr7uPr2dJESEGnVlphGnKsp0_v7QsAQMo_lG3Oza_BiqOn> and https://docs.geoserver.org/latest/en/user/tutorials/cql/cql_tutorial.html<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/rCSP7iTy_hgLkyQPhDcijOqAboai1I5K9xzWwplBLSCgnb9queJPcqKybSULbk9WW5ZWJNswjklhLkK9xf6PERAcc80UXKvm3CqXmUhbGc5fNkc-jnBCkLyDqSChKZtz3OQASff4TlLnpT6UjdFkJN-Co9SF1euxWddAw5AzgflYCu_R8czqRRIyP4hqhuQleziM3q90RdSqTL3yeEL--UiPIh4vrEG9oSH8v7w1pWLp0SZwrOH8J9s3xMvEzl8vfY4qMo5UICFj9GnlPXRfgK0JeNU3Z3ubehNCWCRDX4cwjFLAVaDa3fgHbiCGhoKglyPElVdscpRqQgH0ysZwUjpaQcZ8DWESGjRuAVZaW0if-w>,
[cid:image008.png@01DA5DBE.BA59AEE0]
and
[cid:image009.png@01DA5DBE.BA59AEE0]
it appears as though we should be able to filter on attribute `id` = Washington rather than FeatureID `id` = states.49
If this is a bug (developers?), I wonder how many systems will break when it is fixed, or whether the best way forward is to simply document that an attribute `id` is special and needs to be quoted thus: "id". Let me know to fix the documentation.
Peter
GeoServer PSC
AWS Solutions Architect
https://github.com/petersmythe<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/aRem_WHLXTzUhXUNwYbKbm1h1d3RPwswXQxXiylBYViDkUvI19TKvQWaz4dN2AX_ItCw2ESujzYOFbDmyZU8qrZcR0Qyh5ljCqu26xr-IG1Y-8oF-_2ljQLoQRNxCXGt-bRDcRC71tTvAtpdBlGeNqWns9_s0gsvXkqVoVKbvxYXO3BsrVYXOhrkjfqlmcZbQDD6mZMeb6F0QUHCLAeblv4yOva3akBeSZd_n8raXfayICuyzZxSy7sgqH0dGifYkkhUbUmsxrtz9TFTO-Lw-JbJaCkuKN6amNO2I-8>
On Sat, 10 Feb 2024 at 21:35, Jody Garnett <jod...@gm...<mailto:jod...@gm...>> wrote:
Huh, I wonder if that is even supported …
The FeatureID check is done different by WFS, and does not always integrate well with functions and so on. There is a configuration option to both use primary keys to generate FeatureID and also make available as an attribute for use with functions.
Are you comfortable trying the same request with an XML query? …to see if it is a problem with the data store, or if it is a problem with CQL constructing a query …
Reading
https://docs.geoserver.org/main/en/user/filter/ecql_reference.html<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/Gg7Et39_60SaAmSH6kelaUtkt1g48FWCVkMFF4fHjKFQ_K3TDSeuJllqMGFtSLd8Z92d-_a2uDiaGwTG4IKsA3pfTmwF1FaeipvwwZ3UbZnh1I0FCrdkG44gDzG7YN3nrepJIEICNBWKb9_Q8YvQknZ7RQjSh964TZ-EJpuzIL9GBJtFP1nn7qLI7hkLOsZYRBjZO649RkJoBns3aFYAFRhmkT3Mq7E5mCVGz2d_SE0r3F44QZeuAnCo6EVv-ACYKGK1xWDnzk_a3jXQudlgnHjmNXoJ2cmU5hSK47L10Eq8ffC4vv84Sw2N8EVRk3EHT77xv1B-NbU7oZqEO7Y6Qi5YIr8Q7pyW_w> you may wish to try:
in('R403139')
Assuming R403139 is a feature identifier.
--
Jody Garnett
On Sat, Feb 10, 2024 at 6:16 AM <wam...@po...<mailto:wam...@po...>> wrote:
Hi,
i'm trying to use a cql_filter on a feature but something is strange.
cql_filter: "id = 'R403139'" is working fine. i'll get only this feature.
but "id in('R403139')" does not give any result (without error messages).
i need a list, because later on there more features will be dynanical selected. e.g. "id in('R403139', 'R1719140')"
What am i doing wrong?
btw: i may add geoserver log file if needed.
--
My projects:
OSM Boundaries Map (*) - not completed
OSM Software Watchlist<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/dTEd2x7zFnSvq2aaJS-GjVXvaEeC8QQEaUaXpFbGB3hjrn-tfOWYeHYxlBhcvu1nASz9jT6NRLvmCsMv9f_KQXLjeEYeAMP9yvHB4iwBn2LEkeRIjzi024ILT9TZGJ63HckpqCfZQMVTQHcFS1bzXQwiWM8_1OKwpXDAjSbA4MS2NB9z1sb5AtZq-ZFAbOM_hveq74YSQo3hsd2i4d3qI_iQEMUBirYhu0bAN5O07jzOAyZSCOlwnbTCRr9ZDGdG2YRzMzuaoFwS4HfRgLNesstr3NrpVJn4IkzJXzHdLL5M5yuC3T7lE1F9WQP8ndeMUp-uzg>
OSM Emergency Map<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/huUb8a-1gpyJumX3kQR1r18RxLGDMix1rEKLCSNBTp9WRHavstSnCjI8-YwYi4UmHlQ9pCYLQ8VBt83JIQ2k9G2eo2HWkGibwiElrvKMmoXClcx7dYwnndSmulikLYiveMWoOR9D3nxTP_DvIUGa-Mlb3LxQXSL0EqHRm3H6lssPGhaGuWwH2AWSlqeRQWj3DgFBkiOIFsOaXseN_rm0686m7GNdeARtc17ylJ777iSKQfVSz8VtwatjW2tuoVPe-TpaAh_WDtohFFxwb5Q8bsYuM0yZ_t6sx6upKyG4F47hGPKuh6wBQMad4pU> (*)
OSM Healthcare Map<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/JZh63A1FTXj8bfUECBYPBqd7Aimj1N-Py5hsYwB0qYmPr-aDXi-DT43So-YK9RWDWFImAMCJwjZVBSGKJytwowBfgaaoHE0Xyi3vHj7m2pR2GhxARljJyXgLPgh1RZBWC63k6UQSjMk_pygvUG5kz2HpyLjuOEw9QDc35is_LYOxFKBCGFwyq1oarojHJsrENGOcJqBdEb_vYQ_MKZqDu6K2b4WGnBOs2V01yAvtQ726BPrqjm-Lmb5VHEyHaZMcLxOnOJX4Iy2ACau8TZhPuyu2RlyNfHmcCMSsoPc5ZnmB6JEO7D7FfWDQr6VP> (*)
OSM Postcode Map<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/IPRdVYa5D7tAoTVF33R5Lo6youkJvzyzuwSoPWV2Bv9oYweNl1HKwk_cgUtSp0PK2vei-LCLC2tdFnSDShWzkOyBCptIUGjHZgUByIcAuW6jIefc1ZVTZLxKMC_fwo6qYvcSDBJ193bQjN_VffhLblIzFMAYiPRntTPm7Pqm69Q4udM7cU6ddcB0kDeTINQJfL3SllyNf9oVdilr0zBvDWGSlsCzcVNwv9ZDYkHfAt0D8R2eaYnrru83CBwhzU02S9BDM2njNMeBXU_8ebZQBdxrJR2zqRRHi6_z89PjIhv2_0gnlCZXLSqpr4Q> (Germany)
*) Europe
_______________________________________________
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://fdfdfha.r.bh.d.sendibt3.com/tr/cl/A8CkADfEmuLFcXdHS_lc_CoXkEPL-NshhPOhhw2QJKVuktfuwD0ovHbJVzw3dB9Ojb09P_GlapyOrQ_wq3mM0dsBTNrrhMtb64tL3evANhD3rS-ulz3_LCQqya6HJ_UBpNC9yvt8lnz_lv5Gb1FmTo-3DjBURb4wa1Ft5B3pfUP0F0tF6H315TCin-c9uwC1YTVO-EPMqYVA9fo_SQXtLEnJ2ayLB4JUYEcUNZZ0ZRnPn26sX2E5hJ0v66-YbZqoa2X-u94ZwecRwLaR9riJ1FxX23FIvKCEtaLevg-XGlVH-xH6CK3Ca-eykSkkEQoNaQ>
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/XkR8EGcUzu-sc8QKJRp_i45mmxJrPkoodKEsySOViiT98p6BKCO0dqE5c3SMUTHx6KLd0hCope2w7hmtfgQah_LHKc1IZft7cE2_mP0cVy4EfuLEwWzq2XfyGBX8eiLvlgIE1VIl53Nf7M7HIGrA-hp2dqd44zk5MI70Zw1DZcxKDBMufxotf9gBZgt63yzbx5BBoP1hbVjBnYp38sbYMloqM7AQ9ScXxxRCHYyxwKGMvRCFbeb_WErzFDsDOzFUN6oPE8iuKdvPpb0sZkgbtEFkvbCbH2YDh0-nagjKpKEYQUX7oWdw27pzBYdayH5CQRkn>
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://fdfdfha.r.bh.d.sendibt3.com/tr/cl/wJWCRfg9hVCWVXTpR9YcSPjMcq3et_9opiaHHdQc91VqDaXoFESvSsbiyHhDNiw6s-td7VgsQQFplRC8CGKsgDZ-CULvcTi3_CEO5K6dwF4zhfwcJuss8M_V7G2K6_Wnh4cv_Km9pENiRnRZfGLeAmCwfKwAu2QPlj3mgXt7N_HvYvo4ce5vCt4-a6q5ejHkQQp-k9E0mVdBOTd05kl0lNn1itvwTPdxQVM41_QBTk7epU9bqmL1A5emMJEgCbIkbSKTnYHFSfcQeqI6hMktRtuXjCYSDSKFQRR4oWkV1BUTIHlwdvE1wFfj1h8qBRqtJxRZfjnL6p7RSO0VE1y-6JutVZXGD9YmxsCxBA4mL1sFsfZRq6BO98ilsShrdocYcXf90J6rKFyC4FgFh8jhzqmgCk3hAM4cFoI32U4J6ismduY>
Geo...@li...<mailto:Geo...@li...>
https://lists.sourceforge.net/lists/listinfo/geoserver-users<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/9jTGd709fuBDPY2xilI2RGE7HahVA2m5-ubdHo7KQfG_kMdckS8BCuq-mDLWeGQT3u82N-KHlb5Iw7fD5BL0Y6j-gZH-99sTPmd9i0gOg35qIkGOttDGa9b_fJfaVjYbUQB2O2dDL8q_f_B5Vh474WuDtb-RxIEucvTTrsZxiCdK3AGtVehSmijUjdt-dmmjqpAwk7R-4zfCNLq1IidcWK1r9HRAnjDelhUgSm1rCbvYMIuzv6ottFoAtbZgotzDkKM6buFM_3wRpNLqRPH1fvwC0vu7GESoZOMvkhWg1hpNJPWMHuWpqW2pIWdSQbdNEycTVSGSsM7lo3PPW8At>
_______________________________________________
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://fdfdfha.r.bh.d.sendibt3.com/tr/cl/3UmbCk-viFUGBkweup_c1XKGMARPbLDy60gntBuwN5k_GjIu3IGPTSVKd8tdXco0_56B88c3gT9p-Oe9zM6pBwx0VUptBYlk5uAyXTqYz8cdLqy4h7rw_1TclOPv5bbGN2aIIqOjMDButDSkL7iKaKhGBAGANCCfipJCNHTlZvTOKfCZKA738bH2A5OMJyrvTGO3RNUigrju2EuaL300whUdmKMgbEcs97CaTS3MVBpDFgVZy2x4v_j-hrypWztB55UvDhBrADl-mRgq-Prtm7B0u4tlqZtkbivdVnFsO39_uX_VVZb31ymhgyMHdJgjTw>
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/JJe3OHb50gwN2tHH0Gex7IAz9j7Lq_evjvvPrzaqCYCK4Rd6ls2F3xMtZmj8ILA5Cp0m133rlbUnnlmJaJokzW6VF2jMOss5chjNHE7GeGKGDyT8d0VCCO8j1P1N6E4x16_QGyU8lez2r0Dm6HPWqVYRzQfypG3ylCT7_iv9o5z86QsjWNS3ST5tbofn0oqxkk541FPvC0kU7A7Pxq51KZHAKo6I_j3GR4SRMUGk0aZH09sYVi8Jyn0GQF3hQ5lq3sF7pNqmY-cTfEgbPt7OoHLaA4XLV6MO0lythdnK9T3mMQzaNNnVa0_2CnhvaGnTQdIm>
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://fdfdfha.r.bh.d.sendibt3.com/tr/cl/odGTLbJ8Gjr62v-MxgL2Jg_3RXaAUdHE7sO0eLAZGeyhfrgxlFBRzWzTnMnn-VgzBnc8hiMZ3KS3B6mNCcJCj-ZuB8oS7EWPuzA21afDS5mwIHSEVGRLnjZAMTlwBVqkgKLboYO9oK9imCPsJvkcDUa0XKc_T4SAxHcwyz4vjrJ1TtqcarL2qW0VSmuBLJmXKfUzlUl8Yy7KSvxC45v8tE7vxF5ruagn7A283hdlM6eu1lnvp2dOM3UWYfNhUBUIRXbAie5a9W107v1g6j3cEvCpU_XcGtWfBx1MgVEnzGForoqygX450MQkgQcL4UF7h7WlKq39wZbvas9Lv5EmX3-mFQaPmXPTGM7UX60tCIC1Z762RGQldmW89ChA9vOXZMwiwXyCz4yYIcJuwUJtKgDMKvze-uqmRGu-qfXOZrWNfzY>
Geo...@li...<mailto:Geo...@li...>
https://lists.sourceforge.net/lists/listinfo/geoserver-users<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/K-Kytzot7habuUMGNaMhnDbx3QFT3w8Y03bhAnf3wDeksDv_qhrBnNRtLxnefzGeWOHToxYe4ZlWkeswMctL53h3KwS7SrZ0tTXUOe5W9xm84bEctA5W0-TM9BveKLvTn3V4IqblGMPEb3qcyOU0A0s3oBdF5gb4NopztJ-XlFRit0UpH4M4h8HHqwcGuY0eJK1rwByFM_q8z9gWfsbXspNNE-0k-F3Vthd9VxIRf18xGy9-Oapf3olfo6MmVy-JpK_pFZ1mBgCOzJOmz7CKP8U_rNjHzX4z_XBTUhL5JPh5hHCGbsX_q3NEps9N41O3tSQIPJ_FTrecLBTRmqVs>
_______________________________________________
Geoserver-devel mailing list
Geo...@li...<mailto:Geo...@li...>
https://lists.sourceforge.net/lists/listinfo/geoserver-devel<https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/3j9gAgV1eEMp7XXaRD2xO0sdAvIqIQsvc6inZCxEc2E9THty4oNfa9lmev9Fk-8GlKFCJrwqrkZVni99Hr_V6mTVvY6MRTOooCQahHieSTFljMcZvzd4VIxt7QS8LbtYzWtTg_0FTbN_55TfeVuOJvxIx2xOHlbSh7gjhNrV39D6pNQ0SFn5QO0r4go6bAxIM1aOKA-A_sHoAGgHDAC0Z3-rxKQPkB_-iK4JEdbepUC_7aRxCfjwuUh_f2X673qbof6IjOJc45pXI4chHdv5zkCo8ca7MSFo_nX-Ix17Lg61qUMnbs6Gf01QCAlIll6Tu9B-w_-1f-wtDHGqDYac>
--
Ian Turton
|
