Thanks for the feedback and I'm glad it sounds like it will be useful. One of the Arches team members raised a few good questions that I've addressed at least in part with some updates to the repo:
1. The example dataset is very small and was added as an afterthought, so it's use is rather limited. Eventually I'll add a more robust example dataset... 2. The scripts use a couple of non-standard python libraries, pyshp and unicodecsv, so if you may have gotten an import error if you've tried the tools already. I added instructions to the documentation for adding those packages to your own python installation. However, I also added the code for those modules directly to this repo so you don't actually have to install them separately. It's recommended that you do, though, for use in any future scripts... 3. Currently, the interface only allows for the addition of 10 entries to a new group. If you need more, you can easily edit the .conflig file directly in a text editor. Just copy/paste/rewrite. Cheers, Adam On Tuesday, May 19, 2015 at 8:51:56 AM UTC-5, Adam Cox wrote: > > Hello all, one of the results of the Arches installation I was creating > for the Cane River Heritage Area is a toolbox I made to help me convert a > bunch of shapefiles and spreadsheets I had into the .arches format. I just > updated the GitHub repository that holds these tools, > https://github.com/mradamcox/arc2arches, so feel free to use them and let > me know how it goes. > > Arches v3 has a utility for uploading shapefiles, but I had some > non-spatial tables I wanted to upload, and also some file geodatabase > tables/feature classes that would have been a messy conversion to .shp > (super long text fields, etc.). So I decided to put effort into making a > good way to convert existing data to the pipe-delimited .arches/.relations > files. I augmented the .config file (now called .conflig) strategy to > ensure that the field mapping from the input datasets could take advantage > of the GROUPID that the .arches files use. That way, a name can be > associated with its name type very easily. Also, though the .arches format > requires that you enter the conceptid instead of prefLabel, I built these > tools to run straight off of your authority documents (you'll have to enter > the path). That way, you can use prefLabels in your shapefiles/feature > classes/tables, and the script will convert that label to the correct > conceptid (e.g. from "Building" in the shapefile to "RESOURCE_TYPE:1" in > the .arches file). There is pretty good error handling at this point to > help you with that process. > > I will be posting more in the next couple of weeks, and hope to improve > these conversion tools as well... > > Cheers, > Adam > -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
