I started learning GIS a week back and I will not fit in as contributor. I am
evaluating alternative for commercial solutions that we currently use.
The commit for enhancedSpatialSupport needs some more changes based on MySQL
8.0 due to deprecation of few more function names. See
On Wed, Jan 23, 2019 at 2:24 AM antopaul wrote:
> Irrespective of funding, these are bugs that prevent using MySQL 8 with
> GeoServer and Geotools.
>
> For those facing same issues - you can fix the issues by changing few
> function names to use prefix "ST_". The actual code used is Geotools.
>
Hi Anto,
why not contributing a PR for this?
If you are interested in supporting MySQL you could step up as the
mantainer in the longer run.
Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==
Ing. Simone
Irrespective of funding, these are bugs that prevent using MySQL 8 with
GeoServer and Geotools.
For those facing same issues - you can fix the issues by changing few
function names to use prefix "ST_". The actual code used is Geotools.
Github -
Dear Anto,
I would say no at least as long as geosolutions people are concerned.
Obviously this could change quickly if someone puts funding on the table
for this to happen.
Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more
Is there any work in progress or planned for supporting MySQL 8?
I am getting below exception with MySQL 8.0.13 and GeoServer 2.14.2 on
clicking LayerPreview.
Caused by: java.sql.SQLSyntaxErrorException: FUNCTION nyosm.asWKB does not
exist
at
I solved the problem by replacing *jts-1.13.jar* with* jts-1.10.jar* in
"/opt/apache-tomcat-8.5.6/webapps/geoserver/WEB-INF/lib"
Thanks a lot, best regards
Paolo
-
Paolo Tomè
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/MySQL-problem-tp5294671p5296582.html
Sent
Mysql version:
/innodb_version 5.5.52
that insert statement is generated in MySQLDialectBasic.java
encodeGeometryValue (
https://github.com/geotools/geotools/blob/master/modules/plugin/jdbc/jdbc-mysql/src/main/java/org/geotools/data/mysql/MySQLDialectBasic.java#L169)
- it uses the standard JTS WKTWriter so you would need to either
Thanks for the quick response.
Who generates the mysql insert statment? perhaps the mysql extension of
geoserver?
There is a way to modify the insert statment?
Thanks a lot
ps. from
https://dev.mysql.com/doc/refman/5.7/en/gis-wkt-functions.html#function_geomfromtext
For example, both of the
Hi,
I am not sure, but I feel that is there is an issue with double parenthesis
then it is rather in MySQL than in Geoserver. See
http://gis.stackexchange.com/questions/200126/are-nested-parenthesis-allowed-in-multipoint-wkt/200134#200134.
-Jukka Rahkonen-
Good evening,
I write because I have a problem on entering points (multipoint) through a
wfs-t with MySQL.
I believe there is an error in the input of MySQL insert statment. In fact,
mysql log shows the following query:
INSERT INTO t_coordinate_ritrovamento_punti_generale (the_geom, species)
OK so I figured out the problem, nothing to do with the view, but was to do
with the content of the data. The view extracted current work items, and
for some reason the data content owners were using 00/00/ 00:00:00 when
there was no date, instead of NULL. Once this undone everything worked.
Hi there,
I have created a view of a table in mySQL and published both through
Geoserver. However when I use layer preview on the view and click the
GetFeatureInfo event never returns any attribution, whereas the table works
fine.
Is there a problem with using mySQL views in Geoserver? The
Message-
From: christian.muel...@nvoe.at [mailto:christian.muel...@nvoe.at]
Sent: Monday, 17 January 2011 7:06 PM
To: Dr. Markus Müller
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] mySQL datastore - display of polygonsfails
[resend]
One quick question
@lists.sourceforge.net
Subject: Re: [Geoserver-users] mySQL datastore - display of
polygonsfails
[resend]
One quick question. You are aware of the fact that mysql does not
implement the full OpenGIS specification.
http://dev.mysql.com/doc/refman/5.5/en/functions
One quick question. You are aware of the fact that mysql does not
implement the full OpenGIS specification.
http://dev.mysql.com/doc/refman/5.5/en/functions-that-test-spatial-relationships-between-geometries.html
Relationship tests are always based on the MBR of the geometries. For
-
From: christian.muel...@nvoe.at [mailto:christian.muel...@nvoe.at]
Sent: Monday, 17 January 2011 7:06 PM
To: Dr. Markus Müller
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] mySQL datastore - display of polygonsfails
[resend]
One quick question. You are aware of the fact
I have no problem using mysql with layers loaded by ogr2ogr
http://www.gdal.org/ogr/drv_mysql.html
On 2011-01-17 09:41, Dr. Markus Müller wrote:
[Sorry for the resend - nobody uses mysql with geoserver on this list?]
Dear listers,
I want to use mySQL as datastore for geoserver but have
Dear listers,
I want to use mySQL as datastore for geoserver but have trouble with
polygons: they are only displayed as points although the geometry type
in mysql is polygon or multipolygon. I use:
- windows vista home premium
- xampp-win32-1.7.3
- geoserver 2.0.2 and corresponding mysql plugin
MySQL has limited spatial capabilities - they do have geometry storage and a
spatial index. The main problem is that all spatial operations are done
against the bounds of the geometries. So they're not exactly accurate. So
if your polygons are all boxes then it'll work great, if not then it'll
All.
I've been using Geoserver with postgres/postgis for years and we use it
in almost all of our tools. I now have a project where the user has an
existing mySQL database. The data are all points, and for the most part
we will be just plotting points, querying the data by some attribute;
22 matches
Mail list logo
