Location of the bank tables (picnic tables) managed by the Bayonne Green Areas Service.
**Collection context**
A first inventory of the bank tables was carried out in 2012.
In June 2020, following the draft participatory budget consisting of the installation of new picnic tables, the layer was updated and completed.
**Attributes**
| Champ | Alias | Type |
| — | — | | — |
| ‘ogc_fid’ | Unique ID | ‘serial’ |
| ‘date_seizure’ | Entry date | ‘date’ |
| ‘isigeo_synchro_lock’ | (internal use) | ‘varchar’ |
| ‘etat’ | State | ‘char’ | ‘etat’ |
| ‘isigeo_iduser’ | (internal use) | ‘int4’ |
| ‘code_insee’ | INSEE Code | ‘int4’ |
| ‘isigeo_user’ | (internal use) | ‘varchar’ |
| ‘angle’ | ‘float8’ |
| ‘isigeo_lot’ | (internal use) | ‘varchar’ |
| ‘date_verif’ | Verification Date | ‘date’ |
| ‘isigeo_synchro_statut’ | (internal use) | ‘varchar’ |
| ‘idetat’ | (internal use) | ‘int4’ |
| ‘localisation_code’ | Localisation code | ‘char’ |
| ‘isigeo_obj’ | (internal use) | ‘int4’ |
| ‘isigeo_statut’ | (internal use) | ‘varchar’ |
| ‘isigeo_lock’ | (internal use) | ‘varchar’ |
| ‘precision’ | Precision | ‘varchar’ |
| ‘idprecision’ | (internal use) | ‘int4’ |
| ‘accessibilite’ | Accessibility | ‘int4’ |
| ‘model’ | Model | ‘varchar’ | ‘Varchar’ |
| ‘date_pose’ | Installation date | ‘date’ |
| ‘idmodele’ | (internal use) | ‘int4’ |
| ‘photo’ | Photo | ‘varchar’ |
| ‘format’ | Format | ‘varchar’ |
| ‘access’ | Access | ‘varchar’ |
| ‘idformat’ | (internal use) | ‘int4’ |
| ‘idacces’ | (internal use) | ‘int4’ |
| ‘photo_comm’ | ‘varchar’ |
| ‘participative_budget’ | Participatory budget | ‘int4’ |
For more information, see [the metadata on the Isogeo catalog](https://open.isogeo.com/s/dfea79f9daa941fbb7fc9248309dc1c4/THU_tcV6SuOT_DsWqcQNzDenuhTV0/r/df21e3940f434b99802177e5c4ab2359).
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.