Activity

1. esgn

   added this to the v0.10.x Refactor MCP tools to improve reliability on the client side milestone on Apr 8, 2026
2. esgn

   added the

   Task

   issue type on Apr 8, 2026
3. esgn

   self-assigned this

   on Apr 10, 2026
4. esgn

   assigned

   mborne

   on Apr 28, 2026
5. esgn

   added

   refactoringRethink code architectureRethink code architecture

   on Apr 29, 2026
6. esgn

   added sub-issues on Jun 13, 2026

   • Add geometry metadata in gpf_wfs_get_features response #136
   • gpf_wfs_get_features => add option to retrieve a transformed geometry #137
   • gpf_wfs_get_features => intersects_feature when typename === intersects_feature_typename #53
   • Study alignment of the gpf_wfs_get_features filtering language with OGC API Features / CQL2 Basic #71
   • gpf_wfs_get_features - why rejecting geometry in select? #82
   • gpf_wfs_get_features change result_type=hits schema #107
7. esgn commented on Jun 24, 2026

   

   esgn

   on Jun 24, 2026

   Last edited by LionelZoubritzky-IGN

   MemberAuthor

   More actions

   @mborne have a look here ;)

   Current status

   • Select attribute
     • select => does not accept geometry field for now gpf_wfs_get_features - why rejecting geometry in select? #82
   • Attribute filter
     • where with home-made syntax (not standard at all)
   • Spatial filter
     • bbox_filter
     • intersects_point_filter
     • dwithin_point_filter => intersect_point_filter is dwithin_point_filter with distance == 0 ?
     • travel_time_filter
     • intersects_feature_filter => uses feature_ref + gpf_wfs_get_features => intersects_feature when typename === intersects_feature_typename #53
   • Order by
     • order_by : list with asc or desc
   • Limit
     • limit => pagination ?
   • Result Type
     • results => returns a featureCollection without any geometry (geometry: null) but with feature_reference. pagination ?
     • hits => gpf_wfs_get_features change result_type=hits schema #107
       • With hits the following parameters are useless: limit, order_by, select
     • http_get_url => Linking MCP geocontext and MCP carto : in search of the best solution #154 has settled the score for the URL schema. To be implemented.
     • http_post_request => To remove or comment. Not necessary.

   Result type refactoring

   result_type refactoring

   • Create a gpf_wfs_count_features (naming to be discussed) to replace the hits option of result_type. This tool will only support the parameters compatible with the hits operation => attribute filter and spatial filter => TODO make an issue
   • http_get_url : We could return a data_url which would be the stateless WFS proxy URL we were discussing in here Linking MCP geocontext and MCP carto : in search of the best solution #154 in each response.
   • http_get_url : The LLM might need to ask just for the URL and not the full response. So what should we do ? Another tool like gpf_wfs_build_get_features_request ?

   Spatial filters

   Question : are they really exclusive ? I tend to think it's easier for now.

   intersects_feature_filter refactoring

   • Spatial feature neighbour_of for gpf_wfs_get_features => intersects_feature when typename === intersects_feature_typename #53 ? Only take a feature id as input.

   intersects_point_filter refactoring

   • dwithin_point_filter with distance 0 could be a replacement

   Attribute filter refactoring

   • is_not_null should be added to the list
   • We could stick to CQL2 operators (=, >=, etc.)
   • We could support OR instead of only AND but that might prove costly ...

   limit refactoring

   • Is limit really useful for the LLM ? Yes it will be useful for TOP N query for example, for testing on a limited subset the WFS query
   • limit is problematic for mcp-carto => To be dealt within the tool description ?
   • gpf_wfs_get_features will not return more than 5000 features to the LLM. 5000 features is already preposterous
   • Still some brain to be spent here ...
8. LionelZoubritzky-IGN

   added a sub-issue on Jul 3, 2026

   • Remove result_type field of GetFeatures(ById) #167
9. esgn commented on Oct 2, 2026

   

   esgn

   on Oct 2, 2026

   MemberAuthor

   More actions

   Remaining work

   • gpf_wfs_get_features => intersects_feature when typename === intersects_feature_typename #53: intersects_feature_filter on the same typename (the neighbour_of idea). A guard currently rejects it and points to gpf_get_feature_by_id, even when intersection_area is requested, which by-id does not support.
   • Add an is_not_null operator to where (current operators: eq, ne, lt, lte, gt, gte, in, is_null).
   • Decide whether where should use CQL2 operators (=, >=, ...) and support OR in addition to AND.
   • Spatial filters: confirm that they stay mutually exclusive, and decide whether dwithin_point_filter with a distance of 0 replaces intersects_point_filter.
   • limit: no pagination yet (default 100, maximum 5000); decide whether one is needed.