Support jsonld for items with null geometry

[doublebyte1]

Overview

Some items, like records, may have no geometry . This is throwing an error on the jsonld representation, because it always expect a geometry. This fix will avoid geometry operations over items that have a null geometry.

Related Issue / Discussion

#1422

Contributions and Licensing

(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)

• I'd like to contribute [feature X|bugfix Y|docs|something else] to pygeoapi. I confirm that my contributions to pygeoapi will be compatible with the pygeoapi license guidelines at the time of contribution.
• I have already previously agreed to the pygeoapi Contributions and Licensing Guidelines

[webb-ben]

Think the @id needs to be outside of the if block

        # Include multiple geometry encodings
        if data.get('geometry') is not None:
            data['type'] = 'schema:Place'
            jsonldify_geometry(data)

        # Set data id
        data['@id'] = identifier

[doublebyte1]

Think the @id needs to be outside of the if block

        # Include multiple geometry encodings
        if data.get('geometry') is not None:
            data['type'] = 'schema:Place'
            jsonldify_geometry(data)

        # Set data id
        data['@id'] = identifier

You are right: this was leaving the id out for geometry null items. Thanks for spotting that: fixed now!