In that case you would ideally find a way for the caching proxy server to
reach the original tiles over plain http (make sure to strip any user's
personal data from the requests!) and save some CPU cycles on both ends,
improving the latency slightly.
You might also want to consider serving larger
Https might not be strictly needed between tile renderxcxer and the cache,
but if this is the only way that you can get to the tiles (eg from the
pucxcxccxczxcxzcxxxblic opensnowmap tile server) you can technically still
use that.
If possible try to use http 2 or at least keep-alive connections.
Hi!
While preparing a dataset for a community import (
https://wiki.openstreetmap.org/wiki/Slovenia_Landcover_Import_-_RABA-KGZ )
we ran into 2 kinds of related problems that originate from Shapefile's
different representation of polygons:
a) duplicated ways: when no tags are present on two
()) after two prior merges (mergePoints()
and mergeWayPoints()).
greets,
Stefan
.
On Fri, Nov 21, 2014 at 6:21 PM, Paul Norman penor...@mac.com wrote:
On 11/21/2014 8:58 AM, Stefan Baebler wrote:
Is ogr2osm being actively maintained?
Yes - but I don't have time to add new features like #28. I'd
There a page in wiki:
http://wiki.openstreetmap.org/wiki/Android
that lists also other OSM software for Android.
Stefan
On Mon, Sep 28, 2009 at 11:21 PM, Stefan Keller sfkel...@gmail.com wrote:
Many thanks for all the hints so far.
Regarding Navit I did not found any sources on the SVN and
On Thu, Sep 24, 2009 at 1:49 PM, Frederik Ramm frede...@remote.org wrote:
One could use the newly provided OAuth mechanism for authentication.
This would then not transmit your password but a token; the token
however would still be transmitted in plain text, would have unlimited
validity until
build log at
http://cruise.openstreetmap.org/builds/osmapi-postgres
currently says:
**Running the tests** Run rake db:migrate to update your database then try
again.
(in /srv/.cruise/projects/osmapi-postgres/work)
You have 3 pending migrations:
40 CreateOauthTables
41
I believe Kelly was interested in static maps (eg paper maps) that
cannot be re-rendered every second.
Instead of providing map insets with higher detail it would be
interesting to have a fisheye style map, which would cover large
areas, but still provide high details in the centre or some other
please DO NOT revert my work without talking to me first. OSM doesn't
stop just because you're on holiday.
+1
Do not get me wrong. Tom undoubtedly puts in a lot of effort and does
great work. However, if the huge community relies on a single person
to do all code checks before deploying it, and
I consider my contributions so minor that i hereby give you all the
power to relicense them as you please.
Stefan
/trying to shorten possibly never-ending license debate :)
Brett Henderson wrote:
I hate to bring this topic up because I don't know if I have the
necessary patience for it :-)
Hi!
It is a nice practice to indicate the file type in the url of the
download link to let users know what they are getting before actually
pushing it down their throat.
Filename on the trace detail page often says somecity.gpx (as at the
time of upload), download link is simply data and the
://www.openstreetmap.org/trace/137465/data.xml
Why .xml extension instead of simply .gpx?
Can we link that in the trace detail page or is there a good reason for
not doing so?
Stefan
Stefan Baebler wrote:
Hi!
It is a nice practice to indicate the file type in the url of the
download link
Some nodes have altitiude (or alt) tag if the altitude is well known
(mountain peaks etc) as vertical precision of GPS is so inaccurate.
You can convert srtm data into OSM vector contours with
http://wiki.openstreetmap.org/wiki/Srtm2Osm
A general page about visualizing relief (including other
On Tue, Nov 4, 2008 at 8:28 AM, Dirk Stöcker [EMAIL PROTECTED] wrote:
On Sun, 2 Nov 2008, Florian Schmitt wrote:
it seems that the lang-* plugins aren't available any more. This means that
new
users who want to use the last stable version 1010 aren't able to change
the
language of JOSM. I
On Thu, Oct 30, 2008 at 12:56 PM, Marcin Floryan [EMAIL PROTECTED] wrote:
I'm not sure whether i have josm-translations.jar (or whatever it is
called), as it is not listed amongst plugins or as a seperate download.
Possibly listing available translations could help.
The way it is solved now
A significant benefit of launchpad based translation is that many
other opensource applications are translated there, giving translators
a wide range of suggestions about how to translate strings.
Applications benefit a lot from consistent translations.
Downside of launchpad based translation is
-dev] Potlatch causing DB inconsistency?
To: dev@openstreetmap.org
Stefan Baebler wrote:
Any ideas what's going on?
I think it's reasonably well attested that, without transactions, this
sort of thing is going to happen once in a while. As posted the other
day, Potlatch's database access code
Iván Sánchez Ortega wrote:
El Miércoles, 25 de Junio de 2008, 80n escribió:
So, I'd like to know if you think it would be a good idea to do load
balancing between several OSMXAPI servers.
This is probably a good idea. Do you have any servers in mind?
Well, for what I've read in the Wiki
really unsure where to go from here, and how to actually
run Osmosis commands as presented at that Wiki page? :-)
Could you please point me in the right direction, if possible? :-)
- Original Message -
From: Stefan Baebler
To: Fire Girl
Subject: Re: [OSM-dev
On Tue, May 6, 2008 at 10:25 AM, SteveC [EMAIL PROTECTED] wrote:
is there anything else that should be put in 0.6? Probably a good idea
to talk about it now.
As project is getting older there are many relatively old GPS tracks in the db.
Older tracks are probably already mapped, or out of
| The api change would be a good time to clean out most of the typos.
| with the node_tags, way_tags and relation_tags table (sorry i've completly
| forgotten these above), they are allready separated.
how do you suppose to do that?
map_features and proposed_tags are not all the valid
Dirk-Lüder Kreie wrote:
I propose to introduce the ability to limit the age of trackpoints
downloaded into the client by introducing an extra parameter age,
eg:
GET
/api/0.6/trackpoints?bbox=left,bottom,right,topage=ageInDayspage=pageNumber
+1! Although it might be easier on
Should be fairly easy to fix that with openlayers:
http://openlayers.org/dev/examples/wrapDateLine.html
Stefan
2008/4/3 Dirk-Lüder Kreie [EMAIL PROTECTED]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luka Frelih schrieb:
hello!
i just noticed that our slippymap resists crossing
On Fri, Apr 11, 2008 at 11:46 AM, Tom Hughes [EMAIL PROTECTED] wrote:
Should be fairly easy to fix that with openlayers:
http://openlayers.org/dev/examples/wrapDateLine.html
I don't think so. The tiles look like they are wrapping round just
fine at the moment - the problem is that the
Hi again!
Osmxapi behaves much better now, but there is a problem with my test node
in planet.osm it is:
node id=29161753 timestamp=2007-12-22T05:59:49Z lat=46.1356895
lon=14.7445634
tag k=created_by v=JOSM/
tag k=name v=Moravče/
tag k=is_in v=Slovenia, Europe/
tag k=place v=town/
tag k=note
25 matches
Mail list logo
