Opened 13 years ago
Closed 13 years ago
#4024 closed enhancement (wontfix)
is Force2d call redundent? (potential overhead)
Reported by: | springmeyer | Owned by: | pramsey |
---|---|---|---|
Priority: | lowest | Milestone: | |
Component: | PostGIS Interface | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: |
Description
I think ST_Asbinary calls force2d internally, but mapserver's postgis driver seems to call force2d manually as well. This is part potential optimization suggestion and part curiousity of mine of whether my assumption that this has overhead is bogus or not.
Change History (2)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
facinating. in mapnik we're barely catching up with ST_* usage in general, so this is immensely good to know directions.
Thanks paul. I guess I will close then :)
Note:
See TracTickets
for help on using tickets.
I almost took it out recently, but actually in PostGIS 2.0 it's possible AsBinary will return 3/4d objects, so forcing them to the dimensionality we want might be good. Contrariwise, it might be even BETTER to ensure the WKB handler can eat the 3/4d representations and remove the call to allow those dimensions to be accessed in MapServer (at least the Z, since mapserver can't do the M)