Right, completely switched. I updated the license and readme to indicate
the plugin is now licensed as GPLv3. Also, the plugin frame is now
centered on the OJ workbench frame. I uploaded release 0.8.2 to
sourceforge.
-lreeder
On Fri, Apr 12, 2013 at 3:33 AM, wrote:
> On 12.04.2013 06:0
I'd opt for #3, with these items being my personal favorites:
* Increased use of layer or project SRID throughout OJ so that
measurements are in proper values.
* Continuation of the UI enhancements you (Ede) and others made in 1.6.
I'm LOVING the standard ctrl-c, ctrl-v, ctrl-z, ctrl-a shortcu
Hi,
I have committed the modifications about WMS 1.3.0 (r3505)
Thanks to Jukka's server, I could test and compare WMS 1.1.1 / WMS 1.3.0
Tell me if lat/lon problems are fixed with all your use cases.
Michaël
Hi,
Thanks for the tests.
I still not master the lat/lon lon/lat problem, but with th
Hi Jukka, Uwe,
In the last snapshot, I've deactivated 1.6.1 ZoomToWMS plugin
and replaced it by a much more simple plugin.
The new one just try to zoom to the layer(s). It is not so obvious
though as it must search for a bounding box which is in the same
SRS as the one asked by the user for this
Hi Stefan, Larry
While updating WMS code, I've found several patches from Stefan
about SID Layer handling.
Seems that SIDLayer inherits from WMS Layer, hence, patches
have been added in WMS code to exclude cases where WMS Layers
are instances of SIDLayer.
The design seems error prone and probably
Appears to be a problem with JTS 1.13, unless the WKB is not conformant to
the spec, and JTS 1.12 was ignoring any problems. I opened bug # 3610843
against JTS.
-lreeder
On Wed, Apr 10, 2013 at 2:58 PM, Michaël Michaud wrote:
> Le 10/04/2013 11:12, edgar.sol...@web.de a écrit :
> > On 10.04.2
Feature Requests item #3610851, was opened at 2013-04-14 13:58
Message generated for change (Tracker Item Submitted) made by michaudm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=679909&aid=3610851&group_id=118054
Please note that this message will contain a full
Hi,
I made two tests:
1) With PostGIS 2.1
select encode(ST_AsBinary(ST_GeomFromText('MULTIPOLYGON(((0 0, 10 20, 30 40, 0
0), (1 1, 2 2, 3 3, 1 1)),
((100 100, 110 110, 120 120, 100 100)))')), 'hex')
Query gives the same WKB that you used in JTS bug #3610843, that is
"0106000200010300
On Sun, Apr 14, 2013 at 3:39 PM, Rahkonen Jukka
wrote:
> Hi,
>
> I made two tests:
> 1) With PostGIS 2.1
> select encode(ST_AsBinary(ST_GeomFromText('MULTIPOLYGON(((0 0, 10 20, 30
> 40, 0 0), (1 1, 2 2, 3 3, 1 1)),
> ((100 100, 110 110, 120 120, 100 100)))')), 'hex')
> Query gives the same WKB th
Hi,
I tried to do the following with spatialite-gui v. 1.5.0 and 1.6.0 which
contain Spatialite v. 3.0 and 4.0, respectively.
select asbinary(geomfromtext('MULTIPOLYGON(((0 0, 10 20, 30 40, 0 0), (1 1, 2
2, 3 3, 1 1)),
((100 100, 110 110, 120 120, 100 100)))
'))
I saved the returned binary c
Hi,
Just compared both strings to the spec,
First string follows the WKB specification
01 endianess
0600 MultiPolygon
0200 Number of Polygons
01 endianess
0300 Polygon
0200 Two rings
0400 Four points
...
Second string follows the Spatialite specification
http://www.gaia-gis
Hi Uwe,
Don't have experience with other databases,
but your description seems to be consistent.
It also means that from OpenJUMP you can :
just use unquoted lower case identifiers if you want a case insensitive
behaviour
any case unquoted identifier for a case sensitive behaviour
One can say i
12 matches
Mail list logo
