PostGIS

I just noticed the c|a|d|p options are missing in the gui. So I assume it always does a create? This is a feature I personally use often, so would be nice to have it. (c|a|d|p) These are mutually exclusive options: I guess we can make it a ... [More] drop down or radio (though typing it in for now would work fine and defaulting it to c) But perhaps its too difficult to implement for this first go around so will tag for future. [Less]

I just noticed the c|a|d|p options are missing in the gui. So I assume it always does a create? This is a feature I personally use often, so would be nice to have it. (c|a|d|p) These are mutually exclusive options: I guess we can make it a ... [More] drop down or radio (though typing it in for now would work fine and defaulting it to c) But perhaps its too difficult to implement for this first go around so will tag for future. [Less]

I guess its too late to squeeze this in for 1.5.0? But I think we really need an Extent function for Geography. Just noticed the Add Datastore feature doesn't work out of the box with geography because its trying to call Extent on it (well that's ... [More] the complaint I get out of the bat). I don't use that mode much anyway so I personally don't care aside from the effect on newbie user experience. Which brings up the other question that we really need to get the word out with 3rd party tools to switch to using the ST_ version of the functions if we hope to ever bury them. I guess that is a story for another day. [Less]

I guess its too late to squeeze this in for 1.5.0? But I think we really need an Extent function for Geography. Just noticed the Add Datastore feature doesn't work out of the box with geography because its trying to call Extent on it (well that's ... [More] the complaint I get out of the bat). I don't use that mode much anyway so I personally don't care aside from the effect on newbie user experience. Which brings up the other question that we really need to get the word out with 3rd party tools to switch to using the ST_ version of the functions if we hope to ever bury them. I guess that is a story for another day. [Less]

Reading the manual on ST_SimplifyPreserveTopology (1) I cannot say if it will avoid introducing intersections between polygons in a MultiPolygon?, or if it only avoids self-intersections in each polygon. This uncertainty can be cleared up by ... [More] specifying which object type(s) are referred to in the phrase "..simplification occurs on a object-by-object basis". mleslie suggested Kevin or Regina will know, and that I assign robe. (1) ​http://postgis.refractions.net/documentation/manual-svn/ST_SimplifyPreserveTopology.html [Less]

Reading the manual on ST_SimplifyPreserveTopology (1) I cannot say if it will avoid introducing intersections between polygons in a MultiPolygon?, or if it only avoids self-intersections in each polygon. This uncertainty can be cleared up by ... [More] specifying which object type(s) are referred to in the phrase "..simplification occurs on a object-by-object basis". mleslie suggested Kevin or Regina will know, and that I assign robe. (1) ​http://postgis.refractions.net/documentation/manual-svn/ST_SimplifyPreserveTopology.html [Less]

As Mark L pointed out in #212

As Mark L pointed out in #212

As Mark L pointed out in #212

Google maps has a special serialization form for linestrings/polygons, which would be handy to emit.