[Geojson] Position Clarification

[Erik Seglem <[e-mail]>]

I was looking over the spec and came across a bit that seems open to some
level of interpretation. In 3.1.1 it says "A position is an array of
numbers." And then goes on to specify the order and "using decimal numbers."

The JSON RFC says the fractional part of a "number" is optional. But, to
me, stating they are "decimal numbers" is an additional requirement on top
of a "number".

This seems to be backed up by the examples all having decimals in them, but
doesn't seem to be consistent across implementations across the community.
Some appear to allow integers, and some stick with floats.

In looking around for answers a Stack Exchange question came up with the
same question as mine:
https://gis.stackexchange.com/questions/429184/are-positions-without-decimals-valid-geojson
but
no definitive answer either. I figured the best thing to do would be ask
this group.

I guess it comes down to is this a valid GeoJSON Point?
     {
         "type": "Point",
         "coordinates": *[100, 0]*
     }

If in fact they do require a decimal place. Does that also apply to the
elevation or just the long / lat? It seems to only say the first two
elements must be decimal numbers, and the third is optional without that
clarification.

Would this be valid?
     {
         "type": "Point",
         "coordinates": [100.0, 0.0, *124*]
     }

And what about bounding boxes? The spec says it's an array and specifies
the length, but not the type of the values.

Would this be valid?
   {
       "type": "Feature",
       "bbox": *[-10, -10, 10, 10]*,
       "geometry": {
           "type": "Polygon",
           "coordinates": [
               [
                   [-10.0, -10.0],
                   [10.0, -10.0],
                   [10.0, 10.0],
                   [-10.0, -10.0]
               ]
           ]
       }
       //...
   }

Thanks,
Erik