I should have mentioned that I am still getting EH data even after that last step of reinstalling Django and Elastic Search.
Thanks, Scott On Wednesday, October 22, 2014 3:46:38 PM UTC-5, Scott Branting wrote: > > Dear Alexei, > > Thank you for your quick reply. > > Yes, I'm a bit perplexed as well. > > Yes, I am referencing the same entitytypeid's found in the resource > graphs. I've sent you the file so that you can look over what I put > together and see if there is a fault there. > > I was reinstalling a bit out of order: start elasticsearch, > install_arches_db, > build, and install_packages. I've changed that and followed the steps > you specified: install_arches_db, start elasticsearch, and > install_packages. I'm still getting persistent EH data that shows up every > time that I view the localhost:8000/Arches/index.htm. I then tried > stepping back and reinstalling Django and Elastic Search and then > continuing on with the install and build and loading of the data management > package. > > Thanks, > > Scott > > > On Wednesday, October 22, 2014 1:28:31 PM UTC-5, Alexei Peters wrote: >> >> HI Scott, >> Welcome to Archesproject! >> From what you've said in your email you should be seeing your new data. >> Does your new data reference the same entitytypeid's found in the existing >> resource graphs? >> Maybe you could send me your new resource_info file and I could test >> locally. Rerunning the install_arches_db script should delete all the >> contents from the database, so I'm a bit perplexed as to why you're still >> seeing the EH data. >> Did you start the elasticsearch process before you reran the >> installation? The steps to reinstall are: install_arches_db, start >> elasticsearch, and install_packages. >> Let me know if I can be of further assistance. >> Cheers, >> Alexei >> >> >> >> >> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173 >> >> On Wed, Oct 22, 2014 at 7:33 AM, Scott Branting <[email protected]> >> wrote: >> >>> >>> We've been following this thread while attempting to import our own data >>> into our installation of Arches v2 on a windows 7 x64 machine. We've >>> modified and replaced the resource_info.csv file with a small amount of our >>> test data and put the new file in the CDS package. We've then gone back >>> through the steps of clearing the running install_arches_db, build, and >>> install_packages. However, at the end of that we're still seeing the test >>> data from English Heritage rather than our new data on the localhost. Am I >>> missing a step(s)? Do we need to make further alterations to certain >>> authority documents or resource graphs? I'm assuming that if it was a >>> syntax error in the new resource_info.csv file that it would have errored >>> out during the build and install process. Is that correct? >>> >>> Thank you and have a great day, >>> >>> Scott >>> >>> >>> On Tuesday, October 14, 2014 3:21:20 AM UTC-5, Eloise Stancioff wrote: >>>> >>>> Thanks Adam! Hopefully, all will go well! >>>> >>>> Have a nice day >>>> Eloise >>>> >>>> On Mon, Oct 13, 2014 at 7:34 PM, Adam Lodge <[email protected]> wrote: >>>> >>>>> Eloise, >>>>> >>>>> From the perspective of a clean Arches install, the order of >>>>> operations would be as follows: >>>>> >>>>> 1. Prepare your authority documents files (including administrative >>>>> area) >>>>> 2. Populate the resource_info file with your own data - per the >>>>> example I gave you >>>>> 3. Run the build process (including data load) >>>>> 4. Configure your settings (including map_config.) >>>>> >>>>> Given that rosy scenario, everything should be easy - assuming your >>>>> data are perfectly set up. >>>>> >>>>> On the front of perfectly set up data… another point of note about >>>>> administrative area authority document: You will want to either delete or >>>>> modify your ADMINISTRATIVE SUBDIVISION AUTHORITY DOCUMENT.values.csv file >>>>> to be consistent with your administrative area data. Specifically, you >>>>> will want to add the appropriate "admin area type" values and remove the >>>>> ones with value type of "geometry". >>>>> >>>>> In reality though, it is likely that you have already attempted to >>>>> build and load data, and that will require some backtracking on the >>>>> software install that Alexei is more qualified to chime in on than I am. >>>>> >>>>> Unless you already know that this order of operations will not work >>>>> for you, then give it a shot. I may have to pass the torch to Alexei >>>>> though on next steps if it doesn't work. >>>>> >>>>> Adam >>>>> >>>>> -- >>>>> Adam Lodge >>>>> Geospatial Systems Consultant >>>>> Farallon Geographics >>>>> 415.317.6625 >>>>> >>>>> >>>>> >>>> -- >>> -- 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. >>> >> >> -- -- 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.
