Thanks to visit codestin.com
Credit goes to github.com

Skip to content

query: Unescaped CR/LF in GeoJSON output #93

@clarisma

Description

@clarisma

GeoJSON output performs simplified string escaping, as it relies on the following:

OSM strings have already been cleaned up during import

But this is not true, only strings that are written into string tables are cleaned this way; rare strings are not cleaned.

Should spec be changed? See #94

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions