-
-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Martin throwing HTTP 500 on complex geometry types #215
Comments
Can confirm that the issue relates to the complex geometry types. The base function source (changed into EPSG:28992 format which I use) does not work, providing these errors:
It can be fixed by wrapping the
This gives me the roads I need: |
Question: as for simple geometries spatial equality seems to remain preserved, can't we include
These all resolve to true. |
I am currently trying to implement a PoC using Martin with Leaflet VectorGrid for visualizing the Basisregistratie Grootschalige Topografie (BGT), which is a standardized dataset representing a variety of objects in the Dutch public area.
I am using the following POSTGIS dump for the PoC which represents a small slice from the entire BGT (all object types in one area): https://geocatalogus.nl/dataset/bgt-imgeo-database-dumps/resource/1ae231d7-5753-4e3b-afe8-e1b2636c474d
Martin finds all table sources nicely:
(side note: although Martin apparently finds many table sources twice (? no idea why), this cannot be the cause of the issue following next, because it also occurs with the
latest.pand
table source, which is found only once.)It works nicely implementing
latest.pand_nummeraanduidingactueel
(house numbers), which has aPOINT
geometry_type
:However, when using
latest.wegdeelactueel
(road section surfaces) andlatest.pand
(building surfaces) a HTTP 500 error is thrown and nothing is displayed:What I noticed is that these have compound/set types like
CURVEPOLYGON
andMULTISURFACE
For some reason I am not seeing any logs whatsoever related to the error, despite performing the following:
docker
based version, starting the container with theRUST_LOG
export provided as an env variable (-e ...
)windows
based version (running with WSL2), firstexport
-ing theRUST_LOG
variable.Martin thus seems to be struggling with these types :)
I have thought about this a bit more and when converting my data into GeoJSON format before (ultimately failed; nobody wants to download a 250MB GeoJSON every time they use the app) I had to use https://postgis.net/docs/ST_CurveToLine.html first before I could use
ST_AsGeoJSON
. One possible fix is to create a function source that does this for me and then using that in Leaflet.However, it can still be a good idea to support these more complex/compound types out of the box if possible :)
Thanks!
The text was updated successfully, but these errors were encountered: