GeoJSONs cannot be read when the properties are ordered differently than expected

For example, reading this GeoJSON results in a NullPointerException:
{"coordinates":[[[1,0.01],[1,-0.01],[2,-0.02],[3,-0.01],[3,0.01],[1,0.01]]],"type":"Polygon"}

This might not be desirable behaviour, since JSON objects are unordered collections afaik and some JSON parsers do not preserve the order of the properties when serializing/deserializing, but instead order them alphabetically, for example.

It also sounds like this is not intended by the standard (https://www.rfc-editor.org/rfc/rfc7946#section-1.2):
"The ordering of the members of any JSON object defined in this
document MUST be considered irrelevant, as specified by [RFC7159]."

Start by reproducing the NullPointerException with the Polygon GeoJSON shown in the issue, then trace the GeoJSON parsing entry point to find where member order is assumed. Confirm the fix by reading equivalent objects with different property orders and checking that both succeed without an exception.