Global Mapper Pro Coming Soon

Export Error

When exporting to a postgres db the file is exported successfully but the spatial reference is incremented by one resulting in a reference of 900914 vice 900913. Is there a way to set the spatial reference so it will come across properly??

Answers

  • bmg_bobbmg_bob Global Mapper Programmer Posts: 2,300
    What version of Global Mapper are you using?  What projection does the data you are exporting use?  What was the source data type? How is that projection encoded in your data (e.g., PRJ file, TAB file, etc.)?

    It sounds like you may have data that is in the Google Mercator projection, but it is identified such that the EPSG code did not match up with what is in your PostGIS spatial reference tables.  In that case, the projection would be added with a code one greater than the largest code currently in your table.  Since the PostGIS tables typically have 900913 (Google) as the largest value, the next one would be 900914.  Here is a link to some information about the EPSG codes used for the Google projection.
  • Hi

    I am using GM V17

    +proj=longlat +datum=WGS84 +no_defs

    The source data came from An ESRI file gdb

    There is a PRJ file

    The destination db has a spatial reference 900913

    So I'm guessing you are correct and the file is being incremented by one

    TIA

Sign In or Register to comment.