Hi,
when i started playing with geootools with same purpose (dynamic SLDs)
I also had same issues. Havent done much since then, I hope these tips
you guys wrote here will help :)
I bookmarked this page while ago, might be helpfull:
http://eskopinski.blogspot.com/2008/11/criando-um-arquivo-sld-co
Hi Jody,
The thing is that i havent been able to even display the shape file on
JMapPane yet. since NetBeans cant find org.geotools.gui.swing.JMapPane
i couldnt find the required dependency for using JMapPane?
Jody Garnett-2 wrote:
>
> Hi Irfan:
> JMapPane can display vector and raster data; I
Hi Irfan:
JMapPane can display vector and raster data; I am not sure what the
rastersymbolizer you will need to configure to display raster data looks
like. Have you tried with a simple world+image file? What does a default
raster symbolizer display for you?
It looks like your pom.xml file is okay
Hi all,
Inspired by recent discussions here, I've begun a revision of JMapPane
class and its associated classes on trunk (= 2.6).
If you are using trunk, please be warned that much of the new code
will _not_ be backwards compatible with the current version. In
particular, the setState / getState
On Wed, 25 Feb 2009 12:46:57 pm Raif S. Naffah wrote:
> ...
> i'm attaching a JUnit test case that shows the alternative for
> addressing the axis order on the client side...
as a follow-up and in the spirit of sharing with the community, i'm
attaching a small JUnit test that shows a reliable way
Hi all,
my scenario covers LineStrings in WGS84 around the whole world. I need to
make a mile-buffer around my LineString and I thought about a solution by:
defining my own oblique mercator projection for every Line segment,
transforming from WGS84 to this projection,
buffering with value of mile
Dear Simone,
thank you very much for these details, I was just trying to figure a
method to check for the ordering out. Great, thanks, this helps a lot!
Martin
Simone Giannecchini wrote:
> Martin,
> about geotiff, be aware that the spec seems to indicate that the axis
> order is *always* lon-lat.
Martin,
about geotiff, be aware that the spec seems to indicate that the axis
order is *always* lon-lat.
The spec is pretty old and I do not think any software would actually
be able to understand lat-lon.
Anyway, this is my reading of it and my experience with many other sw.
Simone.
Hi Martin,
thank you for the hints. And you were right, the doc points to epsg, not
spatialreference.org, my mistake (that cost me a few days...).
The parallel discussion on axisorder and wfs BBOX queries is also very
handy, I had the problem related to a similar issue, but connected to
geotiff
