FacilityID

[rsaathoff]

Something is different with the facilityid from the old tool to the new tool. One issue is that it needs to be named FACILITYID in all caps; however I tried just renaming the column heading and it still didn't like the file on that field.

[steveoh]

What are your inputs to the tool with their data sources?

[rsaathoff]

opensgid.environment.petroleum_storage_tank_facilities

[steveoh]

postgres has all lowercase field names. Why do you think it needs to be uppercase?

[rsaathoff]

The old tool or perhaps the source had uppercase and the tool I use to import is expecting uppercase for some reason. The programmer that designed the import tool has retired and nobody can work on it right now.

[steveoh]

Yeah, the SGID you used to connect to was upper cased. That isn't the case any longer. I suppose you could bring it local and rename it and use that as the source.

[rsaathoff]

if I change the view that supplies the opensgid so it is uppercase will that change it to uppercase in the opensgid layer or no?

[steveoh]

You have no edit rights in the open sgid. I don't think any view changes will make a difference. That may only be presentational or an alias for your project. If that works for you then great. But this isn't something we can fix. If you agree we can close this issue.

[rsaathoff]

I don't agree. How do we change the open sgid?

[steveoh]

You don't. It's a database convention. Every postgresql database is lowercase fields.

[rsaathoff]

hmm

[steveoh]

The programmer that designed the import tool has retired and nobody can work on it right now.

Gaining access and fixing the import tool seems like the correct solution

[rsaathoff]

k, I will see what I can do, thanks