New answers tagged geometry
To help with the "proper definition" part of your question; you have looked at https://en.wikipedia.org/wiki/Convex_hull and gotten what could well be considered a "proper" definition but found it lacking, so perhaps a more "useful" definition For every point inside a convex hull, a straight line to any point not within the hull will only intersect the hull ...
Changing the geometryName property won't have any effect, because the geometry field is defined in the geoServer layer. Create two views which expose each geometry column: See here for an example. Then create layers in geoserver on each view. You can then programmatically change the source layer name in your WFS layer source and call refresh().
When you're using the draw tools, use the draw-end event to get to the geometry that was just created. This is shown in a couple of samples: Add graphics to a map and Drawing tools. If you need your geometry in geographic coordinates (AKA wgs84 AKA lat/long), listen to the draw-complete event as the object your callback gets will have a geographicGeometry ...
The precision of the decimal field is 0. Due to limitations in the dbf format and shapefiles, you will have to create a new column. Make the decimal precision in that 5 or more.
The usual way to deal with this situation is to expose the geometry column you want using a view. Then just point GeoServer at the view rather than the table: CREATE OR REPLACE VIEW parcels_3857 AS SELECT "PARCEL_VIEW".geom_3857 as geom FROM "PARCEL_VIEW";
Is it feasible to just manually edit the vertices and remove the self intersections? I do this a lot (using QGIS because it seems to be less picky about this issue). QGIS also has a 'Check Geometry' tool that will show you where all the self intersections are. I know you said you're running arc but this might be a helpful approach if nothing else is ...
You should cast all geometry DB fields to geography and then do the calculations: SELECT polys.id, sum(st_length(st_intersection(geography(lines.the_geom),geography(polys.the_geom))))/1000 total_lengths from schema.table1polys polys schema.table2lines lines on ST_Intersects(geography(lines.the_geom),geography(polys.the_geom));
With a table in UTM SELECT ST_X(table.geometry) AS X1, --point x ST_Y(table.geometry) AS Y1, --point y ST_X(ST_TRANSFORM(table.geometry,4674)) AS LONG, -- longitude point x SIRGAS 2000 ST_Y(ST_TRANSFORM(table.geometry,4674)) AS LAT, --latitude point y SIRGAS 2000 ST_ASTEXT(table.geometry) AS XY, --wkt point xy ST_ASTEXT(ST_TRANSFORM(table.geometry,4674)) ...
Perhaps a bug in setSimplifyHints? >>>current_layer.simplifyMethod().setSimplifyHints(QgsVectorSimplifyMethod.NoSimplification) >>>int(current_layer.simplifyMethod().simplifyHints()) == QgsVectorSimplifyMethod.NoSimplification False >>>int(current_layer.simplifyMethod().simplifyHints()) == ...
Top 50 recent answers are included