#4554: remove trailing whitespace in tags
---+
Reporter: Cobra | Owner: potlatch-dev@…
Type: defect | Status: new
Priority: minor | Milestone:
Branch: refs/heads/master
Home: https://github.com/joto/taginfo
Commit: 1fc088a95ef10c43be22f7560b7712229c5b47fa
https://github.com/joto/taginfo/commit/1fc088a95ef10c43be22f7560b7712229c5b47fa
Author: Jochen Topf joc...@topf.org
Date: 2012-08-31 (Fri, 31 Aug 2012)
Changed
Hi Stefan!
This is exactly what I was planning to do, but in a much more complicated
way, because of my defficiencies with SQL!
So thanks for your code, this is very helpful. I will also just run it
everyday in a cron task
Then it's not a prioirity for me anymore but I guess it would be good in
Stéphane,
Yes, you’re right in your analysis of how the co-ordinates are stored in the
slim mode tables. This’ll help confirm it for you:
Executing this query against your Postgres database:
select
lon,
lat,
ST_X(ST_Transform(ST_SetSRID(ST_Point(lon / 100, lat / 100),900913),4326)),
hi,
but is it a bug? or am I missing the good reason why there is this factor
100?
I searched the source code to find the reason why there is a x100 on
coordinate, but couldn't find where it's done.
But my guess is that for performance reasons, the field to store x/y was
chosen to be an
That would make sense indeed.
But then if this is confirmed to be a wanted behavior, then we should
document it explicitely somewhere
Thanks to all for your help and advice!
Stéphane
--
Le mot progrès n'aura aucun sens tant qu'il y aura des enfants malheureux
-- Albert Einstein
A journey does
On 09/06/2012 11:39 AM, Stéphane Henriod wrote:
But then if this is confirmed to be a wanted behavior, then we should
document it explicitely somewhere
This is wanted behaviour, the relevant defines/macros and an explanation
are in node-ram-cache.h starting at line 16.
You could probably
On Wed, Sep 5, 2012 at 5:30 PM, Roland Olbricht roland.olbri...@gmx.de wrote:
Dear Martijn,
There are much more tools around reading OSM files, in particular the XML
format, than just Osmosis.
And even more important: It is easy to write a piece of software that reads
XML, and that is
I've been interested in the statistical aspects of mapping for a
while, and in baseball cards for even longer than that.
You may have seen this before. Hang on. I've added something cool.
One question I come back to frequently is If mappers had baseball
cards, what would they look like?
On Thursday, 6 de September de 2012 20:00:03 Richard Weait escribió:
My wishlist:
- mappers to think it's cool and ask for their stats.
/me raises hand
- ideas! What are additional tools that mappers use and how can we
measure them?
Bounding box. Has the mapper edited a small area, or
My wishlist:
- mappers to think it's cool and ask for their stats.
Me 2 (OSM account name robbieonsea)
- designers to take an interest in making it prettier.
- developers to patch and improve.
- ideas! What are additional tools that mappers use and how can we
measure them?
Some stuff
On Friday, 7 de September de 2012 01:32:02 Robert Norris escribió:
How about stats on the 'quality' of changeset comments somehow. Basically
longer the better!
You mean Total number of words in the changesets comments.
--
--
Iván Sánchez Ortega
I like the stats. I'm not so familiar with baseball cards, but I think top
trumps are fun.
My username is LivingWithDragons.
For top trumps, I would add how many performances/songs you've done.
Ivan, I think we now match on conference attendance.
The gap is an interesting stat. I often tag my
13 matches
Mail list logo
