Yes, I seen this answered. But it is not my case. I have measure yet and I do not need in generate.
But if I try repeat this case in result i do not have measure in postgis.
Did you manage to use this method? It's work?
Yes, I seen this answered. But it is not my case. I have measure yet and I do not need in generate.
But if I try repeat this case in result i do not have measure in postgis.
Did you manage to use this method? It's work?
Have you tried Using FME to create a new table where the first features contains measures? If the table has already been created and contains measures then it's possible FME is doing something silly and dropping the measures when writing to the database.
You shouldn't need to use a GeometryExtractor. FME should handele the geometries automatically with PostGIS. Just write out the data.
Yes, I seen this answered. But it is not my case. I have measure yet and I do not need in generate.
But if I try repeat this case in result i do not have measure in postgis.
Did you manage to use this method? It's work?
I think you are right that FME dropping the measure. Yes I have the table and scheme in postgis and I try insert data in db.
PS If I create new table by FME, measure are save.
So, I serche constraint in field geom in current scheme...
may be it 2d...
Yes, I seen this answered. But it is not my case. I have measure yet and I do not need in generate.
But if I try repeat this case in result i do not have measure in postgis.
Did you manage to use this method? It's work?
Ok.
Answer is:
Change type of table_name in geometry_columns on GEOMETRY M instead GEOMETRY
Change type of table_name in geometry_columns on GEOMETRY M instead GEOMETRY