On Thu, 25 Nov 2010, Fichtennadel wrote:
I see your point, but if you look at the template it's not possible to put a
long description in the list of values for sac_scale. And the current
information is misleading, so the idea has been better none than wrong.
There is already a link to the wiki
On 11/24/2010 04:44 AM, Frederick Rama wrote:
For the end-user, there's no
difference in WMS and slippy map anyway, it only confuses them.
Well, Slippy Map supports tiles, wmsplugin doesn't.
signature.asc
Description: OpenPGP digital signature
On Wed, Nov 24, 2010 at 9:47 PM, Paul Johnson ba...@ursamundi.org wrote:
On 11/24/2010 04:44 AM, Frederick Rama wrote:
For the end-user, there's no
difference in WMS and slippy map anyway, it only confuses them.
Well, Slippy Map supports tiles, wmsplugin doesn't.
wmsplugin fetches images
Hi,
On Wed, Nov 24, 2010 at 9:47 PM, Paul Johnson ba...@ursamundi.org wrote:
Well, Slippy Map supports tiles, wmsplugin doesn't.
Ian Dees wrote:
wmsplugin fetches images from WMS in a tiled format.
Both correct - but people don't use the Slippymap or WMS plugins because
they want to
On Thu, Nov 25, 2010 at 12:42 PM, Frederik Ramm frede...@remote.org wrote:
Hi,
On Wed, Nov 24, 2010 at 9:47 PM, Paul Johnson ba...@ursamundi.org
wrote:
Well, Slippy Map supports tiles, wmsplugin doesn't.
Ian Dees wrote:
wmsplugin fetches images from WMS in a tiled format.
Both
On Thu, 25 Nov 2010 12:27:57 -0600, Ian Dees wrote:
On Wed, Nov 24, 2010 at 9:47 PM, Paul Johnson
ba...@ursamundi.org wrote:
On 11/24/2010 04:44 AM, Frederick Rama wrote:
For the end-user, there's no
difference in WMS and slippy map anyway, it only confuses them.
Well, Slippy Map
Ian,
Ian Dees wrote:
There seem to be two methods of display that need to be handled: tiled
(WMS and Slippymap) and static image (ImageLayer). Could the ImageLayer
plugin be made to fit a tiled-image interface without causing too much
trouble?
I would be guessing if I said anything, really.
On 25 November 2010 04:47, Paul Johnson ba...@ursamundi.org wrote:
On 11/24/2010 04:44 AM, Frederick Rama wrote:
For the end-user, there's no
difference in WMS and slippy map anyway, it only confuses them.
Well, Slippy Map supports tiles, wmsplugin doesn't.
You can pass to slippymap an URL
On 25 November 2010 21:31, andrzej zaborowski balr...@gmail.com wrote:
On 25 November 2010 04:47, Paul Johnson ba...@ursamundi.org wrote:
On 11/24/2010 04:44 AM, Frederick Rama wrote:
For the end-user, there's no
difference in WMS and slippy map anyway, it only confuses them.
Well, Slippy
Viesturs Zarins wrote:
Hi All,
Just commited improvements to the multipolygon plugin.
Changes:
- Can now handle polygons consisting of several unclosed ways.
- Supports multiple outer ways and deeper nesting.
- Detects crossings.
- Opens relation editor.
It does not open the relation editor
OK - I said I'd post again with my intentions. Here is a wiki page
that I hope will outline the automatic imagery adjustment mechanism
I've worked out with another mapper:
http://wiki.openstreetmap.org/wiki/True_Offset_Process
Comments are welcome. By now we're happy that we've described
2010/11/25 Dirk Stöcker openstreet...@dstoecker.de:
Actually I oppose this solution, as it is against the basic idea of how OSM
works.
IMHO the OSM solution would be to have no preset at all for sac_scale,
as this is a specialist tag for alpine mountain hiking, not a general
one, as far as I
El día Thursday 25 November 2010 20:02:39, Frederik Ramm dijo:
gvSig, for example, supports most stuff you can think of - shapefiles,
AutoCAD, KML, GML, GeoTIFF and other raster formats, WMS and WFS servers,
direct access to spatial databases etc., and it is written in Java. I
haven't
Hi,
2010/11/26 Dermot McNally derm...@gmail.com:
Comments are welcome.
There's corrections mechanism in twms server
(http://code.google.com/p/twms/source/browse/twms/correctify.py)
The code is not ideal, but it works. (A half a year or so already?)
We're collecting the shifts dataset out of
On 11/24/2010 04:44 AM, Frederik Ramm wrote:
Hi,
On 11/24/2010 09:31 AM, Viesturs Zariņš wrote:
Paris, Syndney seems more accurate but Moscow, Tallin has similar offset.
Is there a way to improve the rectification?
The JOSM slippy map plugin does not have a control for moving the layer
On 11/25/2010 01:23 AM, Viesturs Zariņš wrote:
Otherwise we will end up with lots of data traced with incorrect offsets.
You mean, like the TIGER import? *duck*
signature.asc
Description: OpenPGP digital signature
___
josm-dev mailing list
On 11/25/2010 12:27 PM, Ian Dees wrote:
On Wed, Nov 24, 2010 at 9:47 PM, Paul Johnson
baloo-PVOPTusIyP/sroww+9z...@public.gmane.org wrote:
On 11/24/2010 04:44 AM, Frederick Rama wrote:
For the end-user, there's no
difference in WMS and slippy map anyway, it only confuses them.
Well,
On 11/25/2010 01:02 PM, Frederik Ramm wrote:
I have gone on record in the past saying that JOSM is too bloated (and
I'd *still* like to have a really lean version from time to time), but
as background layers go, I am really tempted to suggest that we try to
hijack one of the existing Open
Paul,
On 11/26/10 07:54, Paul Johnson wrote:
Quantum GIS supports OSM, but I'll be damned if I can figure it out.
The Quantum GIS editor might be suitable for the occasional fix in OSM
but cannot replace a full-blown specialist editor like JOSM. Also,
because QGIS is not a Java program, we
19 matches
Mail list logo
