-
Notifications
You must be signed in to change notification settings - Fork 43
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
Update Geofabrik dbfawk files to match current shapefiles #32
Comments
tvrusso, |
I do not have time to work on testing this issue, nor downloading and viewing geofabrik shapefiles. The community will very much appreciate your efforts. If you are willing to work on this issue, please create a pull request, and maybe support it by posting screenshots and other supporting evidence that you've addressed the incompatibilities of the current set of dbfawk files in Xastir with the current set of shapefiles available from geofabrik. I have time to review pull requests, but unfortunately no spare time to spend working on Xastir myself these days. |
Thanks for the info, will work on cleaning up the files first. After I sent the files above, found I missed one and wrong name for another. Once I get the files cleaned up will look into trying that out. It will be something new to learn. |
Please create a pull request for us to review. It's great that there's a zip file, but it's been there for a few years since the OP said he was going to clean them up. |
In commit dd99425, Curt added a couple of DBFAWK files to support using shapefiles from http://download.geofabrik.de/ in Xastir.
Unfortunately, the shapefiles currently available on that web site do not match the DBFAWK files anymore. The dbf signature is different, and they have clearly changed how the feature type is stored (it's now in an fclass field instead of a type field) I have not checked what range of values the fclass field takes. It may be that the only difference is in the name of the field, but if they reorganized the values of the field, too, then this may take a little more work.
Opening this bug to solicit community assistance in getting this fixed.
The text was updated successfully, but these errors were encountered: