Add coordinate (de-)serialisation, including z #27
Conversation
If the z axis is present in serialisation, i.e. z is not NaN, then export it in Json. Likewise, if it's present in Json, then create the Coordinate with the 3 axis.
|
Hi @joprodrigues, thanks a lot for your contribution. In order to publish your work within the 52N repositories, we need your official permission. For this purpose we have a so called contributors license agreement (CLA) in place. With this agreement you grant us the rights to use and publish your code under an open source license. The contributors license agreement is available here. Please note: as you are working on the code as part of your work it is important, that the CLA is signed by an authorized representative of your company. Further explanations about the contributors license agreement are available here. Finally, we have also prepared an FAQ about the contributors license agreement. We are really looking forward to host your code on 52N. If you have any further questions or need for clarification just let us know. We will be happy to help you. Thanks, |
In addition to all the Geometry types (including point), in some cases the we are interested in (de-)serialising the coordinates themselves.
The deserialisation code aceppts both pairs/triples of coordinates, such as [X,Y, Z], as well as the format {'x': X, 'y': Y, 'z': Z}, where Z is, similarly to JTS, optional and signalled with a NaN.