<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sean Gillies (Posts about formats)</title><link>https://sgillies.net/</link><description></description><atom:link href="https://sgillies.net/tags/formats.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sun, 31 Dec 2023 01:26:22 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Lessons of Event Data Format Design</title><link>https://sgillies.net/2018/08/31/lessons-of-event-data-format-design.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;Read &lt;a class="reference external" href="https://www.tbray.org/ongoing/When/201x/2018/08/30/Event-Structure"&gt;https://www.tbray.org/ongoing/When/201x/2018/08/30/Event-Structure&lt;/a&gt; and
follow the link to the "SEF theorem"
&lt;a class="reference external" href="https://github.com/inlined/versioningishard/"&gt;https://github.com/inlined/versioningishard/&lt;/a&gt; if you're into data format design.
Everything about this blog post applies equally well to the spatial data
domain. If you've ever encountered GeoJSON features with styling directives
mixed in with other feature attributes, you've witnessed the problem of trying
to make unstructured GeoJSON data consistent with structured data (Shapefiles
or whatever).&lt;/p&gt;</description><category>data</category><category>formats</category><category>json</category><category>protobuf</category><category>work</category><guid>https://sgillies.net/2018/08/31/lessons-of-event-data-format-design.html</guid><pubDate>Fri, 31 Aug 2018 15:37:41 GMT</pubDate></item><item><title>GeoJSON in Your Clipboard</title><link>https://sgillies.net/2017/11/03/geojson-in-your-clipboard.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;One of the best properties of a text format, maybe &lt;em&gt;the&lt;/em&gt; best property, is how
easily it can cross application boundaries.&lt;/p&gt;
&lt;div class="figure"&gt;
&lt;blockquote class="twitter-tweet" data-lang="en"&gt;&lt;p lang="en" dir="ltr"&gt;Cool,
&lt;a href="https://twitter.com/qgis?ref_src=twsrc%5Etfw"&gt;@QGIS&lt;/a&gt; can copy
features to the clipboard as GeoJSON - even converts coordinates to WGS84 for
you! (Settings→Options→Data Sources) &lt;a href="https://t.co/igLdEiA8yr"&gt;pic.twitter.com/igLdEiA8yr&lt;/a&gt;&lt;/p&gt;— AJ
(@aj_ashton) &lt;a href="https://twitter.com/aj_ashton/status/926226237789523969?ref_src=twsrc%5Etfw"&gt;November
2, 2017&lt;/a&gt;&lt;/blockquote&gt;
   &lt;script async src="https://platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;
&lt;/div&gt;&lt;p&gt;I'm in the midst of training myself to automatically use pbcopy and pbpaste on
my Mac command line and have yet another example of how readily GeoJSON
travels. After exporting GeoJSON from QGIS to your Mac's clipboard or paste
buffer, you could also send it directly to &lt;a class="reference external" href="http://geojson.io"&gt;http://geojson.io&lt;/a&gt; using either the
Node.js &lt;a class="reference external" href="https://github.com/mapbox/geojsonio-cli"&gt;geojsonio-cli&lt;/a&gt; or Python
&lt;a class="reference external" href="https://github.com/jwass/geojsonio.py"&gt;geojsonio&lt;/a&gt; – by Jacob Wasserman,
with additional Pandas and Jupyter integration features, a must-have Python
module for my line of work – packages:&lt;/p&gt;
&lt;div class="code"&gt;&lt;pre class="code console"&gt;&lt;a id="rest_code_eb9e3552a7994dd28411501140a25a2a-1" name="rest_code_eb9e3552a7994dd28411501140a25a2a-1" href="https://sgillies.net/2017/11/03/geojson-in-your-clipboard.html#rest_code_eb9e3552a7994dd28411501140a25a2a-1"&gt;&lt;/a&gt;&lt;span class="go"&gt;pbpaste | geojsonio&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;p&gt;From your Qt GUI to the operating system clipboard, to the command line, to the
web, and back to another GUI in your browser. As I keep saying, GeoJSON was
never about replacing shapefiles in traditional GIS workflows; the format was
intended to afford new methods and new workflows not easy or not possible with
shapefiles and databases.&lt;/p&gt;</description><category>clipboard</category><category>formats</category><category>geojson</category><category>geojsonio</category><category>json</category><category>qgis</category><category>text</category><category>work</category><guid>https://sgillies.net/2017/11/03/geojson-in-your-clipboard.html</guid><pubDate>Fri, 03 Nov 2017 13:38:05 GMT</pubDate></item></channel></rss>