OSMXAPI currently includes an attribute named osmxapi:planetDate in the
tag to show the age of the data.
It's namespaced because it is not an official attribute of the OSM schema.
There is definitely a need for an attribute that describes the age of the
data and it ought to be part of the OSM sc
Hi,
> SO why does the planet export and/or the osc change files have
> timestamps in their filename? Its a snapshot timestamp and thats the one
> i am interested in. It says that the state i am dumping, and thats what
> the map api call does for a bbox, is current up to date X.
The osc files are
Florian Lohoff wrote:
> On Tue, Sep 09, 2008 at 12:37:14PM +0100, Tom Hughes wrote:
>> Florian Lohoff wrote:
>>
>>> No need for object versioning here - I want to enable everyone to look
>>> at when the data was generated and from which database state.
>> Well for planet that's simple - it isn't ge
On Tue, Sep 09, 2008 at 05:10:49PM +0100, Tom Hughes wrote:
> >SO why does the planet export and/or the osc change files have
> >timestamps in their filename? Its a snapshot timestamp and thats the one
> >i am interested in. It says that the state i am dumping, and thats what
> >the map api call do
On Tue, Sep 09, 2008 at 01:52:24PM +0200, Stefan de Konink wrote:
> Subject: Re: [OSM-dev] osm schema/dtd - planet and request timestamp
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Florian Lohoff schreef:
> > Do you have a url? One can find tons of
On Tue, Sep 09, 2008 at 12:37:14PM +0100, Tom Hughes wrote:
> Florian Lohoff wrote:
>
> >No need for object versioning here - I want to enable everyone to look
> >at when the data was generated and from which database state.
>
> Well for planet that's simple - it isn't generated from any particul
On Tue, Sep 09, 2008 at 12:37:14PM +0100, Tom Hughes wrote:
> Well for planet that's simple - it isn't generated from any particular
> state but rather contains some combination of the states over a period
> of a number of hours as it is created.
>
> So there is no single timestamp we could repo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Lohoff schreef:
> Do you have a url? One can find tons of information in the wiki
> concerning the xsd but all of that seems - hmm - outdated - invalid or
> simply the stuff i am referring to:
>
> http://wiki.openstreetmap.org/index.php/XSD
Florian Lohoff wrote:
> No need for object versioning here - I want to enable everyone to look
> at when the data was generated and from which database state.
Well for planet that's simple - it isn't generated from any particular
state but rather contains some combination of the states over a pe
On Tue, Sep 09, 2008 at 11:15:54AM +0100, Shaun McDonald wrote:
> Subject: Re: [OSM-dev] osm schema/dtd - planet and request timestamp
>
> Florian Lohoff wrote:
> >Hi,
> >with the increasing number of database mirrors satisfying requests for
> >the various types of appl
On Tue, Sep 09, 2008 at 12:31:43PM +0200, Stefan de Konink wrote:
> Subject: Re: [OSM-dev] osm schema/dtd - planet and request timestamp
>
> On Tue, 9 Sep 2008, Florian Lohoff wrote:
>
> > I was looking at http://kinkrsoftware.nl/contrib/osm/osm-0.5.xsd which
> > does no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shaun McDonald schreef:
> The next API release 0.6 will include a version field for each node, way
> and relation. This will do exactly what you are looking for.
This is nonsense, and is not what he is looking for. It will only
massively increase the
On Tue, 9 Sep 2008, Florian Lohoff wrote:
> I was looking at http://kinkrsoftware.nl/contrib/osm/osm-0.5.xsd which
> does not mention something like this.
>
> The main api could simply add the current time as the timestamps.
Check the wiki XSD Schema for the 'latest' version of it :)
Stefan
_
Florian Lohoff wrote:
> Hi,
> with the increasing number of database mirrors satisfying requests for
> the various types of applications it would be a good idea to extend the
> OSM apis DTD/Schema with some timestamps makeing it possible to check
> for the currentness of the data. I'd propose somet
Hi,
with the increasing number of database mirrors satisfying requests for
the various types of applications it would be a good idea to extend the
OSM apis DTD/Schema with some timestamps makeing it possible to check
for the currentness of the data. I'd propose something like
requestTimestamp and
15 matches
Mail list logo
