Latest Contributions by LindsayRaabe_FPCWA

There's a good chance that there are some offline copies (replica's?) of one of the datasets, though I still don't understand how it's such a large file when the other dataset I mentioned that it is based on is only 176MB and would also have just as many offline versions.  ... View more

We've since discovered 2 other layers are doing the same thing, though one of them is even worse with a 7.1GB file size despite being an EMPTY simple point feature service. The other is 2.1GB though it does contain 5,464,106 points.  ... View more

Thanks @KoryKramer for merging my idea with this one. I did do a search but obviously used the different words. I feel like this would be a "simple" (from a non-programmers pointless opinion) improvement that would make a big difference to a good number of people.  ... View more

It would be good if the "Add many" option which appears in many geoprocessing tools when dealing with fields had the option to change how the fields are sorted. At present using a tool (i.e. the Join Field tool) and you go to Transfer Fields section, you can either select individual fields from the provided drop down window (which are sorted as per the attribute table), or you can select "Add many" and check the boxes to add multiple fields, or all fields in a quick, easy manner. In my current use case, I'd like to preserve the ordering of the fields but when I use the Add many option, the fields are sorted alphabetically. I understand this can make it easier to find fields in long lists, but it would be good to choose what order the selected fields appear.            ... View more

I haven't tried either of those - but I definitely will give them a crack. I'm not expecting perfect results and that manual cleanup work will be required, but considering I'm working with a good portion of Western Australias roads, any reduction in data cleaning will save a good amount of time! ... View more

Just tried the Pairwise Integrate and it rejected the inputs outright. Running the INtegrate tool in a new project and browsing to the data directly gave me the same results as above ("successful" but with warnings and no data changed).  ... View more

And the map:   ... View more

I was wondering if the breaks were also superfulous. I'll try that out.  As for the logging file, when I tested it whilst logged in, it did spit out a heap of text (which for the most part I just glossed over as it was working as expected). I deleted the log file, scheduled and logged off, and when it failed, logged in to find that it didn't even create the log file - so I feel it's not actually even getting to the point of executing the script?  ... View more

Hi @Anonymous User . Thanks for the tips. I'm not experienced with the logging side of things. I ended up including the following code at the begininning of my script, tested it (which worked - got a file output with lots of stuff), reset the schedule, logged off and waited - with no joy. Just got the same LOCALAPPDATA error via the email.  import logging logging.basicConfig(filename='python.log', level=logging.DEBUG) logging.debug('Debug Message') logging.info('Info Message') logging.warning('Warning Message') logging.error('Error Message') As for the line that you say isn't required, I removed it and reduced the indentation of all the following lines but got the following error when checking, so put it back in.    ... View more