darkblueb

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • in reply to: Invalid import into postgis #4120

    darkblueb
    Participant

    =============================================================

    67 shp tables attempted, 13 errors


    ERROR: 10m_lakes_europe;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_glaciated_areas;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_lakes;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_ocean;First argument geometry could not be converted to GEOS: IllegalArgumentException: Invalid number of points in LinearRing found 3 – must be 0 or >= 4


    ERROR: 10m_land;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_minor_islands;First argument geometry could not be converted to GEOS: IllegalArgumentException: Invalid number of points in LinearRing found 3 – must be 0 or >= 4


    ERROR: 10m_geography_regions_polys;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_bathymetry_L_0;First argument geometry could not be converted to GEOS: IllegalArgumentException: Invalid number of points in LinearRing found 3 – must be 0 or >= 4


    ERROR: 10m_bathymetry_K_200;First argument geometry could not be converted to GEOS: IllegalArgumentException: Invalid number of points in LinearRing found 3 – must be 0 or >= 4


    ERROR: 10m_bathymetry_I_2000;First argument geometry could not be converted to GEOS: IllegalArgumentException: Invalid number of points in LinearRing found 3 – must be 0 or >= 4


    ERROR: 10m_bathymetry_H_3000;First argument geometry could not be converted to GEOS: IllegalArgumentException: Invalid number of points in LinearRing found 3 – must be 0 or >= 4


    ERROR: 10m_bathymetry_F_5000;First argument geometry could not be converted to GEOS: IllegalArgumentException: Invalid number of points in LinearRing found 3 – must be 0 or >= 4


    ERROR: 10m_admin_1_states_provinces_shp;First argument geometry could not be converted to GEOS: IllegalArgumentException: Invalid number of points in LinearRing found 3 – must be 0 or >= 4

    in reply to: Invalid import into postgis #4118

    darkblueb
    Participant

    a few more nits, from a related tool


    — 10m_coastline —

    Warning 1: Longitude 180.000011 has been modified to fit into range [-180,180]. This warning will not be issued any more

    .

    — 10m_geographic_lines —

    Warning 1: Longitude -180.000015 has been modified to fit into range [-180,180]. This warning will not be issued any more

    .

    .

    — 10m_reefs —

    Warning 1: Longitude -180.000041 has been modified to fit into range [-180,180]. This warning will not be issued any more

    .

    .

    — 10m_land —

    Warning 1: Longitude 180.000011 has been modified to fit into range [-180,180]. This warning will not be issued any more

    .

    .

    — 10m_geography_marine_polys —

    Warning 1: Longitude -180.000144 has been modified to fit into range [-180,180]. This warning will not be issued any more

    ERROR 1: Latitude 90.001225 is invalid. Valid range is [-90,90]. This warning will not be issued any more

    .

    .

    — 10m_antarctic_ice_shelves_polys —

    Warning 1: Longitude 180.000011 has been modified to fit into range [-180,180]. This warning will not be issued any more

    .

    .

    — 10m_antarctic_ice_shelves_lines —

    Warning 1: Longitude -180.000015 has been modified to fit into range [-180,180]. This warning will not be issued any more

    .

    .

    — 10m_graticules_5 —

    Warning 1: Longitude -180.003348 has been modified to fit into range [-180,180]. This warning will not be issued any more

    ERROR 1: Latitude 90.000011 is invalid. Valid range is [-90,90]. This warning will not be issued any more

    .

    .

    — 10m_graticules_10 —

    Warning 1: Longitude -180.003348 has been modified to fit into range [-180,180]. This warning will not be issued any more

    ERROR 1: Latitude 90.000011 is invalid. Valid range is [-90,90]. This warning will not be issued any more

    .

    .

    .

    .

    — 10m_graticules_30 —

    Warning 1: Longitude 180.000000 has been modified to fit into range [-180,180]. This warning will not be issued any more

    ERROR 1: Latitude 90.000011 is invalid. Valid range is [-90,90]. This warning will not be issued any more

    .

    .

    .

    — 10m_graticules_1 —

    Warning 1: Longitude -180.003348 has been modified to fit into range [-180,180]. This warning will not be issued any more

    ERROR 1: Latitude 90.000011 is invalid. Valid range is [-90,90]. This warning will not be issued any more

    .

    .

    — 10m_graticules_15 —

    Warning 1: Longitude -180.003348 has been modified to fit into range [-180,180]. This warning will not be issued any more

    ERROR 1: Latitude 90.000011 is invalid. Valid range is [-90,90]. This warning will not be issued any more

    .

    .

    — 10m_wgs84_bounding_box —

    Warning 1: Longitude -180.003339 has been modified to fit into range [-180,180]. This warning will not be issued any more

    ERROR 1: Latitude 90.000022 is invalid. Valid range is [-90,90]. This warning will not be issued any more

    .

    .

    .

    .

    — 10m_graticules_20 —

    Warning 1: Longitude -180.003348 has been modified to fit into range [-180,180]. This warning will not be issued any more

    ERROR 1: Latitude 90.000011 is invalid. Valid range is [-90,90]. This warning will not be issued any more

    .

    .

    .

    — 10m_admin_0_sovereignty —

    Warning 1: Longitude 180.000258 has been modified to fit into range [-180,180]. This warning will not be issued any more

    — 10m_admin_0_map_subunits —

    Warning 1: Longitude 180.000258 has been modified to fit into range [-180,180]. This warning will not be issued any more

    .

    .

    — 10m_admin_0_boundary_lines_maritime_indicator —

    Warning 1: Longitude -180.000496 has been modified to fit into range [-180,180]. This warning will not be issued any more

    .

    .

    — 10m_admin_0_pacific_groupings —

    Warning 1: Longitude 180.000052 has been modified to fit into range [-180,180]. This warning will not be issued any more

    .

    .

    — 10m_admin_0_scale_ranks —

    Warning 1: Longitude 180.000258 has been modified to fit into range [-180,180]. This warning will not be issued any more

    .

    .

    — 10m_admin_0_scale_ranks_with_minor-islands —

    Warning 1: Layer name ’10m_admin_0_scale_ranks_with_minor-islands’ adjusted to ’10m_admin_0_scale_ranks_with_minor_islands’ for XML validity.

    Warning 1: Longitude 180.000258 has been modified to fit into range [-180,180]. This warning will not be issued any more

    .

    .

    — 10m_admin_1_states_provinces_shp —

    Warning 1: organizePolygons() received an unexpected geometry.

    Either a polygon with interior rings, or a polygon with less than 4 points,

    or a non-Polygon geometry. Return arguments as a collection.

    Warning 1: Geometry of polygon of fid 22 cannot be translated to Simple Geometry. All polygons will be contained in a multipolygon.

    Warning 1: organizePolygons() received an unexpected geometry.

    Either a polygon with interior rings, or a polygon with less than 4 points,

    or a non-Polygon geometry. Return arguments as a collection.

    Warning 1: Geometry of polygon of fid 1368 cannot be translated to Simple Geometry. All polygons will be contained in a multipolygon.

    Warning 1: Longitude -180.000015 has been modified to fit into range [-180,180]. This warning will not be issued any more

    .

    .

    — 10m_admin_0_countries —

    Warning 1: Longitude 180.000258 has been modified to fit into range [-180,180]. This warning will not be issued any more

    .

    .

    — 10m_admin_0_map_units —

    Warning 1: Longitude 180.000258 has been modified to fit into range [-180,180]. This warning will not be issued any more

    in reply to: Invalid import into postgis #4117

    darkblueb
    Participant

    looking better!

    =============================================================

    67 shp tables attempted, 2 errors


    ERROR: 10m_land;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_admin_1_states_provinces_shp;First argument geometry could not be converted to GEOS: IllegalArgumentException: Invalid number of points in LinearRing found 3 – must be 0 or >= 4

    real 3m29.797s

    user 0m41.840s

    sys 0m5.180s

    in reply to: Invalid import into postgis #4115

    darkblueb
    Participant

    more informative errors in PostGIS trunk, sans bathymetry…

    =============================================================

    55 shp tables attempted, 24 errors


    ERROR: 10m_lakes_europe;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_glaciated_areas;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_lakes;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_ocean;First argument geometry could not be converted to GEOS: IllegalArgumentException: Invalid number of points in LinearRing found 3 – must be 0 or >= 4


    ERROR: 10m_land;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_minor_islands;First argument geometry could not be converted to GEOS: IllegalArgumentException: Invalid number of points in LinearRing found 3 – must be 0 or >= 4


    ERROR: 10m_geography_regions_polys;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_admin_1_states_provinces_shp;First argument geometry could not be converted to GEOS: IllegalArgumentException: Invalid number of points in LinearRing found 3 – must be 0 or >= 4

    in reply to: Invalid import into postgis #4113

    darkblueb
    Participant

    hmm learning more here…

    PostGIS 2.0 “trunk” (under development) provides this on the bathymetry

    =============================================================

    12 shp tables attempted, 15 errors


    ERROR: 10m_bathymetry_L_0;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_bathymetry_K_200;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_bathymetry_I_2000;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_bathymetry_H_3000;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined


    ERROR: 10m_bathymetry_F_5000;GEOSBuffer: IllegalArgumentException: Ring has fewer than 3 points, so orientation cannot be determined

    in reply to: Invalid import into postgis #4111

    darkblueb
    Participant

    fyi- here is the error log from the latest script.. 12 files failed to convert…

    =============================================================

    67 shp tables attempted, 39 errors


    ERROR: 10m_lakes_europe;GEOS buffer() threw an error!


    ERROR: 10m_glaciated_areas;GEOS buffer() threw an error!


    ERROR: 10m_lakes;GEOS buffer() threw an error!


    ERROR: 10m_ocean;POSTGIS2GEOS conversion failed


    ERROR: 10m_land;GEOS buffer() threw an error!


    ERROR: 10m_minor_islands;POSTGIS2GEOS conversion failed


    ERROR: 10m_geography_regions_polys;GEOS buffer() threw an error!


    ERROR: 10m_bathymetry_L_0;POSTGIS2GEOS conversion failed


    ERROR: 10m_bathymetry_K_200;POSTGIS2GEOS conversion failed


    ERROR: 10m_bathymetry_I_2000;POSTGIS2GEOS conversion failed


    ERROR: 10m_bathymetry_H_3000;POSTGIS2GEOS conversion failed


    ERROR: 10m_bathymetry_F_5000;POSTGIS2GEOS conversion failed


    ERROR: 10m_admin_1_states_provinces_shp;POSTGIS2GEOS conversion failed

    in reply to: Invalid import into postgis #4110

    darkblueb
    Participant

    well I have the gnarly quoting worked out now.. it was the upper case letters in the field names and table names that were hard.. In general, stick to lower case letters in table names and field names if at all possible.. as far as leading numbers go, you can pre-pend a single letter and still use your naming, if you choose to.. as said, this script now handles it, its just going to make other scripts in the future harder,also…

    in reply to: Invalid import into postgis #4108

    darkblueb
    Participant

    I am building a script that does the auto-cleaning..

    Postgres has its own behaviour about table names and field names..

    In particular, lower case is the default for most things, and starting with numbers requires special quoting. I am trying to catch all the small gotcha’s , but the bathymetry table and field names are particularly challenging.. if possible, maybe the naming could be adjusted the next time around

    in reply to: Invalid import into postgis #4107

    darkblueb
    Participant

    hi- I have done some preliminary investigation with PostGIS. I ran ~67 tables through PostGIS st_buffer(0), (19 failed for various reason, including all of the bathymetry tables) but its a start. More to come…

Viewing 9 posts - 1 through 9 (of 9 total)