[Talk-us] TIGER 2022 PLACE dataset

[MoiraPrime]

I will add my perspective here that in the past I've used TIGER PLACE 
data to upgrade boundaries in Mississippi and add missing ones as well. 
The original TIGER boundaries in OSM may be outdated, and they sometimes 
improve them over time, so carefully looking and comparing them is 
important.

So I think if you're looking at a dataset and importing a TIGER PLACE 
boundary, and you're doing them one by one as needed, that would be fine.

To add a specific example, a couple months ago I imported the TIGER/Line 
2020 Place Shapefile for the city of Diamondhead, Mississippi (Relation: 
‪Diamondhead‬ (‪110003‬) | OpenStreetMap 
<https://www.openstreetmap.org/relation/110003>). This is a city that is 
fairly new. Previously it was simply a Census Designated Place, but 
about 10 years ago the people there officially put in the effort to get 
it established as a city government, and the City's boundary did not 
match what the original CDP boundary was. In this case it was an 
improvement to outdated data, and was personally checked by me and 
compared to the previous data.

On 1/17/2023 10:01 AM, Bill Ricker wrote:
>
>
> On Tue, Jan 17, 2023 at 8:22 AM Aleksandar Matejevic (Hi-Tech Talents 
> LLC) via Talk-us <talk-us at openstreetmap.org> wrote:
>
>     I have a question regarding TIGER 2022 PLACE dataset
>     (https://www2.census.gov/geo/tiger/TIGER2022/PLACE/).
>     Is it OK with the community to add these polygons to the OSM?
>
>
> Can you point to the description of what these PLACE polygons 
> represent and what meta-data comes with each polygon?
>
> What are they in OSM terms? Are they Admin boundaries?
>
> (Do we even consider US Census CDP, Census Designated Place, a 
> mappable entity?)
>
>     I saw there were some imports of the previous datasets in the past
>     years, but lot of polygons are still missing,
>
>
> Can you provide (an) example(s) of what's missing from OSM but in 
> TIGER 2022 PLACE that would be beneficial in OSM?
>
>     and license looks to be compatible with the OSM one.
>
>
> I expect so from history, but for the record of the conversation, it 
> would be good to link and quote it here.
>
>     I am not talking about mass import of the data,
>
>
> Ok good , that's a very different discussion.
>
>     but using polygons and adding them one by one if they are not
>     already added and improving geometries of the existing ones.
>     What is the opinion on this effort?
>
>
> Using individual polygons of compatible license to improve existing 
> polygons or to start a missing but useful polygon of a sort we are 
> trying to curate seems (almost*) unobjectionable.
>
> *Provided that there isn't a better source of compatible license 
> easily available for the polygon in question.
> (E.g. if a specialist agency has lakes, forests that are more refined 
> than Census's, we'd prefer theirs.
> US Census studies settlements for purposes of the enumeration - 
> notoriously did not record One Way direction as Enumerators walk their 
> blocks in cities - not uninhabited wildlands, so will likely have 
> fewer points in a polygon that indicates "no one lives here", while 
> having excellent polygons for "this is an incorporated place, 
> inhabitant count rolls-up to entity # NNNNN named YOUR PLACENAME HERE† 
> at level LL" (we use these as Admin boundaries?) and "this is an 
> unincorporated place and the census definition is this" (maybe we 
> don't, as there's no Now Entering CDP imaginary boundary signage?).)
>
> (OTOH if the better source is not easily available - or will require a 
> high level negotiation to get a compatible license statement from 
> their agency management!  - starting with the CENSUS polygon makes 
> sense, even if it's coarser than we'd ideally prefer.)
>
> † "Your State's Name Here <https://youtu.be/96Wtcpje0uE>" - Lou & 
> Peter Berryman - A Generic Folk-Song praising whatever state they're 
> visiting and performing in today.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20230118/0813dcbc/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: publickey - MoiraPrime at pm.me - 0e8cea74.asc
Type: application/pgp-keys
Size: 698 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20230118/0813dcbc/attachment-0001.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20230118/0813dcbc/attachment-0001.sig>