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
Unless I'm missing it (sorry if I am!) I don't think it's currently possible to exclude (or inclusively select) fields/properties on features during a load. My use case here are U.S. Census TIGER/Line files, which annoyingly have unique fields for each level-type. (COUNTYNS for county files, TRACTNS for tracts, etc.) However, they always have a consistent GEOID property!
I could see this go even a step further and empower you to rename fields (so could standardize things like COUNTYNS and TRACTNS to just NS, for example), but maybe a bigger/separate ask. I also think this probably would make sense in geojson-to-sqlite too.
Thank you!
The text was updated successfully, but these errors were encountered:
Hello! 👋
Unless I'm missing it (sorry if I am!) I don't think it's currently possible to exclude (or inclusively select) fields/properties on features during a load. My use case here are U.S. Census TIGER/Line files, which annoyingly have unique fields for each level-type. (
COUNTYNS
for county files,TRACTNS
for tracts, etc.) However, they always have a consistentGEOID
property!I could see this go even a step further and empower you to rename fields (so could standardize things like
COUNTYNS
andTRACTNS
to justNS
, for example), but maybe a bigger/separate ask. I also think this probably would make sense ingeojson-to-sqlite
too.Thank you!
The text was updated successfully, but these errors were encountered: