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
Our 'raw_project' dataset is getting much bigger due to the addition of calculated fields, zone facts table, etc. While we probably won't have memory limit problems, it would be good to encourage developers to get their project-specific data from the 'raw_project' dataset rather than duplicating the whole thing in geoJSON as is done currently.
In mapView's placeProjects dataCallback (line ~600), convertToGeoJSON should only add core properties to the map geojson - i.e. anything that is used by Mapbox.
nlihc_id
lat / lon
proj_name, proj_addre (needed by the popup)
Updated the showProjectPreview to lookup the project from raw_project instead of using the passed callback data directly (row 806)
Check for anywhere else that the geoJson project.properties data is used and try to convert it to use raw_project instead.
If it is too time consuming to refactor all the uses of raw_project, it's OK to do a partial implementation - refactor any you find, and then switch the convertToGeoJson back to work like it used to. Future pull requests should watch out for instances of using the geojson instead of raw_project.
The text was updated successfully, but these errors were encountered:
Our 'raw_project' dataset is getting much bigger due to the addition of calculated fields, zone facts table, etc. While we probably won't have memory limit problems, it would be good to encourage developers to get their project-specific data from the 'raw_project' dataset rather than duplicating the whole thing in geoJSON as is done currently.
In mapView's placeProjects dataCallback (line ~600), convertToGeoJSON should only add core properties to the map geojson - i.e. anything that is used by Mapbox.
Updated the showProjectPreview to lookup the project from raw_project instead of using the passed callback data directly (row 806)
Check for anywhere else that the geoJson project.properties data is used and try to convert it to use raw_project instead.
If it is too time consuming to refactor all the uses of raw_project, it's OK to do a partial implementation - refactor any you find, and then switch the convertToGeoJson back to work like it used to. Future pull requests should watch out for instances of using the geojson instead of raw_project.
The text was updated successfully, but these errors were encountered: