[Benchmarking] 4-dimensional data in the postgis database?
Paul Ramsey
pramsey at opengeo.org
Fri Aug 13 14:11:27 EDT 2010
Some of the features have legitimate 3d values...
select asewkt(the_geom) from building limit 1;
SRID=4326;MULTIPOLYGON(((-8.40222993700407 42.8050499679355 206.8
0,-8.40236966889325 42.8050182858188 207.1 0,-8.40239837068399
42.8050859669865 207.1 0,-8.40226476888771 42.8051167890218 206.3
0,-8.40222993700407 42.8050499679355 206.8 0)))
Should I force mine down to 2D for consistency?
P
On Fri, Aug 13, 2010 at 10:56 AM, Smith, Michael ERDC-CRREL-NH
<michael.smith at usace.army.mil> wrote:
> When I loaded into Oracle, I specified dim=2 so that is what got created.
>
> Mike
>
>
> On 8/13/10 10:23 AM, "Paul Ramsey" <pramsey at cleverelephant.ca> wrote:
>
>> It's what was provided... Not the best thing for performance, but everyone is
>> on the same level, unless Oracle dropped those dimensions, heaven forfend.
>>
>> P.
>>
>> On 2010-08-13, at 2:43 AM, Andrea Aime <aaime at opengeo.org> wrote:
>>
>>> Look here:
>>>
>>> benchmarking=# select * from geometry_columns;
>>> f_table_catalog | f_table_schema | f_table_name |
>>> f_geometry_column | coord_dimension | srid | type
>>> -----------------+----------------+---------------------------+--------------
>>> -----+-----------------+------+-----------------
>>> | public | ramp | the_geom
>>> | 4 | 4326 | MULTILINESTRING
>>> | public | contour | the_geom
>>> | 4 | 4326 | MULTILINESTRING
>>> | public | point_labels_for_geometry | the_geom
>>> | 4 | 4326 | POINT
>>> | public | building | the_geom
>>> | 4 | 4326 | MULTIPOLYGON
>>> | public | contour_0 | the_geom
>>> | 4 | 4326 | MULTILINESTRING
>>> | public | contour_1 | the_geom
>>> | 4 | 4326 | MULTILINESTRING
>>> | public | contour_2 | the_geom
>>> | 4 | 4326 | MULTILINESTRING
>>> | public | contour_3 | the_geom
>>> | 4 | 4326 | MULTILINESTRING
>>> | public | contour_4 | the_geom
>>> | 4 | 4326 | MULTILINESTRING
>>> | public | contour_5 | the_geom
>>> | 4 | 4326 | MULTILINESTRING
>>> | public | contour_6 | the_geom
>>> | 4 | 4326 | MULTILINESTRING
>>> | public | contour_7 | the_geom
>>> | 4 | 4326 | MULTILINESTRING
>>> | public | industry | the_geom
>>> | 4 | 4326 | MULTIPOLYGON
>>> | public | motorway | the_geom
>>> | 4 | 4326 | MULTILINESTRING
>>> | public | point_labels_no_geometry | the_geom
>>> | 4 | 4326 | POINT
>>> | public | road | the_geom
>>> | 4 | 4326 | MULTILINESTRING
>>> | public | settlement | the_geom
>>> | 4 | 4326 | MULTIPOLYGON
>>> | public | track | the_geom
>>> | 4 | 4326 | MULTILINESTRING
>>> (18 rows)
>>>
>>> benchmarking=# select ST_AsEWKT(the_geom) from contour_0 limit 1;
>>> st_asewkt
>>>
>>> -----------------------------------------------------------------------------
>>> ---------------------------------------------------------------
>>> ----------------
>>> SRID=4326;MULTILINESTRING((2.47923685856342 42.3170588118108 -9999
>>> 0,2.47924854799622 42.3171129031747 -9999 0,2.47923559621537 42.31721190
>>> 53844 -9999 0))
>>> (1 row)
>>>
>>> Ah hem... is this intended?
>>>
>>> Cheers
>>> Andrea
>>>
>>> --
>>> Andrea Aime
>>> OpenGeo - http://opengeo.org
>>> Expert service straight from the developers.
>>>
>>> _______________________________________________
>>> Benchmarking mailing list
>>> Benchmarking at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/benchmarking
>> _______________________________________________
>> Benchmarking mailing list
>> Benchmarking at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/benchmarking
>
> _______________________________________________
> Benchmarking mailing list
> Benchmarking at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/benchmarking
>
More information about the Benchmarking
mailing list