# Srgcreate.exe possible to import GPKG?

**URL:** <https://forum.cmascenter.org/t/srgcreate-exe-possible-to-import-gpkg/2875>\
**Category:** Spatial Allocator\
**Created:** [December 13, 2021, 4:04am UTC](https://forum.cmascenter.org/t/srgcreate-exe-possible-to-import-gpkg/2875 "2021-12-13T04:04:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gwangjin](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/gwangjin/32/1336_2.png) [@gwangjin](https://forum.cmascenter.org/u/gwangjin)\
**Post date:** [December 13, 2021, 4:04am UTC](https://forum.cmascenter.org/t/srgcreate-exe-possible-to-import-gpkg/2875/1 "2021-12-13T04:04:03Z")

</div>

Hello,

I used old spatial allocator `srgcreate.exe`. But I met some problem. Because my vector data is too large (\>2 GB), I cannot export my vector data to esri shapefile. I was able to export my vector data to geopackage (.gpkg). But when I run the script

> setenv WEIGHT\_FILE\_NAME $DATA/shapefiles/SouthKorea2018/320.gpkg  
> or  
> setenv WEIGHT\_FILE\_NAME $DATA/shapefiles/SouthKorea2018/320

an error message is occured:

> ERROR in /work/gwangjin/local/Spatial-Allocator/bin/64bits/srgcreate.exe: Unable to open shape file:/work/gwangjin/local/Spatial-Allocator/data/shapefiles/SouthKorea2018/320.gpkg (WEIGHT\_FILE\_NAME). Exiting…

Should I use recent pg\_srgtools?

---

<div class="post-metadata">

**Author:** ![eyth.alison](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@eyth.alison](https://forum.cmascenter.org/u/eyth.alison)\
**Post date:** [December 13, 2021, 1:26pm UTC](https://forum.cmascenter.org/t/srgcreate-exe-possible-to-import-gpkg/2875/2 "2021-12-13T13:26:14Z")

</div>

The older Spatial Allocator surrogate creation tools have some trouble with larger data and I don’t believe they support the geopackage format.

You can try the newer SurrogateToolsDB which handle larger datasets better.

Since your weight file is larger than 2 GB and can’t be stored in a Shapefile, you might research how to load the data into PostGIS.

But once it is in there, I think the newer surrogate tools should work. If not, please write again.
