Data schema v3

1 view
Skip to first unread message

Cameron Shorter

unread,
Nov 2, 2025, 7:13:52 AM11/2/25
to solarmap-nz-tech
Hey folks,
I've updated our proposed schema, now in a Google Sheet, and invite comments (I've added a column for comments).

I've added the following building attributes, which I think answer important use cases (as highlighted by building energy monitoring apps):
viable_solar_gen_kwh_per_day
building_load_kwh_per_day
grid_export_kwh_per_day
grid_import_kwh_per_day
battery_size_kwh
battery_use_percent_per_day

SigEnergyEnergyUse.png


--
Cameron Shorter
Business Analyst / Engineer / Technical Writer

Jenny Sahng

unread,
Nov 2, 2025, 3:59:05 PM11/2/25
to Cameron Shorter, solarmap-nz-tech
Cheers Cameron! Just had a look through and it looks great, added a couple of comments.

For those new building attributes you've added, just want to confirm this wouldn't be part of the MVP, and would be nulls for the time being? I think they're fields that we'd definitely want in the future, but don't want to spend time trying to estimate/calculate them now.


--
You received this message because you are subscribed to the Google Groups "solarmap-nz-tech" group.
To unsubscribe from this group and stop receiving emails from it, send an email to solarmap-nz-te...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/solarmap-nz-tech/CABqeU%2Bgrc%3Dz0oCYOc5oUrBN3Y5_Dwhz1kg%2B6XSR-Ers2T0rwhA%40mail.gmail.com.

Cameron Shorter

unread,
Nov 3, 2025, 6:37:43 AM11/3/25
to Jenny Sahng, solarmap-nz-tech
Thanks Jenny,
1. Actioned most of your comments as suggested.
2. I'm erring toward not including a run_id yet, instead versioning at the geopackage database level.
3. Acknowledged that we can null extra fields for grid input/export and battery size/usage. (I've commented that we can move to v2 or v3)

Hamish

unread,
Nov 3, 2025, 5:10:28 PM11/3/25
to solarmap-nz-tech
Hi folks,

with regard to a system whereby people can "check out" blocks of the country to process piecemeal, then later abandon or mark as complete, FYI here's the code we used for the bulk LINZ topo data -> openstreetmap uploads some years ago. Not sure if anyone is a django or web app expert who can quickly spin up a local instance, but the instructions are there and I thought I'd throw it into the ring.

Sorry no screenshots, the web server that was running it has now been switched off. It was designed for a different specific task but perhaps the working example gives people some ideas to take further.

Also Rob's LINZ data -> PostGIS (or shapefile) ingestion scripts may be of interest:

And here's another project that I'm not familiar with, but on the guess that Koordinate's and LINZ data service's APIs are "not dissimilar",



regards,
Hamish
Reply all
Reply to author
Forward
0 new messages