Decide on columns in fish_tracking_receivers

inbo / fish-tracking

🐟 Collection of scripts for processing and analysing fish tracking data

3 stars 0 forks source link

Decide on columns in fish_tracking_receivers #6

Closed peterdesmet closed 9 years ago

peterdesmet commented 9 years ago

[x] cartodb_id
[x] the_geom
[x] battery_empty_at
[x] deployed_at
[x] inbo_code
[x] location
[x] location_manager_id
[x] project
[x] receiver_code
[x] receiver_id
[x] remarks
[x] removed_at
[x] created_at
[x] updated_at

The following field was mentioned in #3:

[x] receiver_owner

Should we add that one?

peterdesmet commented 9 years ago

To calculate x/y in Lambert; useM ST_Y(ST_Transform(the_geom,31370)) as y_from_geom.

Since we rounded the coordinates to 7 decimals, the calculated Lambert x/y deviate from the original, but only after 2 decimals. That means they're correct up to centimeters, which is good enough.

ammouton commented 9 years ago

no should not be added however, the colums that I ticked should be added as well I guess.. I assume Ine already gave you some feedback on this since we discussed this together

peterdesmet commented 9 years ago

@ammouton, two more specific questions:

Do you prefer location_manager or river_manager. My preference goes to the first. _Note: since we move this to a separate table (which I have called fish_tracking_contacts), the field will be more something link location_manager_id._
Should the field receiver_owner be added?

ammouton commented 9 years ago

receiver owner can be removed location manager is ok; Ine prefers river manager since the location manager is actually a river manager :-)