Grant Slater wrote:
> Karl Newman wrote:
>
>> If I recall correctly, the database column is not actually set for
>> UTF-8 (but is double-encoded to return actual UTF-8 to the client...).
>> Wouldn't it be a better long-term fix to change the database to UTF-8
>> (or whatever), then presumably
Karl Newman wrote:
> If I recall correctly, the database column is not actually set for
> UTF-8 (but is double-encoded to return actual UTF-8 to the client...).
> Wouldn't it be a better long-term fix to change the database to UTF-8
> (or whatever), then presumably MySql wouldn't allow invalid s
Am Samstag, den 30.08.2008, 08:39 -0700 schrieb Karl Newman:
> If I recall correctly, the database column is not actually set for
> UTF-8 (but is double-encoded to return actual UTF-8 to the client...).
> Wouldn't it be a better long-term fix to change the database to UTF-8
> (or whatever), then pr
On Sat, Aug 30, 2008 at 02:21:52PM -0500, Ian Dees wrote:
> On Sat, Aug 30, 2008 at 12:29 AM, spaetz <[EMAIL PROTECTED]> wrote:
> > And I am looking forward to a performant read-only api that does the "map"
> > call. I know there are at least 2 attempts by Ian dees and blarson to get
> > one and if
On Sat, Aug 30, 2008 at 12:29 AM, spaetz <[EMAIL PROTECTED]> wrote:
>
> And I am looking forward to a performant read-only api that does the "map"
> call. I know there are at least 2 attempts by Ian dees and blarson to get
> one and if other's want to chime in and help that would be great. There's
2008/8/30 "Marc Schütz" <[EMAIL PROTECTED]>:
>> > Presumably the Pastafarian version won't be used often; I would in
>> > fact suggest omitting it to avoid pointlessly upsetting someone.
>> Not including one religion because other religions might not like it is
>> a very slippery slope.
>
> Yes, bu
> > Presumably the Pastafarian version won't be used often; I would in
> > fact suggest omitting it to avoid pointlessly upsetting someone.
> Not including one religion because other religions might not like it is
> a very slippery slope.
Yes, but as there are probably no pastafarian cemeteries
On Sat, 30 Aug 2008, Patrick Kilian wrote:
> ...
>> Presumably the Pastafarian version won't be used often; I would in fact
>> suggest omitting it to avoid pointlessly upsetting someone.
> Not including one religion because other religions might not like it is a
> very slippery slope.
Do you re
Hi,
> I am trying to find out the reason why uploading modifications to relation
> (id=5286) through josm consistently results in the following error:
Steven has already mentioned one of the problems for you, but as you
rightly say there is another problem. I'll give you (and others) a quick
r
Hi,
> Alternatively the Christian crosses could perhaps be made bigger.
That would be definitly easier than tweaking the color to make all the
same average darkness.
> Presumably the Pastafarian version won't be used often; I would in
> fact suggest omitting it to avoid pointlessly upsetting s
Alternatively the Christian crosses could perhaps be made bigger.
Presumably the Pastafarian version won't be used often; I would in
fact suggest omitting it to avoid pointlessly upsetting someone.
I might also suggest using X's instead of crosses for Unknown.
How to handle mixed? non-denominat
I can currently see one problem. The buddhists, taoist, sikh, and some
else to a lesser extent look much darker than some others such as
christian and pastafarian. This could be overcome by adjusting the
darker green colour in the dark ones to a lighter one. Another option
would be to make the icon
Thanks for the reference Steven. I tried to remove the way from the
relation in josm, but when I try and upload the same error gets logged. As
this relation is broken it does not seem possible to remove members from
it.
>From the history of the relation
http://api.openstreetmap.org/api/0.5/relati
On Sat, Aug 30, 2008 at 2:51 AM, Frederik Ramm <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Richard Fairhurst wrote:
> > Well, the relevant bit of the migration is
> [...]
>
> I looked that up myself but didn't go the extra length to find out that
> "string" actually means 255 characters only... I always
Hi,
> yeah, try posting to talk -- i don't think Steve Chiltern reads dev.
Thanks, I'l do that. I just thought that improvements like that are
"development".
> Oh and make it clear in the subject line that you've attached a patch
> -- that always gets people's attention :-)
Hehe. Thanks for the
Hi,
I am trying to find out the reason why uploading modifications to relation
(id=5286) through josm consistently results in the following error:
upload to: http://www.openstreetmap.org/api/0.5/relation/5286...connected
got return: 412 with id 5286
Suggestions to fix these kind of errors are a
El Sábado, 30 de Agosto de 2008, Andreas Kalsch escribió:
> It was the heanet.ie server I had trouble with, not the main server ;)
> My server downloaded the file completely - of course with much more
> speed. But I need it on my PC. I will try FTP from heanet.ie now,
> probably this will work bett
Frederik Ramm wrote:
> Returning an error should be no more difficult than throwing an
> exception there if v.length exceeds 255, only thing I am not sure
> about is whether Ruby will try to be smart and return the length
> not in bytes but in characters...?
irb(main):001:0> 'fred'.length
=
On Sat, Aug 30, 2008 at 11:51 AM, Frederik Ramm <[EMAIL PROTECTED]> wrote:
> I know it is not Osmosis' fault because Osmosis just uses standard XML
> parsing but I'm a bit unhappy about the gigantic waste of processing
> power incurred by all this parsing stuff - it seems anyone touching the
> XML
Hi,
Richard Fairhurst wrote:
> Well, the relevant bit of the migration is
[...]
I looked that up myself but didn't go the extra length to find out that
"string" actually means 255 characters only... I always assumed that we
allowed longer values. There goes the freedom of stuffing your sales
b
yeah, try posting to talk -- i don't think Steve Chiltern reads dev.
Oh and make it clear in the subject line that you've attached a patch
-- that always gets people's attention :-)
On Sat, Aug 30, 2008 at 10:25 AM, Patrick Kilian <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> is this the wrong mailin
Hi all,
is this the wrong mailing list to propose a change like that? Did I miss
some important feedback? Is somebody important (like the maintainer of
the stylesheet) on holiday?
Or did I just waste two days on a change which is listed as priority one
in the wiki but nobody cares about?
Patrick
Ulf Lamping a écrit :
> If the one running the openstreetbug server is willing to face the
> additional traffic, I'm all for adding a link (or maybe even better a
> tab) to the main site.
Actually a tab would be great, I think more intuitive and with less
inhibition for the user. But would need
Frederik Ramm wrote:
> Frederik Ramm wrote:
>> Closer inspection reveals that this is a tag value that has been
>> truncated at character #255, which happens to be in the MIDST of an
>> UTF-8 sequence. Ouch! Who truncates tags to 255 characters?
>
> It's a bit embarassing to keep talking to myself
XAPI has been serving an increased number of ?map style requests in the last
few hours.
It's probably not as fast as the main API for this, but it should scale well
under load.
I hope the new XAPI server will be on-line before the end of the weekend as
well, so that will provide some more capacit
Frederik, I just saw your emails but I'm about to head out and can't
look at it now, I'll try to take a look tomorrow but it sounds like
you've already diagnosed the problem.
If you can organise for the problematic way to be deleted or fixed in
the database I'll re-create all changesets since t
26 matches
Mail list logo
