Probably, yes--thanks for the link. Although I am somewhat hesitant to use official administrative boundaries because I feel like perceived boundaries are often different than official boundaries. As someone walking around the Boston area, or around Stanford, I want the experience to be good everywhere---it doesn't matter much to me whether I'm officially in Boston or Cambridge or Palo Alto or Menlo park.
So these boundaries are sort of meant to be more "places" than specifically cities. But long-term indeed it might not be practical to have these custom boundaries (maybe just removing the boundaries altogether, or loosening them, is the answer)
In my region (an inner suburb of the Northeast Megalopolis) an attempt like this to use vague "place" boundaries would lead to a blur of overlapping boundaries that stretches for ~500 miles.
Comments
If there's no licensing problem, could you just import the current OSM polygons for cities?
e.g. Denver - http://polygons.openstreetmap.fr/get_geojson.py?id=1411339&p...
Based on this I found with DDG search: https://peteris.rocks/blog/openstreetmap-administrative-boun...
Probably, yes--thanks for the link. Although I am somewhat hesitant to use official administrative boundaries because I feel like perceived boundaries are often different than official boundaries. As someone walking around the Boston area, or around Stanford, I want the experience to be good everywhere---it doesn't matter much to me whether I'm officially in Boston or Cambridge or Palo Alto or Menlo park.
So these boundaries are sort of meant to be more "places" than specifically cities. But long-term indeed it might not be practical to have these custom boundaries (maybe just removing the boundaries altogether, or loosening them, is the answer)
In my region (an inner suburb of the Northeast Megalopolis) an attempt like this to use vague "place" boundaries would lead to a blur of overlapping boundaries that stretches for ~500 miles.