...
- e.g. Stanyan Blvd vs Stanyan St (nearest one is Blvd but AVS says St - we should choose BLVD)
- e.g. Broadway vs Broadway St (there is no Broadway St - only alternative is Broadway)
Right now the ETL generates SQL but the SQL is not directly usable because AVS uses char(2) while EAS uses char(3 or 4?).
Because of this the SQL may not be useful.
Val:
Is there something else we can do here instead of this SQL?
For example, I was thinking of adding 2 columns
- update_field ('street_type')
- update_value ('AVENUE')
That way you could construct your own SQL.
link to recorded maps using APN
...