This https://developers.arcgis.com/rest/services-reference/enterprise/query-feature-service-layer/ contains every possible url param that can be sent to a feature service. When creating a pass-through CDF provider certain params need to be supported at the SQL database level before geojson data is handed back to Koop/CDF. I need to make sure each one works and implement additional DuckDB logic if necessary.
✔️ Supported:
wheregeometrygeometryTypespatialReloutFieldsreturnGeometryreturnDistinctValuesreturnIdsOnly - works but needs to be optimized for very large datasetsreturnCountOnly - works but need to make it works in conjuction with a sql where queryorderByFieldsresultOffsetresultRecordCountf
TODO - testing/implementing:
objectIds - this should work but need to testinSR - should we support projections with duckDB/koop?relationParam - I think this should remain unsupported since it doesn't work on Enterprise hosted feature servicestime - should we support datetime queries?distance and units - need to test these work or not. Koop may already handle units but not distancemaxAllowableOffset - might already be handled by koop but need to testgeometryPrecision - might already be handled by koop but need to testdefaultSRoutSRhavingClausegdbVersionreturnExtentOnly - support with ST_Extent or St_Intersects_Extent or ST_WithingroupByFieldsForStatisticsoutStatisticsreturnZreturnMmultipatchOptionquantizationParametersreturnCentroidresultTypehistoricMomentreturnTrueCurvessqlFormatreturnExceededLimitFeaturesdatumTransformationtimeReferenceUnknownClientreturnEnvelope
This https://developers.arcgis.com/rest/services-reference/enterprise/query-feature-service-layer/ contains every possible url param that can be sent to a feature service. When creating a pass-through CDF provider certain params need to be supported at the SQL database level before geojson data is handed back to Koop/CDF. I need to make sure each one works and implement additional DuckDB logic if necessary.
✔️ Supported:
wheregeometrygeometryTypespatialReloutFieldsreturnGeometryreturnDistinctValuesreturnIdsOnly- works but needs to be optimized for very large datasetsreturnCountOnly- works but need to make it works in conjuction with a sql where queryorderByFieldsresultOffsetresultRecordCountfTODO - testing/implementing:
objectIds- this should work but need to testinSR- should we support projections with duckDB/koop?relationParam- I think this should remain unsupported since it doesn't work on Enterprise hosted feature servicestime- should we support datetime queries?distanceandunits- need to test these work or not. Koop may already handle units but not distancemaxAllowableOffset- might already be handled by koop but need to testgeometryPrecision- might already be handled by koop but need to testdefaultSRoutSRhavingClausegdbVersionreturnExtentOnly- support withST_ExtentorSt_Intersects_ExtentorST_WithingroupByFieldsForStatisticsoutStatisticsreturnZreturnMmultipatchOptionquantizationParametersreturnCentroidresultTypehistoricMomentreturnTrueCurvessqlFormatreturnExceededLimitFeaturesdatumTransformationtimeReferenceUnknownClientreturnEnvelope