aws AGPS request type 5

[FVjr360]

I was requesting agps data with the thingy 91 board on aws. By default it fails to resolve (seems like it comes from validateWithType()) saying :

ERROR {"errors":[{"instancePath":"/types/4","schemaPath":"#/properties/types/items/anyOf/0/const","keyword":"const","params":{"allowedValue":1},"message":"must be equal to constant"},{"instancePath":"/types/4","schemaPath":"#/properties/types/items/anyOf/1/const","keyword":"const","params":{"allowedValue":2},"message":"must be equal to constant"},

I noticed that all the request examples were using the following message which does not include the type 5 (NRF_MODEM_GNSS_AGPS_NEQUICK_REQUEST).
_{
"mcc": {agpsMcc},
"mnc": {agpsMnc},
"cell": {agpsCellId},
"area": {agpsArea},
"types": [
1,
2,
3,
4,
6,
7,
8,
9
]
}

I can fix the issue on the thingy by removing 5 from the list. Anyone knows the reason why 5 would not work?

[coderbyheart]

Type 5 (nequick ionospheric correction) is not supported by the nRF9160, so there is no point for a Thingy:91 to request it.

But I see that this was added in nrfconnect/sdk-nrf#10325 by @plskeggs to nRF Connect SDK.

It has not yet trickled down to nRF Asset Tracker.

[coderbyheart]

#736

[plskeggs]

The positioning team at the time told me it wouldn't hurt to send nequick data to a 9160, and encouraged me to just always do it.

[coderbyheart]

Yes, no worries.