[GeoJSON] GeoJSON Digest, Vol 64, Issue 3

[Jeff Yutzler]

I would be interested in hearing from the other GeoJSON contributors. If
temporal support is in fact a non-starter for GeoJSON, perhaps a separate
initiative should be established for the purpose. It would be disappointing
for time to be considered "out of scope" for this group but IMHO the
Wild-West status quo is worse.
-Jeff


----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 2 Apr 2014 12:44:20 -0700 (PDT)
> From: Karl Grossner <karlg at stanford.edu>
> To: geojson at lists.geojson.org
> Subject: Re: [GeoJSON] GeoJSON Digest, Vol 64, Issue 1
> Message-ID:
>         <1923311032.5670497.1396467860197.JavaMail.zimbra at stanford.edu>
> Content-Type: text/plain; charset=utf-8
>
> Sean (and list),
>
> Love the 'little...for a while' reference :^)
>
> I can see why extending the core to include time would be a stretch right
> now, particularly since it can probably be managed pretty well with LD and
> "properties" -- it's then an application level task to interpret a
> "timestamp" or "timespans" property.
>
> The idea of co-equal spatial and temporal extents in a single standard is
> really appealing to my inner ontologist, but any pragmatic means for
> modeling 'Iron Age Britain' and "Neolithic Levant' as GeoJSON (or
> GeoJSON-LD) features will do, and that seems within sight. I do agree that
> attempting fuzzy spatial extents is a similar 'core-or-not' issue.
>
> I will stay tuned and have some sort of working Topotime/LD example to
> show soon -- by mid-May 'for sure.'
>
> I also agree that CIDOC doesn't relate technically at this point but
> thought it worth noting that they are 'in the space' actively looking to
> model space-time. The seemingly increasing traction of CIDOC in some fields
> makes what they do at least tangentially relevant to me -- always looking
> for conceptual common ground.
>
> cheers, kg
>
>
> ----- Original Message -----
>
> > Today's Topics:
> >
> >    1. Re: Time and GeoJSON, redux (Sean Gillies)
> >
> >
> > ----------------------------------------------------------------------
> >
> >
> > Dear Karl,
> >
> > I worked on a little historical gazetteer project for a while and
> continue
> > to be very interested in time. While I'm not in favor of making time part
> > of the GeoJSON core, I think it would be a cool application for
> GeoJSON-LD.
> >
> > I don't agree that CIDOC-CRM or Topotime white papers are good starting
> > points for this discussion. Rather, I think the right starting points
> are:
> >
> >   1. The frequently asked question "how do I represent time series and/or
> > GPX data in GeoJSON?"
> >   2. How can we extend GeoJSON so that "story map" applications (such as
> > http://storymap.knightlab.com/) are simple to develop and so that this
> kind
> > of data can benefit from the ecosystem around GeoJSON (Leaflet, GitHub
> > support, etc.
> >
> > Fuzzy dates and historical calender system bugs complicate the latter,
> > certainly, and I feel that GeoJSON should avoid fuzzy dates as it avoids
> > fuzzy locations. Also, the choice of a standard temporal reference system
> > will be interesting.
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geojson.org/pipermail/geojson-geojson.org/attachments/20140403/89e81a36/attachment.htm>