Track address layer #68

Closed
opened 2026-07-08 21:26:42 +00:00 by eliribble · 0 comments
Owner

Currently in the database we have an "address" table. This is populated by data that comes from Stadia. All Stadia features have a property, layer. See the stadia docs

This story is to add a field to track stadia layers on addresses. Because the set of layers is known in advance, "layer" should be a database-level enumeration. There should be a value for "unknown" which should be the default value and null should not be allowed. You'll need to create a migration with the necessary commands to update the database schema. You should also update any code that creates addresses to set the new field and ensure that the property is used from results that come from Stadia and written to newly created rows.

Currently in the database we have an "address" table. This is populated by data that comes from Stadia. All Stadia features have a property, layer. See [the stadia docs](https://docs.stadiamaps.com/geocoding-search-autocomplete/layers/) This story is to add a field to track stadia layers on addresses. Because the set of layers is known in advance, "layer" should be a database-level enumeration. There should be a value for "unknown" which should be the default value and null should not be allowed. You'll need to create a migration with the necessary commands to update the database schema. You should also update any code that creates addresses to set the new field and ensure that the property is used from results that come from Stadia and written to newly created rows.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Gleipnir/nidus-sync#68
No description provided.