Skip to content

Handling of 3D coordinates with Null Z-values to avoid jsonld renderi… - #48

Open
jwallace94 wants to merge 1 commit into
developfrom
James/DAT-1452b
Open

Handling of 3D coordinates with Null Z-values to avoid jsonld renderi…#48
jwallace94 wants to merge 1 commit into
developfrom
James/DAT-1452b

Conversation

@jwallace94

Copy link
Copy Markdown
Collaborator

…ng errors

Overview

There is an issue with jsonld crashing on data which is a 3D point with a z-coordinate value of "Null". The value -99999 has been cited as an established value of "unknown" by MEGIS and this will fix the excessive logs generated and the error on the frontend.

Related Issue / discussion

https://gajira.atlassian.net/browse/DATA-1452

Additional information

Dependency policy (RFC2)

  • I have ensured that this PR meets RFC2 requirements

Updates to public demo

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant