1.4.0

1.4.0 is here, and so are you! In addition to various bug fixes and security updates, we also bring you normalized date strings, better list options, .json import, and easier export!

⏰⏲️📅 Date strings, time stamps, and date tags 🕰️⌛⏱️

If you have a field or property that has a date-like field or a timestamp, you can normalize it using --date propertyname. We will try to convert it to an ISO 8601 friendly value and save it in xyz_iso8601_propertyname, along with a unix seconds timestamp, xyz_timestamp_propertyname for your time-slicing needs. (UTC for now.)
If you add the --datetag option, we will calculate human-friendly tag buckets such as year@2020, month@april, weekday@thursday, week@21. You can also limit which tags you want using arguments like --datetag month. (Again, these are UTC-based for now, timezones are hard)..

😎🕶️🎧 Find that space using filters 🎧🕶️😎

You have a lot of spaces. They are all important and you love them equally. But you need to find that special one. Why not use here xyz list --filter theoneyouarelookingfor to narrow down your list based on what you added to the title and description?

{{{JSON import}}}

Just like a square is a rectangle, but a rectangle is not a square, GeoJSON is JSON, but JSON is not GeoJSON. But if your JSON file contains (non-nested) lat/lon coordinates, you can now import those non-geojson json files just like you can with a CSV.

🚀📡💫 Get more out of your space 💫📡🚀

• show --raw used to be limited to 5000 features, but if you need more, try --all (this can get long, and you can redirect to a file using >)
• you can also export to GeoJSONL via show --raw using, you guessed it, show --raw --geojsonl

Take care and we'd love to hear from you in issues (because we have issues).