|
@postgis | |||||
|
Celebrating @shapefile day by making all my tables shapefile compliant…
UPDATE pg_attribute
SET attname = left(attname,10)
|
||||||
|
||||||
|
Matt Travis
@Yakus
|
3. pro |
|
Great descriptio
|
||
|
|
||
|
Stefan Keller
@sfkeller
|
2. pro |
|
WTH do you want to celebrate with #ShapefileDay? Ages of data loss? My three(!) cheers go for a #PostShapefileDay, December 4!
|
||
|
|
||
|
Rémi Bovard
@RemiBovard
|
3. pro |
|
I just checked my database, there is a little work to do...
SELECT attname = LEFT(attname, 10) AS is_shp_com, COUNT(1)
FROM pg_catalog.pg_attribute
GROUP BY 1;
Thanks @shapefiIe for this #ShapefileDay pic.twitter.com/cmI2Z9myHN
|
||
|
|
||
|
murat kendir
@murat_kendir
|
2. pro |
|
I use arabic notation (writing only voiceless consonant letters w ascii characters, for exp. Bldng for building), just because of shapefile limitation...
|
||
|
|
||
|
Thomas gratier
@ThomasG77
|
3. pro |
|
I will avoid the recipe as my_very_long_prefix_1colname and my_very_long_prefix_2colname will collide after
|
||
|
|
||
|
Thomas gratier
@ThomasG77
|
3. pro |
|
Instead use the table to identify issues and generate SELECT subquery to alias column directly or using view/materialized view
|
||
|
|
||
|
3XE
@3XE_GIS
|
4. pro |
|
|
||
|
christophev
@ChristopheVe
|
3. pro |
|
Shape what's that ? It's the prehistory of GIS
formats. When it was the flat data age.
|
||
|
|
||
|
Romain
@rmaziere_85
|
3. pro |
|
Et pourtant...
|
||
|
|
||