ODK Collect v2022.2 Beta: select from map, geojson datasets

[LN]

@chun_hing_yap

I think 'the select from map' using geojson and 'viewing filled forms on a map' is actually unrelated

They're related in a context where a form submission represents a single encounter with an entity (person, place, thing). The filled forms map then represents completed work. Because you use repeats to represent your entity encounters, the two indeed don't feel as related. In general, there are tradeoffs between using one submission per entity vs one repeat instance per entity but most scenarios can use either. The one that makes the most sense will depend on data collection and analysis workflows.

@chun_hing_yap

And, I am thinking whether there is a way to display the map in 'select from map' where the the map can distinguish the marker with records and marker without records. This will be a great help for the data collector to identify the marker which have yet to complete for the data entry.

I talked a bit about this in the feature thread and described strategies for cases where one submission represents one entity encounter. @mathieubossaert's example above uses a similar strategy but with repeats. It's a great example!

@Ivangayton

creates a layer with some attributes

@Ivangayton

freak out if an attribute in a geojson is null

Thanks for both of those! We put in a bunch of flexibility and tests at the Feature level but were indeed having unrealistically specific expectations at the top level. I have https://github.com/getodk/javarosa/pull/681 to fix both and I think we'll do a point release for it. If anyone else has geoJSON files that are getting rejected, please share or describe them.

If you have thoughts on any of my other follow-up questions above, we might be able to get some of your other issues resolved in that point release.

@Ivangayton

name:ja

Is this a localization convention that is documented somewhere? We have been thinking about localized labels.

@Ivangayton

if the list of attributes is too long, the Select button at the bottom of the list goes off the bottom of the screen and can't be reached.

Indeed! We've left the bottom sheet unstyled pending feedback on how users want to use it. How many attributes? What screen sizes? Any information on how it would be used in an ideal world would help us make decisions there.