-
-
Notifications
You must be signed in to change notification settings - Fork 307
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
[Bug] Attribute tables vector layers in Natural Earth sample dataset not readable #4172
Comments
The problem might be with a dbf backend being used. I have created a sample data set with the same layers as the Natural Earth full data set, using sqlite as backend, and that works without problem for me (you can download it from https://ecodiv.earth/share/natural_earth_dataset.zip). Not sure if the problem is with my setup, but irrespectively, is there a reason to use a dbf backend instead of sqlite? |
Yes, the issue is dbf as the default backend in that project, it's an old one. Can we use your modified version to upload to the website? @neteler what do you think? |
Since the procedure (https://grasswiki.osgeo.org/wiki/Convert_all_GRASS_6_vector_maps_to_GRASS_7) is quite some work, using the donated updated version by @ecodiv would be very welcome! Was this procedure used? In wxgui, the URL is stored here: grass/gui/wxpython/startup/locdownload.py Line 75 in cb013cc
which points to https://zenodo.org/record/3968936/files/natural-earth-dataset.tar.gz In my view, the correct way to update would be
|
Hi @neteler no, I downloaded the data anew. However, I have now created an updated dataset using the steps as outlined in the link you provided. |
@neteler @veroandreo @baharmon And below the link to the updated global_dataset dataset. Note that I replaced two data layers, roads and railroads with newly downloaded and imported Natural Earth layers, because the one in the original global data set did not contain attribute tables. |
I like it much better to have the dataset updated, too :-) Thanks @ecodiv . |
May I suggest to add a version into the file names to avoid confusion which one is based on the old data and which one contains fresh Natural Earth data? |
OK, let me create for both datasets new versions with all data layers based on what is currently available on Natural Earth, that makes it less confusing. Will do that today or tomorrow. @baharmon, as this would be a new version, would it be OK if I add one or two extra layers to the global data set? |
@baharmon @veroandreo @neteler I recreated the data sets (global data set and natural_earth_dataset) with the latest layers, and with the following changes:
The links to the data sets: |
@neteler @veroandreo @ecodiv I have uploaded both datasets to Zenodo and added @ecodiv as a contributor, but have not yet published them. Please let me know if you would like to review entries. Perhaps we should add GRASS Development team as a contributor too? Here are drafts of the 2.0.0 versions of the Natural Earth Dataset and the Global Dataset. |
Good idea |
@neteler @veroandreo @ecodiv Published. Here are the DOIs. Theses are the DOIs for all records which will resolve to the latest release. Will open an issue on grass-website to update the global dataset links.
|
Describe the bug
The attribute tables of the vector layers that come with the Natural Earth Sample dataset that you can install from within GRASS GIS are not readable. Trying to open gives an error message (see screenshot below). After dismissing the error message, an empty attribute table opens. The same is true if you download (presumably the same) dataset from the website and for the full world dataset.
To reproduce
Screenshots
System description
version=8.4.0dev
date=2024
revision=aa1ba17ef8
build_date=2024-07-06
build_platform=x86_64-pc-linux-gnu
build_off_t_size=8
libgis_revision=bb40fdd5a0
libgis_date=2024-06-18T13:26:55+00:00
proj=9.4.0
gdal=3.8.4
geos=3.12.1
sqlite=3.45.1
Additional context
Reporting here because it influences the experience of grass gis, but perhaps better to report in the grass-website repository?
The text was updated successfully, but these errors were encountered: