Why only one feature returned in REST query (expected 80)

TimWhiteaker — Wed, 31 Jul 2024 15:48:16 GMT

I'm querying the NWM streamflow forecast layer from the Living Atlas. It has 80 time steps, so each feature (e.g., station_id=1620851) should be present 80 times. However, only one feature is returned from the query below. How do I get all 80 features?

https://livefeeds2.arcgis.com/arcgis/rest/services/NFIE/NationalWaterModel_Medium/MapServer/0/query?where=egdb.dbo.LargeScale_v2.station_id=1620851&outFields=*&returnGeometry=false&orderByFields=egdb.dbo.medium_term_current.timevalue&resultRecordCount=80&f=pjson

Re: Why only one feature returned in REST query (expected 80)

TimWhiteaker — Thu, 05 Sep 2024 16:59:44 GMT

It works if I include time=: and timeRelation=esriTimeRelationOverlaps. The colon is a delimiter. I could enter 0:1111111111111111111111111 for time zero and some time waaaaay in the future, to make sure I get all values in the dataset, but I found the delimiter by itself was enough to make the query work. Note that in an update to the server in the coming months, the colon delimiter should be replaced with a comma delimiter.

https://livefeeds2.arcgis.com/arcgis/rest/services/NFIE/NationalWaterModel_Medium/MapServer/0/query?where=egdb.dbo.LargeScale_v2.station_id=1620851&time=:&timeRelation=esriTimeRelationOverlaps&outFields=*&returnGeometry=false&returnTrueCurves=false&orderByFields=egdb.dbo.medium_term_current.timevalue&returnDistinctValues=false&resultRecordCount=80&f=html

Gonzalo Espinoza at Esri deserves credit for providing me with this solution.

topic Why only one feature returned in REST query (expected 80) in ArcGIS REST APIs and Services Questions

Why only one feature returned in REST query (expected 80)

Re: Why only one feature returned in REST query (expected 80)