Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shapefile exportation #34

Open
NicoTex opened this issue Feb 22, 2019 · 4 comments
Open

Shapefile exportation #34

NicoTex opened this issue Feb 22, 2019 · 4 comments

Comments

@NicoTex
Copy link

NicoTex commented Feb 22, 2019

Two issues regarding perhaps the same problem:

  • I can't open the exported shapefile in a GIS (e.g.: ArcGIS). Error explication of ArcGis: "Number of shapes does not match the number of table records". This problem was not there last year.

  • When open shapefile in R software, it opens as a multipolygon with bioregions info not matching with Infomap website output. Last year the exported shapefile used to open in R as specific polygons for each grid cell.

Any suggestion or help ?

@jorgeciencia
Copy link

I have the same problem right now. It is impossible to make the .shp running in ArcGIS. I tried to fix the .dfb object with shapechk and lost the regions identified with InfoMap.

Does anyone know how to make the .shp file going properly in a GIS?

@jivelasquezt
Copy link

I'm experiencing the same issue with the old site (shapefile not opening in arcgis. it does open in qgis but the attribute table is incomplete-only shows one row). And the new site https://www.mapequation.org/bioregions2/ doesn't seem to have an export function enabled.

danieledler added a commit that referenced this issue Mar 7, 2022
@danieledler
Copy link
Contributor

Thanks for the update @jivelasquezt! The issue seems to be mapbox/shp-write#88. In the fix referenced above I downgraded shp-write but in a later update of dependencies I unfortunately updated shp-write again.

Now I have reverted that, so please try again.

Exportation of shapefiles will soon be available on version 2 also.

@jivelasquezt
Copy link

Thanks a lot, looking forward to trying it know. I was able to get around the issue by reading the geojson into R which didn't present any issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants