New to FME. I can't figure out why my writer (a .gdb) isn't writing anymore. I built a step by step PointOnArea inspection on 4.5mil addresses against specific shapefile polygons. I keep all 4.5mil and I just add a column that represents each polygonarea. In AttrMgr I reassign the 1's and 0's to Yes or NO. Everything runs awesome until I try to write the data. It stops immediately. The transformer message is very long but pretty much says something is wrong with every column and row.
Page 1 / 1
I think it should be a 1 or a 0, not a yes or no?
it is, but my customer wanted that translated to a yes and no. So I used an Attribute Manager to change what is > 0 is YES and what is not NO. So is that what messed me up? There's got to be way to do this. My client doesn't want 1's and 0's.
it is, but my customer wanted that translated to a yes and no. So I used an Attribute Manager to change what is > 0 is YES and what is not NO. So is that what messed me up? There's got to be way to do this. My client doesn't want 1's and 0's.
I think another way to have it show YES / NO while still using 0 /1 you will have to change it in Database itself. If you can editing schema without causing any problems with your client, you could use ArcPro to update the Domain Description to Yes / No.
Under code for that particular domain for CODE 0 under Description Yes and for CODE 1 under Description No.
as you can see the value show Yes when you viewing the GDB in arcpro, but when you view it in FME since FME using CODE for the domain it will show as 0.
But to answer your question why the GDB Writer is now failed because Yes/No that you change using attribute manager is no longer in the gdb schema. The schema was expecting only 0 or 1 value in that domain field.
Hope this helps.
I think another way to have it show YES / NO while still using 0 /1 you will have to change it in Database itself. If you can editing schema without causing any problems with your client, you could use ArcPro to update the Domain Description to Yes / No.
Under code for that particular domain for CODE 0 under Description Yes and for CODE 1 under Description No.
as you can see the value show Yes when you viewing the GDB in arcpro, but when you view it in FME since FME using CODE for the domain it will show as 0.
But to answer your question why the GDB Writer is now failed because Yes/No that you change using attribute manager is no longer in the gdb schema. The schema was expecting only 0 or 1 value in that domain field.
Hope this helps.
oh interesting... I guess I was so focused on staying within FME and fixing it there that I didn't think to bring it over into ArcPro and fixing it there. Thank you for suggesting.