Update README with notes about GeoJSON format requirements

Created on 5 January 2023, almost 2 years ago
Updated 2 February 2023, almost 2 years ago

Problem/Motivation

Add an expanded section to the readme.md file to mention lessons learned.

Steps to reproduce

Proposed resolution

Add Section to Readme.md

Lessons Learned:
1. When you create your map data taxonomy vocabulary to hold the GeoJSON map file be sure to pretty print the GeoJSON file before you save it in the term field.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Postponed: needs info

Version

1.0

Component

Documentation

Created by

πŸ‡ΊπŸ‡ΈUnited States Michael.Scott.McGinn

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States andileco

    Can you elaborate a bit on this issue? I had pretty-printed JSON in my field originally, but if I modify it by removing spaces and line breaks, it still works. I could see an argument for not having pretty-printed JSON because it will make for a smaller file. Is your suggestion just to make it easier to read?

Production build 0.71.5 2024