Your certificate contains a public key, the P-256 or secp256r1 or prime256v1 you can see here. However, the key is in uncompressed format (starting with a byte 04 and then 64 random looking bytes) and the domain parameters are specified using an OID with the curve mentioned above. So the only coordinates are those of the public key, and those are always the same 1 + 64 bytes; there is no problem there.
So probably you are talking about R and S as you mention in the question. However, R is a random number and S is the corresponding randomized signature, which means that they are not coordinates.
Now the curve is not specified; it is specified in the issuer certificate which is referenced in this one. However, we can safely assume that it is the same curve we are talking about. Of course, if you are building a verifier, then you should retrieve the curve and public key out of the issuer certificate though.
As you can see in the last part of the certificate:
BIT STRING (568 bit) 0011000001000101000000100010000000000000101000111011101011001100001001…
SEQUENCE (2 elem)
INTEGER (248 bit) 2892853004106127101112322441046660521562717594643885711748150025403073…
INTEGER (256 bit) 1104268754670564871921027255657571260094376165878172031675520861809130…
The random value is 248 bits and the signature is 256 bits. These values simply have to be smaller than the field size. This means that the signed, big endian, dynamic length encoding of these integers can differ. If you have bad code then in this case the R component may be smaller than what you would expect; if you'd just assume 256 bit then you would be in trouble.
What you have to do is to make sure your software will interpret these numbers if they are encoded as 1 byte, as 33 bytes (including 00 padding byte at the left) or any size in between. After that you may have to re-encode them as 32 + 32 = 64 bytes for your signature verification to work.
Or you can just use software that verifies the ANS X9.62 signature format of course. Or use a library that simply accepts R and S as separate numbers using some kind of "bignum" library.
