Jeff + list,
Take a look at the candidate features for future versions of CloudMade's
vector map server:
http://developers.cloudmade.com/projects/vector-tiles/issues
We're planning features that would support the kind of usage you are talking
about, including JSON output and filtering of the
2009/5/31 Frederik Ramm frede...@remote.org:
Hi,
Tels wrote:
Well, one could fetch the data at z17, see it is below some
$ARBITRARY_THRESHOLD, zoom out to z16m, fetch again, and if still below
$THRESHOLD, repeat it until either there is too much data (display
message) or the user-requested
On Thursday 04 June 2009 19:48:30 you wrote:
2009/5/31 Frederik Ramm frede...@remote.org:
Hi,
Tels wrote:
Well, one could fetch the data at z17, see it is below some
$ARBITRARY_THRESHOLD, zoom out to z16m, fetch again, and if still
below $THRESHOLD, repeat it until either there is too
Hi,
Tels wrote:
Well, one could fetch the data at z17, see it is below some
$ARBITRARY_THRESHOLD, zoom out to z16m, fetch again, and if still below
$THRESHOLD, repeat it until either there is too much data (display
message) or the user-requested zoomlevel was reached.
I think the
On Wednesday 27 May 2009 15:20:26 Richard Fairhurst wrote:
Ed Loach wrote:
Is there anywhere though that z13 Yahoo imagery is of any use?
Sure. It's ok for lakes, woods, built-up areas, that sort of thing.
I'm just looking at somewhere near Rhayader and it's pretty useful.
I like Shaun's
On Wed, May 27, 2009 at 12:33 AM, Jeffrey Warren war...@mit.edu wrote:
I'm adding GeoJSON and also structured OSM JSON output formats to a rails
port 0.6 API I'm running; are these changes I could potentially commit, so
such formats could be offered by OSM proper, or are they too specific a
Andy Allan wrote:
Ideally the load on the main API should be for
editing-related purposes only.
Out of interest, do we have any stats on the proportion of server load
caused by each client?
(not sure I really want to ask that question...)
cheers
Richard
--
View this message in context:
Richard Fairhurst wrote:
Out of interest, do we have any stats on the proportion of server load
caused by each client?
(not sure I really want to ask that question...)
I'm not sure you did either ;-)
I have some logs here from the bulkapi servers for one day about a week
ago, and
Tom Hughes wrote:
Richard Fairhurst wrote:
Out of interest, do we have any stats on the proportion of server load
caused by each client?
(not sure I really want to ask that question...)
I'm not sure you did either ;-)
Heh.
I suspect a lot of the Potlatch load is caused by people trying
On Wednesday 27 May 2009 14:22:27 Richard Fairhurst wrote:
Tom Hughes wrote:
Richard Fairhurst wrote:
Out of interest, do we have any stats on the proportion of server
load caused by each client?
(not sure I really want to ask that question...)
I'm not sure you did either ;-)
Heh.
On 27 May 2009, at 13:22, Richard Fairhurst wrote:
Tom Hughes wrote:
Richard Fairhurst wrote:
Out of interest, do we have any stats on the proportion of server
load
caused by each client?
(not sure I really want to ask that question...)
I'm not sure you did either ;-)
Heh.
I suspect
RichardF:
I suspect a lot of the Potlatch load is caused by people trying
to
edit large areas at z13.
We pretty much have to keep offering z13 because for most of
the
world, it's the only level at which Yahoo imagery is available.
Is there anywhere though that z13 Yahoo imagery is of any
Ed Loach wrote:
Is there anywhere though that z13 Yahoo imagery is of any use?
Sure. It's ok for lakes, woods, built-up areas, that sort of thing.
I'm just looking at somewhere near Rhayader and it's pretty useful.
I like Shaun's suggestion of defaulting to z17 and let users zoom
out.
So
Shaun McDonald wrote:
Or just default to z17 (until there is some data metric stuff),
and let people to zoom out themselves. This would help a lot
when editing in places like London with a GPX trace.
Further to previous message, though, I do think you're right with the GPS
traces - this
On Wed, May 27, 2009 at 1:40 PM, Shaun McDonald
sh...@shaunmcdonald.me.uk wrote:
Or just default to z17 (until there is some data metric stuff), and let
people to zoom out themselves. This would help a lot when editing in places
like London with a GPX trace.
and when people zoom out to z13,
I'm adding GeoJSON and also structured OSM JSON output formats to a rails
port 0.6 API I'm running; are these changes I could potentially commit, so
such formats could be offered by OSM proper, or are they too specific a
need? I'll be posting the changes online regardless.
The osm JSON will be an
16 matches
Mail list logo
