search

LCacheux68224 / Oursins

Analyse de flux en oursins
5 stars 3 forks source link

Origin/Destination fields not getting populated from data table #4

Open danaja opened 9 years ago

danaja commented 9 years ago

On Oursins screen the Origin/Destination drop downs don't get populated. The value drop down does. I've loaded a table with the following structure and have a shape file layer with the relevant coordinates for the points. The Geographical ID field of the "Extract coordinates from Layer" section doesn't get populated either. I'm using QGIS 2.4.

"Origin","Destination","Flow" 1610,2107,7 1610,2347,10 1610,4078,0

danaja commented 9 years ago

Went through the code and realized that those fields were accepting only string fields. I'm actually using a spatial grid which is why the locations are indices. Got it to work by adding a leading character

LCacheux68224 commented 9 years ago

Ok, I always use string fields for IDs, but I can add the possibility to use numeric fields (integer) too if need.

magerlin commented 8 years ago

As a transport planner I really like your plugin but it would be VERY nice to be able to use numeric fields as IDs since the data sources I use can vary and adding extra columns just to change data type makes your data messy in my opinion.

Bericender commented 8 years ago

I still get no valid datas found as an error message.

I have set it up as

Flow table odmatrix Origin: origin_loc Destination: destination_loc Value: value

layer: loc_known GeoID: id

Table info (odmatrix): origin_id integer (i.e. 4327) origin_loc text (i.e. 'POINT 38.0789 -5.78263) destination_id integer (i.e. 4392) destination_loc text (i.e. 'POINT 38.0289 -5.78563) value integer (i.e. 10)

Table info (loc_known): id text (i.e. '4327') location geometry (Point, 4326)