Avoid varchar(max) make sure you have a Primary Key and spatially
index...ogr2ogr will index and primary key for you
On Aug 26, 2016 3:20 PM, "BMason" wrote:
> We can select 10 or so of the most important columns to display and we are
> doing this but users want to see all 200 of them, not just
Ogr2ogr works well for conversion as well as quantum gis
On Aug 26, 2016 3:20 PM, "BMason" wrote:
> We can select 10 or so of the most important columns to display and we are
> doing this but users want to see all 200 of them, not just 10. So I
> guess
> that we are forced to use something li
We can select 10 or so of the most important columns to display and we are
doing this but users want to see all 200 of them, not just 10. So I guess
that we are forced to use something like SQL server.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Shapefile-with-200
If you can't change/convert the SHP file (200+ fields? Really?) and the file
is read-only, perhaps you could try using an OGR provider connection to a
VRT file (http://www.gdal.org/drv_vrt.html) pointing to the SHP file and in
the VRT file, only select out the columns/properties of interest. That
p
Is it necessary two have 200 fields in a SHP file? Normally at that point
you are better with a spatial database
On Aug 25, 2016 6:56 PM, "BMason" wrote:
> Hello, I have a polygon shapefile with 200+ fields. Most fields are
> empty.
> When selecting one polygon to view using the selection pane
Hello, I have a polygon shapefile with 200+ fields. Most fields are empty.
When selecting one polygon to view using the selection panel in mapguide,
it is too slow to be of any use. Is there a limitation with mapguide and
shapefile fields? Is using REST a better option? If so, is there any