Hi,
normally GeoServer figures out the srid of the data from the
geometry_columns view/table,
without needing to look at the data. Checking the first record found is the
last resort, and works only
if there is data of course.
So, could it be that the user you specified in the datastore connection
parameters is not granted
access to the geometry_columns view?
Cheers
Andrea
On Tue, Feb 5, 2019 at 7:50 PM jason.k...@q-free.com <jason.k...@q-free.com>
wrote:
> All,
>
> We're noticing an issue attempting to access a GeoRSS feed from Geoserver
> pointed at a Postgres database. It seems to be intermittent and seems
> that
> the it happens when we start Geoserver and there is no data in the table
> that the layer is in. If we start Geoserver with data in the table it
> appears to work fine. We have several other layers that do not display
> this
> behavior when Geoserver is started and there's no data in the table. They
> all appear to be configured in a similar and correct fashion.
>
> We were able to get SQL logging and determined exactly which query is
> happening when we receive the error, and the query that's happening when we
> do not. The difference of course is the SRID. When Geoserver is started
> with no data in the table the query uses '0' as the SRID even after data is
> entered into the table. When it's started with data the query uses '4326'.
>
> We have been unable to track down what would cause this behavior and ANY
> help or direction at this point would be greatly appreciated! Here are the
> where clauses of both queries:
>
> Failing:
> WHERE
> "start_point"
> && ST_GeomFromText(
> 'POLYGON ((-83.65630587023 36.53687411899, -83.65630587023
> 39.44093367457,
> -75.34445594167 39.44093367457, -75.34445594167 36.53687411899,
> -83.65630587023 36.53687411899))', 0)
> AND ST_Intersects(
> "start_point",
> ST_GeomFromText('POLYGON ((-83.65630587023 36.53687411899,
> -83.65630587023
> 39.44093367457, -75.34445594167 39.44093367457, -75.34445594167
> 36.53687411899, -83.65630587023 36.53687411899))', 0))
>
> Succeeding:
> WHERE
> "start_point"
> && ST_GeomFromText(
> 'POLYGON ((-83.65630587023 36.53687411899, -83.65630587023
> 39.44093367457,
> -75.34445594167 39.44093367457, -75.34445594167 36.53687411899,
> -83.65630587023 36.53687411899))', 4326)
> AND ST_Intersects(
> "start_point",
> ST_GeomFromText('POLYGON ((-83.65630587023 36.53687411899,
> -83.65630587023
> 39.44093367457, -75.34445594167 39.44093367457, -75.34445594167
> 36.53687411899, -83.65630587023 36.53687411899))', 4326))
>
> Please let me know what else I can provide.
>
> Thanks in advance!
> Jason
>
>
>
> --
> Sent from:
> http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html
>
>
> _______________________________________________
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
--
Regards, Andrea Aime == GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime
@geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054
Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339
8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it
------------------------------------------------------- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
