OSMXAPI currently includes an attribute named osmxapi:planetDate in the
osm 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
I would like to remove area support for all perlscripts I wrote and that
understand the parameter --area=...
The reason for this is, that it's confusing and the area excerpts from
Frederik are mu more precise. So this feature is no longer needed in my eyes.
Any objection?
--
Jörg (Germany,
On Wed, Sep 10, 2008 at 6:08 PM, Stefan de Konink [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://api.openstreetmap.org/api/0.5/node/169532897
Looking at the last tag... that looks pretty wrong to me. And don't go
fixing the tag... if the database outputs
On Tue, Sep 9, 2008 at 4:43 PM, Florian Lohoff [EMAIL PROTECTED] wrote:
On Tue, Sep 09, 2008 at 07:32:34AM +1000, Brett Henderson wrote:
As Jochen mentioned, the --write-pgsql-dump task and subsequent import
using
COPY statements should be faster. I've looked at getting osmosis to
stream
Hi all,
Now, we have a working i18n branch for the osm rails_port. This setup
is done by using globalize and click-to-globalize plugins. As of now
all/most strings of website can be translated using the present
translation interface. We even have l10n statistics, translation
update feeds and
Hi list, hi Dirk,
Please improve your patch a bit nevertheless:
a) if the first checkbox is unckecked, all 5 elements should be
disabled.
b) if the second checkbox is checked, username and password should be
disabled.
You were right about your comments for enabling/disabling the
components.
6 matches
Mail list logo
