You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The City of Cupertino maintains a GIS layer of every business licensed by the city and updates it monthly. This dataset is in the public domain as a work of a California government agency. It would complement the ongoing countywide, SDP-based POI import in #23.
Unlike the SDPs, the features in this dataset lack addresses, but they do have license numbers that could potentially be joined to addresses in the license databases. The BusinessActivityType field seems to have a fixed set of values, but it’s only slightly more granular than the SDP categories, so our workflow would probably have to involve some manual review case by case. We can deprioritize or omit features with a BusinessLicenseType of HOME OCCUPATION, which seems to consist of home-based services that we’ve also had to be careful about in the SDP import for privacy reasons.
The text was updated successfully, but these errors were encountered:
A relatively small number of features have a StartOfBusinessDate, dated from circa 2005 to present. These features would also be eligible for inclusion in OpenHistoricalMap. MapRoulette isn’t currently available for OpenHistoricalMap, so we’d need a different workflow for that import. On the other hand, there’s no need for conflation with existing POIs in OHM, and conflation with buildings would look different due to a separate building import in #34.
The City of Cupertino maintains a GIS layer of every business licensed by the city and updates it monthly. This dataset is in the public domain as a work of a California government agency. It would complement the ongoing countywide, SDP-based POI import in #23.
Unlike the SDPs, the features in this dataset lack addresses, but they do have license numbers that could potentially be joined to addresses in the license databases. The
BusinessActivityType
field seems to have a fixed set of values, but it’s only slightly more granular than the SDP categories, so our workflow would probably have to involve some manual review case by case. We can deprioritize or omit features with aBusinessLicenseType
ofHOME OCCUPATION
, which seems to consist of home-based services that we’ve also had to be careful about in the SDP import for privacy reasons.The text was updated successfully, but these errors were encountered: