Hi,
I suppose you have read the OGC specification:
"Layers may include a element that suggests minimum and maximum
scales
for which it is appropriate to display this layer. Because WMS output is
destined for
output devices of arbitrary size and resolution, the usual definition of scale
as the
Rahkonen Jukka wrote:
Hi,
> "Layers may include a element that suggests minimum and maximum
> scales
> for which it is appropriate to display this layer. Because WMS output is
> destined for
> output devices of arbitrary size and resolution, the usual definition of
> scale as the ratio of
> m
I'm working on a little tool that creates a grid in which each cell of
the grid is a polygon. You can create the grid with any rectangular
dimensions, specify the number of columns and rows, and also a
rotation. The tool also allows you to create attributes for each cell
based on the row and column
I have used the core JUMP API in numerous projects, primarily for easily
modelling features (spatial + attributes) and having convenient IO
(especially for shapefiles!)
I had the same need for a simple interface to the JUMP IO classes. I
simply wrote a bunch of utility functions to do IO on t
Thanks very much for posting the code Martin. I'll have to see if I
can't get this into the SVN for OpenJUMP. Do any of the developers see
a problem with this?
The Sunburned Surveyor
On Dec 11, 2007 4:28 PM, Martin Davis <[EMAIL PROTECTED]> wrote:
> I have used the core JUMP API in numerous proje
